Deus Ex natural ordered writers: exact-control media prerequisite missing
No Chrome or natural observation was launched. The first blocking boundary
is prebrowser fixture loading: the exact published integration control needs
test/binaries/notepad.exe, SHA-256
e7b01ab85a35ba6f577067d13efa522dc3d605de7712340e4acaf7065f866340.
That file is absent in the assigned retained runtime. Checked canonical paths
under /home/user/*/test/binaries/ and recursive retained test/binaries/
contained no matching Notepad file. The task forbids media copies, so the worker
did not import it, substitute another PE, or bypass the required control.
This follows Worker integration
and upstream light provenance.
Source is published 0d3a8cbedfd04773d46701db2d940a18daa6d180.
Evidence is in scratch/runs/20261104-deusex-natural-ordered-writers/.
No emulator defect was demonstrated; no production fix or pixel patch was made.
Preparation and exact-control failure
Read-only preflight verified all 542 retained manifest inputs, the browser
cache checker, Puppeteer 25.7.0 CJS/ESM imports, actual prepared driver imports,
and 153 served inputs with exact hashes, isolation headers and no-store.
These checks applied to the retained baseline. Its WASM was 129a71a0…, rather
than the integration-qualified 4ddc8336…; two D3D JavaScript dependencies and
two WAT fragments also differed from the source revision.
After baseline preflight and cheap tests, a retained 69,798-byte unified patch
updated only those four files. The byte-exact published optional adapter was
staged separately. The existing vendored compiler rebuilt, on the assigned box,
build/wine-assembly.wasm to SHA-256
4ddc8336097ef4b8503c6e6d2bb7fb05a2a1084800322523c8959b7128ca217a
and compatibility WASM to
d4c5171a2865a1dbc360d53e3a32fbfa2149e1bcdabaf57ee6dad4bd9338a367.
No module binary was copied. The ordinary build gates were not rerun; this is
an exact-output reconstruction, not a new full-build claim.
The exact integration.cjs, SHA-256
a7e6101701d8b63e39f16c3b94691936b5a3f84491b2afa90fa8c2590c0e427f,
then failed reading Notepad before load_pe or fixture x86 execution. The
supervisor stopped immediately. The queued transport, original optional/pixel
controls, replay and composed-actual tests did not execute. No fresh physical
Worker parity or arithmetic-control result is claimed. offline-terminal.json
and offline-1.log preserve the failure. Final served-byte qualification of the
rebuilt module was not reached; the retained baseline manifests still name the
old module and must not be reused as a qualified launch manifest.
The local published adapter regression and run-owned composition checks passed.
The composition embeds the exact predecessor
producer-next-boundaries-fixed.cjs body and published adapter, preserves the
optional predicate sampler and owning mainWorker/MMX-slot-0 binding, and prepares
fresh Draw IDs and loaded module generations. Its intended limits are one Chrome
of at most eight minutes, one collector interval of 10M blocks/120 seconds, and
an ordered adapter capped at 1M delivered boundaries, 256 records and 10 seconds.
Output caps and raw-surface-before-PNG ordering were checked; these remain
prepared capability, not observed runtime behavior. An additional predecessor
cheap test could not read its previously compressed capture at the hardcoded raw
path; it likewise supplies no new passing result.
Evidence limits and custody
There is no fresh setup descriptor, palette selection/allocation, overlapping store or owning consumer evidence from this task. No original registers, code, arguments, ESP/EIP, guestcalls, Draw or repaint were forced. No capture was made, so there is no fresh raw buffer, host/surface PNG or personal visual review to claim. Natural instruction/block gaps and allocation lifetime remain unresolved; observed pointer generation would still not establish allocation lifetime.
All 31 remote run files (456,733 bytes) were recovered or matched against identical local staged inputs with complete size/SHA-256 verification. Exact source SHA, relevant binary diff, narrow patches and helper hashes are retained; there is no source-tree archive or game-media copy. Own compiler/supervisor PIDs were gone and Chrome processes were empty at 12:02:28Z.
Box bx_g8gbdt7c is left RUNNING (API idle, healthy/hydrated), expiry
2026-11-04T12:34:58.651Z. Custody was returned on the messageboard; coordinator
owns shutdown. The next authorized attempt needs the exact integration fixture
already available through an approved media path, followed by completed controls
and final served-byte preflight. This worker stops with this concrete prerequisite
blocker; no successor, other-box access, lifecycle operation or deployment began.