AoW II: corrected registry inventory; original held on canceled comctl32 transfer
Worker aow-registry1715; evidence:
scratch/runs/20261106-aow2-registry-input-gameplay/ (ignored).
Tested main 23eeaaa889ca3f415fba9c1c9f9c92b9cbc981a2.
No production emulator, collector, guest or media changes. Gameplay goal was
not reached: zero army commands and no movement-point or terrain acceptance.
Preparation remained run-local and unexecuted until the coordinator's explicit 18:05:38.537880–18:50:38.537880 UTC grant, including cleanup. Fresh checks found 87 predecessor PIDs absent, 18 ports refused, nine profiles absent and four locks free. No workers or test boxes were created or assigned.
The retained next-browser-input-pins.json was preserved, then refreshed from
current DLL_PATHS, SYSTEM_DATA_FILES, the registered app and its real local
manifest. The inventory checks existing files/hashes, binaries/ and
test/binaries/ aliases, all 19 registered DLL files and the import closure of
31 native PE modules, including app-local packages and DLLs. There are 1,661
pinned URLs, 2,776 alias records and no missing required files. It separately
derives exact run-local transformed Worker and virtual observer bodies; the
original and generated shell use one shared transform helper. All 1,064 media
references match before and after; media was not copied.
The locked full build passed. Both current modules passed disabled/armed public
COM controls: 27 draws per cell, equal independent pixels, counters and
architecture; armed cells retained 159 CPU and 57 GPU events. Sparse observer
and per-Worker drain persistence controls passed. Seven retained strict
transport proofs were reused after exact adapter/collector hash checks;
production collector remains 0808b400aca53cd8547a1d47d6ef2c4f3c06823a1bf723a87bbe329cf240a220.
One generated setup failure is retained: the custom transformed Worker
response omitted COEP. Chrome reported coep-frame-resource-needs-coep-header
and ERR_BLOCKED_BY_RESPONSE; the immutable first fault remains in
shell-control-native-current/. Only the run-local server headers were fixed.
The fresh generated shell in shell-control-native-current2/ passed with
caching disabled, 181 verified bodies, all three actual host font loads,
native oleaut32 demand/DllMain and actual running main Worker bytecode identity.
The oleaut32 body is 598,288 bytes, SHA256
baeb2f7c1b8be56738d34e1d1ddf8e0eebd3a633215dc1575e14656be38b939d.
The sole registered original Launch was 18:09:24.626 UTC. Its actual main
Worker is slot 0, endpoint 1, target AA9C930F1DC8C7A3BE71D2B5C362AE5F,
session E64959ECA1754E3BDEF85644F97D93B2, instantiated standard module
2fa9f377dde5e477eb811baceb64032889fbe9b27a664b213477e84627e5eb94.
The compatibility control module is
3dd82e987c0683b45f28860748b6a19151b6623f578f10d70d201b798baf2a6a.
At 18:09:25.794, the strict collector faults on
binaries/dlls/comctl32.dll, Network.loadingFailed, canceled true,
net::ERR_ABORTED. Owning page session AA5DBA71684E5646B16F81DD040ED769,
target 0D036F9CCB69B613996B8007E066DE66, Network 666315.271,
Fetch interception-job-170.0. This exact Fetch body was already captured,
verified against its present registry pin and continued: 577,808 bytes,
SHA256 28a41e6a35c4509924a32a99841a815cf49e1d3ee6912ec26a823e45472edfa4.
The separately identified server request 170 finishes HTTP200 with the same
bytes/hash and no server abort. Browser/server identity namespaces are distinct.
The later browser cancellation's cause remains unknown. Neither a missing pin
nor an emulator mismatch is established, and verified body bytes do not justify
ignoring the retained required-request failure.
I personally reviewed initial.png: startup and a loading dialog waiting for
general.rfs, not menu/world. The main Worker is alive with completed slices
and IO yield 12; there is no observed render endpoint. Twenty-four durable CPU
drains contain zero CPU/DX/GPU producer events and zero births, an observation
gap during startup rather than evidence about terrain production. No game
input followed Launch. The fault was not cleared, no response was obtained
through another transport, and the original was not restarted. Native DOM
receipt observation uses Window capture; only the native Launch was sent.
The original closed normally at 18:11:18.284, Chrome and driver exit 0.
Exact Git SHA, relevant binary diffs, new-file patches, module identities,
failed setup, first-fault identities and reviewed captures are retained.
Cleanup is recorded in final-cleanup.json; box ID/state/expiry are null.
Audio and logical gameplay FPS remain unknown. Historical accepted army moves
remain separate and unchanged.
Next: a bounded generated full-shell control covering comctl32/native DLL demand and owning request terminal events, identifying why the verified Fetch later receives ERR_ABORTED. Do not weaken required-response collection or repeat the original without a separately authorized launch. World inspection, two ordinary army commands/points and earliest terrain producer remain open.
Follow-up: generated comctl terminal control
records successful direct native comctl demand, but the matched package graph
hits an immutable required Ml42ND50.bpl cancellation before comctl. The
original cancellation's cause remains unresolved; no original was repeated,
no required fault was ignored, and gameplay remains gated.