Upgrade cellular client to v10 with readable play and assisted steering

This commit is contained in:
dingo
2026-10-14 19:53:28 -04:00
parent 75b8bbb333
commit 68958a9e54
21 changed files with 1603 additions and 93 deletions
+10
View File
@@ -1,5 +1,15 @@
# Project status and next steps
## Client update - 2026-10-14 (v10)
The desktop cellular client now negotiates v10, exposes mutations with funded
costs, engulf/bud feedback, reserves, death and restart, and retains unresolved
requests through reconnect. Automatic feeding, adjustable/precision steering,
food approach assistance and a responsive teal interface address playtest
usability. See [CLIENT](engineering/CLIENT.md) and the validation entry for
checks and remaining live-play/hardware qualification. No deployment or world
state change is part of this client update.
## Current gate - 2026-10-11 (M11.3 exploratory probe)
The maintainer reports that the Git checks passed, `evo-region` is running, and
+66 -2
View File
@@ -2,8 +2,9 @@
This opens a resizable native window showing camera-controlled environment habitats
and organisms either from a local in-memory fixture authority or from one dev
region over an authenticated dev session. It does not run an ecosystem locally,
predict remote state or implement cellular gameplay.
region over an authenticated dev session. Cellular play uses the authoritative
v10 server; the client presents observations and sends intentions. The separate
engineering motion probe predicts only its synthetic marker.
Contract: [client architecture](../architecture/CLIENT_ARCHITECTURE.md), ADR-0078.
Camera/input: [contracts and limits](CAMERA_INPUT.md), ADR-0079.
Environment: [presentation and encodings](ENVIRONMENT_RENDERING.md), ADR-0080.
@@ -28,6 +29,69 @@ short notifications expire and can be dismissed.
## Build and run
### Cellular v10
Choose **Cellular play (v10)** before connecting, or add `--cellular` to the
connection command. For the current M11.9 DEV opening use grants for world 100,
region 4 and fresh playtest accounts (ADR-0123). The client does not deploy or
provision a region.
- **Cell:** energy and C/N/P/other reserves, latest maintenance/movement/intake,
and Engulf/Bud buttons. Engulf and Bud are individual requests; automatic feeding
resumes after their action tick. The server chooses prey and funds/places descendants. Last observed
engulf/bud feedback stays visible with its tick, even after later idle ticks.
- **Food:** automatic feeding defaults on and targets the first stocked, contacted
patch in the owner's ordered view. Manual selection disables auto-feed; Stop
feeding disables it too. Speed (1-100%), precision (20% of selected speed), and
Slow near food are local intention preferences. The latter defaults on and limits
approach speed toward 500 um/s within 1 mm of a stocked patch, recomputed from the
observed phenotype. Protocol integer precision can exceed that cap at extreme
speeds. These preferences never change authoritative speed, contact or intake.
- **Evolution:** choose one unranked mutation from the owner's earned offer.
The current development-2 cellular trial uses per-second capability rates and
maintenance; mass is in femtograms. Plain-language descriptions explain each
capability change. Construction energy and all four matter costs use the amended
v10 candidate records (ADR-0129); choices are disabled when current reserves cannot
fund them. The server rechecks funding when the request commits.
- **Life ended:** the server's cause, when delivered, and **Start new life**.
Each new life uses a new request ID. Duplicate clicks and reconnects reuse the
outstanding request, and held world input is cleared while no current life is
available. A missing view alone is never presented as a known death.
- **Log:** the last eight discrete requests and optional engineering panels.
Sent/admitted are distinct from committed. A committed engulf/bud intention
does not itself prove biological success; the tick feedback reports its effect.
The dark teal UI uses the existing embedded scalable font. At narrow sizes the
Evolution panel becomes the **Life** tab; panels remain within the viewport and
scroll vertically. Existing Ctrl+= / Ctrl+- scaling and rebindable movement apply.
Food patches have a thin contact boundary and a stock marker, with amber for the
current target and dimming while disconnected. The camera starts at a closer 6 mm
view and keeps the followed cell beside the journal. Organism shapes and biological
colour encodings remain those of ADR-0081 for every controller.
One discrete request is outstanding at a time. During an automatic reconnect its
ID and original payload stay in memory. Bud/engulf recovery queries the original
action; mutation recovery repeats the exact selection. A lost reply remains
unresolved until an authoritative final result arrives. **Keep result as unknown**
retains it in the bounded record and permits another explicit request; it does
not cancel the original. Request history is not persisted across app exit or an
explicit disconnect to the launcher.
Existing protocol limits: a mutation result lost across a server restart may
remain unresolved (the host's final-choice replay cache is transient); type 27
death notices are not a historical death query. Automatic feeding uses observed
contact, so a patch crossed entirely between observations can still be missed;
slowing near food reduces that risk without predicting authority.
Coordinate contract discrepancy found during this work: the cellular bridge sends
ADR-0102 lower-left footprint coordinates through the general presentation's
centre-offset fields. Assistance deliberately interprets only cellular-session
coordinates as the bridge sends them. Renderer/bridge geometry changes are deferred:
a future scoped contract amendment should either carry an explicit coordinate
convention or consistently convert the cellular presentation to centres, updating
contact assistance, picking and replication tests together. This upgrade does not
silently change the shared organism geometry contract.
After [explicit SDL preparation](CLIENT_DEPENDENCIES.md), in a compiler shell:
```sh
+36
View File
@@ -1,5 +1,41 @@
# M9.8b/c UI state, launcher and event bounds
## Cellular v10 application state
`apps/evo-client/cellular_play.hpp` owns toolkit-independent presentation state:
the current owner life/offer, latest death notice, one outstanding discrete action,
and at most eight completed or unresolved records. It never changes biology.
Receipts are admission only; outcomes settle a request. A refused retry cannot
disprove a lost original reply. Mutation `not_ready` may mean an uncertain durable
reservation, so it remains unresolved. IDs never wrap; stale offers, dead lives,
unfresh sessions and duplicate clicks cannot submit new choices.
Reconnect drops the offer until a fresh owner view, cancels unsent queued actions,
and retains sent requests for reconciliation. Life changes cannot carry a queued
action to the new life. Delayed final replies can update retained unknown records.
New lives receive new birth request IDs; retries of an outstanding birth keep its
ID. Death messages are deduplicated so a retained notice cannot end a later life.
Meaningful engulf/bud diagnostics retain their observed tick and reset on life
change. UI does not infer action success from a receipt, empty view or vanished offer.
`cellular_controls.hpp` selects only stocked patches in observed contact, scales
movement intentions for speed/precision/food assistance, and compares every mutation
cost channel with the displayed reserve. `cellular_scene.hpp` renders each patch
in at most three clipped rectangles; the application reserves that worst-case
budget before drawing organisms. No dependency or simulation rule changes.
The v10 panels consume this state and return actions; the app owns session sends.
Cell/Food/Log tabs and a separate Evolution panel replace the default engineering
panels in cellular mode. A narrow viewport moves evolution to a Life tab. Log can
show the existing engineering panels. The existing platform adapter owns the
palette, rounded geometry, embedded font and input capture. `client-ui-model`,
`client-remote-session` and `client-panels` exercise state, loopback v10 delivery,
production widget clicks, duplicate suppression and bounded layout under NDEBUG.
`evo-client-panel-tests OUTPUT_DIRECTORY` additionally saves actual rendered
review BMPs at 640x480, 960x640 and 1280x800, including the death screen; those use
explicit test presentation values and are not evidence of a live DEV playtest.
Owned, toolkit-independent state; all calls on the client main thread. No authority
or simulation state. Time is explicit monotonic milliseconds supplied by the host.
+3 -2
View File
@@ -28,8 +28,9 @@ outcomes. The UI adds a responsive cellular HUD and dark teal theme using the
existing toolkit/font. See [CLIENT](CLIENT.md) for operation and protocol limits.
Human accessibility/hardware checks and first-session/repeated-life observations
remain. Existing v10 signals do not provide detailed engulf refusals, full mutation
prices, or historical death/result recovery across every server restart.
remain. The amended v10 signals now display detailed engulf refusals and mutation
prices, with affordability checks. Historical death/result recovery across every
server restart remains a protocol limitation.
## Progress
+35
View File
@@ -7494,3 +7494,38 @@ Executed locally: MSVC Debug 69/69, network 75/75, client-network protocol/QUIC/
session/cellular 15/15 (`evo-client.exe` was in use and not relinked); the WSL
PostgreSQL C++ suite; g++-14 `-Werror -Wshadow` and clang-tidy-19 on the changed
sources and server main; clang-format 19.1.5.
## 2026-10-14 — desktop v10 play flow and presentation
Client-only integration of ADR-0121/0125/0127/0129, including the amended 64-byte
mutation candidates: choice costs/affordability, per-channel reserves, latched
engulf/bud diagnostics, death and restart. Discrete requests preserve their exact
identity through reconnect and keep uncertain results explicit. Automatic feeding
and speed/precision/food assistance send bounded intentions only. Responsive teal
panels, closer framing and three-rectangle food patches use existing dependencies.
Executed locally:
- MSVC Release/NDEBUG `tools/windows-check.ps1 -Preset client-package -Action check`:
17/17 passed (117.56 s), including v6-v10 codec, QUIC sessions, remote-session
recovery, production panel interaction and client smoke/lifecycle checks.
- WSL Ubuntu Clang 19 Release warnings-as-errors build of the client and changed
tests; `ctest --test-dir build/tidy-client-network -R
'client-(ui-model|panels|remote-session)' --output-on-failure`: 3/3 (37.96 s).
- Clang 19 ASan/UBSan `client-asan`: UI model, panels and lifecycle 3/3 (27.21 s).
- clang-tidy-19 on changed client translation units, with app headers included:
no owned-code findings; the final model/panel rerun also passed.
- Repository `format-check` with clang-format 19 and `git diff --check` passed.
- Production SDL/ImGui panels rendered with explicit test observations at 640x480,
960x640 and 1280x800, plus death screen. Screenshots inspected in
`build/v10-review`; UI tests cover mutation/bud/restart clicks, disabled
unaffordable choices, duplicate suppression, clipping and scroll bounds.
Limits: these are loopback and synthetic presentation checks, not a live DEV
playtest or hardware/DPI/accessibility qualification. The existing client-network
executable was locked by running client sessions; those were left running and the
separate client-package preset validated the Windows executable. Initial sandboxed
Ninja subprocess startup required rerunning the authorized build outside the
sandbox. No new dependency, simulation version/golden, deployment or World0 change.
The existing cellular lower-left versus general presentation centre-coordinate
discrepancy and proposed scoped resolution are recorded in CLIENT.md; shared
organism geometry was not expanded as part of this gate.
@@ -10,9 +10,10 @@ trial value (ADR-0098, ADR-0120, ADR-0124, ADR-0125, ADR-0128).
- A DEV region provisioned with the `cellular-v4` opening (rules 5: engulfment,
detritus, budding wildlife, offline freeze) on a server image that passed CI.
- An engineering client with the v10 path: movement, feeding, engulf, bud, the
mutation offer and chooser, and the death and restart flow. Those screens are the
maintainer's (M11.8 client half); a session without them tests less, and the
notes must say which were present.
mutation offer and chooser, and the death and restart flow. These screens are now
implemented (see CLIENT.md), including amended v10 costs and engulf reasons.
Record the client build and steering/feeding assistance settings; older clients
test less, and the notes must say which screens were present.
- A fresh grant bundle per participant (`renew-dev-m10.sh` output) and a three-hour
session window.