Forsaken current browser world, input and Quit, November 18

The unchanged registered forsaken_demo reaches the original Normal Volcano world on published source in ordinary production browser Workers. A changes the room/corridor geometry, Ctrl reduces PULS from2000 to1994, and A+Ctrl reaches the corridor with PULS1980. The ordinary Quit route terminates the guest with ExitProcess(13). Enemy target damage/defeat and a causal runtime repair remain unproved. White combat/death imagery prevents a reviewed aimed continuation. Evidence: scratch/runs/20261118-forsaken-current-browser-world-combat/.

Actual source, module, media and backend

The immutable source is published 5af3bae93d429aab2e742128a7f15ed85f8a9adc, compiled through the existing Git-backed memory-only server and repository compiler. The actual retained 2,417,153-byte module is 3616571e62633952e31159f01a35e86651c1a04aa54ed7ab78af22ecf369ad11. A fresh Git rebuild matches; late bytecode reads match in all four live Workers (three guest Workers and the render Worker). The earlier detached Worker has no bytecode observation and is explicitly recorded closed. Shared runtime WIP and later publications are excluded from this tested graph.

All873 pins match both the predecessor and postflight: the existing installed manifest, original executable and871 manifest files. No media is reinstalled, copied, modified or remapped. The original executable remains SHA256 366ec5d0943daca839836296f9fb52724e94dc155630c6b0c30d7181106b5e24. HTTP response hashes, Git/binary differences, owned run-input patches and recovery instructions are retained. No source tree snapshot or media archive is created.

The exact route is index.html?debug&threads&no-log&d3d-renderer=webgl&gl-renderer=webgl&app=forsaken_demo. The Direct3D selector is d3d-renderer; the additional GL selector does not name the Direct3D backend. Actual endpoint1 is d3dim-gps, render Worker target 852EF8EDC5001AB9037021C09A87A146, backend webgl1, on Chrome151.0.7922.108, ANGLE/Mesa Intel UHD620, Mesa23.2.1. The browser is headful on an authenticated private Xvfb/Openbox display, with ordinary default slicing and Workers.

The initial menu observation records7221 completed executor draws and422 presents. The after-level diagnostic records85982 draws,3611165 triangles, 1680 presents and4380 readbacks. Published read-only producer counters report 68066 GPU draws, zero fallbacks and zero declined draws;4379 readbacks are charged to the GPU-destination Blt/BltFast fence. This is a supported WebGL draw/readback/DirectDraw presentation route, with no software-backend fallback observed. These cumulative observations span the menu/level/menu interval; they are not individual action counter deltas. In particular, the bridge's last PRESENT-frame statistics remain at an older1271-presents frame during world play and must not be mistaken for a current executor snapshot. No backend parity, FPS, audio or full27 claim follows.

Calibrated capture and ordinary input

The complete menu/start/movement/fire/Quit sequence and finite policies are written before the original launch. Whole private-display XGetImage capture and PNG encoding have a10-second ceiling; CDP transport has15seconds, command work90seconds, startup180seconds, original runtime1200seconds with240seconds reserved for Quit, and final native-exit observation60seconds. Independent release children have a fixed5-second fallback,20-second prearm ceiling and ordinary holds at most1800ms. No limit is extended in flight.

The authored browser control first establishes a complete yellow triangle, then ordinary Enter changes its background from blue to red. A+Ctrl+Space uses exactly matching key/code DOWN and UP, independent timer releases and passive physical-neutral checks. Escape reaches authored guest exit0. Late actual module reads match in both control Workers. An initial control closes because the bridge is not initialized; another positively refuses before DOWN because a calibration incorrectly inherited the original's four-minute Quit reserve. The next fresh authored control corrects these startup/budget issues. Those control scopes remain closed; none is original-game crash evidence.

Original captures use the same whole private-display route, with one lightweight page-identity read on either side. No synchronous Worker state-read chain is required for an image. Selected whole captures show the original Single Player, Start Normal, Volcano confirmation/loading and starting room. Natural loading enters gameplay without an extra Enter. No debugger is enabled until after world movement/combat; Workers are never started paused.

