Heretic II WebGL final-frame recovery: provisioning path blocker

2026-11-12. Run scratch/runs/20261112-heretic2-webgl-final-2025/. The original exit-bound pixels remain UNKNOWN. The fresh WebGL-first attempt stopped during local provisioning validation, before uploads, remote commands, or an original browser. No native exit, final frame, visible native diagnostic, or emulator defect was observed in this attempt. No production patch was made.

The parent final-frame observer (657570ab2) and runtime boundary (8f68731a1) retain their existing scope. Parent1945's stale SoftwareGL chain was not retried or promoted into an exit frame/cause. Parent1910's exact whole-four/current04 living SoftwareGL world, HUD31, native backward movement, and released interval were accepted as the prior control. SoftwareGL was not repeated; this is not a new paired comparison. The parent1110/1135/1910/1945 RECOVERY.md references were read and remain authoritative.

Freshness handling exercised before allocation

The unchanged browser's emitted capture and execute functions, actual request.cjs/transport consumer, and unchanged bound chain ran locally against a synthetic identity fixture and real Chrome screenshot/input paths. The identity fixture is explicitly synthetic; this is not original full22 admission or a new original owning-GL qualification.

A full 1024×768 PNG was captured and reviewed. After 121,222 ms of real elapsed time, the new caller-side check returned LOCAL_STALE_REVIEW, with zero submitted commands and the chain still open. No guest/host clocks or guard limits were changed. The actual emitted read-only capture command then obtained a new bound fullframe; that complete PNG was reviewed before one native Enter command. Chrome recorded exactly one trusted down/up pair. Both ACKs succeeded, the independently armed release was acknowledged, Chrome exited 0, and its profile was removed. See local-freshness-report.json and local-freshness/.

The run-only caller checks local PNG SHA, nonnull full22 binding, review text, and the unchanged 120-second age bound before invoking the remote command submission path. The remote request also requires the exact locally reviewed label/SHA/identity/capture time to remain current. A stale local refusal leaves read-only capture available; submitted terminal chains remain non-replayable. All22-null, wrong PNG SHA, missing review, and invalid-time checks passed.

The five parent observer/passivity tests passed again. qualification.json checks 16 inherited files byte-for-byte, including the final bootstrap, retain.js, worker-frame.js, the browser, and ten qualified controls. The parent's actual current04 x86 → owning-worker/GL640×480 synthetic Exit8 evidence was reused by reference; it was not relabeled as an original witness.

Exact blocker and source boundary

The prepared 2,464-file closure retains source baseline 8a834a3dc7affc8c6e53245beab56e87a32b81e8 and expected CPU/owning-GL module 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17. These are prepared pins, not recovered live modules from this attempt. Original media and all four crate0400 files were checked unchanged together: server.ssv 2,752 B, game.ssv 62,728 B, demodocks.sav 1,395,332 B, demodocks.sv2 90,112 B; exact hashes remain in crate-manifest.json. No original save, fallback, configuration, or media was written.

The only runtime file differing from the parent closure was lib/renderer-input.js. To exclude the newer Pause/NumLock behavior, its exact parent bytes were staged from Git (187,872 B, SHA-256 4235d20d7fc2404b38f6e4f7f80c92d5f94f1513b4d6d7dcf04be34162a4b087). The worker staged those bytes through a run-directory symlink into /dev/shm while disk was near its floor. Hash validation passed, but the provider's stronger containment validation rejected the resolved path as provider outside root. This staging choice caused the blocker.

provision_chunked_files validates every local provider's resolved path before entering its upload loop. Its actual provision child joined 1, with separate stdout/stderr EOFs. The sole upload-journal record is the terminal validation failure: no upload began and no remote command was submitted. The caller and control failure became terminal and were not replayed. No helper was modified after allocation. pre-provision-blocker-check.json retains the exact offending path, resolved target, expected SHA, parent wait and zero-effect boundary.

Before another allocation, stage this exact Git input as a regular file inside the checkout, and exercise the provisioner's actual resolved-path validation alongside SHA checks. The caller freshness experiment succeeded; it does not supply the missing provisioning qualification. Neither this local path failure nor the earlier stale-scene failure explains native WebGL ExitProcess8.

Recovery and lifecycle

Source recovery is Git plus final-relevant-source.patch and owned-helper.patch/manifest; media is referenced by existing path and SHA. No source/media archive was made. RECOVERY.md, retrieval-verified.json, and SHA256SUMS.json preserve the unique local evidence. There were no new remote logs, captures or modules to retrieve. The superseded disk-blocker draft is explicitly historical: free disk recovered above 1.5 GB before allocation; reserve remained PENDING/unapplied and no RAM gate was used.

Private box bx_uamnntxs had an independently observed two-hour watchdog armed before creation; initial expiry 2026-11-12T22:28:08.481Z. Unique local evidence was hash-verified before normal stop at 20:28:58.699Z. Final state is archived, expiry null; receipt stop_ef14633ac946414e completed, forced false, error null. The stop child actually joined 0 with both EOFs. The detached manager's actual parent wait and the watchdog's actual parent wait also both record 0 with separate EOFs. No inherited box was changed, resumed or deleted. No other worker or public deployment was launched.

The original final completed owning-GL frame, its ordering relative to native API entry/exit notification, and any visible diagnostic remain UNKNOWN. There is no guest RE, disassembly, extraction, patch, substitute DLL, forced guest call, additional console command, new save, runtime repair, full27/parity/FPS/ audio/general crash-free claim.