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
- Retained direct and package controls: all 187 and 191 required-body receipts
respectively pass the corrected offline terminal assessment. Both actual
main Workers instantiated standard module
9be4491daf35df204ca50486165952dad7bb5a9766828374083a6d16edde3a92. There are no required Network failures. The package cell retains the actual registered three seed packages in order, five lazy native files, ordinary registry/fonts, native import patching and nonzero DllMain returns before the generated caller's CreateWindow marker. This is generated control evidence, not visible gameplay or native comctl qualification. - The current native-demand variant imports and actually calls
oleaut32!VariantInit. A prefilledvt=0xffffmust become zero before its window marker; otherwise its x86 branch reaches UD2. The direct native cell passes all 188 required-body receipts, actual native image/import binding, DllMain EAX=1 and the post-call marker. Its actual standard module is35a76b15b9b50a3b0c7a9acb3ea0623f951407eb77616d554e4438c9be256924. The matching package/native-call cell was not run. These two module generations must not be presented as a matched native API comparison. - Native oleaut32 is 598,288 bytes, SHA256
baeb2f7c1b8be56738d34e1d1ddf8e0eebd3a633215dc1575e14656be38b939d. Package arm: sessionBE90B2FB1B3BF184566DF25B886E75EF, Network1550038.272, Fetchinterception-job-173.0, server UUIDad921b8e-d12d-40e1-8575-70b02f495c57. Native direct: sessionBDE7F81F325E35965A3AE30DF8844C4C, Network1555581.269, Fetchinterception-job-170.0, server UUID33c35d89-66d2-4ff9-8086-2c513b663e6a. Each has a unique unredirected request/HTTP200, successful body/continuation commands, one loadingFinished, no loadingFailed, UUID-linked matching server finish, and normal caller stream bytes followed by EOF. Caller clocks and Node receive order are retained separately; no cross-clock causal ordering is inferred.
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.