Q3 bound original input observation
Evidence: scratch/runs/20261110-q3-bound-menu-input-0015/.
The explicit q3-bound-input-v1 preparation option prearms a bounded, passive
page observer in the original runtime. Defaults remain inert. Shared input,
providers, guards and the Nox observer remain unchanged. There are no guest
hooks, guest calls or guest writes. The existing capture/admission chain still
authenticates the actual CPU/render modules; this observer does not infer a
guest UI decision from a host dequeue or shared FIFO head advance.
Records distinguish absolute, pending-relative and locked pointer modes, DOM trust/motion/keys, presentation/virtual cursor, production renderer entry/return, host event dequeues and shared DI drains. Command observations require the exact previous observed image SHA/identity. Result images require the command label and same identity. Owner replacement, deadline and record limits stop observation. Console records preserve the prearmed interval even if later input fails.
Focused controls execute the actual generated consumer, pre-navigation script,
capture body, native mouse/key delivery helpers, production DOM bridge, renderer
and host input. All three pointer modes and a 50ms Enter pulse pass. Inactive
observation refuses the generated command before dispatch. Controlled services
do not prove native guest/menu execution. Original ui.qvm is read in memory
from the pinned demo package: Enter 13 branches to instruction 35444 in its
default menu-key handler; this supports activation of the selected menu item.
The locked build and current foreign-closure, terminal-cleanup, readiness-wire and input-phase-service controls pass. The supplementary historical wire test refuses its retired admission pin; no provider was changed to satisfy it. An offline preparation initially refused altered authenticated caller bytes; the retained caller was restored exactly and fresh preparation passes.
Implementation commit: 7243910e1 on main, immediately published using strict
SSH. Exact Git, relevant patches and small run inputs are recorded; no source or
media archive was created. The already accepted crisp fixture and its
cancellation/physical prerequisites were reused with original SHA/size provenance,
without new fixture visual acceptance or a new fixture launch.
One original launched with the observer prearmed. The sole image was separately
model-reviewed: a clear main menu, Single Player highlighted. SHA-256:
c7ce3332bda47fd9bb06ffdfee62c721e74de1800eb27ceb302c2e9c05c0d28e.
The existing chain authenticated loaded CPU and render module SHA
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18.
Passive startup records establish pending-relative mode, focused canvas, virtual
cursor (319,239), released buttons, empty queue and zero DI counters. Backing is
640×480, rect (0,34,945,855); the aspect-fit presentation is retained. These are
this run's observations, not a reconstruction of the earlier failed click.
The first command requested native Enter, 150ms, then 1000ms settling. The worker
incorrectly supplied its capture/review object as the caller's review argument.
The retained publication caller expects plain review text and itself constructs
the capture-bound review object. The nested object caused
TypeError: review.review?.trim is not a function at 00:26:51.588Z, before
observer command binding, markDispatch, admission or native key dispatch.
The refusal is terminal. No Enter reached the game, no result image exists,
and original menu consumption, its previous failed-click cause, arena movement
and firing remain unestablished. This is an invocation error, not a guest defect.
The exact generated-consumer regression now seals this malformed-review refusal
with zero markDispatch and native sends; shared guards remain unchanged.
Owning native cancellation followed immediately. There were zero Input.*
requests and zero CDP requests after the terminal command failure, no capture,
retry, quit or extension. Kernel drain is complete, native exit -15, no remaining
or unreaped children; generated, prelaunch and runtime parents have actual waits
and separate stdout/stderr EOFs. The local controller also exited with an actual
wait and both EOFs. Its launch-transport child required local kill (-9); remote
custody is established separately by the retained kernel proof, not that receipt.
Box bx_tb4pwwu2, UUID c7fbdb60-166b-4350-b533-a471d8bd2805, had an
independently observed immutable 25-minute watchdog deadline of 00:49:22.141Z;
initial API expiry was 00:49:21.485Z. All 69 settled artifacts / 65 unique
artifacts (1,542,383 bytes) were independently retrieved and SHA/size verified;
a second remote inventory matched before exactly one delegated normal stop.
Final independently reread state: ARCHIVED, expiry null, unforced completed
receipt stop_3e7390a48863acdb at 00:27:42.854Z. Watchdog actual wait is 0 with
separate EOFs; allocation parent also waited with separate EOFs. No owned live
box remains. /home stayed above 5GB free. No nested workers or local Chrome.
Next requires a separately assigned original attempt using plain review text at the retained command API, with this observer already armed. No current native retry is authorized or performed. This single task stops and releases its files.