Twelve ordinary original gestures produce13 trusted matching key/code pairs (the paired A+Ctrl gesture has two keys). Every independent release child has actual wait0, both output EOFs and passive physical state0, including final promotion Enter. CDP completion is transport evidence; no native per-action ACK is invented or required. No guest polling, focus/clock forcing, configuration, INI, registry, game or ownership/generation changes occur.

World, firing and the bounded combat blocker

world-neutral.png shows five lives, SHLD/HULL128, PULS2000 and MUG5 in the readable Volcano room. after-primary.png shows PULS1994 after Ctrl800. after-thrust.png shows a larger/closer doorway after A1200, with unchanged ammo and full shields/hull. These are causal primary-ammo and movement evidence.

A+Ctrl1800 reaches the next corridor. The selected external whole-display image approach-whole-external.png shows the corridor, PULS1980, SHLD0/HULL79 and a bright flash. Its timestamp is after release, so it is not a midpress capture or action-admission image. approach-result.png becomes white, with faint text; the text is not qualified as an enemy kill. combat-settled.png remains white after passive waiting. Player damage is observed; its exact attacker and enemy target damage/defeat are not established. No aimed shot or secondary attack is sent using an unreadable target scene.

Escape still opens the original pause menu. The visible selection marker moves from Set Up Biker to Quit to Main Menu under Up; Enter restores the complete 3D main menu. This excludes interpreting the white interval alone as a proved runtime crash. Prior additive/texture/coverage investigations remain binding: white pixels and additive state alone do not identify a rendering defect. No speculative clear, blend, input or guest patch is justified here.

The concrete next blocker is a readable, living target interval that separates target damage from outgoing ammo and player damage. Any renderer repair first needs complete causal inputs for a naturally whitening draw or a demonstrated incorrect transition, followed by authored native and normal-browser oldfail/ newpass, focused neighbors, locked build and a fresh affected original. This task makes no production-code repair and claims no such repair counterexamples. The final canonical build under /tmp/wine-build.lock passes on the later shared worktree; this is a build gate check, not the immutable original's source identity.

Ordinary Quit and lifecycle limits

After Quit to Main Menu, Up visibly selects EXIT GAME. Enter reaches the original promotion; Enter dismisses it. The actual page process object reports exited, runningfalse and guest code13; console records the original back-buffer error Cannot call D3DAppShowBackBuffer while bRenderingIsOK is FALSE, then ExitProcess(13). The final whole display shows the shell ready. This proves ordinary Quit termination, with an error exit rather than clean exit0. It is distinct from subsequent browser/process cleanup.

The three calibration scopes have actual browser, display, driver/supervisor, watchdog and enclosing-launcher waits with separate EOFs; the successful one exits0. Original guest termination, all independent UP waits, all32 command receipts and the final whole image are retained. However the original enclosing tool wait returns143, causeUNKNOWN, during host cleanup. Browser, display, driver/supervisor, independent watchdog and enclosing-launcher wait files are missing; no original wait/EOF completeness claim is made. The advisory board watcher's tool wait is also143, with its sender/EOF unavailable. The external coordinator-owned worker wait is unavailable to this worker.

No runtime endpoint is queried or input replayed after that closure. A separate finite15-second native-supervised filesystem/process cleanup observes the recorded browser already absent, stops only the two recorded private-display processes, verifies all three PIDs absent, removes the profile/authority, and checks HTTP/CDP listener absence through /proc/net/tcp without connecting. That cleanup controller and its supervisor have actual wait0/both EOFs and no leaks. Orphan display-process waits remain unavailable; absence is not a wait.

Evidence metadata is published last. Free /home stays above1.5GB; no RAM gate, box, agent, worker, Python, Wine, public deployment or held-title run is created. Box IDnull, stateNOT_CREATED, expirynull, stop receiptnull. Forsaken remains outside the provisional historical list; full27 membership and parity stay open.