Nox instantiated module admission and first click consumption
The repaired instantiated-module admission succeeded in the one authorized original native observation. Gameplay stopped at the first mouse nonresponse. Multiplay, Jack and bunker staff were not reached. No second native attempt was made.
Evidence: scratch/runs/20261110-nox-instantiated-cursor-gameplay-0234/.
The original ran with published b80751e74 and 3605b177f, plus the published
CRT revision e7e0312bd. 9deab9f96 adds the real Worker offline controls.
git-base.txt, owned.patch, repaired-base.txt, repaired.patch, and the
explicit plans retain exact Git recovery. Git is the source archive; no source
archives or media copies were added to evidence. Q3, LBreakout and shared
providers remained read-only. The accepted fixture 682f77655 and readiness
repair bce2b316f were reused unchanged, without a native preflight rerun.
One observation
The emitted original URL selected nox_demo, threads and WebGL. Production
primary module SHA-256 was
4f2c69a1528e01a9ab5127201d5e8a222da2a35236377a1351f444f55fa5a7d9,
2,186,099 bytes; compatibility was
5bf29fae3d0c6918df98973ef29297a77a81df0e0b0a917b8adac8bec256df69,
2,188,745 bytes. The actual installed observation instance was
716d28c256b2d204e83a3e73a3bcd843e1afab9d62c957f868b762faacef19f5,
2,186,872 bytes. Both canonical and observation modules were compiled in the
Worker; admission selected and reread the installed observation instance.
Each of the three images was inspected individually. Startup showed the
original copyright/title splash. Ordinary Escape input produced a main menu
with a Really Quit dialog. A click on its visible No button returned a transport
ACK, but the next image retained the dialog. Owning custody SIGTERM was the
next action after reviewing that nonresponse, at 02:41:59.660Z. There was no
later game protocol, input, capture, retry, quit or extension.
consumption-analysis.json binds the click to the prior image and actual
Worker identity. The click interval contains 751 records: 228 natural original
CALL/entry/return triplets, 33 DirectInput entry/return pairs and one command
begin. All 33 GetDeviceData returns succeeded on the acquired relative mouse
device. Exactly two returned data: offset 12, value 128, followed by offset 12,
value 0. These are the original button press and release, with original record
consumer entry and return observed. There were no returned X/Y axis records.
The original cursor remained (0,0), including both cursor-update triplets.
All 32 GUI hit-test CALL/entry/return triplets used (0,0) arguments. FIFO
drain alone is no longer the only evidence: original consumption was observed,
but it did not target the requested button.
The page observer independently shows the first absolute move changing the
renderer reference from null to (351,295) without advancing the axis FIFO.
The production handleMouseMove path in lib/renderer-input.js computes
relative axes only when a previous reference exists. Both button records were
subsequently queued and consumed. This proves the missing initial relative
motion at the input boundary; it does not establish any later gameplay.
Same-worker offline repair and controls
The Nox observation route now returns the read-only original cursor with its
command arming receipt. Before click, double-click or drag dispatch, the route
requires the renderer reference to equal that cursor. Missing or unequal
references refuse before native input. This prevents the proven invalid first
click without inserting hidden pointer motion or changing shared providers.
Move commands remain available for separately reviewed physical anchoring.
The guard has offline validation only and is published as befbafc5b.
The real Worker control executes the actual emitted attached-Worker handler
and installer over a Worker message transport, validates the emitted original
launch URL, runs actual WineAssembly.init, compiles the canonical module,
installs the observation instance, verifies its identity and exercises sticky
first-failure behavior. Compiled fixtures exercise natural CALL/entry/RET and
GetDeviceData/GetDeviceState returns. All eighteen owner binding mutations
refuse. Ten emitted move/click controls include success, wrong binding,
incomplete calls, first failure, missing reference and desynchronized reference.
Refused clicks produce zero input or capture and reject a later command.
The production pointer observer's three controls pass, now explicitly reproducing first absolute movement returning only buttons with no axes. The real automatic-cancel fork/wait control passes with separate stdout/stderr EOF. Locked builds pass. The original legacy driver sweep encountered stale source pins after the offline guard changed its closure; its evidence is retained. The final driver sweep uses a newly generated closure and all 27 controls pass, including exact source/module/media refusals, startup failures, held input, first-failure terminal behavior and capture-label admission.
No live guest state or clock stores, artificial guest handler calls, deadline changes, local Chrome or nested workers were used.
Lifecycle
Only bx_qjsbp62a was created, UUID
f1f2de0d-3994-4c8a-b3ea-6791ce0caf00. Its independent watchdog was armed
before allocation with an immutable deadline of 2026-11-10T03:04:32.494Z;
initial API expiry was 03:04:33.786Z. Custody reaped all 334 owned descendants
with complete kernel fork lineage, actual parent return 1 and separate stdout
and stderr EOF. Owned processes and ports were absent before final retrieval.
After retrieval exited, independent rereads verified 64 references, 59 unique
contents, 23,443,512 bytes, four finalized gzip streams, and three PNGs including
chunk CRCs, inflation and scanline bounds. Only then did the sole delegated
watchdog request unforced normal stop. Receipt stop_07f09657a63480a1 completed
at 02:42:48.841Z. Independent API and receipt lookups confirm archived/stopped,
expiry null and forced false. The watchdog supervisor actually waited, return
0, with separate stdout/stderr EOF. Both watchdog processes are absent. No
box was resumed or deleted; preexisting boxes were untouched. Home free space
remained above 1.5 GB.
Next work needs a separately authorized original observation after a reviewed physical pointer anchoring sequence, or an explicitly scoped shared input provider repair. The remaining gameplay target is still Multiplay -> Jack -> bunker staff. This task releases its files and stops.