feat(galaxy): add the G0 continuous Atlas substrate

[colorpulse6]

Summary

• add a fresh, isolated continuous-galaxy save namespace with deterministic fixed-point coordinates, authored anchors, seeded procedural cells, knowledge/confidence, and recoverable migration
• add the responsive hybrid Galaxy Atlas, route preview/commit journals, supply/time travel, caused interruptions, blind discovery, and deterministic DevPanel fixtures
• adapt Hostile Picket, Kepler, Ashfall sortie, and the Ashfall Region/POI loop through strict Galaxy-owned projection and outcome boundaries without mutating legacy progression
• harden hydration, persistence retry/recovery, operation/POI presentation, keyboard behavior, and fresh-save shape after production-export playtesting
• record the complete verification matrix and the remaining hands-on closure playtests without prematurely marking G0 done

Why

G0 is the substrate for replacing numbered-world progression with a continuous, explorable galaxy while retaining the existing campaign as an isolated legacy experience. The implementation establishes stable spatial and historical authority before hubs, colony decay, and future operations build more dependencies on the old W1-W8 coordinate model.

Verification

All required commands ran from game/ and exited 0:

• npx tsc --noEmit
• yarn colony:test — 284/284
• yarn engine:test — 282/282
• yarn sprites:test — 4/4
• yarn build — static export passed
• NEXT_PUBLIC_DEVTOOLS=1 yarn build — static export passed
• git diff --check origin/main...HEAD

Independent final code review: approved with no blocking findings.

Production-export playtest

Tested with npx serve out -l 3000 in fresh Chromium profiles at 480×854 and 1280×900:

• Galaxy begin/continue hydration and reload: zero console errors
• legacy cockpit/star map and W1-L1 completion through NEXT LEVEL, hub return, and reload persistence
• DOM/keyboard selection, pan/zoom, responsive mobile and desktop layouts
• direct Ashfall arrival and fresh-session Region opening
• hostile interruption launch and retreat; reload remained on the exact cycle with no duplicate tick
• deterministic blind discovery persisted the same fact/coordinate across reload
• low-supply block and in-transit reload fixtures
• canonical presentation for Hostile Picket, Kepler, Ashfall sortie, and Cinder Relay Ruins

Detailed evidence: docs/playtests/2026-07-16-g0-atlas.md.

Remaining manual acceptance

The roadmap intentionally leaves G0 short of DONE until a final touch-device pass and live end-to-end completion of hostile success/failure/emergency retreat, Kepler, Ashfall sortie, and one Region POI. Their reducers, adapters, rewards, legacy isolation, and idempotency are covered by deterministic tests; this is a hands-on acceptance gap, not a known code blocker.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →