Disciples II corrected-hover quest continuation, 17 November 2026

Evidence: scratch/runs/20261117-disciples2-corrected-hover-map-action/.

The newly authorized single fresh original advanced through New Quest, The Search for Timmoria, default Undead Hordes, and default Warrior Lord with Average difficulty to the actual quest introduction. Its Continue intent then exceeded the 500 ms confirmation limit. UNKNOWN permanently closed the controller; independent fallback physical UP acknowledged. No later HTTP, capture, rebind, replay or second original followed. No map action, turn consequence or native Quit is established.

The runtime used published aaf64d847db877d2df308d4c4eac54e82dae6ec2, source SHA-256 dfb7c6ab548382393d98bb352ee591e279da543d55abb6295319e1354f793f61, and module 33ef36c2de1c86ca1302b5659f02bb48f1794dfc4e20945821251198f04cb03e. All 4,581 Git source bodies independently matched; owned patch bytes were zero. Foreign worktree changes were recorded and excluded. Compilation and sealing preceded the fixed 3,600-second native clock, independently prearmed 3,620-second watchdog and 300-second Quit reserve. Main, Worker and child inheritance passed before launch. All 128 original media hashes passed. Only the shipped scenario .sg was present; no imported save, f.sg, media copy, EXE, configuration or clock change was used.

The module and repaired runtime source match the predecessor native proof; only callback-review metadata differs in its source inventory. Reused proofs include native mapping seven cases, queued normal/slow65 recheck/early cancellation, fourteen synchronous BUTTON cases with the retained inventory adapter, and focused transform/guard/SDL/currentquest tests. The original slow65 and unadapted schema failures remain retained. Hashes of 654 predecessor artifacts were reverified. The legacy input-scope baseline failure remains explicit and its assertion was not weakened. No new production change required another build or duplicate native qualification.

Five finite intents confirmed natively in 58.8–161.9 ms and independently released in 119.2–152.3 ms after consumption. Each used a fresh complete personally reviewed menu frame and a new nonce. New Quest confirmed in 67.1 ms; this progress does not prove the hover repair caused the previous timeout.

The introduction Continue intent used canvas (963,620). Its final retained public log shows MOVE and fallback UP at the intended native (780,522), with no corresponding DOWN. The terminal guard state was not queried after timeout. No per-poll timestamps or removal receipt establish the exact queue removal point, native empty-pump delay, or cause of the missed deadline. Bypassing the hover barrier or widening limits would therefore be unjustified; no new semantic repair is claimed. A future investigation needs bounded public pump timing evidence before attributing this failure.

Owned cancellation reaped the native process, watchdog and both supervisor parents with actual zero waits and both EOFs. The sealed holder was hash-verified and normally closed with an actual zero wait. All recorded process identities are absent and the loopback port is closed. This cleanup was host cancellation, not native Quit. No boxes were created: ID/expiry null, state NOT_CREATED, stop receipt N/A. The original authorization is consumed; no retry is authorized by this report.