Original GLTron: local browser WebGL capture blocker, 2026-11-14

The sole current local browser original reached its menus and native paused arena through actual WebGL 2. Two controlled live corners, a natural round outcome and native Quit remain unproved. After ordinary Start Game, the next full-scene screenshot exceeded the controller's fixed 3,000 ms CDP deadline. The controller classified that capture as UNKNOWN and closed the attempt. No steering, pause, outcome or Quit input, or second original followed.

Evidence: scratch/runs/20261114-gltron-browser-webgl-turns/result.json. The first failure is a proof-transport deadline, not a demonstrated guest, producer, renderer or input fault. No production runtime repair was made. The new controller, GL binding and test remain uncommitted WIP with exact patches retained; this run does not approve their gameplay-to-Quit closure. This publication commits the report only.

Actual browser and renderer

Local Chrome 151.0.7922.108, V8 15.1.206.16, used actual guest and render Workers. Debugger bytecode reads independently hashed both executing modules in memory: each matches the 2,200,987-byte standard module c94ccf1b179f18bd4b47867445afed8cef2f1393b19aabfd259c7f3b94a7be09. No module copy was retained. Launch source was main 525d1f3bf41080e8b8ac8fd4772f3abd79c1e7a7, plus recorded dirty/new-file patches. All 675 launch pins remain unchanged.

The actual owning render Worker endpoint is api:gl, endpoint 1. Successful context 1 is current for owner 0 and hwnd 65537; its device matches the observed WebGL context. The guest producer reports gl_sw_enabled=0. The context reports:

WebGL 2.0 (OpenGL ES 3.0 Chromium)
ANGLE (Intel, Mesa Intel(R) UHD Graphics 620 (KBL GT2),
       OpenGL 4.6 (Core Profile) Mesa 23.2.1)

Permanent binding followed personal review of the nonblack original menu, with 450 frontend draws, 46 presents and 46 bitmap transfers already observed. At failure cleanup, the same owner/context had 2,071 frontend draws, 111 presents and 111 bitmap transfers. Device draw calls numbered 2,182, including presentation work. Existing GL readPixels calls numbered zero: this browser published through image bitmaps and the compositor; the selected PNGs are browser screenshot readbacks. No extra GL draw, swap, readback or publication was forced. Observer wrappers preserve arguments and returns.

The toolbar still displays Notepad because GLTron is absent from the public desktop selector. The ordinary direct app=gltron route, exact media, actual guest identity and owning GL endpoint establish the application and backend; selector labels are not proof.

Actual native GL was not executed here. The separate native note reports native llvmpipe LLVM 20.1.2 / WebGL 1 and remains native CLI evidence only. Browser-reported context identity implies no physical-GPU, FPS, parity, audio or full-27 result.

Reviewed scenes and first failure

All four retained result-named PNGs were personally viewed:

Two separately reviewed Enter pulses opened Game and selected Start Game. Both received DOWN/UP acknowledgements and observed guest keyboard messages; UP ACKs arrived 84 and 87 ms after DOWN. Scene ages at DOWN were 14,056 and 11,440 ms, within the 30-second menu limit. There were no gameplay DOWNs or held keys after either gesture.

Command 5 requested the next scene. At 2026-11-14T19:54:13.011Z its Page.captureScreenshot deadline expired. No completed arena.png or ACK exists. A separately labelled diagnostic screenshot then succeeded during failure cleanup; it did not reopen admission or supply a replacement intent. The guest still reported running, trapped:null, processExited:false and status 259 before host teardown. No crash, renderer error or input UNKNOWN is established by the capture timeout.

The original config assigns human control to player 1 with A/S steering and assigns player 3 to AI. No winner appeared here. Historical PLAYER 3 WINS cannot supply a controlled victory or this run's missing corners/outcome.

Validation, provenance and shutdown

The queue verified LTris recovered and Barrage actual controller/native, watchdog, outer-child and outer waits, both EOFs and heavy release. prior-terminal-gate.json retains those records; GTA2's withheld WebGL arm was not treated as another runtime wait.

Final focused controls and the full build passed under the heavy lock; the build additionally held /tmp/wine-build.lock. Controls cover finite keys, irreversible Quit reserve, production renderer edges, GL selection beside a legacy endpoint, ambiguous ownership refusal, passive-observer semantics, permanent identity replacement, actual independent scheduled/EOF release children, and UNKNOWN/no replay. One preliminary ownership mock omitted the production renderer's key-state method; its fixture error and corrected green test are retained.

Blank actual Chrome preflight delivered 22 trusted events, balanced for all admitted keys, a 1,500 ms pulse and independent 1,750 ms EOF fallback. Maximum observed hold was 1,749 ms. All release children were waited with both EOFs; Chrome/controller/watchdog/outer-child waits were zero. These controls are not gameplay evidence.

The sole original used Threads, ordinary browser realclock and a launch-only host Slice selection of 1,000 blocks. Guest registry, media, config, AI and state were unchanged. All 92 media paths match the native predecessor. Of 290 successful original HTTP responses, 289 match launch pins; test/binaries/tlbs/stdole2.tlb was not pre-pinned, and its observed hash/size is explicitly retained. Git SHA plus binary dirty/new-file patches preserve source identity without source archives, media bundles, frame series or WASM copies.

An independent watchdog armed before the controller with immutable 600/620-second deadlines. The controller also had a mechanical irreversible gameplay cutoff at 420 seconds and separately reviewed Quit controls; failure ended the attempt before that phase. Actual controller wait was 1 after 84.530 seconds, both EOFs. Chrome host close was 0, not native Quit. Watchdog, supervisor, outer-child and outer waits were 0, both EOFs; the watchdog did not fire and the heavy lock was released. Nine recorded owned PIDs are absent, four ports closed and both browser profiles removed. The initial board watcher's tool session ended 143 without a durable tail-child wait/EOF receipt; those values remain unknown and both recorded PIDs are absent.

No box was created: ID null, state NOT_CREATED, expiry null, stop receipt N/A. Free /home disk stayed above 12 GB and the 1.5 GB floor. Foreign WIP is untouched. The next prerequisite is a reviewed capture-transport policy that accommodates slow scene captures while preserving action freshness and closed input custody. This bounded task stops with the blocker; no further original or retry is performed.