Original GLTron direct capture review and live interval — 2026-11-04

Run: scratch/runs/20261104-gltron-direct-view-live-interval/. Input: e9c76cecec8caa6c75c4e505ecddf25569f5921f and gltron-live-gameplay-interval-20261104.md. Old evidence remains unchanged.

Before Chrome, exercise the actual command queue, shot producer and successful ACK client, then VIEW the ACK's exact path in the same tool invocation. The offline image is explicitly a replay of the predecessor's real startup PNG, not a new screenshot or gameplay observation. Its source and SHA are recorded. The live operator uses this same command client and image relay.

Require the fresh MDK2 demand-entry-continuity explicit local release. One external /tmp/wine-local-runtime.lock covers software then WebGL, one launch each, stopping the entire pair at the first fault. Limits remain 360 combined browser seconds, 60 bootstrap, 60 per command, 180 cleanup; absolute Chrome 23:30Z and cleanup 23:33Z with full reserve. No separate diagnostic Chrome.

Personally VIEW startup, Game menu and paused arena before their dependent ordinary Return. After reviewing the arena, ordinary Return unpauses and starts a read-only, bounded trail/wall ray observer sending balanced native A/S when the forward distance is below 90 arena units, preferring the clearer side. It reads original Game/Player/Data/trails without writes and runs during capture, review and measurement. Input is rate limited to one turn per 300 ms; it does not guarantee survival against moving opponents or between slices.

The original source's PLAYER_IS_ACTIVE requires positive player speed. Pinned executable initData at 0x403229 sets Game.pauseflag at +12 to 1; doCrashPlayer at 0x4033ee follows Game at 0x43d224, Player stride 12, Data pointer +4, and writes speed at Data+8. The hash and exact bytes are checked. Each pre-arm/interval observation now requires four players, winner -1, pauseflag 1 and finite positive player-one speed, with translated reads retained and round/data identity preserved. Matching callbacks alone is insufficient. Crash/finished and missing-liveness negatives reject without arming, including both real compiled modules. These are offline fixtures.

After a fresh personally VIEWed live capture, immediately arm the unchanged production 0x4051a9 entered nonzero-dt lifetime counter, pace zero. The exact named capture must be at most five seconds old, with matching generation and active table; all owner/main-thread/tier/visibility/frozen/foreign-counter, monotonic brackets/reset/wrap and minimum-five-second guards remain required. The after image returns through the same ACK relay. A numerical interval is pending until its after image is personally reviewed as live gameplay.

Capture the exact first fault and owner context, stop both backends, close only owned Chrome through normal Browser.close, and verify PID/start/actual zero exit, Node/server/ports/flock closure. No guest code/state/config/pacing, freeze or host-step edits. Git SHA and relevant binary/new-file patches are the source archive; existing media/modules are referenced by path and SHA. Box ID/state/expiry N/A; coordinator owns future boxes and shutdown.

Bounded original outcome

Fresh mdk2-demand-entry LOCAL HEAVY RELEASE arrived at 20:10:41Z. Before Chrome, 69 focused checks passed, both modules executed the original branch under all four tiers with translated rejection guards, 50 production marker checks passed per module, and the locked full build passed. Preflight recorded Git 86dc176a3b25a1eda252d1f4b83a1e30a8bb417b, relevant binary patch and owned new-note patch, 654 pins, all 92 original media, 365 prior HTTP records and 1,010 offline HTTP resolutions. The predecessor's 81-file seal, 2,414,951 bytes, is unchanged. No media/modules/source snapshots were made.

One software Chrome started at 20:14:29.612Z. Personally VIEWed startup, Game submenu and paused arena before the respective ordinary Return actions. gameplay-before.png was returned in the command ACK and VIEWed in that same tool invocation: yellow cycle, blue grid, new trail, no pause message. The immediately subsequent tool invocation submitted measure without an extra ACK-only or image-path turn. Nevertheless capture-start-to-arm was 10,566.935000181198 ms, above 5,000. The runner rejected STALE_GAMEPLAY_REVIEW at approximately 20:15:08.145Z, before arming. The pre-Chrome rehearsal had tested ACK-to-VIEW composition but had omitted timing the subsequent reviewed action. That omission is repaired below.

Exact rejection: callbacks 0x42a200, read from guest 0x42b230 translated to offset 250416; generation 1, main thread 1, chain 0, uop 1, tier guard 0, marker 0, lifetime count 0 and pace 0. The actual module was canonical 78a0b1d61b23428a1ae909d739440ae0de059bbbd84a69a2ad3e4c37471ad664. The matching owning Bridge/OpenGLHostBridge held software context 1, software: true, gl_sw_enabled() == 1, with no WebGL context observed. Frozen was false and host steps zero. All 234 served responses matched pins, including all 92 media. No physical GPU performance was measured.

Unlike the predecessor's crash, this run retained a live player through the rejection. The maintenance observer sent two balanced trusted native S keys to screen, at 20:15:01.077Z and 20:15:04.681Z. Direction changed 3 → 0 → 1, trailOffset 0 → 1 → 2; the rejected owning snapshot records speed 8.5, winner -1, pauseflag 1, and the exact original translated player/data chain. Personally VIEWed counter-rejected.png: yellow driving cycle, continuous trail, bent yellow minimap path and no crash/pause banner. This is a rejection capture, not an after-interval review. No counter interval, software rate, WebGL launch/rate or paired comparison exists. The pair stopped at first fault.

Tested offline repair after the fault

The actual old producer passes a dead player with matching callbacks; the new pre-arm and interval liveness guards reject dead/zero/NaN speed, finished pause/winner states and replacement rounds. Both compiled modules execute the new dead-player rejection with original translations and released markers. Native steering geometry and balanced key release on failure are tested. The actual queue/shot/ACK composition rejects foreign paths and failed ACKs.

The missing dependency was the complete capture → VIEW → reviewed action latency, not just capture → ACK → VIEW connectivity. The runner now requires a fresh successful offline review-only rehearsal before any Chrome launch. The shot producer records host capture-start epoch conservatively before the page evaluation, alongside the original page monotonic epoch. The reviewed action verifies exact path/name/hash and a nonnegative age at most 5,000 ms; failure is recorded and cannot qualify the pre-Chrome gate. A stale live measure is also refused before queueing a guest command. The authoritative browser monotonic guard and all original acceptance guards remain unchanged. Machine-only positive/negative fixtures do not count as personal review.

After the fault, the actual offline historical-image relay was VIEWed in one tool invocation; the next invocation used the actual review-only client. It passed at 4,597 ms. The real pre-Chrome gate accepted that exact proof offline. This establishes a possible operator handoff within the deadline; it does not guarantee future latency under browser load, original survival, or any measurement. No original/backend retry followed. The small margin is explicit; future attempts must repeat the complete rehearsal and still pass the live five-second guard. Remaining dependency: a separately authorized original with both timely reviews and a valid guarded interval of at least five seconds. Count-marker, read/steering/observer and tier overhead remain included in any future measured rate; no overhead percentage is established.

Closure and publication

Normal direct Browser.close was requested at 20:15:08.600Z. Chrome PID 1061895, start ticks 187047886, actually exited 0 with signal null at 20:15:08.764Z. Node PID 1061882, start ticks 187047837, and wrapper exited 0; both exact PIDs and profile-matching Chrome processes are absent. HTTP 37749 and DevTools 42501 refused connections, server was not listening, the correct local flock was free, and the owned profile was removed after those checks. Total Chrome lifetime including closure: 39,152 ms. Explicit local heavy release posted at 20:16:15Z. No signals or foreign process termination.

Final validation: 71 focused checks including both compiled modules, all four original-branch tiers and executable scene/liveness negatives; 50 production marker checks per module; final locked full build, syntax and diff checks pass. Publication SHA is recorded in the run's publication record and append-only messageboard. Box ID/state/expiry N/A; coordinator owns future boxes and shutdown. Stop after publication/release.