FOLLOW-UP / EXACT PROMPT WE SENT
Describe the failure.
Ask for the repair.
By Alvin
A follow-up prompt is another instruction to the coding agent, with the existing program as its starting point. We supplied a copy of Quiet Descent and sent the complete text below. Keep your first file too, so you can compare the result.
Focus selects a button for the next key press. A pointer hold keeps a mouse button or finger pressed. Keydown and keyup are press and release events; window blur means switching away from the game window.
Complete brief / keep the acceptance checks
Update the existing 001-lunar-lander.html. In the current build, holding Enter on the focused Rotate left button leaves the craft upright, and holding Enter on the focused Fire engine button uses no fuel. Fix these keyboard controls.
Make all three flight buttons respond while Enter or Space is held on the focused button, just as they respond to a pointer hold. Release that input on keyup or loss of focus. Repeated keydown events must keep one hold active. Preserve the global arrow-key and Space shortcuts when no flight button is focused. Keep Launch/Restart and Pause/Resume working with their normal keyboard activation. Handle window blur, pointer cancellation, and overlapping keyboard/pointer holds so controls never remain stuck or release another active input.
Keep the physics, landing rules, speed readout, layout, and offline single-file format unchanged. Check the repaired controls and existing flight behavior. Report which checks you actually ran and which remain untested.
Executed November 15, 2026: one repair run, Codex CLI 0.144.0, default GPT-5.6-Sol. A new isolated session received the failed file and this exact prompt. We kept our independent test harness separate from the agent.