Return Fire A1 flag objective

Run: scratch/runs/20261109-return-fire-a1-flag-objective-1758/.

The task queues behind Q3 arena1748 and Nox1750. No runtime is admitted until both publish their final release and allocated boxes have verified normal stops. Historical ReturnFire1727 missing joins remain FAILED and are not prerequisites for this explicitly authorized fresh assignment.

Prepared inputs and route

The actual current 698-file driver/media closure passes its offline preflight. All 125 original provider rows match the retained 1727 manifest; seven small run-local input path substitutions select this fresh run. The locked build reproduces primary 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18 and compat ecb45716 (full digest in postbuild-input-check.json). Source is recorded by Git SHA and relevant binary diff; run inputs have individual patches. No source-tree or media archive is made.

The shipped help specifies H ground fire, J bunker map, K vehicle information, and per-vehicle screen/vehicle-relative movement. It requires jeep retrieval after enemy flag exposure; the green/chiming beacon points to the exposed flag and red points home. The live J map and selected vehicle's control mode must be reviewed before movement.

The source-derived destination is A1 (55,56), BNO_FLAG owner1, northeast of home (47,66). The documented road runs south to (47,68), east to (50,68), north to (50,58), east to (55,58), then north to the building. Clearance remains untested. The helicopter alternative stays inland northeast. Historical captures show the matching road bend and building after the initial bounded helicopter movement; their appearance is a navigation clue, not attack proof.

The fresh map checker reproduces the historical 12-exception A1 fit against the other three original worlds. That check is preparation, not current gameplay.

Offline validation

The locked build, five native-key tests and six detached lifecycle scenarios pass. Lifecycle tests cover real launcher-session death, verified completion, independent deadline survival, immutable UUID/deadline/binding refusals, corrupt evidence refusal, uncertain API without retry, and actual child wait/EOF records. These tests use a fake box API. A mistaken --help test invocation failed its output-directory assertion before any delegate; the proper explicit-directory test then ran successfully. No native runtime attempt was consumed by that error.

Runtime outcome: resource gate failed before allocation

At 2026-11-09T18:16:01Z, the shared /home filesystem had 1,494,417,408 bytes free, below the owner's required 1,500,000,000-byte floor. This task's preparation occupies less than 1 MB and has no dispensable large files. No foreign files were removed. runtime-gate-failure.json retains the measured failure. No native attempt follows this terminal gate failure.

Q3 arena1748 had published final release; its receipt reports bx_7de5kh4r archived with unforced completed stop_92a6058ee1659620. Nox1750's final release was still pending when this task stopped preparing. Neither predecessor was controlled by this task. Historical ReturnFire1727 missing joins stay FAILED.

This task created no box, UUID, deadline watchdog, browser or original game. Box ID/state/expiry/normal-stop API receipt and runtime delegate joins/EOF are NOT_CREATED / N/A. No stop is required for an uncreated box. The six offline lifecycle cases have their own genuine fake-API delegate wait/EOF records; they are not live-box qualification or substitutes for historical missing joins.

No current map, attack, exposure, pickup, return, or gameplay success is claimed. The offline route remains a source-derived plan. The next separately assigned attempt needs disk space above the floor, both predecessor releases and verified normal stops, a fresh immutable detached lifecycle UUID, one native preflight, then at most one original attempt under the unchanged controls and guards.