Restoring the idle animation after the landing
Randi now enters the original ordinary idle program in the same animation call that completes the landing reactions.
Retrospective on October 13, 2026. Published here on October 25, 2026.
The landing does not end with a frozen pose. Build 0.14 added the original ordinary idle program, including palette restoration, velocity presets, frame words and its looping behavior.
The idle starts inside the same call that finishes the supported landing actions. It keeps the original countdown and selection rules, and uses the preserved original graphics.
The scene’s END command clears the original event lock. That exposes the next player-input callback, which was not yet implemented. The Java world therefore stops explicitly at that boundary instead of continuing under an invented event state.
What changed
- Added the bounded ordinary idle parser and same-call restart after the supported landing actions.
- Retained the original animation cache, delay and direction-change behavior.
- Applied the original END event-lock clear and made the unfinished input handoff visible.
What we verified
- The initial idle suite passed 118,845 Java assertions, with source-program and original-pixel audits. Later builds expanded these checks.
What remains unfinished
- This idle coverage was limited to the verified fresh opening context. Build 0.15 later corrected the fresh equipment/palette selection used by that context.
Next in the rebuild
Trace the original controller callback and the character refresh required after the event ends.