Tavern Key acquired; living door continuation blocked

Run 20261112-heretic2-connected-tavern-key-route-0002 acquired the original Tavern Key using connected original map routes and native controls. The native console explicitly reported You picked up the TAVERN KEY. (software2/key-console-after.png). Native save key0002 reported Saving game... Done (software2/key-save-enter-after.png). All four engine-written files were recovered and SHA-256 verified in key0002-key-first-manifest.json; the final-preserved manifest proves they remained unchanged after subsequent normal Load attempts.

The requested completion condition was not achieved. The ornate locked timber-room door was not opened. The first return attempt died after the key save, and the next two reload attempts also ended with Corvus dead before ordinary surviving movement could be established. The final third normal reload attempt likewise ended dead. Thus there were three normal key reload attempts ending dead, in addition to the initial post-save return death. No living key checkpoint or surviving normal-load continuation is claimed. Exact health and the cause of these deaths remain unknown; no runtime defect was proved.

Recovery started original Easy docks, then mounted all four exact courtyard2330 files. The living courtyard restore was confirmed. Read-only original BSP cross-sections and a clearance-sampled advisory path supplied connectivity clues; native movement supplied traversal proof. The route went north through the timber gap and lamp passage, west through the low corridor, north around the central structure, west across the timber frontage, and south to the closed gate near (576,504). Corvus stood north of the original lever near (496,524) and used forward plus Space; the native gate rose. Native run/jump crossed the enemy courtyard, passed the southern arch, followed the narrow lane west of the timber obstruction and entered the east-running recess. Ordinary movement crossed the original key position (936,-656,12), producing the pickup message. No actor, map, configuration or save bytes were edited.

All completed images were separately displayed before dependent input. However, two Pause preconditions were misclassified: key-return-west-face followed a full world image without a Paused banner, and bounded-native-render followed a console/black image without that banner. Their balanced trusted key-edge traces do not establish valid Pause preconditions or survival. The historical crossing-review gap and arch2218 deaths remain retained limitations. Earlier airborne enemy and later courtyard/recess threats remain uncleared; no new kill is claimed.

Pinned runtime: source 0db20330ccd6761a705eea70c5dd9bfc7704c147, WASM ce57f0ad80254b974a0d8bcd4e2c9cbf396d2357cbdc7874e6084e980e1e68e1. Full closure audit passed 3,608 provision files and 2,638 runtime pins, including ACK client and helpers. Native Pause helper regression passed. Git identity, relevant binary diff and owned helper patches retain provenance without a source/media archive.

Final local verification passed 1,121 references, 883 unique raw contents, 101 PNG/capture bindings, 101 ACKs and 56 balanced trusted Pause traces (subject to the two precondition exceptions above). All earlier 48 references, route2307 four files and courtyard2330 four files remained exact. The courtyard and key checkpoint bytes also remained exact in the final runtime export. Unique evidence was recovered/hash-verified before normal box shutdown. An extra remote rehash command exceeded the OS argument-size limit and did not run; it is not claimed as a pass. Local recovery hashes and final verification passed.

Box bx_ryr29h7m normally ARCHIVED at 2026-11-12T00:38:17.912Z; stop stop_0abe7e510eea1234 completed nonforced/error-null at 00:38:17.929Z, before initial 00:47:11.655Z expiry. Chrome exited 0; remote controller actual parent wait/EOF completed 0 and observed runtime PIDs were absent. The local long-running launch wrapper returned 143, so local launch EOF0 is not claimed. Independent prearmed watchdog completed actual parent wait/EOF0 and unfired. No box remains running, no resume/delete, workers or public deployment. Observed /home free space stayed above decimal 1,500,000,000 bytes.

Next: investigate why the native key checkpoint cannot retain a living continuation, or replay the now-known connected route from the verified living courtyard checkpoint with less threat exposure. Then acquire the key, escape to safety, open the timber-room door and prove a new Save Done/normal Load/ordinary movement/released survival checkpoint. Keep key0002 as pickup evidence; do not replace the known living courtyard recovery with it.