Quake II browser current-display capture, 2026-11-14

Evidence directory: scratch/runs/20261114-quake2-browser-current-capture/. The prior CLI original and the GLTron originals remain permanently closed. Their missing combat/native-Quit outcomes and historical UNKNOWNs are unchanged.

The owned tools/quake2-browser-controller.cjs is a self-contained derivative of the released GLTron controller and immutable-ticket binding at 5bec44a8. Older helpers and the production runtime remain read-only. The registered quake2_demo route retains its complete media, +set vid_ref gl +menu_main, relative mouse declaration and cooperative 10,000-block schedule.

A completed current-display ticket reads retained copied pixels and original publication/display/request/readback timestamps. Later painting never refreshes those timestamps. Pending, failed, cancelled and UNKNOWN tickets cannot be replayed. The controller pins one actual browser process/start token, page, process/window objects, guest Worker/instance/module and owning GL Worker/module. Visible complete output and identity remain necessary at every admission.

The derivative adds bounded passive preflight for one personally chosen event. Each readiness probe has a new nonce and keeps the original scene/intent deadline: five seconds for play, thirty for menus, with at most three seconds of passive observation within that deadline. It observes ordinary Worker readiness without events, prearming UP, tickets, publication, forced hold end or timestamp writes. It revalidates the complete owner/module identity after natural readiness and retains the final synchronous live paint gate. Scene expiry before any request produces NOT_SENT and requires personal review of a new raw scene and a new intent. Owner changes, occlusion and UNKNOWN close the chain. Any failure after UP prearm or an input request remains terminal.

Only one finite key is allowed per intent, at most 1,500 ms, with an independently prearmed 1,750 ms UP and actual child wait/EOF evidence. All holds execute and release before the next personal decision. Enter as fire additionally requires an explicitly reviewed selected weapon, ammo and visible enemy identity. Menu navigation, ambient opening damage, fire animation and handler ACKs cannot prove an outgoing hit. Native Quit and host teardown are separate. The 180-second Quit reserve is irreversible and never synthesizes an action.

Validation and publication

Controller and focused test are published on main as af8db2f5615a87e80f78bb3736edbfebf1a13cd4, before the original launch. Strict pull/push completed with actual zero waits and remote main matched. The locked full build passed in 59.357 seconds. Focused policy, real child UP, loopback transport and identity controls passed, as did twenty checks across five renderer suites. Actual Chrome trusted key and mouse controls passed, including finite 1,500 ms holds and independent 1,750 ms fallback UP.

chrome-v1/report.json passes the production compositor/WebGL Worker controls:

These are synthetic workload controls, separate from the sole game original. The natural-end callback is an admission proof, not guest input or combat.

Sole original: complete capture, unsent intents, terminal capture precondition

Golf and TicTactics' actual native/watchdog/supervisor-child waits, both EOFs, heavy release and exact PID absence were personally verified before heavy work. Historical ancillary UNKNOWNs and tool exit 143 were retained; no additional wrapper gate was imposed. The runtime and all older helpers were read-only.

The sole original launched 23:23:09.806 UTC, with immutable 1,200-second runtime and independent 1,220-second watchdog deadlines. The unchanged browser route was index.html?debug&threads&gl-renderer=webgl&app=quake2_demo. Actual scheduling and startup logs confirm the registered 10,000 budget. The complete registered media/config and +set vid_ref gl +menu_main were unchanged. No map, console command, config, seed, AI, clock or renderer write was made. Browser clock and gameplay continued normally.

original/host-bootstrap.png was personally reviewed before one ordinary trusted fullscreen consent click. Its recorded mousedown/up/click all targeted the host button, with no canvas mouse event. No permission override or CSS hiding was used. No pointer-lock or guest mouse request was sent.

original/startup.png was personally reviewed: complete fullscreen native Quake II title/main menu, GAME selected above MULTIPLAYER, OPTIONS, VIDEO and QUIT, dark textured background and native startup log. One permanent binding pins browser PID 4139527, guest process 1000, HWND 65537, actual guest Worker and instance, and owning GL Worker/endpoint/module. Both recovered Worker modules have SHA-256 c5d48cf634f3dcd14453f82be512f879459d305d92c2d3ffb6cc0d8c603fb398. This is actual WebGL ownership evidence, not a physical-GPU claim.

The first current-display ticket was explicitly complete, read during a later Worker hold, then cleaned up as complete with cancel returning false:

Original timestamp UTC
Display/publication 120 23:23:41.954
Request/readback start 23:23:41.973
Readback completion 23:23:42.192

The personally chosen finite Return then expired during passive preflight, NOT_SENT/effects 0, before UP prearm or DOWN. A newly requested complete raw scene, original/main-menu-new-review.png, was personally reviewed before a new distinct Return intent. Its publication was 224 at 23:24:06.776, request/readback start 23:24:06.792, and completion 23:24:06.966. Its original timestamps were retained. That distinct intent also expired without prearm or DOWN. No scene, intent or probe nonce was replayed or refreshed.

The two intents produced 83 unique passive probe nonces, including six observations of natural readiness. No readiness observation survived the complete asynchronous identity validation and final gate/deadline sufficiently to admit input. Only host-release-config.json exists; there is no guest key release config, delivery, UP prearm or DOWN request. These are positive passive expiries, not failed physical requests relabelled as passive.

A further manually requested raw scene encountered held/in-flight paint at its pre-request check, before any third ticket was created. The preserved CAPTURE_PRECONDITION_REFUSED permanently closed the chain. Its null ticket observation is truthful: this was a precondition failure, not a failed, pending or UNKNOWN ticket. The two earlier tickets remain complete. There was no retry, reopen, rebind, source repair during the original, or second game.

original/first-failure.png was personally reviewed as a diagnostic of the same native main menu. It is not an input-admission scene. Solo play, selected weapon/ammo, actual enemy identity, firing, persistent damage/defeat and native Quit are unproved. No navigation, fire animation, ambient/friendly damage, player win or other gameplay success is claimed. Host teardown is separate from native Quit.

Shutdown, recovery and partial result

The Node browser controller (the supervisor's native child) exited 1 after 92.199 seconds. This OS wait is not a native guest-Quit outcome. Chrome, independent watchdog and supervisor child each have actual zero waits and both EOFs. The watchdog observed the actual controller wait and did not fire. All exact PIDs 4139510/4139511/4139512/4139527 are absent, the HTTP endpoint is closed, the browser profile is removed and the heavy lock is released. The invoking outer tool returned 143; its separate wrapper wait remains UNKNOWN. Those ancillary facts do not replace the actual recorded waits.

original-release-reviewed.json records zero drift across 744 source/input pins and 68 registered media/control rows. Git commit plus relevant binary patches preserve uncommitted source, including the owned new files during the controls. served-and-loaded-pins.json verifies served bytes and actual loaded Worker module hashes. No source archive, frame series, media copy or WASM copy was made. Only named selected PNGs remain; pruned-image hashes are recorded. The original is permanently closed and runtime custody was released to JezzBall before report finalization.

result.json records a partial task (dashboard outcome failed because combat/native Quit were not achieved), with actual waits, selected images and hash-verified artifacts. The concrete remaining obstacle is that the preserved live readiness gate and full asynchronous identity validation could not admit one reviewed input within the bounded passive observation, followed by a terminal held-paint capture precondition. A future authorized task would need to address that boundary before another original; this task makes no retry.

Box ID null; state NOT_CREATED; expiry null; stop receipt N/A. /home stayed above 1.5 GB free. No box, worker, deployment, full-27, FPS, audio or physical-GPU qualification was performed. This bounded task stops.