AoWII long startup: real menu, callback boundary before map

Run: scratch/runs/20261118-aow2-long-startup-map-terrain/. The fresh normal production browser reached the real main menu. It did not reach the map, army selection, movement points or terrain diagnosis. One reviewed Scenario click was followed by an actual thread 3 callback driver failure. The scope closed UNKNOWN immediately and was not queried or replayed. No production repair is claimed.

Preparation and controls

The immutable published graph is Git 23437f4ca2d0a03e2d347f9017e51aeb7b7e5981, module SHA256 d8e7c4b0fe678597cfeedc7af57c91659c6c13bc76260d55826c21cfcb647490. This differs from the predecessor's 5af3/3616571e graph. Its unchanged registered age_of_wonders2_demo entry and 1,083 installed file pins are recorded in prepared.json; foreign shared-tree overlays were excluded. The corrected run-local two-window controller was reused. Runtime sources were reconstructed in memory from Git, without a checkout or source snapshot.

Before the original, the actual native Device7/software fixture rendered RGB565 red at [600,300], distinguished a narrow non-covering strip and passed seven whole-memory hash checks. The bounded observer's source/slot, copy, lifetime, return/receiver and real-error controls pass. These qualify the observer, not an original terrain cause. Normal-browser authored two-window controls reproduce the old missing actor binding, bind foreground main 65538, reject changed process/actor identities, render the yellow triangle/maroon frame after independently released Space, and reach ordinary Escape Exit0. Whole control images were personally reviewed before their respective inputs.

The original's startup allowance was fixed at 900s, total 1800s, final 180s reserved for ordinary Quit and cleanup. Independent cleanup backstop 1820s was armed before the driver. Nothing was extended in flight. The enclosing run-local launcher wrote this configuration directly; the shared launch() convenience method still has its older 900s cap and was not modified.

An origin-tip equality assertion raced another worker's publication after the graph/controls were prepared. The shell nevertheless launched the original. The publication receipt was then sealed using a published-ancestor check. This preparation-order blemish is retained; source/module/media and budgets were already fixed, and no running graph was changed.

Natural startup and bounded failure

Native custody began at 08:37:04.243 UTC. The visible launcher was admitted at 08:38:12.292 and personally reviewed: it was still waiting for the first program window. At08:39:09.843 the next whole capture showed the actual Age of Wonders II main menu with Campaign, Scenario, Load Game, Replay Intro and Quit. This is actual startup progress, not a timer-only failure, capture refusal or proof of the map. No startup profiler was needed or collected.

The first and only ordinary game gesture selected the reviewed Scenario button at browser [678,609]. Trusted browser DOWN/UP events are retained, as are native-facing WM_LBUTTONDOWN/UP log rows and the independent release child's actual exit 0/wait/both EOFs. Retained physical key/button states are neutral. The last whole PNG still shows the main menu; the filename scenario-mode.png does not establish a Scenario transition.

At08:39:38.365, the actual log reports: [ThreadManager] worker thread 3 slice: Process send callback exceeded drive limit. The controller recognized its first-fault predicate and closed at 08:39:38.453. No later endpoint request, original replay or additional original followed. The chronological association with the Scenario click is not proof that the click caused the callback failure.

bounded-cause.json binds actual served source hashes, all four instantiated CPU Worker modules, input chronology and the sole error throw site. In this exact graph, GuestThreadHost._driveThreadSendToLink reaches that error only after its 10,000-iteration loop fails to return a completed/deferred/unavailable receiver result. Nested resolution, blocked-yield pending and ordinary resume paths share that bound. The ThreadManager free-run rejection handler supplies the actual thread 3 log prefix. The last retained main slice is seq 28587, yield 17 (incoming-send message point), with no trapped value. This is a finite callback-driver boundary, distinct from the 900s startup budget.

The actual failed request, receiver frame and mix of loop branches were not retained by the current diagnostic path. Their underlying guest/scheduler cause remains UNKNOWN. A frame-scoped natural callback trace is the next needed evidence; changing the drive limit or callback semantics without it would be speculative. No renderer, DLL, audio, guest, config, registry, media, clock, focus or native acknowledgement substitution was made. The old strip that excludes [600,300] remains excluded as causal terrain evidence.

Transport, shutdown and recovery

The original has 435 hash-authenticated actual consumer completions, including the real required Borland BPLs, oleaut32 and MSS32 bodies. Canceled Network events remain distinct from those application-reader completions. There was no Fetch interception or required-body substitution. Requested WebGL is not an executed game Device7/backend claim: retained page bridges are absent and no map render Worker observation was reached.

Original ordinary Quit was not attempted after UNKNOWN; host cleanup is separate. Native-supervise reports exit 1, no poll error and no leaked owned processes. Actual Chrome 0, driver 1, watchdog 0 and enclosing-owner 1 waits and both EOFs are retained. The authored control has the corresponding exit 0 chain. Both independent watchdogs have no trigger. Original minimum /home free space was 1,936,027,648 bytes. Owned profiles were removed after custody waits/EOFs were retained and hashed. No test box was created: ID null, state NOT_CREATED, expiry null, stop receipt null.

The audit verifies source/module/media, independent release and closed-scope custody. No runtime code changed, so a repair build or affected-original oldfail/newpass is not claimed. Exact Git, relevant binary diffs, owned helper patches, selected named whole PNGs and recovery instructions are retained; result.json is written last. No other agents/workers/boxes, Python, Wine, deployment, media copies or source archives were used. Ownership is released after final sealing.