Q3 plain review and native Enter
Evidence: scratch/runs/20261110-q3-plain-review-native-enter-0035/.
Implementation/test commit: c26ca83c5, immediately published on main with strict
SSH. The retained API receives plain review text and constructs its own
capture-bound object. No production guards, shared providers or Nox files changed.
Before allocation, the actual freshly generated controller launch function read the exact command/review JSON from a live pipe, invoked the real Session.request and retained owned_command, and emitted the exact publication program. External launch/cancellation and transport services were inert offline seams. The program then ran through the actual generated consumer command body, observer binding, admission seam, native key helpers, production DOM bridge, renderer and host input. Enter150ms plus 1000ms settling and the exact plain review string pass; these controlled services do not establish native guest execution. The existing three pointer modes, Enter50ms, malformed nested review and inactive-observer refusals also pass. Current foreign closure's 27 refusals, input phase service controls and locked build pass. The ordinary offline fresh-directory and output path adapter errors were corrected in this task, before allocation; their logs remain. The accepted fixture/physical/cancellation chain was hash-verified and reused, with no fixture launch or visual reacceptance.
One original started with the bounded passive observer prearmed. The separately
inspected startup PNG clearly shows the original main menu, Single Player
highlighted, SHA 071e67af263b2d4eb65a3e9b186648d5c15a8569e1da99fb13e9568f1db06968.
The existing chain authenticates both CPU and renderer module SHA
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18.
The corrected plain review invocation reached native input. Two native CDP key
requests and trusted DOM keydown/keyup for Enter13 are recorded. Renderer entry
and return and host dequeues of WM_KEYDOWN, WM_CHAR and WM_KEYUP are observed.
Host dequeue does not prove guest UI consumption.
The first live failure, at 00:37:06.130Z, is Q3 image owner mismatch in the
observer's result-image binding. The capture identity contains mutable slice
telemetry: the startup and result identity objects differ only at slice.
The observer compares the entire objects. This is the concrete failed check;
there is no claim that a process/module replacement occurred. The offline
controlled identity was constant and did not expose this case. No guard was
changed after the live failure and no second run was attempted.
The already-written result PNG was recovered after cancellation, hash-verified
and separately inspected offline. SHA:
f307cdf0f37f214948dc2dc86b6e4e2e385467190cd36c923ebaa9e139810e4b.
It remains a clear main menu with Single Player highlighted. It establishes no
arena, movement or firing, and no cause for the lack of a visible menu transition.
No dependent action was issued. There were zero CDP requests after the first
failure, no later input/capture/retry/quit/extension. Prearmed console records
preserve the causal limits.
Owning native cancellation completed immediately through the retained failure path: native exit -15, complete kernel drain, no unreaped children. Generated, prelaunch and runtime parents have actual waits with separate stdout/stderr EOFs. The local controller and outer parent also waited with separate EOFs. The launch transport child required local kill (-9); remote containment is established by the kernel drain and remote waits, separately from that local receipt.
Box bx_cdgs7a2v, UUID cbeb25e9-844d-4129-99f5-ea0ba117732a, had an
independently observable immutable watchdog deadline of 01:00:20.393Z, initial
API expiry 01:00:19.743Z. All 79 settled artifacts / 74 unique artifacts
(1,671,396 bytes) were independently retrieved and SHA/size verified. A second
remote inventory matched before exactly one delegated normal stop. Final root
API reread: ARCHIVED, expiry null, receipt stop_bf1e475ec1862cc7, completed
unforced at 00:37:39.667Z. Watchdog and allocation parent actual waits are zero,
with separate EOFs. No owned live box remains; /home stayed above 5GB free.
Exact Git and small patches are retained; no source/media archive, local Chrome
or nested workers were used.
Next work must address the observed full-identity comparison versus changing slice telemetry offline, preserving genuine owner/module replacement refusals, before any separately authorized live attempt. Guest menu consumption remains unestablished. This task stops and releases its files.