Q3 relative menu run: stopped before allocation on source drift

The original NEXT/world attempt was not launched. Fresh preparation pinned929 providers, current primary module d5dd33faadee5a0f77ac35347ecf0e4efe5efc86d92b03ef45ffe5adee83aea0 and compatibility module a5d7569b2315787832b7e1e720aca05e4de8012c809ac7a7e7896a29452d057f. The run-specific original invocation enables Q3_MENU_POINTER_CONTROL=1 and preloads the published bae02f6a1 helper immediately after native composition. No relative counts were chosen: there was no fresh original cursor capture. NEXT selection, guest consumption and world movement/fire remain NOT_VERIFIED.

At13:10:45Z, validation found concurrent edits to lib/guest-thread-host.js, lib/guest-worker.js and four WAT providers owned by Q21425. The actual no-spawn prelaunch subsequently refused with startup provider mismatch: lib/guest-thread-host.js. Source/module coherence was no longer established. No repinning, historical substitution, shared-client repair, runtime retry, input or capture followed. The first rejection and expected/observed SHA/size pairs are retained in first-reject.json.gz. The locked build passed, but does not establish the prepared closure after drift.

Offline tests passed: explicit relative-pointer actual composed command control, generated original invocation, prelaunch refusals, actual caller pipe/numbered ACK/EOF controls,44 dependency controls, input evidence and delivery controls. The separate offline startup test failed: its inert original-positive fixture still advertises historical module a320d4c8…, which the current-module admission correctly rejects. This failure is retained separately and was not retried. No local Chrome or native game ran; these tests use inert browser seams.

The1305 actual fixture/cancellation evidence references were SHA/size/gzip-CRC verified and the five control files matched1345 during preparation. Reuse was prepared for unchanged control mechanics only; no qualification was repeated, and no current-module native or gameplay proof is claimed. The later shared provider drift prevents promoting that preparation into runtime evidence. Native lifetime remains REVOKED; allwriters/edictABA and historical unresolved lineage/EOF remain UNKNOWN. This task does not resolve predecessor cleanup gaps.

API verification retained the exact predecessor bx_rfgz429k, UUID 5adf5b34-c76e-447d-b734-996cfe43bfd0, state ARCHIVED; the board records PHYSICAL_DRAINED. Its completed unforced stop stop_c6f706024295cebc ended 2026-11-09T13:03:19.518Z; initial expiry 2026-11-09T13:24:02.050Z, final archiveAfter null and expiresAt NOT_RETURNED. No new box was created, so new box ID/state/expiry/stop receipt and runtime watchdog/join are NOT_APPLICABLE. The25-minute watchdog was not armed because preparation failed before allocation. No lifecycle stop was issued by this task.

Evidence: scratch/runs/20261109-q3-relative-menu-native-progress-1415/. Git base 5e86db9cbcfd0ab7aedd20316a492685335a71f1, initial relevant patch, observed concurrent drift patch, small owned run-input patches and pinned media paths/hashes provide recovery. No source archives, media or module copies were made. SHA/size/gzip-CRC checks cover retained evidence; free/home stayed above 1.5GB. No production code changed. No agents/workers/deployments or shared-client/custody/host/WAT/Q2/Redline/HeroesII/CLAUDE edits.

Next: after the concurrent owner publishes a coherent source/build closure, a separately scoped original run can pin it and attempt the reviewed cursor correction. This worker stops with the concrete preallocation blocker.