Current native scene and fresh prearm repair

Evidence: scratch/runs/20261115-gta2-current-scene-prearm-repair/. This document describes the implementation and publication checkpoint. The run's compact result.json records subsequent final-revision qualification, any first blocker, original-game authorization, and sealed closure.

Scene diagnosis

The preserved predecessor final-head-main-memfd/control/first-modal.png, SHA-256 99a7452e192345a310ed68c0d3b4a4ac562a43d4ef3f44d8dc6dbf6c5c7d50f9, is visibly nonblank when opened directly. An independent PNG decoder checks CRCs and all five row filters. Literal raw samples identify teal desktop, white main client, gray modal client and the caption gradient. Two initially incorrect sample locations and their failures remain in evidence. The prior empty-root-image observation does not establish blank native pixels, a paint bug, or the historical 500 ms UNKNOWN cause. That endpoint stays closed.

The new authored PE uses ordinary public GDI: UpdateWindow, GetDC, CreateSolidBrush, FillRect, GetPixel, ReleaseDC, DeleteObject and SetWindowTextA. It paints one literal swatch below the modal and publishes the actual GetPixel return in the visible title. Current genuine-native main and Worker runs return 0035A7E1. Independently read backing, logical, displayed and full PNG pixels equal RGB (225,167,53), with one visible display owner, matching context/canvas ownership, DPR 1 and physical UP. Twenty-eight independent decoder/publication controls cover malformed pixels/CRC, all row filters, occlusion/publication ownership and mismatched public API return. These are authored diagnostics, never a repaint intervention in an original.

The first current fixture failed before a scene: genuine COMCTL32's synchronous DllMain needed its genuine COMMCTRL NE companion resident. The corrected fixture installs COMMCTRL through the ordinary required-file manifest at C:\\commctrl.dll, including its required byte size. COMCTL32 remains the only PE seed; COMMCTRL loads through its native installed-name NE path. COMCTL32 SHA-256 is 28a41e6a35c4509924a32a99841a815cf49e1d3ee6912ec26a823e45472edfa4; COMMCTRL is 39bbfafa8b759ebfcf6a00ee878fa494581a9144891bbd788bded61441de13f9. The first missing-size correction failed and is preserved. An omitted committed font JSON also correctly failed the audit view, then was included.

Current source and physical-input path

The binding now requires the actual injected page body. Both main and Worker paths inventory the page; Worker additionally inventories the actual owning CPU and applicable render target. The old Worker omission became an observed refusal once the page-body flag was made strict. Unknown executed HTTP scripts refuse instead of being ignored. Every gesture gets new debugger sessions, current script/context identities, actual module wire bytes, process PID/start identity, owning context/endpoint/backend/epoch, native HWND generations and focus, current review nonce and physical-UP observations.

Actual WineAssembly function bytes are freshly SHA-256 hashed inside the page and compared against the exact current host class. Original physical handler bodies and injected guard bodies remain separately verified. This avoids a second large host-body transfer without accepting a retained body digest. Fresh independent owner/native observations overlap source/module transfers; both before/after owner checks remain required. Full current file pins and PID identities are checked before arming and before physical DOWN.

After arm, the independent child must confirm a new one-use token against its still-current executed-source inventory and the actual page/native scene. The original physical DOWN handler cannot consume without that token. Source, context, module, focus, owner, handler or native HWND changes invalidate it. EOF/cancellation before confirmation produces UNSENT without sending cleanup input; an already confirmed gesture retains the independent finite UP path. A permanent UNKNOWN allows zero subsequent protocol requests, input, rebinding or replay. Test-only additional reads after refusal exist solely in models to prove they cause no native reads/effects.

Chrome 151 rejects Debugger.setScriptSource as unavailable. The authored source-fault control records that result and executes a distinctly authored additional script under the actual pinned HTTP URL instead. Its new source identity is observed and refuses after arm before DOWN. This is evidence of additional executed-source invalidation, not successful live editing.

Initialization and audit timing

One child/transport is initialized for one gesture. It compiles both helpers from the very buffers whose SHA-256 digests it reports, and those digests must match the current pins. Reading a file after require() would not prove the bytes that Node compiled. Initialization retains no source inventory, module bytes, native observations, review or prior input authorization. The child then accepts one configuration and performs all current guards anew within 500 ms. Runtime/transport setup is reported separately. The aggregate three seconds begins before initialization; UP is due within 1750 ms and each actual hold must stay 80–1400 ms. No deadline or required observation was removed.

The run-local audit loader constructs a committed Git blob manifest before runtime, checks object IDs, and places it in a write/grow/shrink sealed memfd. Each child verifies that immutable pool. Owned source is excluded and always read fresh. Runtime reads and explicit HTTP text responses select the same source view; unrepresented tracked runtime source refuses. No per-import Git process runs during timed guards, and no source tree is archived. Four authored view controls cover exact module/sync/callback/promise bytes, altered blobs, altered HEAD, omitted tracked source, sealed writes, and fresh mutable reads. Audit speed is not production-game performance.

