SuperTux 0435: offline preparation, NO_BOX STOP

The requested fresh level progress was not achieved. No SuperTux box, Chrome, original execution, runtime input or gameplay capture was created. Evidence: scratch/runs/20261109-supertux-diagnostic-gameplay-0435/.

The required exact warcraft-actual-close-0435 ARCHIVED PHYSICAL_DRAINED board release never arrived. At 04:34:43Z, that worker instead posted RUNTIME_RELEASE NOT_CREATED PHYSICAL_DRAINED NO_ARCHIVE_NEEDED and RELEASE STOP NOT_ACHIEVED: its offline preflight invocation used BROWSER_DEADLINE1900000000000 and failed the existing 30-minute assertion. This is the upstream worker's reported failure; no Warcraft runtime result was independently established here. Its suggestion that the runtime slot was free does not satisfy this task's exact release requirement. The owner's explicit upstream-failure rule therefore requires NO_BOX STOP. no-box-stop.json.gz preserves the exact board lines and zero create attempts. No allocation watchdog was armed because allocation was never reached. Box ID/state/expiry/stop receipt: null / NOT_CREATED / null / null.

Before that failure, offline preparation passed:

I read the 0415 and 0400 notes and the original recovery/control recipe, and personally inspected 0400's retained current.png, SHA-256 76611a395c2714a2b8541735021cc2f52cb3f12e5aea79c38ee4045e090c19f8. It shows the world map with score 75 and three coins, which is not new progress. The historical 0400 cause remains UNKNOWN. No native Pause, client prompt choice, first-level exit or new visible consequence was reached in this task. The 12-second freshness cap, 8-second aim and other caps were not changed.

Recovery uses the recorded Git base, provider references and small binary patches for run-specific inputs. There are no source/media/module archives. Local evidence SHA-256, sizes and gzip CRC are retained. The board watcher actually waited -15 with separate stdout/stderr EOF. Free /home remained above 1.5 GB; no agents, workers, peer-box operations or public deployment occurred.

Only this note is published. Next requires separate authorization with an explicit valid upstream release or an owner change to that prerequisite. This single task stops after publication.