Outlaws current original browser attempt, 7 November 2026

The first current browser blocker is unsupported Worker NE guest lifecycle. The unchanged registered outlaws_demo, C:\OUTDEMO\oldemo.exe, working directory C:\OUTDEMO, empty arguments and original companion manifest launch once in the ordinary production guest Worker. Nested DLL initialization throws Worker NE guest lifecycle is not implemented, yield 18. Its enclosing error is DLL initializer did not return: module=0xbde000, with completed:false, exited:false, halt:3. The original Worker detaches and the app disappears before the first capture. The driver's subsequent identity guard rejects one isolated registered app required. No original screenshot, native input, movement, turn, weapon response or enemy encounter is obtained. October CLI walking/turning is historical evidence and does not satisfy this browser task.

Evidence: scratch/runs/20261107-outlaws-current-browser-combat/. recovered/original/console.jsonl contains the nested cause and stack; startup-state.json has an empty app list and detached original guest Worker. Readiness had briefly returned true after six polls, demonstrating that guest existence alone does not establish sustained startup. The selected driver refuses capture after identity loss and closes normally without replay.

Current lib/process-boot.js:1020 explicitly rejects neBackend:'worker' at yield 18; lib/ne-guest-bridge.js:30 and lib/guest-worker.js:945 retain the same unsupported boundary. The existing NE lifecycle note documents main/cooperative support and Worker refusal. node test/test-ne-guest-service.js passes, including its explicit Worker rejection and nested main/cooperative lookup checks. This is an implemented fail-fast backend limitation, not evidence of a new CPU, API-return or memory mismatch. No emulator change, new regression or full build was made for this documentation-only result. Do not remove the refusal or change the original guest backend to manufacture gameplay evidence.

Before allocation, the selected helper import closure and all 149 lib/*.js files, including Worker/importScripts paths, are pinned. The deferred worker-observe.js read is explicitly included. The exact selected attach handler passes missing-file rejection and successful evaluate/resume checks. The same driver also passes an actual local Chromium production guest/render Worker attach using the generated public COM fixture and its original staged module. Its full fixture screenshot was personally inspected; the exact quit ACK and absent local PIDs/ports/profile/writer/held input are verified. This fixture proves observer attachment, not original NE startup.

Passing independent release, identity, stale/UNKNOWN rejection and exact ACK controls are reused from recent Darkstone controls by recorded identical helper and production hashes; unrelated controls are not rerun. The real selected driver entry accepts a constructed 25-minute deadline and rejects 35 minutes, expired and NaN before Chromium/guest creation. The immutable original browser deadline is 2026-11-07T12:47:48.722Z. No focus, lock, guest configuration, memory, clock, code or save modification and no UNKNOWN replay occurs.

The local original fixture was absent initially. Recovery used the tracked acquisition recipe and existing extractor/verifier, with one bounded download of the exact 14,186,356-byte outdemo_v2.exe, SHA-256 501f37aa475b6c27c87ce04e30b5207f91b81603cb376aaa9ffde1647a40e7b3. All 31 original records and 30 unique installed paths verify. The canonical ignored fixture is test/binaries/candidates/outlaws-demo/; duplicate extracted media and the downloaded package were removed after verified preparation. No media/source archive is retained. Manifest SHA-256 is 8b292f9b154c32d22c5ed64d6651fb33f3d1f8350cc30dbf35e847e51aa2b6a5; original executable SHA-256 is 46b72a094e891494cfa8f411d1942ea9dd7f06151d28f2af4bc1c1dca1e4ec79. The original readme, SHA-256 bd9c69ea913398e82d1e7d96b802ebeb54131e82265601291bb4d1fb840e6b96, documents Up for forward, Left/Right for turning, Ctrl for primary fire and Z for secondary fire. No assumed historical menu coordinates were used.

Tested source is main c60f5c8a3e6920a29da75737bbd9847b769e9d76 plus relevant-tracked.patch and lib-wininit-boot.new.patch. Owned new helper and note patches preserve additional inputs; Git remains the source archive. All 492 staged pins verify before and after execution. All 178 successful served bodies match those pins. The response audit retains 15 HTTP 404 probes, including optional system TLB and DLL lookups; these are not silently counted as present dependencies. The captured terminal cause is the explicit NE Worker rejection. The recovered actual guest module matches standard module e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467. Chrome is 151.0.7922.71, headless, with native inner viewport 1024×712; the page renderer is Win98Renderer/CanvasRenderingContext2D. No original render Worker endpoint is observed before exit.

One fresh UUID-idempotent 40-minute box, bx_9r5pcp9q, is created at 12:22:49.032Z with expiry 13:02:48.893Z. Serial supported upload stages all 492 pins; no SSH, forbidden retry, old-box resume or second original launch occurs. All 24 unique terminal artifacts (2,251,358 bytes), including the live module, are recovered and SHA-verified before the explicitly delegated normal nonforced stop. Original PIDs 6399/6406 are absent, ports 33019/45881 are closed, profile and writer lock are absent, and native/held input is empty. The box is confirmed archived at 12:24:39.892Z, stop completed with forced:false and expiry null. Local qualification runtime is also clear; sampled /home free space remains above 2 GB.

Next work is scoped Worker NE lifecycle support with a failing-before nested original-style DLL regression and the required focused tests/locked build, followed by a newly assigned original browser attempt. Movement/combat, audio, FPS, whole-game correctness and backend parity remain unverified.