Nox passive pointer observer shipped; native fixture image rejected
Commit 7dcbcea5d525687a0676cafd09fa396afc38eb69 is published on main.
It finishes the explicitly transferred four-file observer work. The observer
is disabled by default, bounds its duration and record count, restores wrapped
methods/listeners, and only reads guest input state. It records DOM coordinates
and relative counts, lock state, canvas/presentation geometry, virtual cursor,
production renderer delivery, and actual DI FIFO head advances. A head advance
is consumption evidence, never a menu-decision or target-hit claim. Commands
and images carry prior image/hash/owner bindings, including capture-only
commands. No guest state, clock, callback, or acceptance condition is written.
The offline DOM adapter now faithfully removes window/document listeners. The generated-consumer test exposed and repaired capture-only images retaining the preceding command binding. Generation also tolerates a descendant main commit only when every pinned source/module/provenance byte remains identical; the reviewed Git recovery base remains explicit. Actual Q3 source changes correctly rejected a stale plan; that lane was left untouched and the remaining controls used a fresh plan.
Validation in scratch/runs/20261110-nox-listener-adapter-gameplay-0033/:
- Fresh default-observer-off generated-consumer suite: all 27 controls passed.
- Ten actual generated observer controls passed: the previously accepted 37-command route, failed 12-command route, five review/image binding faults, malformed label, and real 20-second mouse/capture nonresponses. Each generated output was independent and created at its actual relative depth. Both routes ACK in the peer, but their divergent tenth DOM destinations and complete command/image bindings are verified. Neither ACK proves guest acceptance.
- Separate generated command control passed all 12 image bindings.
- Three compiled production controls passed: absolute, pending-relative and locked-relative input, using the production browser bridge/renderer, generated native mouse caller, and exported real production DI FIFO drain. They verify no observer guest-memory stores and cleanup at completion, deadline and limit.
- Final
flock /tmp/wine-build.lock bash tools/build.shpassed before the explicit four-path commit and immediate strict-SSH pull/push.
The same worker then made the single authorized native experiment. One changed
fixture started on one leased box; the original was conditional and never
started. All 863 staged inputs were verified. The native plan's exact committed
base was 001103a7cf0990bcb7387b1563bc9b339cffe4b3, a descendant of the observer
commit. The module catalog remained primary SHA-256
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18
and compat ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf;
no original guest module or guest consumption was reached.
The first returned fixture-before.png was separately model-viewed and rejected:
it shows the desktop Read Me window, with no fixture target or crosshair.
Its authenticated SHA-256 is
45363d56944064c12166613b51d4cb52294a07dffae7afbb3da165d8045ef445.
The existing console preserves one observer-arm record with a 640×480 canvas
at CSS (20,40), cursor (100,100), unlocked state and empty DI FIFO. This
establishes installation/geometry, not visible publication. Why the drawn
fixture is absent from that image is unproved; visibility/compositing must be
resolved before another authorized attempt.
No before-image review authorization was published, so the fixture click never ran. Immediately at 01:02:10.180Z the worker used pidfd plus exact start ticks and command identity to SIGTERM the owning native supervisor. No later game protocol, input, capture, retry, quit or deadline extension occurred. The kernel collector completed with exit -15, 149 owned/149 reaped tasks, no remaining or unreaped tasks and no collector failure. Its actual parent wait returned 1 with separate stdout/stderr EOFs. Named processes and both ports were absent/closed; the stale owned profile was removed only after confirmed process absence.
All 93 artifact entries (90 unique contents) were retrieved and independently
reread by SHA-256 and size, with gzip/PNG checks, before the sole delegated
normal unforced stop. Box bx_nfhbm8v7 is archived, current expiry null.
Receipt stop_810fb307a8f23280 independently reports completed, unforced at
2026-11-10T01:03:48.573Z. Watchdog UUID
f920983d-82de-49b8-85bb-79ed0180277c retained its immutable deadline
2026-11-10T01:26:08.328Z; initial API expiry was 01:26:08.956Z. Its independent
supervisor recorded actual wait 0 and separate output EOFs. No owned live box
remains.
Inherited PID 3062540 was absent; its retained 27-control completion was recovered without signalling. Causes of launcher 12536/53510 exiting 143 remain UNKNOWN. Recovery uses exact Git commits, small owned/source patches, pinned media paths/hashes and unique logs/captures, with no source/media archive.
The observer is shipped, but Jack/Bunker navigation, staff use and visible staff target impact were not reached. Next: fix and test the fixture's visible publication boundary before a separately authorized native attempt. This task stops at its first live unusable image.