AoW II current package controls; original held at disk floor

Evidence: scratch/runs/20261117-aow2-current-package-native-terrain-gameplay/ (ignored). No production change, original launch, terrain capture, army input, or ordinary game Quit. Historical accepted moves 20 -> 13 -> 10 and the unresolved producer of black point (600,300) remain unchanged.

The retained generated full-shell control now completes its package path with the strict default collector. The old cancellation cause is still unknown. No required failure was cleared because bytes arrived. Current main deliberately removed native comctl32 loading in owner commit a6e88fb7d; its InitCommonControls call now uses the builtin implementation. Restoring the old native mapping would change current behavior and was not attempted.

Current observations

Driver corrections and limits

The retained assessment incorrectly requires every request/response/terminal to share one session. Actual paused Worker startup has the parent's request and the child's response/finish, with an explicit startup binding. Parent Fetch interception also captures child importScripts responses. The run-local assessment now checks the explicit parent relationship, exact Network ID and independently captured matching child body, with separate command identities and UUID-linked server receipt. It requires complete coverage and rejects actual required failure, missing/duplicate terminals, wrong session, redirect, bad server body, rejected continuation and incomplete collection. No production collector or host behavior changed. Original driver exits 1 from its obsolete assertion are retained; offline assessments do not rewrite those exits.

The recorded old pin map and its listed gzip were absent. Only current web, system and generated-control native inputs were pinned afresh; no game-media inventory or media copy was made. An omitted TTF pin failed strictly and was corrected before the successful controls. A later native setup caught a shared module changing after pinning, also retained as failure. The successful native cell serves its pinned module buffer and retains actual instantiated bytecode.

The canonical locked build passed, as did 129 collector lifecycle cases and ten offline assessment controls. All three full generated-shell screenshots were personally reviewed: teal shell and logs, without a visible game scene. No logical FPS, audio, gameplay, native game exit or terrain ownership claim.

Blocker and cleanup

Free disk fell below the enforced 1.5 GiB floor (1,520,451,584 bytes observed against 1,610,612,736). No further browser was launched. Own reproducible duplicate assessments/modules were removed or hash-verified and hardlinked; unique logs, captures and modules remain. Post-cleanup space was still below the floor. No other agent's files or old artifacts were cleaned.

Every created Chrome process closed normally with code 0 and both pipe EOFs; all five browser PIDs are absent, ports refuse connections and profiles are removed. Each driver ran under an independent, prearmed deadline supervisor; actual close/wait and both EOFs are retained. No box was created: ID/expiry null, state NOT_CREATED, stop receipt NOT_APPLICABLE.

Next requires durable disk headroom, then the matching current package/native caller comparison if still needed, followed by the unused single authorized registered original. Reuse these controls where exact inputs remain equal; do not invent a cause for the historical ERR_ABORTED or repeat media inventories.