Evidence boundaries at publication

Both ordered source/build/runtime releases were personally verified before taking the lane: corrected GL release aa5ae2f8035f9683e07cd924d0a1b280d2a8b194f4a69508964f5bde36084f7b (679 indexed hashes, 155 waits with both EOFs, 509 absent PID/groups), and Sims release 1cabc869cb1737af7556187a06ed51398b098848a6c2ac5e5828cd8e362b3970 (2,657 current hashes, 540 such waits, 555 absent PID/groups). Both locks were free. Foreign WIP is preserved and excluded from committed-HEAD audit source.

Intermediate unpublished main and Worker runs each completed both visible modals, public DOWN=1/UP=3, the released native scene and actual native ExitProcess. Main current confirmations took 304/394/307/307 ms; Worker took 240/443/298/252 ms. Their separate initialization and actual finite holds are recorded. Each gesture independently recovered 2,220,339 module bytes on main and 4,440,678 on page+Worker. These are intermediate passes, not final source qualification. Earlier 500 ms UNKNOWN endpoints remain closed with no retry.

Source-after-arm, focus, context, module, duplicate arm and post-arm rebinding controls have refused before physical DOWN. Exact-byte initialization controls cover EOF, changed source pin, changed PID start and real aggregate deadline with zero CDP observation/input requests. Independent source/body, native ABI, physical input, source guards and both shared and HEAD+whole-owned locked builds are required before publication. The final published revision still needs its own complete native main+Worker and refusal-matrix evidence before an original is authorized. No model or fresh endpoint repairs an older UNKNOWN endpoint.

Original runs remain conditional on those complete current guards. Only one ordinary registered GTA2 software run may then use the genuine 71-file media set, unchanged real ticks/defaults, 900 native seconds, 920 independent watchdog seconds and irreversible final 180-second native Quit reserve. Software SUCCESS plus closure alone permits a separate bounded WebGL run. The first causal failure ends that pair. No private-game reads, OCR, solver, tracking, autoaction queue, cheats or clock/config/physics edits are permitted. Native Quit is distinct from host stop. Historical DMusic exact original API return remains UNOBSERVED and FT target invocation remains UNPROVED.

Git SHA plus binary diffs preserve relevant source and owned new files; only small inputs and selected logs/screenshots/pins/closure belong in the ignored run. No agents, workers or boxes are launched. Box ID/expiry are null, state NOT_CREATED, stop receipt NOT_APPLICABLE.

Published-revision first blocker

Implementation commit 9005ce1b84dde2611fed0c747ba30f7e1e8c21fb was published with strict pull/push. Both shared and committed-HEAD+whole-owned locked builds passed. The current pixel/source/confirmation/input/protocol tests passed, as did FT relay, LS32, ThunkConnect16, Win4 DllEntryPoint, Win16 brush and native Quit ABI checks. One repeated shared ABI compile refused its already-existing output filename; the preceding shared compile and full HEAD compile passed. The initial authored loopback preinit test failed because its server did not acknowledge WebSocket close. Its child receipt was not persisted, so that child identity remains UNKNOWN in evidence; it is not counted as native closure. The corrected receipt-first server controls passed, including real 3-second initialization expiry with zero CDP observation/input messages.

final-main exercised that exact published revision. The first three freshly reviewed gestures confirmed all current gates at 198, 254 and 350 ms, with separate initialization of 99, 113 and 121 ms. Both visible native modals and public DOWN=1/UP=3 were observed. The fourth, intended Escape, failed before arming or physical DOWN. The fresh module request began at 181 ms and returned at 481 ms; byte verification completed at 491 ms. Source completion was 497 ms, final file-pin checking began at 498 ms and finished at 545 ms. The 500 ms guard refused, permanently closing that endpoint. No Escape DOWN or native Quit occurred on the published run, and no subsequent protocol request was sent. A local terminal-diagnostic command file was mistakenly written after the failed receipt lookup; the closed process never consumed it. That file and the zero-later-request proof are preserved rather than silently removed.

This is the first remaining concrete blocker: the complete actual current source/module/pin path does not consistently fit the mandatory 500 ms guard. It is not a proven explanation of the predecessor's historical UNKNOWN. Final Worker qualification and the full final-revision refusal matrix were not reached; intermediate passes do not qualify them. No original software or WebGL run was authorized or launched, and original gameplay/native Quit remain unobserved. A future repair needs a complete qualifying path, or independently proven immutable identity reuse with all required invalidations and a fresh native lease. This task does not introduce such reuse or waive the guard.