TR2 presenter-getter native observation — 2026-11-08

The sole fresh native run still produced no qualified DX display joins. The first new production integration repair addresses the compositor's no-menu query invalidating its own pending sources. The new branch fixture fails with qualified0 before this repair and qualifies1 with an actual red RGB565 display pixel afterward. This is a branch-specific repair, not a claim that the entire compositor export facade now qualifies. No in-game movement or weapon input was sent.

Evidence: scratch/runs/20261108-tr2-presenter-getter-native/.

Exact native closure and observation

The native source commit was dbcee2b50a466b0abb62cf9c934fc8f94210b4e8. All 595 individual providers were checked before allocation. Published lib/host-imports.js and lib/render-worker.js exactly match 9c93a0f13, and lib/d3d-render-worker.js includes 2483eec51. Only the two getter-repair files differ from the preceding accepted runtime. Eight HTTP pins, helper syntax/dependencies and existing media paths/hashes were retained and checked. 190 accepted evidence references were independently reread; accepted controls, the prior decoder/compositor baseline and prior locked build were reused without standalone reruns. No peer WIP or older Git fallback entered runtime.

The independent observable 25-minute watchdog was armed before the sole UUID-idempotent box creation. Box bx_rbx878gk was identified idle before startup. Free disk was 12 GB. The accepted subreaper custodian held its own remote runtime lock before browser startup through descendant drain. The local runtime lock was never held during remote provisioning, supervision, retrieval or analysis.

All six blank-page trusted 500 ms key preflights passed. Graphics was reviewed with Hardware 3D Acceleration, Full Screen, 640x480 High Color and default focused OK. Enter admission age was 8,716 ms, below 12,000 ms; the independently released physical interval was 501 ms. The next capture shows Lara in Venice. The actual owning WebGL endpoint, CPU/render instance/module binding and full 4096 observation journal passed. The native module SHA-256 was 6cf120d0d3b3db1823a8105eb26ef52a9093a7f871c37a46117475e213fda1c0.

Before arming, raw was null/unobserved. Retirement gives **69 raw = 0 qualified

First new branch and repair

The preceding integration fixture observed the decoder exports but supplied a raw native instance to renderer windows. A diagnostic with the observed compositor instance reproduced qualified0 and identified menu_bar_count as the first call advancing the host version. The complete diagnostic remains in baseline-compositor-exports.log. It also found later conservative transitions from window-style and screen-coordinate exports; those remain unresolved.

menu_bar_count reads the menu blob pointer before translating any nonzero blob through g2w. Translation can materialize lazy storage, so treating the entire export as read-only would be unsound. A zero item count also does not prove that no translation occurred: an allocated empty menu has a nonzero blob pointer.

src/09c5-menu.wat now exposes get_menu_bar_blob_guest, which only reads the window/menu metadata and never translates a guest pointer. Within the existing writer ticket, lib/render-worker.js returns zero directly for an absent blob. A nonzero blob still invalidates host versions before calling the original counter, including an empty allocated menu. Modules without the branch query retain the original conservative behavior. Metadata/count exceptions poison the epoch. The window lookup's hint globals are instance-local; no guest or shared canonical bytes are written by the metadata query.

No page/version equality, writer exclusion, poison, source/request/owner or composition condition was relaxed. Nonzero gamma translation and arbitrary standalone mutators retain their previous invalidation behavior.

The extended directx-layer fixture isolates this first compositor branch while preserving the other scene exports' earlier fixture behavior. Actual WAT, dispatcher/swap, native RGB565 decode and compositor yield baseline0, corrected1 and the red display pixel. All 20 refusal variants also pass with this branch observed. Additional real-WAT checks cover an existing window without a menu, an absent window, an allocated empty blob and a populated blob. Legacy-module, exclusion and metadata/count exception guards pass. The initial full-facade diagnostic failure is retained rather than reclassified as success.

All seven focused tests passed after this production change. The required flock /tmp/wine-build.lock bash tools/build.sh passed. Callback census review and check passed. The changed local module is retained by its SHA-256, d8facd0658b7f158c6e60bef2de0936471f438f8bf41e9240fd75635f1d319dc. It was not run against the original game. Local runtime locking covered only the local focused execution and was released before analysis.

Custody, recovery and next step

All 78 remote artifact references (9,924,432 bytes, 71 unique hashes) were retrieved and independently reread for size/SHA-256 before normal shutdown. Four PNGs passed chunk CRC validation. The drain checked all 30 recorded parent/descendant/custodian PID/start identities absent, subreaper completion, launcher absence, closed HTTP/DevTools ports, absent profile/writer, released input and remote lock release. No descendant exception was accepted. The normal/watchdog delegates exited and the supervisor has no children.

Normal stop stop_bb68018e16c68f7f completed at 11:48:31.484 UTC, forced=false, error=null. Final box bx_rbx878gk is archived, stopped at 11:48:31.465 UTC, active expiry null (initial expiry 12:11:45.834 UTC).

Recovery uses exact Git SHA, relevant binary diff, small owned-file patches, existing media paths/hashes and unique modules/captures. No source archive, repeated media bundle, old-box resume, deployment or subworker was used.

Next, diagnose the remaining observed compositor calls with the retained cheap full-facade diagnostic before spending another original run. Screen-coordinate helpers really write scratch storage and can call host imports; do not blindly classify them as getters. Actual native qualified canonical/DX display joins remain required before reviewed Up/Space/Control. Full27, parity, audio, game FPS and simulation FPS remain open.