Stabilization evidence archive

These numbered reports record work and checks at the time of each batch. Their status, plans, branch names and follow-up instructions can be outdated. They do not establish that the current ability overhaul or shared scene passes the same checks. Use the current roadmap, handoff and live source for current work.

The reports remain at their original paths so links and detailed evidence remain usable:

• 01–25: targeted defects, scene/menu wiring, Unity CLI/player checks, settings and persistence. Open the relevant numbered batch-XX.md for its exact scope and result.
• 26–34: planning contracts for input, run lifetime, player, combat, shared stages, rewards and services. These are design-era records, not proof those systems are implemented as described.
• 35–36: run lifetime and minimal shared scene. The shared scene was a foundation, not a playable arena.
• 37–46: input slots, sessions, binding profiles and capture, config compatibility and a Linux persistence check. The records are evidence for isolated slices, not complete production input integration.
• 47–58: follow-up sequencing, menu layout, character/player setup, movement, stats, damage, dash and player-owned ability work. Check dates and source revisions before relying on an older implementation description.
• 59: ability-module design, recorded before the later code-owned ability migration.

For current Unity results, see the ability CLI report and first playable-path batch. Keep raw evidence and per-batch caveats rather than merging old pass counts into a current verification claim.