KKnD mission selection and stable-camera commands — 2026-11-06
Source preparation completed; runtime is blocked by the required predecessor
releases. No new original session was started. Evidence belongs to
scratch/runs/20261106-kknd-stable-camera-command/. The runtime gate requires
ordered exact FINAL runtime AND file RELEASE ALLBUILDSFINISHED releases for
ArannaSemanticMenu0800, PTCTTextureCorrectness0810 and ConanFirstDrawLifetime0820,
with independently reopened cleanup. KKnDCaps0745 is already FINAL.
The retained authentic demo README.TXT gives left-button selection and movement:
select a unit or drag-select a group, then left-click valid land to order movement.
Right-button dragging fast-scrolls the map and right-click deselects. Arrow keys
scroll; Enter centres the base. These are unsuitable while proving a fixed camera.
The same guide says Options offers a mission briefing summary. The prior right-button
camera shift is consistent with documented game behavior; no emulator discrepancy
has been established and no production repair is proposed.
Personally inspected the predecessor's Evolved menu, mission-entry instructions and four-infantry selection image. The mission-entry image shows building instructions, not a mission title. Clicking visible Walkover text alone did not establish loaded mission identity. The new route must report actual evidence honestly; its filename, an intended menu choice or the demo's recommended mission is not sufficient.
Prepared observation-only adaptations reuse the retained real-origin recovery,
required size/hash rejection checks and actual instantiated owning Worker identity
via guestWorker.link. Window-capture trusted down/up events, completed CDP release
records and renderer button state will establish balanced release. Only left-button
mouse commands are permitted by the prepared run helper. Before/after screenshots
must show a selected unit changing position relative to at least two fixed terrain
landmarks, with a second ordinary response in the same bounded original lifetime.
No tests, build, browser, original session, box or guest modification has run in this assignment during source preparation. Git commit and relevant binary diff, owned new-file patches, and existing media path/size/SHA-256 will preserve recovery; source trees and media are not copied into evidence.
At the 08:49:25 UTC read-only gate check, KKnDCaps0745 had its exact FINAL release; its 27 PIDs were independently absent, three ports refused connections and two profiles were absent. Aranna0800, PTCT0810 and Conan0820 had no matching FINAL releases. Aranna had announced a runtime window of 08:45:32–09:30:32 UTC. A free lock or an elapsed window cannot substitute for the required releases and cleanup. The new original allowance remains unused; no 45-minute active window began.
The prepared helper sources remain unexecuted drafts. A read-only release-check script initially had a Python reserved-keyword syntax error; it was corrected before producing the gate record, without opening a browser or running a guest. No repair or regression testing was warranted because no emulator discrepancy was demonstrated. Documentation whitespace validation passed. The worker releases its own files and observation watcher, leaving predecessor resources untouched.
Next: once all three ordered FINAL releases exist, independently inspect their owned cleanup, refresh source/module/media pins, run the retained required-file recovery checks, then use one bounded original lifetime. Establish loaded mission identity from visible briefing/menu evidence if available, verify selection, order left-button movement well inside the playfield, and compare unit positions with two fixed terrain landmarks plus a second ordinary response. Inspect every claimed image, record release, stop at the first new failure, and clean up owned local resources. This source-only report establishes no additional gameplay, mission, movement, performance or audio result.