Heretic II: side arch reached, close encounter retained
Original west2150 loaded alive, Corvus used the original Ring controls, and ordinary movement crossed the side arch into the timber-framed room. Native save arch2218 acknowledged Done near (933.31,612.05,34.04). Its complete four-file set was recovered and normal Load restored Corvus alive beyond the arch three times. Two nearby humanoids killed Corvus during each subsequent movement/combat check. Surviving ordinary movement after Load was not verified, so the full requested done condition remains unmet. This is a concrete gameplay continuation limit, not a proved runtime defect or evidence of corrupted saves.
Evidence: scratch/runs/20261111-heretic2-west-side-arch-progress-2218/. The preferred checkpoint is arch2218-arch-first-manifest.json, with files software2/native-saves-arch-first/{10,11,12,13}.bin. Final export hashes are identical after all three Loads. The level save is 1395853 bytes, SHA-256 1f6d94daac0fa1952d7367a26dcdf4081caeb51e9cd0c3dc340d9ab56c1abc09. Restore all four together after initializing original Easy docks; issue normal load arch2218. The earlier 36 original references plus all four west2150 files remain exact. west2150 remains the earlier fallback.
The run restored west2150 through the native console after Easy docks initialized. Its full world showed upright Corvus, nearby flyers, and the side arch. Native Pause was established. Original w selection and Enter defense produced a blue Ring burst. Bounded native Pause cycles with ordinary arrow controls aligned with and crossed the arch. The new room and a humanoid were visible in beyond-side-arch.png before saving. Flying-threat elimination, exact health, and unattended safety are not claimed.
verify-models-wait.png, retry-release-wait.png, and final-models-two.png show live restoration of the new checkpoint. Enemies approached during load/console transition and overwhelmed Corvus. The final console explicitly records Corvus died. The first two unsuccessful checks and the final backward+Shift attempt are preserved. No save was overwritten after the initial successful Save. Future work should resume the encounter with immediate original-control defense/withdrawal, or use the intact west2150 fallback to approach it differently.
Runtime identity remains source 0db20330ccd6761a705eea70c5dd9bfc7704c147, WASM ce57f0ad80254b974a0d8bcd4e2c9cbf396d2357cbdc7874e6084e980e1e68e1. Remote prelaunch audit passed 3499 provisioned files and 2533 runtime pins, including inherited helpers and this task's ACK client. Native Pause/helper regressions passed. No actor, game, map, configuration, or save byte edits were made; the engine wrote arch2218. No shared code repair or new build was needed; the matching prior build proof is retained. Git SHA, relevant binary diff, and owned helper additions as patches preserve source provenance without a source archive or repeated media.
Recovery verified 599 initial and 10 late references, 463 unique raw contents, 61 valid PNGs with matching capture bindings, 61 successful numbered ACKs, and 14 balanced trusted native Pause cycles. Initial remote raw bytes were independently rehashed before ordinary quit. All 40 original references and all new checkpoint bytes passed final checks. Each completed image in this run was separately inspected before dependent input. The parent's exit-align to west-cross same-batch prior-review gap remains an explicit historical limit; this run does not erase it.
Private box bx_qfm8a42p normally archived at 2026-11-11T22:41:19.611Z, before initial expiry 2026-11-11T23:02:36.885Z. Stop stop_335c25be96380837 completed, forced=false, error=null. Chrome exited code0; the remote controller parent recorded actual wait/stdout EOF/stderr EOF/code0, and observed runtime PIDs were absent. The local launch wrapper returned 143, so local transport success/EOF0 is not claimed; its missing early shutdown record was resolved by a later read-only observation of the completed remote parent record. Independent watchdog exited unfired with actual wait/EOF0. No live handoff remains; do not resume or delete the archived box by default.
Shared /home briefly fell below the decimal 1500000000-byte floor during unrelated shared growth; the low observation was 1490862080 bytes. The task run then occupied only about 15 MB. This was reported on the messageboard, and coordinator cleanup restored headroom before final recovery. Final observed free space was 2584326144 bytes. No RAM gate, workers, or public deployment were used.