chore: add hackathon repo guardrails

.gitignore

@@ -14,4 +14,3 @@ reports/
 artifacts/
 checkpoints/
 server/data/generated/
-

.pre-commit-config.yaml

@@ -0,0 +1,16 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.11.0
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-toml
+      - id: check-added-large-files

AGENTS.md

@@ -45,6 +45,7 @@ Do not leave silent divergence.
 - Do not broaden the task family beyond the single stellarator environment unless explicitly requested.
 - Do not add broad “other sciences” claims to docs or demo copy unless there is real supporting evidence.
 - Do not narrate hypotheses as validated facts.
+- Do not add new tests during the hackathon unless the user explicitly requests them.
 - Do not add complicated reward shaping until the simpler version has been tested against actual trajectories.
 - Do not optimize notebook/training work ahead of local environment stability, remote environment stability, and baseline comparisons.
 
@@ -58,7 +59,7 @@ Any change to the environment should preserve or deliberately update:
 - terminal conditions
 - reward semantics
 
-If you change one of these, update the corresponding documentation and tests in the same task.
+If you change one of these, update the corresponding documentation in the same task.
 
 ## Reward Design Rules
 
@@ -88,7 +89,6 @@ If a human cannot act coherently from the observation, fix the environment contr
 - `baselines/`: random and heuristic baselines
 - `training/`: evaluation or training notebooks
 - `demo/`: demo assets and scripts
-- `tests/`: focused tests for environment contract and repo behavior
 - `docs/`: public-facing planning and submission docs
 
 ## Validation
@@ -99,10 +99,9 @@ Current useful commands:
 
 ```bash
 python3 -m py_compile fusion_lab/models.py fusion_lab/client.py server/environment.py server/app.py server/physics.py
-python3 -m pytest -q tests/test_repo_scaffold.py
 ```
 
-As the repo grows, add more targeted tests instead of depending only on broad end-to-end runs.
+For this hackathon repo, prefer smoke validation, manual playtesting, and runnable demos over adding test coverage.
 
 ## Git and Change Discipline
 

README.md

@@ -32,7 +32,6 @@ fusion-design-lab/
 ├── docs/
 ├── fusion_lab/
 ├── server/
-├── tests/
 ├── training/
 ├── openenv.yaml
 ├── pyproject.toml
@@ -43,6 +42,8 @@ fusion-design-lab/
 
 1. Implement the environment contract in `server/environment.py`.
 2. Implement the VMEC-backed physics loop in `server/physics.py`.
-3. Add one stable local episode test.
-4. Run manual-playtest episodes before heavy training work.
+3. Run manual-playtest episodes before heavy training work.
 
+## Hackathon Working Note
+
+This repo is intentionally biased toward executable demos, manual playtesting, and clear environment behavior over building out test coverage during the hackathon.

baselines/README.md

@@ -5,4 +5,3 @@ The first baseline milestone is:
 - one random agent
 - one simple heuristic agent
 - one short comparison run on the frozen task
-

demo/README.md

@@ -5,4 +5,3 @@ Expected contents:
 - one stable episode capture
 - short demo script
 - any exported figures used in the 1-minute video
-

docs/FUSION_DESIGN_LAB_PLAN_V2.md

@@ -1,7 +1,7 @@
 # Fusion Design Lab — Plan V2
 
-**Hackathon:** OpenEnv Hackathon, March 7-8, 2026  
-**Track:** Statement 3.1 (World Modeling — Professional Tasks)  
+**Hackathon:** OpenEnv Hackathon, March 7-8, 2026
+**Track:** Statement 3.1 (World Modeling — Professional Tasks)
 **Status:** Judge-aligned rewrite of the main plan
 
 ## 1. Submission Thesis

fusion_lab/__init__.py

@@ -1,2 +1 @@
 """Shared client-side package for Fusion Design Lab."""
-

fusion_lab/client.py

@@ -6,9 +6,7 @@ from openenv.core.env_client import EnvClient
 from fusion_lab.models import StellaratorAction, StellaratorObservation, StellaratorState
 
 
-class FusionLabClient(
-    EnvClient[StellaratorAction, StellaratorObservation, StellaratorState]
-):
+class FusionLabClient(EnvClient[StellaratorAction, StellaratorObservation, StellaratorState]):
     """Thin typed client wrapper for the remote OpenEnv environment."""
 
     def _step_payload(self, action: StellaratorAction) -> dict[str, object]:
@@ -24,4 +22,3 @@ class FusionLabClient(
 
     def _parse_state(self, payload: dict[str, object]) -> StellaratorState:
         return StellaratorState(**payload)
-

fusion_lab/models.py

@@ -49,4 +49,3 @@ class StellaratorState(BaseModel):
     budget_remaining: int = 6
     constraints_satisfied: bool = True
     history: list[str] = Field(default_factory=list)
-

openenv.yaml

@@ -4,4 +4,3 @@ type: space
 runtime: fastapi
 app: server.app:app
 port: 8000
-

pyproject.toml

@@ -18,6 +18,7 @@ physics = [
   "vmecpp",
 ]
 dev = [
+  "pre-commit>=4.0.0",
   "pytest>=8.3.0",
   "ruff>=0.11.0",
 ]
@@ -35,4 +36,3 @@ target-version = "py311"
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]
-

server/__init__.py

@@ -1,2 +1 @@
 """Server-side package for Fusion Design Lab."""
-

server/app.py

@@ -15,4 +15,3 @@ def healthcheck() -> dict[str, str]:
 @app.get("/task")
 def task_summary() -> dict[str, object]:
     return TASK
-

server/data/README.md

@@ -1,4 +1,3 @@
 Baseline VMEC inputs and related static assets belong here.
 
 Do not commit generated solver outputs or large transient artifacts.
-

server/environment.py

@@ -17,4 +17,3 @@ TASK: Final[dict[str, object]] = {
 def environment_status() -> str:
     """Return a simple status string until the full environment is implemented."""
     return "scaffolded"
-

server/physics.py

@@ -18,4 +18,3 @@ class PhysicsEngine:
     @property
     def status(self) -> str:
         return self._status
-

training/README.md

@@ -1,4 +1,3 @@
 Training and evaluation notebooks belong here.
 
 This repository treats notebooks as supporting evidence for the environment, not the primary product.
-