Warcraft III live producer cadence, 2026-11-20
Run: scratch/runs/20261120-warcraft3-safe-trace-live-source-cadence-original/.
The fresh original reached its animated main menu. The whole private 800×600
host-consent frame and main-menu frame were personally reviewed. The trusted
host click had an independent UP, native owner binding succeeded, and both
actual Workers attested module 10bdae2c56c79eeb5d0b4ebbc602c8a233e36351380da274a70f7f5e25363564.
The CRT/media references, including 887eb5…, were hash-verified before launch.
The authentic MainMenu.fdf S shortcut remains the documented next action.
The task reused the committed d13e56268 passive diagnostic without another
safety calibration. Its fixed 256×8 numeric ring never serializes renderer or
event objects, touches their getters, or invokes producers. The shared bridge
remained byte-identical to SHA-256
91069c0446876b6528c72db09517e45a1fe3a7122a1444bc3dc5408f8ed22c2b.
Hex's frozen baseline and all input guards remain independent and unchanged.
The retained ring has all 50 contiguous records: 23 observe entry/return pairs,
one protocol-validation pair, and one dequeue pair. The maximum observed
check_input interarrival was 1310.15 ms during startup/menu. The executed
host.js source calls observe from actual check_input; the executed RPC
source samples only when the guest invokes that import, nominally at least
100 ms apart. Its native-message-wait observation is a separate source. These
facts establish actual producer activity, not why an interval is long. No
pending CDP status operation occurred, and no blocking page task was attributed.
One whole-root review capture completed. Recorded phases were approximately 28.3 ms for the first focus query, 71.9 ms for XWD, 88.3 ms for encoding, 0.56 ms for the original RGBA read, and 12.8 ms for the second focus query. No prepare, final socket capture lease, game DOWN, S press, or independent game UP occurred. There was no profiling session or profiling flush.
The scope permanently closed at 17:18:38.643 UTC on its actual HOME-floor check. The retained checkpoint minimum is 1,499,860,992 bytes. Checkpoint and scope checks use separate statfs calls; the exact second reading was not logged. There were 75 ordinary requests and zero subsequent app/input/frame requests. No replay followed. Single Player, Prologue, Thrall movement, objectives and normal Quit remain unrun. Producer starvation and status scheduling remain unproved; no causal production fix is justified by this execution.
The finite 245/260-second supervisor reports no leaks; all 22 tracked PIDs were subsequently absent. Browser, host-UP, both unused release helpers, Xvfb and window-manager waits retain actual exit/EOF receipts. Profile, display socket, lock and authorization were removed. The assigned unbound Chromium singleton socket/cookie were removed only after the runtime audit. The separate finite board watcher was terminated and checked nonlive; its parent wait was not retained. Assigned temp root/cache and proofs were preserved. No test box was created: ID null, state NOT_CREATED, expiry null, stop receipt null.
Only this note changes tracked content. No production changes, focused-test rerun, or full build were needed; the prior 35 focused and Worker ON/OFF passes remain references, not new results. That prior build completed but did not retain its exit status; this task does not upgrade that evidence. Exact Git, binary diffs, owned new-file patch, media references, recipes and cleanup receipts are retained in the run. Publication status is recorded in its final result.