StarCraft squad selection attempt (2026-11-17)

No squad attack, enemy consequence, objective progress or native Quit was proved. The single authorized fresh original ended after 315.019 seconds through the supervisor's disk/deadline watchdog. Native exit 0 is an orderly host SIGTERM shutdown here, not ordinary Exit Program. The original is closed.

Evidence: scratch/runs/20261117-starcraft-original-squad-enemy-consequence/result.json.

The existing registered starcraft_shareware entry and ophelia terran1 arguments were unchanged. All twelve prior registered dependency/media pins matched; an additional existing system stdole32.tlb was recorded separately. The fresh briefing showed Chau Sara and Destroy the rebel base. The shipped mission tip explicitly described box selection and holding CTRL while clicking a unit to select multiple units of that type. No mission, media, configuration, save, console, cheat, seed or clock override was introduced.

Published controller commit 29bba0738 permits a personally reviewed Ctrl-click selection using the existing finite transport. Actual native fixture controls covered this modifier gesture, ordinary Attack, its separate target, physical release and waits. The original first selected an SCV, visibly 60/60, Kills 0. A separately reviewed Ctrl-click selected a Marine, visibly 40/40, Kills 0. Only one Marine selection was established by its HUD. No combat command was issued; an input receipt is not a squad selection or enemy-damage proof. Three expired local preparations sent no input and were retained.

The same shipped tip's ordinary box-selection alternative was added as one finite DOWN/move/independent-UP gesture in published commit d92c78c26. Policy tests require both endpoints from the same whole scene and permit this gesture only for selection. An isolated actual native fixture used the exact original's retained module and verified consumption/release for the box gesture and Attack/target. Both code publications followed focused tests and a passing locked canonical build. The original's module was never replaced. Its only source drift was this explicitly recorded controller extension. Before any original box input, the capture helper locally refused the already terminal native process. It sent no endpoint request. No rebind, endpoint replay or second original occurred. The single-unit Ctrl-click observation does not establish a runtime defect or authorize an affected-original rerun.

The old original's enclosing-wait gaps remain historical gaps. This attempt used the published durable launcher directly around the native supervisor, with an independently prearmed 1250-second enclosing watchdog. Small actual normal/error process cases returned 0/7 with actual parent waits and separate stdout/stderr EOF receipts before the original. Native, supervisor, independent release children, watchdog and enclosing-command waits for this attempt are retained; the board watcher also has its actual tail wait and both EOFs.

The native watchdog was armed for 1220 seconds, but its deadline-or-disk branch fired around 315 seconds. Its source checks the 1.5 GB free-disk floor. Because the recorded deadline was still about 905 seconds away, the disk condition is inferred as the trigger. The exact low-water byte count was not recorded. This means the requested continuous free-disk condition was not maintained despite preflight and later readings above 1.5 GB. The safety guard was not weakened. The native log records host SIGTERM, not guest Exit Program; the watchdog's later conditional KILL does not prove a KILL reached a live process. Native and watchdog waits returned 0 with both EOFs. Shutdown still reported 11 abandoned parked Enter calls and active guest threads; no clean guest-thread shutdown claim is made.

Git SHAs, binary relevant/untracked patches, run-input patches, source pins, registered media hashes and the tested module identify this execution. Six named whole PNGs remain after all sixteen produced images passed PNG CRC, inflate and 800×600 checks. No source archive, media copy, frame series, worker, box or deployment was created. Box ID/expiry are null, state NOT_CREATED, stop receipt not applicable. All owned runtime scopes are released.

Next work requires fresh original authorization and sufficient shared disk headroom. The published box-selection gesture can then be used to establish a visible surviving squad before any attack. Enemy damage/destruction requires separate attributable before/after/persistent evidence; mission completion and native Quit remain open.