AoWII required-body prerequisite and terrain observation, 2026-11-18

Evidence: scratch/runs/20261118-aow2-required-body-terrain-cause/.

The historical oleaut32.dll cancellation remains unexplained. Its retained caller delivered 598,288 bytes and EOF before the owning Network session reported net::ERR_ABORTED. EOF does not replace the strict browser terminal. No DLL implementation, resource exhaustion or rendering cause follows from that sequence, and the old runtime scope stays closed.

Published preparation

The older coherent source remains Git 0a823095cd147c43d362384efd33a312cc2766c7 plus the retained restored-package patch, with published 81ad6c802 thread manager. Standard module SHA256 is 87ef39648a61ed6f54ca4ab8de1926de02c651eb2d99655015dc7e5de5407009. This is explicitly an older pin, not current main. Source checks and actual generated-control Worker bytecode extraction bind that distinction.

The old preparation assumed that current files still existed and that the thread manager was unchanged. Both assumptions now fail before any browser launch. The new AoWII-specific recovery helper accepts missing/changed text only after reconstructing Git plus the recorded patch and verifying its expected SHA256. Media cannot take this recovery path. The native generated control then passes all 191 strict required-response terminals and reaches the real Native VariantInit returned vt=0 marker. No DLL bytes, registry or game state are substituted.

The actual main-page WineAssembly.fetchAssetBytes streaming reader and a real browser Worker reader independently consume binaries/dlls/oleaut32.dll: 598,288 bytes, SHA256 baeb2f7c1b8be56738d34e1d1ddf8e0eebd3a633215dc1575e14656be38b939d. Both pass unchanged strict transport assessment. The path's actual filesystem alias and requested spelling are recorded separately. Worker transport control is a JavaScript reader, not an additional native guest-loader claim.

Two separate negative native-browser controls serve the genuine DLL bytes through deliberately delayed responses at the same path with explicit control queries. An explicit AbortController produces ERR_ABORTED; a 6.5-second body delay exceeds the unchanged 5-second collector deadline and produces body timeout. Each closes UNKNOWN, with no subsequent endpoint requests or replay. These controls qualify detection, not the historical cancellation's cause. The synthetic collector suite passes 129 cases; focused recovery tests reject altered hashes/media recovery and prohibit EOF-only acceptance.

The canonical locked build passes. No shared runtime behavior changed. The qualified passive Device7 observer, native covering-red/narrow-strip and whole-memory controls remain reusable; their first original kick was target upload, not proof of completed draw output. The fresh original's result will be recorded below after its single authorized observation.

Single causal original: concrete startup blocker

The fresh registered original was launched once after publication 0dfe680b9. The complete launcher image was personally reviewed before ordinary Launch. The exact source/module/media preflight passed; no game controls were sent.

At 03:10:05 UTC, required package test/binaries/win98-games-a-d/Age%20of%20Wonders2%20demo-SW/extracted/Ml42ND50.bpl failed with owning Network ID 2346097.272, canceled net::ERR_ABORTED. The controller immediately closed REQUIRED_BODY_UNKNOWN, before game startup. There were no subsequent observation/input requests, replay or additional original.

Offline assessment binds its request, server UUID, captured body, continuation and caller. Fetch captured and verified 468,992 bytes, SHA256 c503b230760bfc9f3c315f91911c3b90471368115fabf227e4e95d0e34a30993, then continued the original response. The actual application reader delivered 468,992 bytes and EOF. The server independently finished with the same hash. The owning Network session nevertheless reported loadingFailed, with no loadingFinished. No explicit signal abort/cancel or earlier stopLoading, target-close or detach command appears in those records. The failure precedes local closure; cleanup is not its initiating event. These observations do not identify a cancellation cause or authorize accepting the request.

The historical oleaut32 failure itself was not reproduced: the fresh failure is a different required package. The native prerequisite passed this packaged graph, whereas this registered original did not. A Worker Debugger bytecode capture matches the pinned module, but the later slot/endpoint ownership read was not reached; compilation alone does not establish game execution. Game-owned completed Device7 ground draw vertices/texture/state/viewport/coverage, effective raster acceptance and last writer were not reached. There is no fresh terrain, army consequence or ordinary Quit evidence. The observer's qualified native fixture is not relabeled as game output. No production defect or rendering repair is proved; the conditional affected additional original was not used.

Lifecycle and retained evidence

Each of the five controls and the single original had a finite independent disk/deadline watchdog and native-supervise containment, with no RAM gate. All driver, Chrome and watchdog waits and both pipe EOFs are retained. The original exits driver1, Chrome0, watchdog0; native-supervise reports exit1, no survivors and no poll error. The original's watchdog minimum /home free space is 2,128,592,896 bytes, above the 1.5 GB floor; its deadline did not fire. Owned tmpfs profiles were removed only after retaining waits/EOF and hashing the custody records. External tool waits were observed too.

An actual browser control separately qualified the prearmed independent UP: after a trusted DOWN without its normal acknowledgement, the independent process delivered a trusted UP. No original game input used that capability. No Device7 observer receipt was collected from the original. No boxes were created: ID null, state NOT_CREATED, expiry null, stop receipt null. No workers, Wine, Python, foreign edits, deployment, media copies or source archives were used. Exact Git, owned patches, source/media pins, selected named PNGs, module recovery and final metadata live in the run.

Work stops at the concrete required-body blocker. Investigating why a fully consumed intercepted response gets a canceled Network terminal needs new causal evidence; neither its cause nor the terrain defect is inferred here.