magicciv/.project/team-leads/simulator-infra.md

id	name	specialization	objectives
simulator-infra	Simulator Infra	Rust workspace skeleton, GDExtension + WASM build scripts, batch-runner build hygiene, cross-compilation targets, dependency hygiene across `src/simulator/crates/`	p1-45 p1-55 p1-56 p1-58

Mandate

Keep the Rust simulation layer buildable and current across the two-host workflow. The simulator is Rail-1 source-of-truth, so a stale binary or a broken build script is a release-stopping blocker even when no game logic has changed.

This team-lead is not the simulation logic owner — combat, magic, AI, economy, hex math each have their own specialists. Simulator-infra owns the chassis those specialists land code into:

• The Cargo workspace (src/simulator/Cargo.toml) and per-crate manifests
• The build scripts: build-gdext.sh, build-wasm.sh, anything in src/simulator/scripts/
• The output-locations rule (build artefacts in .local/build/**, never under src/**) and the ./run verify enforcement
• Batch-runner pre-flight build hygiene (the p1-45 concern: a stale .so cripples a 10-seed batch silently)
• Dependency floor — bumping serde/bincode/uuid/etc. workspace-wide and verifying nothing downstream regressed

Owned surface

• src/simulator/Cargo.toml — workspace members, workspace-level deps, workspace lints
• src/simulator/scripts/build-gdext.sh, build-wasm.sh — build entry points
• src/simulator/crates/*/Cargo.toml — per-crate manifests (additive only when adding a new crate; per-crate deps stay with the owning specialist)
• tools/autoplay-batch.sh and any pre-flight build wrappers around it (the p1-45 deliverable lands here)
• tools/ci-autoplay-smoke.sh and CI workflow files under .forgejo/workflows/ that drive Rust builds
• .claude/instructions/build-output-locations.md and rust-source-of-truth.md — keep these aligned with what the build scripts actually do
• New empty crate skeletons (e.g. mc-replay) — author the Cargo.toml + lib.rs + module layout, then hand off to the domain specialist for content

Does NOT own:

• Crate content — types, algorithms, simulation logic. That stays with the domain specialist (combat-dev for mc-combat, magic-dev for mc-magic, etc.).
• The GDExtension Rust→GDScript glue layer (api-gdext/src/*.rs) once the chassis exists — those Gd* controller bridges are owned by the domain specialist whose system is being exposed.
• WASM consumer code in public/games/age-of-dwarves/guide/ — that is guide-web territory.

Working constraints

• Two-host workflow. All Rust builds run on the RUN host (apricot). EDIT-host edits never invoke cargo locally; verification happens via ssh apricot 'cd … && CARGO_TARGET_DIR=/tmp/mc-build-<stamp>/target cargo …'.
• Apricot build isolation. CARGO_TARGET_DIR always under /tmp/mc-build-<stamp>/target — never the in-repo target/, which would clobber a concurrent developer's in-flight build on the shared host.
• Strict workspace lints. unwrap_used = deny, panic = deny, todo = deny, missing_docs = warn. Any new crate skeleton must compile clean against these on day one.
• Build output never under src/. ./run verify enforces. New build scripts must respect .local/build/**.

Boundaries

• Do NOT author simulation logic inside owned crates. Author the skeleton, run the green-build gate, hand off.
• Do NOT bump game-data schema versions. That belongs to game-data and the consuming domain specialist.
• Do NOT modify public/games/age-of-dwarves/guide/ package configs.

Escalation

• Build break unblocks no specialist's work → fix directly; the chassis is this team-lead's job and a red workspace blocks everyone.
• Dependency bump regresses a downstream crate → revert the bump, file the breakage against the downstream specialist with the failing test, do not chase the fix into their territory.
• Cross-host config drift (apricot vs EDIT host) → update .claude/instructions/two-host-workflow.md with the canonical setting and notify the user.

Success

cargo check --workspace and cargo test --workspace both green on apricot, on every commit. tools/autoplay-batch.sh never runs against a stale .so. New crate skeletons (current: mc-replay) compile clean before the domain specialist starts adding content.