Warcraft III post-recovery pending-producer attempt, 2026-11-20
Evidence: scratch/runs/20261120-warcraft3-post-recovery-pending-producer-cause/.
The fresh original scope permanently closed at 17:27:43.608 UTC on the actual
HOME-floor guard, before host review, native binding, preparation or authentic
300 ms S. The retained checkpoint minimum was 1,498,669,056 bytes; the separate
scope check's exact byte reading was not logged. There were 150 ordinary
requests and zero after closure. No replay is authorized by this result.
The committed d13 fixed 256×8 numeric passive ring and prior 35 focused checks, real Worker ON/OFF and native S/independent-UP controls were reused. All 36 historical references were hash-verified before launch. The frozen graph served module 10bdae and CRT 887eb5; the run stopped before actual Worker bytecode attestation. No producer readiness or whole main-menu review qualified.
Early page CPU sampling began before navigation. Each ordinary reply recorded page performance origin/time with bounding Node monotonic timestamps. After closure, predeclared profiling-only cleanup drained the ring once and stopped sampling, both within 2500 ms. No status operation occurred. Startup samples and callback intervals cannot establish the pending-status timing cause.
No production code or guards changed. Single Player, Prologue and player movement remain unproved. All 18 supervised PIDs retired; browser, Xvfb and window-manager waits retain exit/EOF receipts. The finite runtime/cleanup deadlines were 245/260 seconds, with no leak reported. No box was created: ID null, state NOT_CREATED, expiry null, stop receipt null. Run result and recovery notes retain exact Git/diffs, media references and cleanup details.