Q2 synchronous owning-CPU transport (1425, OFFLINE)
The concrete 43ec0e8cd gap is repaired with an explicit, default-OFF shared metadata binding. WineAssembly.armQuake2WriterObservation() sends setup to the actual main CPU Worker after loading; it never arms the idle page instance. The WAT observer publishes its existing 21 unsigned fields into one 128-byte private region. A monotonic atomic sequence encloses each publication. CPU execution publishes nonzero PC before executing and zero after returning; reset/invalidation and arm changes also publish. REP fault reentry restores the existing owning PC through the same mirror. Unbound/unarmed guest hotpaths have no new callbacks, guest reads or JS allocations. Armed observation intentionally costs atomic metadata stores and retains the existing instruction-watch behavior.
tools/quake2-shared-writer-witness.cjs exports pageSource({globalName,identity}), executable in the actual page realm using the retained admission identity. It verifies process, endpoint and admitted object identities, awaits the explicit setup once, and installs a synchronous observer. Supply the same globalName as writerWitnessGlobal to the existing passive chain. Each of its six existing copies is already bracketed by the unchanged 43ec0e8cd reader. Each boundary performs one metadata snapshot, with no guest read, RPC, await, guest-state write, retry or predicate change. A busy/torn/unsettled snapshot is INVALID, never retried. await globalThis[globalName].close() is explicit teardown outside the copies; generation-checked teardown cannot disarm a later arm. Binding is once per CPU instance lifetime; fresh attachment after close requires a fresh instance. Boundary capacity is bounded and exhaustion is sticky INVALID.
Every raw field is retained: PC, address, width, epochs, overflow, invalid flag, range bounds, sticky host-import marker and observer arm generation. Arm generation is not parse/frame identity. Process/Worker/module/endpoint/memory/buffer replacement, retirement or ambiguous transport invalidates access. Sequence saturation and epoch overflow fail closed. These are completed owning-instance gs-helper receipts, with the existing armed REP coverage, not an atomic guest-memory copy or complete instruction history. Intermediate PCs are unavailable when epoch delta exceeds one. All-writers, aliases, peer CPU, raw-host writes, lifetime, parse generation and frame ABA remain UNKNOWN. nativeQualification remains false. No message timestamp is used.
node tools/quake2-owning-witness-transport.test.cjs executes production GuestThreadHost, WorkerLink, guest-worker, the built shipped CPU and the actual serialized reader. It runs the actual host API method and executable page-source install, then actual capture/progress calls. A test-only Worker wrapper signals completion of real export replies in unused metadata padding to schedule deterministic OFF/ON interleavings; it supplies no observer receipts and changes no production source. The original EXE supplies pinned instruction bytes, without copying the EXE into evidence. Actual async export boundaries FAIL; the shared boundary observer PASSes. All 21 fields are checked against actual owning exports. Both primary and compat CPU runs pass:
- Six OFF/ON store cases: same byte, store inside the first copy, publication 403527, frame clear 403342, client clear 409221 and saturated epoch. All preserve architecture/lazy flags, guest bytes, exact read order and executed acceptance predicates; stable reads total 13,068.
- Busy/torn/unsettled snapshots, sequence exhaustion, invalid/overflow flags, owner/module/endpoint/worker/memory replacement, transport ambiguity, retirement, reset, rearm, close and stale close fail closed. Sticky evidence cannot recover after a rejected boundary.
- Six actual Worker publication-to-generated-health-consumer cases: first loss (98), signed death (-1), UNKNOWN, each with successful and failed independent UP. The original first terminal stays sticky; later passive ticks perform zero reads. Raw publication receipts survive the actual health sink.
Health testing replays the exact historical c443739b5 custody provider from Git in memory only to construct the retained generated consumer with inert startup. That provider is not executed. Concurrent 1435 custody changes cause current production composition and the old passive suite's composition phase to refuse the historical SHA. The refusal is retained in passive.log; no provider assertion, acceptance predicate or custody code was changed. Native qualification and native retry remain unauthorized/unperformed.
Focused final results: primary + compat transport PASS; existing 15 writer cases PASS; 66 REP observer cases PASS; 17 native-write-core cases PASS; 182 REP absent-page restart cases PASS; existing serialized reader boundary and passive-damage tests PASS. The locked complete build passes. Evidence is scratch/runs/20261109-quake2-owning-witness-transport-1425/: Git bases, small binary diffs including owned new files, logs, SHA/size and gzip CRC inventory. Git is the source archive. No media/module/source-tree archive copies, browser/local Chrome, original/native runtime, new boxes, other workers or deployment were used. New box ID/state/expiry/stop receipt: NOT_CREATED / N/A. Q3's runtime remains untouched.
Next work is separately authorized coherent source/module pin preparation and any native experiment; this task stops after publishing the tested bridge. Current custody drift is not waived by the offline historical health fixture.