Implement M9.3 camera navigation and bounded input intentions

This commit is contained in:
dingo
2026-10-01 17:26:35 -04:00
parent 04c7715646
commit bb0412cd0f
19 changed files with 899 additions and 27 deletions
+8 -8
View File
@@ -2,17 +2,17 @@
## Current gate — 2026-10-01
M9.2 adds an opt-in native `evo-client`, immutable presentation frame contract and
RAII platform/renderer lifecycle ([ADR-0078](adr/0078-native-client-lifecycle.md)).
Resize/pixel scale, focus, minimized/hidden windows, reset/loss and orderly close
are covered by Windows/Linux tests. Direct X11 linking resolves the observed
M9.1 unload allocation issue in repeated sanitizer checks. See
M9.3 adds local-mm pan/zoom camera mapping and bounded sequence/tick input
intentions ([ADR-0079](adr/0079-camera-and-input-intentions.md)). Focus loss,
UI capture/release and saturated event batches cancel held input. WASD controls
an intention indicator; arrows/wheel navigate the presentation fixture. See
[CLIENT.md](engineering/CLIENT.md) and [VALIDATION.md](engineering/VALIDATION.md).
Updated remote Gitea client execution remains unverified locally.
Next: **M9.3**, camera and bounded input intentions. The window displays a static
presentation fixture, not organisms or a connected world. No deployment,
simulation rules, persistent formats or world state changed in M9.2.
Next: **M9.4**, rendering microscopic environment views. The client displays a
camera-controlled fixture, not organisms or a connected world. Its tick is a
local input fixture counter. No deployment, simulation rules, persistent formats
or world state changed in M9.3.
The sections below retain earlier milestone delivery history.