Heretic II: courtyard route and native Health Vial retained
Run scratch/runs/20261111-heretic2-courtyard-tavern-key-2330/ restored the complete four-file route2307 checkpoint after initializing original Easy docks. Normal Load restored living Corvus in the low-ceiling stone chamber. Ordinary forward movement, comma left strafe and released-control survival passed before continuing.
Ordinary movement crossed the courtyard containing timber debris, the tall masonry doorway and the airborne blue enemy with green projectiles. Corvus passed through the yellow-lit right arch, followed the lamp-lit stone passage, and used the open gap in a timber barrier to reach a second cobbled courtyard. A native forward jump cleared the low timber obstruction. The second courtyard contains stacked crates, a raised rack and small fire, a barrel and a stone pillar beside the entry passage. The original map was inspected read-only for item locations; it supplied route clues, not pickup proof.
The crate traversal used original movement, jump (a) and action (Space). The completed native console subsequently reported HEALTH VIAL. and OFFENSIVE MANA, small. This establishes actual native pickups. Exact health and the numeric healing amount remain unknown. The Tavern Key was not acquired, its locked door was not opened, and no new kill or complete threat clearance is claimed. The first courtyard's airborne enemy remains unresolved.
Native save courtyard2330 reported Saving game... Done. Its four engine-written files were recovered and SHA-256 verified in courtyard2330-progress-first-manifest.json. Normal load courtyard2330 restored upright living Corvus in the second courtyard beside the stone pillar, barrel and crate. Ordinary forward movement, left strafe and a bounded observation with movement/attack/defense released all survived. courtyard2330-final-preserved-manifest.json proves the checkpoint bytes remained unchanged afterward. All 48 prior references and the original four route2307 files remained exact.
Preferred recovery is the complete new courtyard2330 set, after initializing original Easy docks, followed by normal Load. The slot restores after the native Health Vial and small Offensive Mana pickups. Do not mix files or edit save bytes. The earlier route2307 remains a fallback. Native loading produced temporary black/console frames before the world appeared. Each completed image used for dependent input was separately inspected first. The historical parent crossing-review gap and arch2218 deaths remain explicit limits, not requalified by this run.
Runtime source was 0db20330ccd6761a705eea70c5dd9bfc7704c147, WASM SHA-256 ce57f0ad80254b974a0d8bcd4e2c9cbf396d2357cbdc7874e6084e980e1e68e1. The full closure audit passed 3,580 provision files and 2,611 runtime pins, including the ACK client and referenced helpers. The native Pause helper regression passed. No runtime defect was proved and no shared runtime, actor, map, configuration or save bytes were patched. Git source identity, the relevant binary diff and owned helper patches preserve provenance without a source-tree or media archive.
Final verification passed 977 references, 767 unique raw contents, 88 PNG/capture bindings, 88 ACKs and 56 balanced trusted native Pause cycles. The first 957 remote references were independently rehashed before ordinary quit. All unique evidence was recovered and hash-verified before box shutdown. Chrome and the local/remote actual controller parent waits completed 0 with EOF; observed runtime PIDs were absent. The independent deadline watchdog completed 0 and unfired.
Task-created bx_6zg96n89 was normally archived at 2026-11-11T23:58:11.039Z; stop stop_d36343971c201bc3 completed nonforced/error-null at 23:58:11.056Z, before initial expiry 2026-11-12T00:15:31.302Z. No live handoff, resume, deletion, workers or public deployment. Observed /home free space stayed above decimal 1,500,000,000 bytes; no RAM gate.
Next: restore the new complete checkpoint and seek a connected route to the original Tavern Key. Its original map item is at (936, -656, 12); direct travel from this courtyard is blocked by walls, so ordinary connected-route exploration remains necessary. See the run's RESULT.md, RECOVERY.md, final-local-verification.json and normal-archived.json.