Stronghold explicit idle input initialization
The production availability defect is repaired: real Win98Renderer construction now initializes _activeInputEvent to null and _mouseButtonsMask to zero, and real WineAssembly construction initializes its _lastInputEvent to null. The last-event field belongs to the host, so this repair also touches the separately claimed, unowned host.js. No controller supplies missing values, no live events are reset, and no guard, RPC fast path or guest-worker code changes.
Evidence is scratch/runs/20261104-stronghold-explicit-idle-input/, starting from c599a8923. The new focused test constructs both real classes, exercises production mouse enqueue/dequeue, physical press/release, captured movement, foreign-queue ownership and actual host input imports. It rejects active events, stale last events and nonzero physical masks, including zero-button captured movement, and verifies construction of another instance cannot clear live state. Existing relative mouse, browser-worker focus, dialog capture, immutable capture, strict native guard, immutable queue and actual operator qualification tests pass. The locked full build passes. The callback census refresh changes only the host/renderer entries in this commit; peer Deus observer/guest-worker entries are preserved separately and restored to its working tree.
The retained bx_c5e39n22 runtime reused all media and both retained modules. Only the exact constructor delta, small helpers and focused fixture were staged; 2415 pins were verified, with updated hashes for the two changed source files. Actual Puppeteer 25.7 CommonJS/dynamic imports, five HTTP pins/isolation checks, controller ACK/aggregate/fault/deadline fixtures, and the actual operator's eight unavailable-input rejection paths passed before the single browser. Additional host-import fixture coverage was added locally after launch and passed; it does not change production code or the running driver.
I personally inspected fresh captures at steps 2048, 4096, 6144, 8192 and 10240. Loading continued through streamed media, Firefly splash, then Enter Your Title / Lord Crusader / Start Game. At 10240 the actual host renderer identity matched, all raw field-presence flags were true, active/last were explicitly null, mask was zero and queue empty. The unchanged strict qualification accepted this actual state before any guest input.
One balanced Start Game click at native (398,274), browser (438.3875,500.72333333333336), reached the original Demo V1.1 main menu at 10496. The corrected Crusader native (304,144), browser (337.3375,360.4433333333333), reached the actual Choose type of Crusader game dialog at 10752. Both fresh scenes were personally inspected, matched their existing exact scene patches and had strictly drained input before further navigation.
The first unexpected scene followed the documented left-map selection at native (266,305), browser (296.4875,534.1233333333333). At step 11008 it shows the trail map 1. Arrival, 1100 A.D., Dec 1123 A.D., and Not available in the demo. It is not Zephyr scenario selection or world gameplay. All stepping/input stopped there; only quit and recovery followed. No alternative tower guess, repeated click, native scenario Start, ordinary world action, second browser or reload occurred. The next runtime task must correct the menu-route interpretation from the retained actual picture before attempting Zephyr; the present run does not prove scenario/world availability.
The browser closed normally at 06:07:47.537Z, well before the 06:15 hard close. Full-SHA recovery verifies 220 closed logical files, 172 sequential per-guest ACKs totaling 11008 steps (maximum 64), 1033 served-file pins and exactly three balanced clicks. Three independent constructor-field removal mutations each fail the real construction regression. The final expanded focused fixture also passes on the retained runtime after closure. Actual exec 06:09:22.104Z confirms Chrome/driver absent and all 2415 staged pins unchanged; API state is idle, healthy and hydrated. Source custody uses exact Git SHA, relevant binary diffs and owned new-file patches, not source snapshots or repeated media/modules. The assigned box remains RUNNING; expiry is 2026-11-04T06:21:54.275Z and shutdown ownership remains with the coordinator.