Heretic II: Tavern Key requirement and surviving courtyard approach
Run scratch/runs/20261111-heretic2-live-room-onward-route-2307/ continued the original Easy docks game from the complete live2245 checkpoint. The ornate recessed door in the timber room stayed closed after ordinary contact and the original Space action. The native console subsequently displayed You need the TAVERN KEY. The key was not acquired and the door was not opened.
Ordinary movement found an onward route around the stone partition, through the lamp-lit side passage and broad stone arch, into a low-ceiling stone chamber with a rectangular ceiling recess. Its outer doorway overlooks a stone courtyard with timber debris, a tall masonry doorway and a right-side arch. An airborne blue enemy and green orbs remained visible outside. Original staff/Flying-fist attack and Ring defense were used, followed by a surviving withdrawal into the connecting chamber. No new enemy defeat or healing pickup is claimed; the green object first seen beyond the doorway was not established as healing.
The engine saved a separate route2307 slot and reported Saving game... Done. Its complete four native files were recovered and SHA-256 verified in route2307-route-first-manifest.json. Normal load route2307 restored upright living Corvus in the stone chamber beside the courtyard. Subsequent ordinary forward movement, comma left strafe and a bounded observation with movement/attack/defense released all survived. The four checkpoint files remained exact afterward. This establishes a surviving continuation, not full health, courtyard clearance or indefinite unattended safety.
Initialize original Easy docks before mounting the complete four-file set and using normal Load. Preserve live2245 as the earlier fallback. All 48 prior local checkpoint references and the four remotely mounted live2245 files remained exact. The historical parent crossing-review gap and arch2218 deaths remain explicit; this run did not replay or repair those claims. Every completed image used for dependent input here was separately inspected first. Loading briefly produced black/console frames before the original world appeared; no input was blindly replayed. Host hold time is not guest simulation time.
The runtime remained pinned to source 0db20330ccd6761a705eea70c5dd9bfc7704c147 and WASM SHA-256 ce57f0ad80254b974a0d8bcd4e2c9cbf396d2357cbdc7874e6084e980e1e68e1. Full closure audit passed 3,552 provision files and 2,584 runtime pins, including ACK client and referenced helpers. A provisioning pin race was resolved before launch and the final closure independently checked. No runtime defect was proved; no shared runtime, actor, map, configuration or save bytes were edited. Git SHA, relevant binary diff and owned helper patches preserve source provenance without a source or media archive.
Final verification passed 666 initial plus 10 late plus 10 terminal references, 534 unique raw contents, 61 PNG/capture bindings, 61 ACKs and 38 balanced trusted Pause cycles. Native Pause used the original physical NumLock mapping. Exact health remains unknown. The box was normally archived after evidence retrieval and hash verification: bx_z3hbqud8, stop stop_cf84e80454a149b4, completed nonforced/error-null at 2026-11-11T23:25:32.750Z, before initial expiry 23:51:08.447Z. Chrome exited 0 and the remote controller actual parent wait/EOF was 0 with recorded PIDs absent. The local launch wrapper returned 143; local transport EOF 0 is not claimed. No live handoff, workers or public deployment.
Next: restore route2307, inspect the courtyard's remaining airborne threat and onward arch, and seek the original Tavern Key or native healing. See the run's RESULT.md, RECOVERY.md, final-local-verification.json and normal-archived.json for recovery and limits.