Showcase StarBound with a recorded demo and clear contributor documentation

Author: vnmoorthy

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,28 @@
+name: Report a bug
+description: A control, calculation, export or rendering behavior is not working.
+title: '[Bug]: '
+body:
+  - type: textarea
+    id: behavior
+    attributes:
+      label: What happened?
+      description: Include the tab, action, expected behavior and actual result.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: How can we reproduce it?
+      description: List the steps. Attach an exported scenario JSON when the issue involves a result.
+    validations:
+      required: true
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      placeholder: Browser, operating system, public demo or local commit
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Supporting evidence
+      description: Screenshots or error messages are useful. Do not include local lab tokens or credentials.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Explore the live simulator
+    url: https://starbound.vnmoorthy.chatgpt.site
+    about: Try the controls and export a scenario before reporting a numerical issue.
+  - name: Read the model and its boundaries
+    url: https://github.com/vnmoorthy/starbound/blob/main/docs/PHYSICS.md
+    about: Separate an assumption change from an implementation error.

.github/ISSUE_TEMPLATE/scientific-correction.yml

@@ -0,0 +1,34 @@
+name: Suggest a scientific correction
+description: Challenge an equation, assumption, unit, system boundary or interpretation.
+title: '[Science]: '
+body:
+  - type: dropdown
+    id: category
+    attributes:
+      label: What needs attention?
+      options:
+        - Equation or implementation
+        - Scenario assumption
+        - Missing physical process
+        - Documentation or interpretation
+    validations:
+      required: true
+  - type: textarea
+    id: current
+    attributes:
+      label: Current claim or behavior
+      description: Link the equation, source line or documentation passage and include units.
+    validations:
+      required: true
+  - type: textarea
+    id: proposed
+    attributes:
+      label: Proposed correction and evidence
+      description: State the system boundary and cite a primary source or provide a reproducible derivation.
+    validations:
+      required: true
+  - type: textarea
+    id: validation
+    attributes:
+      label: How should we validate it?
+      description: A reference result, limiting case or independent calculation is particularly useful.

.github/pull_request_template.md

@@ -0,0 +1,11 @@
+## Change
+
+Describe the problem and resulting behavior.
+
+## Evidence
+
+For numerical changes, include the units, system boundary, source or derivation, and a reference result. Identify whether this corrects an equation or changes a scenario assumption.
+
+## Validation
+
+List the relevant checks you ran and any remaining limitation. Ordinary changes should not require model inference.

.gitignore

@@ -46,3 +46,6 @@ next-env.d.ts
 # Presentation finalizer temporary workbook snapshots
 /.chart-data-*/
 .gstack/
+
+# Microsoft Office lock files
+~$*

CONTRIBUTING.md

@@ -4,6 +4,8 @@ Useful contributions include independently sourced corrections, reproducible mod
 
 Before proposing a scientific change, state the system boundary, units, source, current behavior and expected behavior. Distinguish changing a scenario assumption from correcting an equation. Preserve the host-side grader and publish all benchmark attempts when changing an evaluation protocol.
 
-Run `npm run typecheck`, `npm test` and `npm run build`. Keep runtime logs, model credentials, local lab tokens and private reasoning out of commits. No model call is required for ordinary CI.
+Run `npm run typecheck`, `npm run lint`, `npm test` and `npm run build`. Keep runtime logs, model credentials, local lab tokens and private reasoning out of commits. No model call is required for ordinary CI.
 
-The numerical model is illustrative. Do not present a new default value as a measured Mercury capability without an appropriate source and validation. UI result numbers must come from the engine.
+The numerical model is illustrative. Do not present a new default value as a measured Mercury capability without an appropriate source and validation. Physical UI metrics must come from the monthly engine or the explicitly separated engineering calculators. Concept imagery and illustrative motion must remain labeled.
+
+Start with the [documentation index](docs/README.md). Use the scientific-correction issue form for equations, assumptions and system boundaries; use the bug form for reproducible software failures.