Original owning readiness and natural Draw

One fresh original boot passed the repaired owning-worker selection, reached GIsRunning=1, and observed the complete natural Draw checkpoint return pair. The recovered owning raw surface is entirely zero. Personally reviewed PNGs show a black host game area and a mostly black surface with a small blue fragment at its upper-right. These are diagnostic captures, not verified gameplay. Object lifetime and viewport-to-host binding remain unknown; no FPS claim follows.

Evidence: scratch/runs/20261104-deusex-owning-original-native/. The driver is unchanged from bc7555e5629c30c40779d1e1c33db36c9f92e55a; see owning readiness repair. No shared production, adapter, driver or test file was edited for this attempt.

Exact inputs and admission

Assigned box bx_sc8tbhpz was live, healthy and hydrated, forked by the coordinator from the stopped/snapshot-verified bx_t2kna5qz. The old attempt was not resumed. API-key policy denied SSH (api_key_action_forbidden); the existing exec/file transport provided actual remote process and filesystem verification instead. Only two small published driver files and run-specific supervisor inputs were staged. No source, module or media tree was copied or rebuilt.

All 489 inherited input pins matched. In particular, the ordered adapter remains 9,057 bytes / c33adc61c76406e896e9a0cb2dc373fdffd4c3c330ed758121bc48a63b017092, recoverable from Git 36661cb71b738cf08d91ad51edf55e97084423af. The inherited six-file production reconstruction patch and exact source pins remain the recovery recipe recorded by the preceding natural run. The newer shared adapter 835d15be… was never substituted or repinned.

The entry's --check and --preflight verified prepared original driver fcfe9b91543e28046fe098b703458ea820471d6757e9280881224b0c6753bb21, unchanged inspector and all 20 original helpers. Retained local gzip reports were read without rewriting them. All twelve original prerequisites passed again, including real Puppeteer 25.7.0 CJS/ESM imports, executable access, original integration, queued transport, optional/pixel boundaries, replay, composition, HTTP script graph and repeated input/served-module checks. Actual HTTP responses retained COOP same-origin, COEP require-corp, and Cache-Control: no-store.

Actual served module Bytes SHA-256
normal 2,147,323 4417305d70322467441aef51e888b0fe66451d9c60da0c734eeb23f5a22c0a6b
compatible 2,149,936 07fb4e75d05177271097dcd67d84e2629272b50073074bbdea8825ce10b4ed34

The historical 4ddc8336… / d4c5171a… modules were unused. The actual browser entry received DEUSEX_CLOSE_AT=2026-11-04T16:17:00Z; the full original eight-minute maximum plus the five-minute recovery reserve fit before launch. Its earlier relative deadline was 16:08:42.159Z. Original first-fault/readiness/Draw limits, per-source caps and raw-before-PNG order were unchanged. Prior generated outputs and profile were moved intact to a separate closed-prior directory; the sole browser used a fresh profile and no old log stream was resumed.

Natural result and pixel limits

Chrome 151.0.7922.108 launched at 16:00:44.976Z, PID 14450, driver PID 14442. The original executable path matched. The preinstalled selection gate waited for actual initialization, bound the page's WorkerLink/module/memory/endpoint/slot to its uniquely marked browser Worker, checked provenance, then ran the unchanged inspector. Foreign targets received no guest evaluation by this gate. The exact marked target/session strings were not separately emitted as an evidence file; their equality checks are in the pinned executed driver. Readiness and subsequent queued responses record slot 0, endpoint 1, thread 1.

At 16:01:06.483Z the original readiness predicate passed: native flag 1 and a visible 640×480 source-bearing window, HWND 65539. The single original queued Draw interval ended naturally after 23,952.87 ms / 993,084 charged blocks, with status render-route-return-candidate-unverified-lifetime. Entry, lock call, lock, unlock call, unlock, tail call, tail, epilogue and saved caller were all observed; observedReturnPair=true. It observed one MainLoop Tick return. These observations do not establish object lifetime, scene authority or playability.

The unlock identity's pixelsWa=475484160, HWND 65539 and 640×480×16-bit layout match recovered raw-surface-4.bin: 614,400 bytes, SHA-256 34c69899504b36f13e8b22120cf0fd894e61fcd6b046fb8535b79cc491fa3b3f. All 307,200 raw RGB565 pixels are zero. The later surface PNG differs at 714 pixels and contains the tiny blue upper-right fragment. Thus neither atomic frame equality nor a completed viewport-to-host presentation is established. Both actual PNGs were personally viewed. No gameplay gesture, configuration write, reload, retry or second collector interval was introduced.

The once-only production cache option retained limits of 1,000,000 boundaries, 256 records and 10,000 ms per source. Core hash 2de35e0b4cf498e3587c76c0d0d332e5c29e1915986a79fa1521d8124a4c6167 bound before execution at row 1 / base 281845760 / size 1802240 / generation 1. SoftDrv hash 25d14f3b6cca27053aa05b191424f4c0c0dffe0837406b44eb606cb9d8aeae18 bound at row 4 / base 289816576 / size 757760 / generation 1. Both source reports ended at boundary-limit, sequence 1,000,000, with 501,290 duplicate boundaries and zero operation records. Final binding status is explicit-stop, with 996,625 observed public runs. History remains unknown: capped zero records prove neither complete cache history nor absence of internal WAT activity. The separate unverified-media event was not adopted as Core or SoftDrv.

Recovery and next prerequisite

The single invocation exited 0; Chrome closed normally at 16:01:32.290Z. Both driver/browser PIDs were absent, no Chrome remained, and HTTP 8123 and CDP 38139 were closed. Recovery verified full SHA-256 and size for 355 files / 14,732,602 bytes; a second complete inventory matched. Unique logs, raw captures, PNGs and closed-profile evidence were recovered. Existing exact helpers, media and modules are referenced by path/hash. Git SHA, relevant binary diff and small input/implementation patches preserve recovery without source snapshots or tars. Local inspection rechecked every recovered file, all raw hashes, checkpoint coverage, raw/Draw address identity and the stable inventories.

Custody returned at 16:02:51Z: bx_sc8tbhpz RUNNING (API idle), healthy, hydrated, expiry 16:34:32.047Z. No box access follows that handback. The coordinator exclusively owns snapshot/shutdown; assigned close/recovery/stop milestones remain 16:17Z / 16:22Z / 16:27Z. No public deployment occurred.

Next work is to qualify why the natural owning raw frame is black and how its viewport storage reaches the displayed surface, using the recovered observations before any separately authorized fresh runtime. This closed attempt must not be resumed. No verified gameplay screenshot has yet been obtained.