Recoil snapshot native progress, 2026-11-08

Run: scratch/runs/20261108-recoil-snapshot-native-progress/.

This task closes on a substantive tested repair of the first newly demonstrated native-menu integration defect. The sole fresh original reached living gameplay, then its 100 ms Escape action failed the existing delivery bound. The original closed immediately; there was no replay, second original, ordinary M/C/arrow DOWN, attack, guest write, forced scene, configuration, clock or seed change. Ordinary M consumption and reviewed ramp/control access remain open.

The accepted co-located bound-input.cjs, compound-v4.cjs and browser-snapshot.cjs from ecefbec5e were reused byte for byte. Before allocation, all 771 providers passed exact size/SHA-256 checks. The explicit manifest preflight exercised the real hermetic preloader and transitive HUD decoder with an intentionally wrong ambient PIN_FILE overridden. The small closure adds the snapshot inputs and local observer inputs to the inherited 757 pins. Remote provisioning uploaded 772 entries including the manifest; remote preflight and all 771 pins passed again before the only original Node PID 5743 started at 10:07:30.839Z. Selected published source remains 49874a81c5ae180c20a15c6bb169d9041f028cae, module 6cf120d0d3b3db1823a8105eb26ef52a9093a7f871c37a46117475e213fda1c0. Peer WIP is excluded.

The actual-browser source-stall750ms corrected temporal-pair qualification, seven snapshot identity/freshness cases, inherited timing/browser suites and launcher qualification are reused by retained path, size and SHA-256 in closure-check.json. No accepted suite is repeated. Both complete guest/render source-byte checks per HUD probe, exact instances/epochs, uncached validation, 250 ms freshness, temporal pair, immutable deadlines and independent releases remain unchanged. This original did not reach its compound HUD probe.

Native outcome and first new failure

Reviewed Software/OK, Game > Start, NEW GAME, user/Medium and START led to native Island Storm loading. The first briefing showed 1.1 Operation Short Circuit; a later passive capture showed 1.4 Go to Landing Site. No briefing cycling input was sent. Natural camera/transport/disembark waits are retained individually. review/hud-check-two.png shows the living tank, health 100, timer 00:00:06, the route ahead, and the documented M map control.

There are 19 original commands, 18 exact ACKs, and one terminal UNKNOWN. Command 18, native-pause, requests Escape for 100 ms. Its exact identity admission at 10:14:56.756Z includes the actual guest/render module hashes, Worker instance and renderer epoch. At 10:14:56.935Z it fails input delivery exceeded hold bound: the independent physical release has started before the DOWN acknowledgement completes. The existing finally path awaits release; the failure closes admission and the browser. Chrome exits 0 at 10:14:59.384Z. No retry or compound input follows.

The original browser did not persist the thrown hold receipt; exact DOWN/UP receipt times and native Escape consumption therefore remain unknown. The original command, admission, sticky transport closure, first-failure records and passive log are preserved. A final visible native MENU was not captured, so the native-menu interval is unknown, not zero. The reviewed living-HUD capture begins at 10:14:44.390Z; approximately 12.366 wall seconds lead to Escape admission. That is an enclosing observed wall interval, not an exact active simulation interval. Loading, briefings and opening camera time are separate from MENU and active gameplay; no timer/FPS or pause-freeze inference is made.

Tested generic native-menu repair

New small native-menu-entry.cjs constructs an explicit 500 ms Escape menu command, rejects any shorter/different budget before dispatch, invokes the unchanged bounded hold, and persists success or thrown failure receipts. It never silently extends an existing request or retries a late/UNKNOWN DOWN. browser-menu.cjs integrates validation before admission and the receipt-writing helper in the actual key dispatch branch. It is a separately pinned correction; the original browser and manifest remain unchanged. menu-runtime-pins.json contains the corrected browser/helper closure. No production source edit or production build is claimed.

launch-menu.py prepares the corrected explicit-manifest launch envelope. menu-launch-preflight.json verifies the real preloader, HUD decoder and menu helper, overrides a wrong ambient manifest and removes the baseline fixture flag. This preflight starts no browser and does not authorize another original.

test-native-menu.cjs runs six focused cases in actual blank Chrome. A real trusted Escape DOWN with its acknowledgement delayed 180 ms reproduces failure under the former 100 ms request; the explicit 500 ms action passes. A 650 ms acknowledgement still fails and releases once. A 750 ms passive sampler cannot postpone independent release. UNKNOWN is terminal with no replay, and invalid menu budgets cause zero effects. The unchanged bound-input.cjs provides all physical hold behavior. Receipts and native trusted events are retained in native-menu-fixture/cases.json.

test-menu-browser.cjs then runs the corrected actual full browser entry with a new generated native-image fixture, explicit hermetic manifest, exact admission chain and a fixture-only 180 ms Escape acknowledgement delay. The command ACKs; its receipt records 500 ms from start to independent release, trusted native Escape DOWN/UP, empty physical state and cleared bitmap. The reviewed fixture image shows MENU. This is generated integration evidence, never native Recoil menu/consumption/route evidence. Both fixture browsers exit 0; all enumerated PIDs are absent, ports closed, profiles and writers absent. The local runtime lock is held only during each actual local Chrome run and released afterward. Provisioning, remote runtime, retrieval and lifecycle supervision hold no local runtime lock.

Retrieval and publication

All 231 remote references / 18,128,825 bytes / 191 unique hashes were matched or uniquely retrieved, then independently read and rehashed before normal stop. All 26 remote PNG references pass CRC decoding. Known remote launcher, monitor and Chrome PIDs are absent; HTTP/CDP ports, profile and writer are drained. The final passive arrow/button state is released; no unobserved Escape bitmap sample is substituted for a receipt.

The one UUID-idempotent box is bx_v8tuc3a4, created 10:07:09.351Z with initial expiry 10:33:09.223Z. Observable independent normal-stop and 25-minute watchdog processes were armed before allocation. The immutable watchdog deadline is 10:32:09.064Z. After verified retrieval, normal delegated shutdown archives the box at 10:15:34.521Z, expiry null. Receipt stop_ada15dc1ed3ccb75 completes 10:15:34.539Z, forced false, error null. Both lifecycle children exit 0 and the supervisor has no remaining children. No old box was resumed/deleted, public deployment or subworker used. Free disk remains above 5 GB.

verification.json checks the original command/ACK/failure evidence, module identity, retrieval hashes/PNG CRCs, cleanup and the tested correction. Its first local attempt assumed concurrently collected command rows were ordered; that diagnostic remains in verify-unordered-first.log. Numeric command ordering fixes the verifier and the completed verification passes, without replaying runtime input. Exact Git identity, relevant binary diff, small owned-input and correction patches, plus existing media paths/hashes provide recovery. There are no source/media archives. Only this documentation note is published. Owned containment, missing-artifact and schema checks pass. The repository-wide checker retains seven unrelated containment errors in older peer runs.

Next requires a separately authorized original using the explicit 500 ms native menu-entry helper, then the unchanged qualified snapshot gate for ordinary M and reviewed ramp/control movement. Objective completion, full27, parity, audio and simulation/game FPS remain open.