Diablo II field/combat attempt — 2026-11-06

First blocker: the field exit was not located and traversed within the one bounded original. Field navigation and combat remain UNKNOWN. The personally reviewed route progresses from the wagon through the waypoint/forge area, along the inside of the palisade, around its bend and toward a dirt opening beside a stone wall and torch. Final captures still show camp structures. No bridge crossing, Blood Moor entry label or identified enemy was observed. No attack against an enemy was dispatched; no attack animation, damage or death is proved. This does not advance GLD3D-CORPUS-27-20261006 to field/combat qualification.

Evidence is scratch/runs/20261106-diablo2-field-combat/. Relevant images are review/town-before.png, road-02-later.png, palisade-05-wait.png, corridor-10-wait.png, opening-fresh.png, road-gap-13-wait.png, final-position.png and final-idle.png in that review directory, with matching capture hashes, states and capture-reviews.json. Labels such as “settled”, “arrived” and “idle” are operation names, not findings: several still show walking and terrain scroll. The final twenty-second read-only wait still changes terrain position after an ordinary click at the reviewed hero feet. Settled final arrival is unverified. The life orb appears red-filled, but no numerical health or combat-related health change is established.

The unchanged recoverable numbered queue and ordinary keyboard bridge were reused after nine transport controls, six actual-executor recovery controls and a balanced eight-event keyboard check passed. Production source/modules/media matched the preceding software-town run at preparation; its unchanged keyboard control evidence is referenced in reused-generated-controls.json. This original uses WebGL only. Five stale commands were consumed and refused before dispatch with zero effects. Fresh personally reviewed captures and new IDs continued on the same original queue. The 12-second scene guard, current registered-app check, capture hash review, duplicate-ID refusal and terminal partial/UNKNOWN semantics remain intact. Twenty-three ordinary inputs were admitted; capture waits and normal quit are separately recorded. No blind coordinate sequence was used.

Ordinary H, prompted by visible HELP [H], opens the game's help screen after a settling wait. The pixels document Ctrl to run, Shift to attack standing, Tab for automap and the HUD Run/Walk Toggle. A second ordinary H closes help. One ordinary click used the documented HUD toggle; a running-mode change is not proved. An exploratory mini-panel click initially described as a compass icon actually opens Game Menu [Esc], as its tooltip and settled menu show. Ordinary Escape returns to the world without choosing Save and Exit. This correction is retained in the capture reviews; no automap inspection is claimed.

Tested source main commit is 0638d4f128e8e54d74598cbb2bb7c32654926f91, with the recorded relevant dirty diff and new-file patch. All 592 runtime pins match remotely before and after execution; the genuine installed25 files match their established hashes. All 195 pinned successful HTTP responses/bundles match. Four live Worker bytecode captures match standard Wasm 6cd858302895de91df5af17e3a3742281e31f369ddb6528d7b96252b3423caac. Compat was provisioned only. A later shared-tree change to lib/host-imports.js prevents an unchanged-local-tree claim; its tested bytes are verified directly from the recorded Git commit, which matches that pin. No source archive is needed.

Actual render owner 2C62699CB4A56BA845A63D4767048FED, endpoint 1, is legacy/WebGL. Town-before → final-idle adapter draws advance 26,722 → 147,287 and completed fences 5,995 → 14,790. Owning-worker endpoint observations are retained throughout; endpoint errors, software draws and fallback-software draws remain zero. These establish owner progress alongside the reviewed pixels, not physical GPU timing, FPS or performance. Environment is Chrome 151.0.7922.108, V8 15.1.206.16, isolated guest Workers, 1024×768 viewport and 640×480 game buffer.

Fresh boat bx_mq773vtk was created after persisting/fsyncing its UUID Idempotency-Key. Initial expiry was 2026-11-07 00:47:31.255 UTC. The single original began 2026-11-06 23:48:39.772 UTC. Chrome exited zero at 00:16:30.880; normal cleanup completed 00:16:30.903. Controller and Chrome are absent, both private ports refuse connections, and the profile/writer lock are absent. All 458 inventoried run files were retrieved or matched to retained inputs and captures. After retrieval, delegated normal stop stop_9411ed9b5eff64a2 completed 00:17:20.011, forced=false, error=null; state is archived, active expiry null. Start through confirmed stop took 1,720.239 seconds, within the retained 35-minute cap and the authorized 40 minutes.

No production repair, local runtime/build, guest memory/config/save edit, media substitute, second original/backend, resume, held-operation retry, HTTP403, automated safety flag, benchmark or full27/parity claim occurred. Free disk stayed above 2 GB. Only this findings note is committed. Git plus the relevant/input patches, media paths/hashes, unique module, captures and receipts preserve recovery. Artifacts precede result.json. Next work would need a separately authorized attempt that identifies the native exit before spending the traversal window; this worker does not launch it. Files and boat ownership are released at completion.