Stronghold current hover diagnostic, 2026-11-04

One original local attempt obtained authentic current Custom Game hover pixels. The evidenced recognition boundary is repaired and tested offline. No Custom Game press, preset, Start, native install, guest write, retry or gameplay occurred. Evidence: scratch/runs/20261104-stronghold-current-hover-diagnostic/.

After MDK's explicit18:53:13 local release, the attempt launched current main ad00f603fc687244bb18bffd6893ab5af4c1ac31 plus the recorded prelaunch binary patch. All2429 filesystem pins,1856 original media paths and164 full-body HTTP preflight pins passed. All1038 actual served responses matched their pins. Original EXE path remains test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe, SHA256 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f. Normal module SHA256 is 78a0b1d61b23428a1ae909d739440ae0de059bbbd84a69a2ad3e4c37471ad664; compatibility module is 99b579cd17b57f94145df92ae6d28110f24fc284d13a1b2c0ebe3596bd10a77f. Media and modules are referenced by existing path/SHA, never copied.

The worker personally viewed the selector, title dialog, main menu, Crusader hover and ChooseType before dependent input. Title/menu original balanced input and ACK guards passed. The composed install-route and ChooseType review passed with current pixels. The sole subsequent original input was a mouse move to native543,292, followed by64 acknowledged steps and drained input. The observation branch then captured and requested personal review before the old exact hover acceptance. It retained the original capture, geometry, presentation, immutable queue, execution owner, freshness, deadline, input telemetry, drainage and ACK guards. Its receipt terminally forbids a press.

browser/route-native-boundary-3.png, step8832, SHA256 4ce3636696bc900f85b97e1bfd7a4039e72c7ffad3d88525e64b8d069fa1d1c0, was personally viewed: right towers highlighted, Custom Game heading and Customize your own Crusader game description visible. The input-free fresh capture is browser/route-native-boundary-4.png, SHA256 4d6e4a46798e276f677a9401445624027d7082e5787018a62a6b0efcdc3e7cb6. The original freshness assertion passed despite unrelated log-panel pixels differing. The historical classifier returns unknown for this authentic hover. No old79-capture audit was repeated, and no synthetic hover was accepted.

The correction compares the same four fixed hover regions with a SHA-pinned authentic historical hover. Every RGB pixel and each clipped40×15 tile counts; 1200×900 geometry and full crop opacity are required. No alignment, scaling, mask, exempt pixel, invented acceptance hash or changed historical helper is used. The Custom Game heading remains exact. Measured differences and bounds:

Region x,y,w,h Changed/error Overall limits Tile limits changed/error
110,315,660,75 113/1804 130/2200 20/450
160,480,260,120 321/7028 360/8500 65/1700
345,630,195,33 0/0 0/0 0/0
240,676,400,25 39/987 50/1300 16/600

The shared route classifier evaluates the complete hover identity before the bounded unhovered ChooseType identity. Both authentic current captures and the historical hover pass. All26 historical routes retain their scenes. Twenty-seven hover pixel negatives reject: each region shifted in five ways, concentrated map/description changed pixels, header tile error, changed exact heading, both unhovered ChooseTypes and a wrong menu scene. Four nonopaque regions and cropped geometry reject. Existing20 before-input negatives pass. Ten actual composed post-move tests reject stale ticks, foreign targets, changed pixels, invalid reviews and unviewed receipts in both ordinary and observation routes, before any dependent down/up. Original source tamper and omitted closure pins still reject. The transport fixture using authentic current hover followed by historical shell passes balanced down/up and the four-shell-sample terminal cap; it is offline evidence, not current gameplay. Both module executable owning callback fixtures, title/menu tests,33 local contract negatives plus an actual foreign child, normal-close fixtures and the locked full build pass.

The mandatory0/1/1 owning observer source remains unchanged and installed before first script. Actual slot0 compile/send/instantiate and exact target evidence is retained. Its callback command scope was never armed because no Custom Game gesture occurred; no live callback or post-press qualification is claimed. The diagnostic ended before the correction was tested. Its terminal route cannot resume, and a retry was not authorized. There is no authentic current post-press scene in this run, so original gameplay remains unproved.

The local contract required720s browser,60s bootstrap,40s command and180s cleanup reserve, with absolute Chrome cutoff21:00Z/cleanup21:03Z. It bound the actual host/boot/PID/start/nonce/run/pins and both module hashes. The correct /tmp/wine-local-runtime.lock serialized the attempt. Normal shutdown now sends CDP Browser.close and waits for actual child exit rather than relying on Puppeteer's potential process-kill fallback. Chrome943381 actually exited0 with signal null at18:57:48.654; quit11 was acknowledged. Owned Node943369 and Chrome were absent, HTTP46387 refused, and the runtime flock was available. The execution wrapper separately returned143, cause unproved; this is not represented as a normal wrapper exit. Prior MDK SIGKILL remains unproved too. The local slot was explicitly released18:58:20 for GLTron. The owned Chrome profile was removed after exit. Box ID/state/expiry are NA; the coordinator owns future boxes and shutdown.

Next is a separately authorized original attempt using the tested correction, with fresh review and all unchanged dependent guards. This run grants no preset, Start, world or hostile-engagement claim. Git SHA plus relevant binary patches preserve both prelaunch and final source states; unique logs/captures are sealed without source trees, snapshots, archives, media or module copies.