# Neutron GamePort Follow `../AGENTS.md` and `../prompt.MD`. This is the local Git repository. Do not configure a remote, push, upload originals or use cloud CI. Originals are in `../Original/` and must remain byte-identical; verify using `python3 tools/recon/inventory.py ../Original --verify docs/original-manifest.json`. Use .NET 10, Silk.NET.Vulkan Vulkan 1.3+, SDL3 and shared Linux/Windows x64 code. Keep recovered data/algorithms distinct from unverified approximations. Require runtime evidence before claiming working gameplay or platform compatibility. ## Working map - `src/GamePort/`: runtime, platform, rendering, assets and game systems. - `tools/`: Python analysis/extraction tools (stdlib where practical). - `tests/`: original-data regressions and bounded parser tests. - `scripts/`: local dependency, build, test and packaging entry points. - `docs/`: durable evidence and continuation notes. - `.tools/`, `.nuget/`, `artifacts/`, `dist/`: ignored local generated data. Build from this directory with `dotnet build`, `dotnet run`; project-local SDK is selected by `source scripts/env.sh` (consult README for verified invocation). Python tests: `python3 -m unittest discover -s tests -v`. Local builds: `scripts/build-linux.sh`, `scripts/build-windows.sh`; tests: `scripts/test.sh`; packages: `scripts/package.sh`. ## Coordination Native subagents supported, max three investigators alongside primary. Explicit exclusive file ownership; primary reviews, integrates, tests and commits milestones. Binary agent: `tools/binary/`, binary/graphics analysis. Asset agent: extractors, asset/format docs, extractor tests. Infrastructure agent: runtime/build scripts and infrastructure report. Primary: GAM loader, gameplay/recon/docs and integration. Coordinate any ownership transfer before editing shared files. No agent commits other agents' active changes. Keep updates concise, save detailed evidence to disk. Use bounded endian-aware parsers, portable paths, clear C#, deterministic tests, and explicit unmanaged ownership. Build frequently. Update `docs/progress.md`, `docs/tasks.md`, `docs/decisions.md`, and compatibility evidence before transitions. Current mode is user-requested gameplay/gadget implementation. On2026-10-27 the user parked collision recovery and requested gadgets. This overrides the earlier feature-expansion pause; retain evidence before gameplay assumptions. Preserve the35a2a66 body milestone/0272f7b release notes and remaining C4/C5 gates for return. The initial architecture checkpoint is documented in docs/checkpoint/review.md; use the playable 69d0187 baseline as a comparison tool. Read docs/checkpoint/README.md, coverage.md and implementation-plan.md before gameplay changes. Current gadget controls/resources/primary-fire findings belong in docs/gameplay/. Distinguish static recovery, implementation, port tests and original runtime evidence. Main owns integration/runtime; gadget investigators have exclusive named files, not shared directories. Use REA for original-binary investigations from now on, including delegated investigations. Preserve its Evidence and cross-check relevant addresses/bytes; record provider gaps explicitly and use supporting analysis when needed. Ordinary source edits and builds do not require a REA call. Local REA/Ghidra is available through scripts/rea.sh; see docs/rea.md for the ignored launcher environment and JDK paths. Existing client MCP registration was not changed. Use generated copies, preserve complete Evidence/snapshots, and keep static decompilation distinct from source execution. Current C3 continuation: docs/checkpoint/control-phase-implementation.md; remaining body/wrapper/camera gates are in its final section and the implementation ledger. Current C4 follow-up is docs/checkpoint/collision-response.md with ceiling-wrapper, body-root-registration and camera-handoff reports. The source sphere kernel is isolated/probed; do not treat it as live capsule replacement. Next integration report is collision-body-probe.md: source grid/retry component and seven original dispatcher comparisons, contact/material/friction contracts and ten ordinary-body observations are recorded. collision-body-implementation.md now records matched ordinary composition and VR04 static-only live integration. Next: original dynamic actor eligibility/pair state and special contacts before lab/outside expansion; shared camera state remains separate. Retain modern render/noclip boundaries.