AoWII required DLLs, native audio and two moves, 2026-11-17
Evidence: scratch/runs/20261117-aow2-required-dll-audio-gameplay-progress/.
One fresh registered original completed two ordinary moves with Party movement
20/20 → 14/20 → 8/20, then ordinary menu Quit and native ExitProcess(0).
Both Mss32 audio threads progressed through thousands of wait completions and
returned normally during Quit. No new production change was needed. The tested
thread manager is published 81ad6c8022229f25aa35b2baf0f0ee8bbeac9df7;
the actual instantiated standard module remains SHA-256
87ef39648a61ed6f54ca4ab8de1926de02c651eb2d99655015dc7e5de5407009.
Required-DLL boundary
Bounded offline examination of the previous closed run binds the vclx50 request
to its page/session, server UUID, Fetch capture and continuation. The actual
application reader delivered 248,832 bytes and then EOF before CDP reported
net::ERR_ABORTED. No signal abort, reader cancellation, navigation, stopLoading
or target-close cause appears in that retained sequence. The next Ml42ND50 body
was captured but its continuation failed on the already sticky collector fault.
The historical cancellation cause and strict terminal remain UNKNOWN;
server finish and the old non-hashing caller log do not establish acceptance.
No old endpoint was queried or reopened.
The present-path prerequisite reused the prior direct188/package191 native VariantInit proof and exact source/module/media reconstruction. A generated native caller with the full packaged graph, the published manager and unchanged strict collector then passed all 191 required response checks, including browser loadingFinished for vclx50 and Ml42ND50. Native VariantInit returned vt=0. Two local harness errors are retained: an omitted generated-icon route stopped the first attempt before guest execution; after correction, the native marker was present but a raw-JSON string poll failed to recognize its escaped quotes. The latter run's complete strict receipts and actual native marker were assessed offline successfully; no third control run or weakened response rule was used. The local harness route/poll bugs were corrected. No production defect was inferred from them.
The newly authorized original passed all 797 required responses in final offline assessment, with no required first fault. Required inputs stayed required; there was no abort exception, consumer ACK substitution, refetch or filesystem patch. The historical UNKNOWN remains separate from this present-path success.
Native audio and gameplay
The passive bounded observer retained per-slot slice/wait counts, first/latest
replies and short histories. Slot1 advanced from 16,102 slices/390 completions at
the menu to 62,694/16,191; slot2 advanced from 997/996 to 23,695/23,694. Their
native start addresses are respectively 0x1324520 and 0x1343980. Neither had
the old duplicate-completion fault during gameplay.
During ordinary Quit both returned through the existing armed ThreadProc return
sentinel: threadReturned:true, DWORD0, no trap, ESP exactly equal to their owned
stack top. Each final reply executes two guest blocks after a single last wait
completion. Their raw terminal EIP0 observations are retained, not suppressed.
The prior defect instead had two completions, zero following guest blocks and
threadReturned:false. No ThreadProc, audio, scheduler or crash-policy change
was made in this task. The observer's broad historical filename
passive-first-fault.jsonl also records these normal returns; the positive return
contract, not that filename or EIP alone, determines their meaning.
Personally reviewed whole images show Main menu → Scenario → Single → default Julia Human → Start → Click to begin. Selection established a six-unit Party at 20/20. The first confirmed move took five units southeast of the tower, leaving the hero there, with 14/20 remaining. The second confirmed move reached a distinct southern tile with 8/20 remaining. Plotted paths alone were not counted as moves. The known black-ground rendering defect remains visible.
Escape opened the ordinary save-before-exit prompt. No returned to the main menu;
Quit opened the demo outro, Next reached its final promotion screen, and Exit
closed the native game. The subsequent capture records [ExitProcess] code: 0,
--- Program exited ---, running false, stopped true, Ready, and no guest windows
while Chrome was still open. Two late main-worker unexpected message
diagnostics (sliceDone, exportResult) remain in the log; no guest trap was
reported. Trusted page down/up events are balanced; native dequeue logs and
visual outcomes are preserved separately.
Validation and lifecycle limits
The unchanged strict assessment passed191 for the generated current path and797 for the original. Focused offline checks verify the exact manager/module, both required DLL completions, retained historical UNKNOWN, balanced trusted input, audio progress and positive native returns, and guest ExitProcess0. The published fix's 59 scheduler checks, failing original baseline, focused wait/bootstrap/wave fixtures and canonical locked-build PASS are reused from the predecessor result. Its two broader cross-thread failures and scoped-render-yield failure remain explicit identical baseline/fixed limitations; they were not rerun or hidden. This task changes only this findings document, so no new code build is claimed.
The independent deadline/floor watchdog was armed before Chrome. Native exit
was captured at 1794948306970 milliseconds, before the deadline at
1794948334.378 seconds. Cleanup reached that deadline before the queued local
stop command was consumed: the actual terminal is deadline-after-native-exit,
not an acknowledged command21 stop. Actual Chrome−15, driver124, watchdog0 and
supervisor143 waits with both pipe EOFs, empty scopes/children and hash-verified
custody retrieval are retained. The original's external helper tool ended143;
its keeper-wait receipt is missing and remains UNKNOWN, never reconstructed
from process absence. Both generated controls have actual external keeper waits
and EOF receipts. Disposable profiles were removed only after custody retrieval.
No box was created: ID null, state NOT_CREATED, expiry null, stop receipt NOT_APPLICABLE. Git plus exact recorded patches remains the source archive; media was referenced by path/hash, never copied. No private guest calls, forced pump, clock/config/media/save changes, source archives, foreign cleanup, workers or deployment were used. Full visual parity, FPS and audio quality remain open. The historical cancellation cause and missing external keeper wait also remain explicit limitations. The worker releases its files and stops after publication.