Forsaken stable startup and gameplay admission, 8 November 2026
The demonstrated none -> owning renderer startup rejection is repaired and
qualified in the run-local browser helper. The fresh original WebGL session
passed that boundary, reached the reviewed Single Player submenu, then stopped
at a new post-input capture work-deadline blocker. Volcano/HUD/thrust/fire
and the software Direct3D arm remain open. The previous run's rejected logo
Enter remains a failure; it was neither replayed nor relabeled.
Evidence: scratch/runs/20261108-forsaken-stable-startup-gameplay/.
No production emulator or transport implementation changed.
Tested startup composition
bound-input.cjs reuses the released Re-Volt startup phase. Before binding it
passively waits for actual renderer attachment, then requires two complete,
identical readings of the production guest Worker, recovered module, owning
renderer endpoint/Worker/module and WebGL context. Pending observations preserve
process, guest-owner, document, canvas and module object identity across samples.
The pending phase does not evaluate a guest Worker that may be waiting for its
renderer callback. Context identity comes from the actual returned OffscreenCanvas
WebGL context, observed while delegating the original context creation once.
Software readiness requires the actual native legacy endpoint/module instead.
The software branch was not verified on the original in this task.
Captures require this binding; a current personally reviewed capture is then required for admission. Startup sampling cannot be reentered after binding. Existing exact identity, 120-second scene freshness, closed-chain, exact ACK and independently armed UP behavior remains. The unchanged numbered transport has the same command work and immutable browser/cleanup deadlines.
Before allocation, qualified-before/ reproduced the old endpoint transition
with production guest/render Workers and zero input. qualified-context/
qualified the repair with the actual production Workers and f965 module:
missing renderer timeout, prebinding process replacement, postbinding endpoint,
renderer-owner and process-owner replacements, every reviewed identity field,
stale-scene refusal, and a trusted ArrowUp DOWN/UP after stable capture/admission.
Negative controls produced zero dispatches. The generated caption/white-canvas
image was personally reviewed; it is helper evidence, not original gameplay.
The two initial local fixture attempts briefly navigated the original launcher route before the generated fixture. That routing mistake was corrected before the final qualifications and allocation. Retained served logs show no original EXE response in any local fixture; each separately HTTP-pinned the original manifest. These attempts are retained as distinct preallocation evidence.
The actual Python request helper/numbered ACK path passed 0/1/2/10-second waits, Enter/A/Escape/arrows/Ctrl/Space and A+Ctrl/A+Space controls. Oversized waits and insufficient immutable deadlines refused publication. The inherited sticky marker negative is referenced rather than clearing a task marker to repeat it. Independent-UP slow-observer and injected-UNKNOWN controls, the fallback-counter test and all eight capture-deadline tests passed. The expensive original capture composition was not thereby proved to fit every command's work budget.
Fresh original and new causal boundary
Only fresh box bx_kncsxd8j and one original browser were used. The current
production route was index.html?candidates&no-log&threads&app=forsaken_demo&d3d-renderer=webgl.
Passive startup observations retain 52 absent-endpoint samples, beginning
01:36:13.061Z, followed by actual endpoint 1 at 01:36:43.410Z. Readiness
completed after 54 attempts. Each explicit passive delay was at most eight
seconds; there was no long simulated guest-clock jump.
The original proves owning legacy WebGL endpoint 1, actual guest/render module
SHA-256 f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121,
and a 640x480 WebGL 2.0 context reporting ANGLE / Intel UHD Graphics 620 /
Mesa 23.2.1. Guest Worker GPU flags are true. Endpoint controls report ready,
completed commands and zero error. Retained checkpoints report zero GPU
fallbacks, renderer errors, inline software draw completions and fallback
software draw completions. This is actual owner/context evidence, not a toolbar
or unrelated software-GL flag.
Personally reviewed observations:
unbound-diagnostic.png: readable Single Player main menu during passive startup. This diagnostic never supplied an input binding.review/startup.png: by the bound capture the menu had entered its green loading sequence. It was not used as a reviewed playable world.review/settled.pngandreview/dismiss-attract.png: automatic demo/intro tunnel views with Acclaim logo and no player HUD. These are excluded from player movement/combat claims.review/menu-return.png,review/copyright-continue.png: copyright and Probe intro screens after ordinary Escape/Enter controls. Natural sequence progress can confound attribution to a particular short pulse.review/intro-passive.png: main menu with Single Player highlighted. The next Enter used this reviewed capture and the stable owning identity.review/singleplayer.png: Single Player / Start / Normal / Back submenu. This is a fresh native menu transition beyond the previous startup rejection.
Command 6, ID start, selected Start from that reviewed submenu. Its
admission completed; Enter began at 01:40:10.008Z and independently scheduled
UP began at 01:40:10.758Z. The completed hold receipt has no release error.
retrieved/original/start-state.json was produced during the subsequent capture
composition: it reports the same live legacy endpoint, WebGL module/context,
zero renderer error and advancing owner controls. There is no completed
start.png or success ACK.
At 01:40:25.497Z, the unchanged consumer's workEnd expired: the requested
1-second settle plus its fixed 20-second work allowance had elapsed. The first
fault is command work deadline; never resend. The ACK client then observed
runtime first fault and retained sticky UNKNOWN. This is after dispatch and
release, unlike the old predispatch identity rejection. Six earlier commands
have exact success ACKs; this seventh command was consumed once without a
success ACK. No further input, capture request, retry, original relaunch or
software arm followed. original-input-stopped.json remains present.
The proven blocker is the end-to-end command budget expiring during post-input state/capture composition. The logs do not identify the exact outstanding CDP operation at expiry, so no narrower Worker-stall or renderer-failure cause is claimed. Earlier captures already demonstrate expensive composition: startup state time 01:37:17.987Z precedes screenshot time 01:37:34.328Z; another passive capture spans state time 01:39:11.338Z through completion 01:39:27.783Z. A successful startup test and lightweight request fixture did not cover this original menu-transition workload. No emulator mismatch was demonstrated, so there is no speculative emulator repair or new full-build claim.
Recovery, verification and shutdown
Source identity is main 8a6ca96982daa4b500616a6bc02c3e50c8df1bfd,
relevant-source.patch, new-lib_wininit-boot.js.patch and the owned helper
patches. Git is the source archive. All 873 original fixture paths remain
unchanged, including executable SHA-256
366ec5d0943daca839836296f9fb52724e94dc155630c6b0c30d7181106b5e24 and
manifest SHA-256
587ce145ab73a3fed2c7136425bb6a7bcf28def312d430c8bf7d1be802b2260b.
All 1,487 staged pins match before and after execution; 645 successful
served responses match their pinned bytes. No source tree or media archive was
created. Chrome was 151.0.7922.108; threads were enabled.
All 108 remote references / 100 unique contents, 9,933,688 reference bytes, were retrieved and independently size/SHA-256 verified before normal stop. Five original key holds have completed independent-release receipts, including the final UNKNOWN command. Chrome exited zero; controller/browser PIDs, HTTP/CDP ports, profile and writer lock are absent. Local fixture browser resources and lifecycle delegates were also checked after completion. Sampled free disk was above 5 GB; there was no RAM admission gate.
The observable detached 25-minute watchdog was armed before allocation.
Box bx_kncsxd8j is archived, current expiry null, original expiry
2026-11-08T02:00:31.506Z. Normal stop stop_5706284f2b266637 completed
2026-11-08T01:41:31.792Z, forced:false, error null. Both lifecycle
delegates exited zero and the supervisor has no children. No box was resumed
or deleted and there was no public deployment.
Next: locally qualify the actual production capture/admission composition against the observed slow menu-transition workload, retaining fixed deadlines, strict binding and first-UNKNOWN closure. Then a separately assigned fresh run can finish WebGL followed by software Direct3D Single Player/Volcano, reviewed HUD, thrust/look, ammunition consequence and reachable enemy interaction. Full 27, parity, FPS and audio remain open. This single-task worker stops here.