Readable Q3 fixture passes; original menu click has no visible transition
The explicitly authorized fixture usability change is implemented in the owning Q3 module. Native startup and supported Enter effect both pass separate image review and exact pixel comparison. One original Quake III attempt reaches a clear main menu, but its acknowledged Single Player click leaves that menu visible. That is the first concrete application-effect blocker. Owning native cancellation followed immediately; no later protocol, input, capture, retry, quit or extension was sent. No original arena movement/fire or production rendering-defect claim.
Evidence: scratch/runs/20261109-q3-readable-fixture-arena-2355/.
Implementation commit: b3d0207c8 on main, published immediately with strict SSH.
Exact starting Git and relevant small patches are retained; Git remains the source
archive. There are no source/media archives. Game media use the existing pinned
paths and hashes. Shared providers stayed read-only.
The owning generated-response handler now supplies a 320×200 window/client, framebuffer and GL viewport to the same public x86 thunk, GuestWorkerLink, render Worker and production host publication chain. Display backing is 320×200, with an opaque 2D context and smoothing disabled. The solid-red triangle retains vertices (-1,-1), (1,-1), (0,1) on opaque black. Trusted, nonrepeated Enter changes the model translation to +0.5 in x (80 pixels); vertices and viewport dimensions stay fixed. Owner replacement or an earlier fixture error refuses drawing/input. The historical blurred-image STOP and all terminal, review and native-input admission guards remain in force. No historical review was republished.
The focused visual test executes the actual generated handler response, fixture function/public x86 thunk arguments, production renderer-input handlers, real host frame publication and composed bound capture consumer. It checks dimensions, vertices, primitive, clear/color alpha, display-context opacity, smoothing, trusted/untrusted/repeated/wrong-key effects, owner replacement, frame identity and capture identity. Six pixel-corruption controls and three actual native-control consumer/numbered-ACK cases include bad initial SHA and indistinct-input review refusal. Historical 64,000-pixel blur reconstruction still passes. Controlled services in these tests do not claim native GPU execution.
Native fixture startup PNG: SHA-256
7f88084dce5315685df97421b7d28ae667438b038e8cb6c0df8ca6c8e01c2268,
5,424 bytes. Separately inspected: crisp canonical red triangle on black.
Native input PNG: SHA-256
fec45e9e8dce62e1d05ae761ba3b6463356a1f446c536bbd16f6e6a4fe466b27,
5,201 bytes. Separately inspected: clear 80-pixel right translation, clipped at the
right canvas edge. Each capture independently matches all 64,000 expected canvas
pixels in all RGBA channels, with zero mismatches; every outside pixel is white.
Fresh native geometry in both states is backing 320×200 and rect (8,8,320,200).
The actual Enter held/released physical receipt passes. The complete cancellation
prerequisite, kernel drain, actual waits and separate stdout/stderr EOFs pass.
Only then was one original launched through the normal native route, with the
selected CPU/render module SHA-256
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18.
Startup SHA 0e130c75865d7faca52d68bd9c02a5d040bc2fbf8fe116f99160a40321a3afed
shows the clear original main menu. Its separate review admits one ordinary native
click at canvas-relative (0.5,0.34), 150ms, followed by 1000ms settling.
Returned SHA 14b5921ae2e49bb9505465b236af9664e36613b316ae22b475f523fa818eb1ae
still shows the main menu. Both images were separately inspected, with fresh
640×480 backing / rect (0,34,945,855). The mouse ACK establishes delivery only;
no menu transition or cause is inferred. The failed result was never admitted
for another input. Exactly two original captures and one original command exist;
trace analysis finds zero protocol requests after the model STOP and no original
Browser.close request. Original kernel exit -15, complete drain, actual parent
waits and separate EOFs are retained.
Focused visual controls, service review (7), wire revocation (8), actual generated readiness/error/missing-reply, terminal cleanup and current foreign closure (27 refusals) pass. Locked builds pass twice. Supplementary legacy fixture-input tests refuse retired startup-provider bytes (the first invocation also lacked their required environment); the old page-session harness expects a normal stand-in exit after a terminal refusal, whereas the preserved terminal policy terminates it. Those failures remain in the logs; no shared provider or guard was changed to satisfy them. Native computed CSS/DPR were not separately queried; exact returned pixels, fresh rect/backing and identities are retained instead.
The independently observed box is bx_t75wty3s, UUID
1b2b5ee9-c058-47a4-9615-801ac71ac169. Its immutable 25-minute watchdog was armed
and independently observed before create; original API expiry was
2026-11-10T00:28:06.992Z, watchdog deadline 00:28:07.717847Z. After both native
process trees settled, 153 artifacts / 135 unique artifacts (3,659,790 bytes) were
independently retrieved, reread and SHA/size verified; a second remote inventory
matched unchanged BEFORE exactly one delegated normal unforced stop.
Final independently reread state: ARCHIVED, expiry null; receipt
stop_e77b60790eabf838, completed unforced at 00:09:39.068Z. Watchdog actual wait
is 0 with separate stdout/stderr EOFs. The outer allocation tool wrapper returned
143 without its own wait record; its truncated stdout gzip and recovered complete
JSON prefix are both preserved, explicitly separate from the watchdog's actual
wait. No live owned box remains. /home stayed above 5GB free.
Next: a separately authorized diagnosis of the original menu click's application effect before any further arena attempt. This task stops here and releases its files; it does not retry the original or reinterpret the historical visual STOP.