AVP2 child handoff: required LithTech request cancellation
Run: scratch/runs/20261107-avp2-child-gameplay/ (ignored).
The single authorized original attempt stopped at a required-body network
cancellation. Marine world, movement, attack and original screenshots remain
unproven. No guest bindings, clocks, private handlers or production code changed.
Local boundary repairs and verification
The run-local staged-browser.cjs reuses the predecessor's unchanged
gated-controls.cjs, entry-identity.cjs and passed input/consumer controls.
reused-controls.json records their hashes and passed evidence references.
There was no redundant initialized-game qualification run.
Source review established that lib/browser-shell.js constructs dynamic child
IDs as vfs:<normalized guest path>. lib/resources-icon.js:482 tries the
pre-extracted PNG as an Image; on failure it retains the glyph and falls back
to executable icon extraction. The run-local child-boundaries.cjs permits
only an absent, unpinned 404 Image response at decoded path
icons/apps/vfs:c:\lithtech.exe.png, without a query. Required runtime/media
responses retain the production status, length, SHA-256 and lifecycle checks.
Worker inspection omits a target only after it has left Puppeteer's live Worker
set and evaluation reports TargetCloseError or the exact detached-context
message for that Worker URL. Live errors still fail. The focused Chromium
fixture uses the production response collector and actual icon loader. It
passes eight opposing icon-policy controls, real Worker closure during an
outstanding evaluation, detached-target inspection, live-child evaluation and
live-error rejection. Fixture-development failures are retained separately;
child-boundaries-tests4.log and child-boundaries-tests.json are the passing
result. All local fixture browsers were closed.
The repaired 619-file executable closure passes its actual CommonJS dependency
and full hash/length regression. Five predecessor pins changed solely to adopt
published allocator repair ef2709a76: three WAT files and the canonical and
compatibility modules. adopted-runtime-drift.json records old/new identities.
No other predecessor runtime pin changed. The selected canonical module is
f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121
(2,182,500 bytes). Original 18-media recovery and registered manifest checks
pass. This task makes no new build claim; the adopted repair's locked build
was already published, and this task changed only ignored helpers and notes.
One original attempt, no input or replay
Separate normal-stop and independent 25-minute watchdog OS processes were
armed before allocation. One fresh UUID-idempotent request created
bx_na9nty5d at 21:33:16Z. Watchdog deadline: 21:58:16.864Z; initial platform
expiry: 22:08:16.708Z. Local /home had over 5 GB free; remote prelaunch also
enforced over 5 GB. Remote assembly verified all 619 runtime files, helper
hashes, resolved Node closure and original 18-media recovery before launch.
Actual command: node scratch/runs/20261107-avp2-child-gameplay/staged-browser.cjs,
with PINS_FILE=browser-input-pins3.json, OUT_LABEL=remote-webgl,
WINE_TEST_BOX=bx_na9nty5d and the immutable allocation deadline. Local fixture
flags and NODE_OPTIONS were absent. Chrome 151.0.7922.108 ran headless on
index.html?debug&candidates&threads&no-log&d3d-renderer=webgl&app=avp2_demo.
Original AVP2.exe consumer EOF is proved: 57,344 bytes, SHA-256
36a772c2340ea7e415d8213d92b7a18d9541ef07c53b028d8a8ec475caf79b7d,
bound to the actual initiating request, document, execution context, target and
session. Actual instantiated launcher bytecode was recovered and matches the
selected module. This is not initialized child CPU/render admission.
The first collector fault occurred at 21:33:53.992Z for required media URL
test/binaries/candidates/avp2-demo/game/lithtech.exe, request 6082.274:
Network.loadingFailed, canceled=true, net::ERR_ABORTED. The server completed
HTTP 200 and the response collector captured, verified and continued all
950,272 bytes, SHA-256
599795e648481fa0009adbb453708ada57b4c20a9ea0b727b3991c2f1600e0c6.
Network lifecycle nevertheless failed; captured bytes do not replace successful
runtime consumption. Required checks were not weakened.
At 21:33:54.023Z the console records the original launcher's ShellExecute of
lithtech.exe -cmdfile avp2cmds.txt, then launcher exit 0 at 21:33:54.042Z.
The command file was generated by the guest, never staged or edited. Thus the
first fault precedes the console handoff; its cause is not established as
launcher-exit cancellation or an emulator mismatch. The later dynamic-icon 404
received the new exact optional policy, but could not continue after the
collector's earlier sticky fault. It was not the first failure in this run.
The boot capture drained the collector and failed closed. No force capture,
original screenshot, menu/world review or ordinary gameplay input occurred.
Final state has child process 1001, no guest Worker and no render endpoint;
owning-workers-latest.json is empty. No live child ownership or rendering
success is claimed, and the original was not replayed.
Evidence, lifecycle and next step
All 27 unique remote artifacts (3,374,639 bytes) were retrieved and checked by
length and SHA-256 before requesting normal stop. Remote cleanup verifies both
owned ports closed, no live owned processes, no profile and no held input.
Browser exit was 0. Normal stop stop_05221afbd4f9c85f completed at
21:34:44.138Z, forced=false. Box state is archived; current archiveAfter is
null, so retention expiry is unknown. Both lifecycle delegates exited after
confirmed stop. No public deployment occurred.
Source base recorded before staging:
b8b27fda18b44606e2ed89ab418c5705973e4720.
Git remains the source archive: source-diff.patch, new-files.patch, owned
helper patches, runtime/helper pins, recovered instantiated module and existing
media path/SHA-256 references preserve recovery inputs. No source archive or
duplicate media was retained. Later unrelated shared-tree commits do not
silently change the recorded tested pins.
Next: locally isolate why this required LithTech fetch reports cancellation after a verified response continuation, using the retained request lifecycle. Keep required body and consumer checks strict. A further original attempt needs separate authorization; this task's single original grant is spent.