AVP2 initialized entry and staged dependency boundary, 7 November 2026

Marine gameplay remains unverified. One fresh box was allocated, but its browser closed before navigation because the staged runtime omitted tools/return-fire-body-driver.cjs. No original executable was fetched or consumed, no original module was instantiated, and no original launcher/menu, world, movement or attack was reviewed. The failed entry was not replayed.

Evidence: scratch/runs/20261107-avp2-initialized-entry/ (ignored). Source base: 2e0538a525b760c01416086424f57030c12bc93e, plus the retained relevant tracked patch and untracked source/helper patches. No emulator source changed in this assignment. The recovery amendment is tested locally; it has not been exercised in another original session.

Initialized production composition

The repaired predecessor staged-browser.cjs and gated-controls.cjs were reused. The staged browser continues to use production attachPinned and its actual consumer observer, without HTTP fulfillment, refetch, changed transport, private guest handlers, guard relaxation or fabricated consumption.

The first local registered Boids SDK control failed closed on concurrent lib/gl-compat.js source drift. A separately pinned local run then failed on its missing icons/apps/dx_boids.png. Both exact failures are retained; neither was reclassified as success or granted a broader absence policy. These two runs did not initialize guest Workers.

The subsequent direct-API control uses the existing SDK Boids EXE and original D3DRM DLL through public WineAssembly.init, loadExe, loadFiles, loadDlls and run. It uses the staged driver's same production response adapter, paused-target observer, real production Workers and release helper. This is a local SDK control, not AVP2 or a successful registered-launcher qualification. The first direct control had an incorrect registry-variable lookup after CPU initialization; its failure is retained. Corrected controls closed normally.

direct6/qualification-initialized-state.json and identity-admission.json record actual initialized guest-worker.js slot0/endpoint1 and the process's shared d3d-render-worker.js, initialized image base4194304 and legacy WebGL endpoint1. Both Workers' actual CDP bytecode hashes equal the served module: 2,182,493 bytes, SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467. The actual extracted module is retained. D3DRM's ordinary DllMain returns1; the guest issues real draws and completed render fences. The production completion reports WebGL2 through ANGLE/Intel UHD620/Mesa23.2.1, with zero transport or software draw fallbacks. This is initialized execution and rendering evidence, not Worker-script startup alone.

The run-local entry-identity.cjs strengthens admission to require the same live process/instance/renderer/window/guest-link/render-endpoint references, visible current foreground window, matching keyboard and foreground instance, process ID, main slot, initialized CPU and render modules, actual owning render endpoint, native provider and completed fences. It additionally binds the page CDP session/target/default execution context/unique context/frame/document URL and timeOrigin, checks freshness, and requires complete HTTP receipts. entry-identity.test.cjs accepts the actual initialized receipt and rejects41 mutated receipt copies covering these boundaries. These are receipt mutation controls, not claims of41 live document or Worker lifecycle experiments.

The personally inspected direct6/boot.png shows the SDK sample's cyan wireframe terrain and sparse objects. ordinary-keyw-input-ack.json records a trusted KeyW down/up pair targeting the production screen canvas, followed by released physical/async state and an empty queue. No input consequence or AVP2 gameplay is inferred from that SDK screenshot.

direct6/composed-stalled-down.json withholds the acknowledgment only after a real trusted KeyW DOWN. The repaired helper independently sends trusted UP; both the current command and queued Enter reject, the Gate retains UNKNOWN, no Enter is sent, and the helper holds no keys. Its immediate state snapshot still has pending guest input/async state; it is not a guest-consumption receipt. The driver then performs ordinary cleanup, without replaying input. Fresh standalone Chromium release tests and opposing never-settling/rejected keyboard/mouse controls also pass. The inherited consumer matrix is referenced and hash-checked in reused-consumer-matrix.json, rather than repeated.

One fresh box and precise failure

Normal shutdown was explicitly delegated to a separate OS process, and an independent OS watchdog was armed before allocation. The POST used a fresh UUID Idempotency-Key. Box: bx_x5u8c96v; immutable25-minute watchdog deadline 2026-11-07T16:54:49.476Z; original platform expiry 2026-11-07T17:04:49.168Z.

The selected runtime manifest had616 files. Individually pinned files and bounded chunks were uploaded without an archive. A deterministic reused-helper path error put five control inputs under a doubled absolute path; three were missing from their intended paths and two already had identical correct copies. Two failed pre-mutation checks are retained. Verified relocation of the three missing files succeeded before assembly, without executing an original. All616 staged hashes and all18 original media hashes then passed. Puppeteer was installed with browser downloading disabled.

The single entry browser started Chrome151.0.7922.71, then require failed at staged-browser.cjs:123 because the production adapter had not been included in the Node staging closure. remote-evidence/remote-webgl/driver-failure.json and terminal.json preserve the failure and normal browser exit0. The intended original route remains index.html?candidates&app=avp2_demo with the driver's existing diagnostic/threads/backend flags. Navigation was never issued. There is no avp2 alias and no successful original fetch-consumer receipt.

staged-closure.test.cjs resolves the actual production Node modules, rejects the used manifest, and verifies the619-file recovery manifest after adding tools/return-fire-body-driver.cjs, tools/browser-response-body-collector.cjs and tools/browser-consumer-completion.cjs. The uploader now derives helper paths relative to the checkout; its amendment is retained. This repairs a run-local staging defect, not an emulator defect. No production source or game settings/bindings/clocks changed, and no mandatory emulator build was needed. The original attempt was not repeated after these repairs.

Recovery, checks and shutdown

All18 original media identities and the exact registered17 companion set pass; AVP2.exe is excluded from the companion manifest. No generated command override was added. media-references.json records existing paths, lengths and SHA-256, including original autoexec.cfg and Profiles/Default.prf. Git is the source archive: source SHA, relevant tracked patch, untracked source patch and owned new-helper patches are retained. No source/media archive was created.

Reproduce the focused retained-input checks from the checkout root:

node tools/verify-avp2-recovery.js
node test/test-candidate-browser-manifest.js
node scratch/runs/20261107-avp2-initialized-entry/entry-identity.test.cjs
node scratch/runs/20261107-avp2-initialized-entry/staged-closure.test.cjs
node scratch/runs/20261107-avp2-initialized-entry/input-controls.test.cjs
node scratch/runs/20261107-avp2-initialized-entry/input-opposing.test.cjs

Unique remote evidence:13 files,6,128 bytes, retrieved and verified by size and SHA-256 before the normal-stop request. The remote audit confirms both owned ports closed, no live owned process, no browser profile and no held input. Stop stop_67ea332256058a93 completed at 2026-11-07T16:33:10.173Z, forced=false; box state is ARCHIVED. Current archiveAfter is null and archival retention is unknown. The independent watchdog was verified alive before and after normal stop, then both lifecycle delegates exited. Local owned browsers, profiles, ports, held inputs and board watchers are closed; /home remains above2GB. No public deployment occurred.

Next boundary: qualify the complete Node and browser staging closure using the619-file recovery manifest, then obtain fresh actual original consumption and instantiated-module evidence before seeking reviewed launcher/menu, Marine world, ordinary movement and visible attack/target consequence. The local initialized SDK proof does not fill any of those original checkpoints.