Q3 GL readiness and current original gameplay — 2026-11-08
The run-local observer now admits actual native WebGL using completed, owning GL draw and presentation evidence. SoftwareGL and WebGL positive controls and all requested negative controls passed through real production guest/render Workers before the single fresh box was allocated. Original SoftwareGL reached Q3DM1 and visible burning torches, but movement and ammunition-reducing fire remain unproved. Original WebGL reached the native level menu, then its difficulty-selection command exceeded the unchanged command-work deadline. That command is UNKNOWN, input closed, and no replay occurred. This is not a parity, FPS, audio, full27, or emulator-failure claim.
Run: scratch/runs/20261108-q3-gl-readiness-gameplay/ (ignored evidence). Read before work: CLAUDE.md, the current AGENTS instructions, the predecessor note, and its exact result.json and final-validation.json. Their SHA-256 values are retained in local-validation.json; all predecessor failures and its proven zero-effect deadline refusal remain untouched.
Observer correction and actual-path controls
Only run-local helpers changed. producer-ready.cjs, worker-observe.js, bound-input.cjs, and browser-run.cjs replace the renderer-family mismatch: native WebGL cannot require SoftwareGL's d3dStats.glTriangles. Empty D3D statistics alone never admit input.
The passive observer associates the actual GLRenderWorker adapter with the OpenGLHostBridge it constructs. It forwards each original operation once. Receipts count successful batch execution, successful backend draw calls with positive vertex count, and actual sendFrame presentation associated with the current guest owner/context/window. The readiness selector requires one matching GL endpoint/backend, the bound guest slot, an owning current context, completed batches, presentations and a positive layer write sequence. Native WebGL additionally requires its real WebGL context and positive completed draws/vertices. SoftwareGL additionally retains positive owning CPU triangles, completed software-front batches and its ready, completed, error-free legacy transport. Two observations must preserve target/endpoint/adapter/bridge/owner/context/window identity and advance completed draws and presentation. Binding still independently reads the CPU and render Worker module bytes and requires the immutable staged SHA.
The existing capture-before/admit/input/independent-release/capture-after chain remains. Sticky UNKNOWN, stale review refusal, 120-second review age, 20-second command work, two-second ACK allowance, 30-second cleanup reserve, 50-second request ACK window and browser deadlines were retained. No guest clock, scheduler, configuration, game state, media or emulator implementation was forced or changed.
generated.cjs launches the production GuestWorkerLink and RenderWorker Manager with the standard module, constructs a normal guest window and uses public native x86 GL thunks to draw a red triangle. This exercises production /lib/guest-worker.js and /lib/d3d-render-worker.js, rather than mocked page labels or fabricated positive counters. local-controls.cjs uses the same establishReady, capture, numbered request/consume, admission, ordinary Enter input, independent release and final capture path as the original driver.
Final control receipts: local-software-final/local-controls.json and local-webgl/local-controls.json. Both positive arms passed. Each arm dispatched zero input for zero draw, missing current context, wrong guest owner, renderer replacement, stale review, module mismatch, controlled CDP UNKNOWN and nonowner GL counters. The nonowner test projects real completed counters onto a different owner; it does not manufacture a positive draw. Missing context uses public WGL unbinding. The stale refusal preserves only the already-qualified refresh path; the other invalid bindings close input. local-webgl/old-predicate-comparison.json records old readiness false with d3dStats: {} and corrected readiness true, including advancing owning draws/presentations and both module proofs. Both red-triangle images were personally reviewed.
Failed fixture iterations are retained, not called passes: missing cross-origin isolation, missing production GDI host imports, absent published slice statistics, and an overlarge CDP return object. local-validation.json records every iteration and confirms Chrome exit zero, closed ports and removed profiles. Final successful controls preceded fresh-box creation. Unchanged generic controls were not separately requalified. No emulator build was needed for this run-local observer/documentation change.
Current original arms
One UUID-idempotent allocation, bx_uzdgnzm4, was created at 03:26:53Z after controls passed. The independently supervised observable 25-minute watchdog was armed before allocation, with immutable deadline approximately 03:51:53Z. Both GL and D3D URL selectors matched each requested arm. The original full pak recipe was reused: 90 chunks, assembled size 46,853,694 bytes, SHA-256 e77abad2466f45a0a7ea018445528f9b95a0fe7789fa1abc1a7718bbf0754b08; temporary chunks were removed. No source archive or repeated media bundle was made.
SoftwareGL ran first, from 03:27:17Z. Its corrected readiness proved the owning software GL context and legacy transport, completed software-front work, CPU triangles and advancing presentation. Reviewed native main menu → Single Player → Q3DM1 Arena Gate → difficulty → Fight led to the original textured courtyard and current HUD. The selected difficulty remained Bring It On; the command label difficulty-easy does not prove an easier selection.
Before action, retrieved/software/focus-observation.json showed document focus, active screen canvas, pointer lock on that canvas, guest focus HWND 65543 and no held mouse button. The ordinary event history includes trusted input. software/world-progress.png shows ammo 100 and health 116 in the courtyard. Two 1500 ms Mouse1 holds were executed with independent release, but fire-current.png and torch-fire.png still show ammo 100, machinegun pickups and successive opponent scores 1 and 2. torch-fire.png also shows the rocket-death message and a burning wall torch. These intervening deaths/respawns confound action attribution; neither fire nor controlled movement is accepted. A subsequent 1800 ms W hold's held and final views show “Fragged by Major”, opponent score 3 and a close burning wall torch. No turn or further approach was attempted after that death. The torch view is accepted as a current rendered view, not as proof of controlled approach or fire.
SoftwareGL had 15 exact successful command ACKs, including normal quit, and Chrome exited zero at 03:34:42.561Z. An immediate read-only serial-drain check found its controller PID still alive during cleanup timers and refused to launch the second arm. This failed check remains in drain-software-remote-result.json and first-error.json. A distinct complete check at 03:35:00Z proved both processes absent, both ports closed, profile and writer lock absent, and no UNKNOWN. Only then was WebGL launched. There was never a concurrent second heavy runtime.
WebGL launched at 03:35:01Z with immutable browser stop 03:43:01Z. Corrected readiness opened input at 03:35:21.953Z despite empty D3D statistics, using the actual owning WebGL endpoint/context, completed draws/presentations and independent CPU/render module proofs. This box's actual WebGL1 provider was ANGLE Intel Mesa Intel UHD Graphics 620 (KBL GT2), OpenGL 4.6 Mesa 23.2.1, rather than the predecessor's SwiftShader provider. Reviewed screenshots show native main menu and Q3DM1 level selection, including yellow Fight focus after ordinary Up.
g-level-fight was refused as a stale scene before dispatch, effects zero. A new capture refreshed the scene and new IDs continued; that refused ID was never replayed. Final command g-open-difficulty was admitted, held Enter for 500 ms and completed independent release at 03:39:14.991Z (trace hold.release, three milliseconds). Its post-action capture then stalled at the page-owner Runtime.evaluate read. At 03:39:35.432Z the unchanged command-work deadline fired. The pending page-owner request was about 7.7 seconds old at that snapshot; passive hold sampling also contains an approximately 11.2-second read. These are observed latency locations, not a diagnosed emulator defect. There is no final capture or ACK for this command, so its result is UNKNOWN. first-failure.json, first-browser-failure.json, transport-closed.json, the full await trace and original-input-stopped.json preserve the closure. No further input or replay occurred. Chrome exited zero at 03:39:36.721Z. WebGL difficulty/world/movement/turn/fire/torch were not accepted.
One local quit request without mandatory waitMs failed schema validation before publishing a command. local-quit-schema-refusal.json preserves zero effects; a new valid quit ID was used. It is distinct from both the predecessor deadline refusal and the current WebGL UNKNOWN.
Reproducibility, cleanup and next work
Staged source SHA: 6138f2546f6d8b7b1d2f2ebaf8ff274acbb67297. runtime-pins.json contains the exact 920 staged inputs. The runtime source paths matched the predecessor; relevant-source.patch, the boot-file patch, owned-helpers.patch, media references and small run-specific inputs preserve relevant uncommitted/new hunks without archiving the source tree. Both owning Workers in both original arms used standard module SHA-256 f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121 (2,182,500 bytes). Original media is referenced by existing path and SHA in media-refs.json.
retrieved/terminal-checks.json verifies all 920 remote pins unchanged, browser exit zero, absent controller/Chrome PIDs, closed ports, absent profiles/writer locks, 15 SoftwareGL ACKs and six WebGL ACKs plus its final unacknowledged UNKNOWN. retrieval-final-verification.json records 295 remote references and 265 unique SHA-256 hashes; retrieval-verified.json independently reread every local artifact before requesting normal stop. Local disk stayed above 5,000,000,000 free bytes; no RAM gate was used.
Box bx_uzdgnzm4 was normally stopped after verification, archived at 03:40:47.011Z, receipt stop_9b3457880c51032d, completed at 03:40:47.030Z, forced: false. Initial expiry was 03:51:53.299Z; final archiveAfter is null. Both watchdog children returned zero and the supervisor's final remaining-child map is empty. No box was resumed/deleted and no public deployment occurred.
Next work is to resolve or locally bound the observed post-input page-owner capture latency while retaining current budgets and sticky UNKNOWN, then use a fresh authorized run for current WebGL Q3DM1 actions/torch. SoftwareGL still needs action evidence across a live interval without a death/respawn boundary and visible ammunition/projectile consequence. This run establishes the corrected readiness path and current SoftwareGL torch rendering, not the outstanding gameplay claims.