KKnD ordinary left-button commands — 2026-11-06
The single original session reached visible Evolved gameplay and Escape opened
its ordinary Options menu. The briefing request supplied no visible mission title,
and the subsequent Return to Game click did not dismiss the menu. Input stopped
at that first clear new failure. Loaded mission identity, new unit selection,
commanded displacement and a second unit-command response remain unverified.
No emulator discrepancy or production repair is established. Evidence is in
scratch/runs/20261106-kknd-left-command-gameplay/.
The authentic registered demo README (16,126 bytes, SHA-256
b814f64adb4ae9a84b962a762c241e934efc9019559f173b0b7b3f44ad1c9c13)
documents left-button selection, drag selection and destination movement.
Right-drag fast-scrolls; right-click deselects. The prior right-button camera shift
therefore establishes no emulator discrepancy. The Options menu offers a mission
briefing summary; that is the intended route to identify the loaded mission.
No mission label follows merely from an intended menu click.
Personally inspected predecessor evolved-menu.png, mission-entry.png and
group-selection.png: visible Evolved menu, building instructions and selected
infantry respectively. None proves the loaded mission's name or unit displacement.
Retained commands 20–24 show drag selection followed by the right-button action.
Run-only helpers reused the complete registered fixture, real-origin
DDRAW recovery, required size/hash rejecting controls and actual owning Worker
identity through guestWorker.link, slot/endpoint and instantiated CDP bytecode.
They recorded trusted window-capture input edges, completed releases and renderer
button state. No right-button input was issued. Before the original, a generated
page exercised the exact adapted coordinate/command helpers with ordinary and
letterboxed presentation, trusted click/drag/key down/up, final zero buttons and
rejection of a right-button request before button edges. This generated page had
no emulator, Worker or guest instance. Its owned browser cleanup was independently
verified before opening the original.
The required ordered exact FINAL releases for PTCT0810, Conan0820 and
LegacyMipFixture0900 were observed before acquisition. Including Aranna0800,
independent cleanup reopened 620 absent PIDs, 37 refused ports and 34 absent
profiles. Four locks were free and no heavy runtime was present. Conan's cleanup
uses processes, not pids: the initial checker kept the gate closed; a premature
board PASS claim was corrected append-only before checking all 438 Conan PIDs.
No runtime ran during that source-only correction or queue wait.
The immutable runtime window was 09:59:27.939525–10:44:27.939525 UTC, including
cleanup. Unchanged 16-file media hashes, the registered manifest and authentic
DDRAW recovery passed. Actual production host.loadFiles rejected wrong required
size and SHA-256 before browser creation. Source/mirror/module identity and actual
HTTP source/module responses passed. The owning CPU Worker was bound through
guestWorker.link slot 0/endpoint 1, thread 1, 536,870,912-byte memory and actual
instantiated CDP bytecode at startup and terminal capture. Its standard module was
2,178,624 bytes, SHA-256
3b7511d12f3e8d364eb6bf29cdeed8b53af07abc53644d4f186e46f8620da149.
Actual parent VFS DDRAW and KKnD executable hashes matched the retained authentic
pins; DDRAW was not marked a static module.
Postprocessing found four shared library files changed since launch. Their tested
bytes recover exactly from the recorded launch commit, and all actual browser
responses matched the launch pins. postrun-source-drift.json distinguishes these
later shared edits from this run; they were not edited or retested by this worker.
The original opened at 10:00:17 UTC. Personally inspected startup-01.png,
mission-menu.png, evolved-menu.png, mission-choice.png, mission-entry.png
and gameplay-entry.png. The route clicked New Missions, switched to Evolved,
clicked the visible Walkover text and OK, and continued past building instructions.
That sequence establishes an intended menu choice, not the loaded mission name.
The gameplay image shows the Evolved base and infantry. Escape at 10:02:48 opened
the reviewed game-options.png menu over the same scene.
The left click on Mission Briefing at native (320,166), 10:03:09.819, supplied no
visible title in mission-briefing.png; audio is unqualified, so this absence alone
is not classified as an input defect. The documented Return to Game click at
native (320,190), 10:04:10.729, also left the menu visible in the personally reviewed
10:04:22 capture. Despite its name, before-selection.png is that stopped menu,
not a selection or movement image. This is the first clear new failure. Only
read-only state/VFS observations and harness quit followed; no retry, Escape
fallback, unit command, restart, forced state or speculative repair followed.
The original closed at 10:05:24.632. terminal.png was also personally inspected.
balanced-release.json proves seven trusted mouse-down/up pairs and one trusted
Escape down/up pair, seven completed mouse releases, one completed key release
and terminal renderer buttons zero. The parent VFS handle observation retains
mute_16.lvl and mute.slv paths without asserting they identify Walkover. All 11
images, including the blank generated control page, were inspected; there is no
new unit-selection or displacement claim. FPS and audio remain unqualified.
Owned cleanup passed at 10:06:07: 26 absent PIDs, four refused ports, two absent
profiles and four free locks, with disk above the required floor. Browser log says
CLOSED worker completion; the tool reported process exit 143, which is retained
without treating it as a guest crash. No boxes were assigned (ID/state/expiry N/A).
Exact Git SHA, relevant binary diff, owned helper/doc patches and existing media
path/hash references preserve recovery without source trees or media archives.
No production changes were made; no additional emulator regression or full build
was required. The prior fixture worker's locked build is not claimed as this
worker's test.
Next requires a separately authorized original that resolves the ordinary in-game Options-menu click boundary before attempting fixed-terrain movement. Inspect its actual input consumption before proposing any repair. This stopped assignment authorizes no further runtime or stopped-lane retry.