Project status

Updated 2026-10-30. For execution order use the playable-game roadmap; for the next chat use the handoff. Inspect the live source and Git status before working.

• Ability/player: code-owned definitions, per-player state and hooks are in place. The 121 inventoried Ability assets were archived and removed after their data migration. Not every ability's full behavior has been traced or tested. Production player setup passed a controlled two-Soldier Play Mode check including Dash, Frenzy, weapon, movement and cooldown; a full run has not passed. See the check.
• Shared stage: Gameplay.unity is a development foundation, not a complete playable production scene. Stage 1–3 use the same generator with different data and appearance; the selected LevelData must configure the common scene. See the arena comparison.
• Input: new Unity Input System foundations exist, but production player and menus still have legacy input paths. New input routing, keybinding UI/persistence and physical-device validation remain open.
• Integration: real menu-to-stage entry, combat, spawning, reward acquisition, stage completion/retry and full gameplay remain unverified together. Report individual checks at their actual scope; compilation does not prove gameplay.
• Next version: backend/reporting IDs, progression and authored values must remain compatible. Build, IL2CPP stripping and platform checks are separate from an Editor run; no release-ready claim has been made.

The latest migration checkpoint at this update was 2b9e44b0 on dev-0.9.0-bootloader; inspect current HEAD and working tree because work may have continued. Earlier implementation history, Git recovery notes and historical checks remain in the previous status record. The issue register is historical evidence as well as a list of leads: recheck a finding against source and later batch reports before assuming it is still open.