Add M10.8c-2 client handoff switch and evo-server handoff configuration
Foundation / checks (deploy) (push) Successful in 3m20s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (client) (push) Failing after 12m9s
Foundation / checks (network) (push) Successful in 13m2s
Foundation / checks (tsan) (push) Successful in 8m7s
Foundation / checks (checks) (push) Successful in 32m1s
Foundation / checks (postgres) (push) Successful in 42m43s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

ADR-0096. The engineering client follows a HandoffOffer into the next region
with its ticket (no grant, no pause, the view kept) and a Redirect to the
probe's owner, picking grants by region claim in rising serial order.
evo-server gains --m10-area, --m10-handoff-key and --m10-neighbour (dev
only), wiring the PostgreSQL probe and handoff ledgers; the probe tool writes
multi-region bundles and reports handoffs and redirects.

Refreshes the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 21:56:42 -04:00
co-authored by Claude Opus 5.5
parent a7a3d12283
commit dabeee8e8b
14 changed files with 635 additions and 129 deletions
+2 -1
View File
@@ -538,7 +538,8 @@ handoff ADR; EXPERIMENT durable probe records): 10.8a schema v12 probe records a
transfer state machine with a PostgreSQL fault matrix done; 10.8b signed handoff tickets and
ticket admission (durable stage, commit and control move) done; 10.8c-1 session protocol v4,
durable probes in sessions, edge crossing, ghosts (schema v13) and a two-region loopback test
done; 10.8c-2 client switch and server configuration, 10.8d two-process kill tests follow. 10.9 planned.
done; 10.8c-2 client switch (offers, redirects, multi-region grants) and evo-server/probe
configuration done; 10.8d two-process kill tests follow. 10.9 planned.
**Entry:** M9 client/session evidence and M7/M8 dev/stage durability. Read
NETWORK_ARCHITECTURE, PERSISTENCE_ARCHITECTURE and ADR-0017. The M9 transport is
+4 -1
View File
@@ -84,7 +84,10 @@ the session. M10.8c-1 wires the regions:
- the destination shows arriving probes as ghosts (schema v13) and opens the marker where it
crossed.
Next: 10.8c-2, the client switch and server configuration.
M10.8c-2 has the engineering client follow crossings (ticket, no loading screen) and
redirects, with grants picked by region in rising serial order. evo-server gains
`--m10-area`, `--m10-handoff-key` and `--m10-neighbour`; the probe tool writes multi-region
bundles. Next: 10.8d, two evo-server processes on PostgreSQL with kills at each step.
## Previous gate - 2026-10-02
+33
View File
@@ -187,3 +187,36 @@ controllable before M11.
It passed 3 times in a row on Linux and also passes on Windows.
- Not yet: the engineering client's switch (offer, redirect, multi-region grants),
evo-server and probe configuration (10.8c-2), and real processes on PostgreSQL (10.8d).
## M10.8c-2 client switch and configuration (2026-10-06)
- **Engineering client** (`apps/evo-client/remote_session.hpp`):
- On `Close(handed_off)` after a HandoffOffer it learns the destination's address (one
lookup), keeps the frozen view, uses no grant and connects at once with the ticket. The
panel shows "handing off", then the region and the count of crossings.
- On `Close(moved)` after a Redirect it connects to the owner with a grant for that
region.
- Grants are picked by their region claim. They are used in rising serial order
world-wide (durable control refuses a serial not above the newest), and a grant
outdated by one already used is discarded.
- A new region or epoch resets the views.
- **evo-server** (dev only, with the M10 listener):
- `--m10-area X0,Y0,X1,Y1`: the region's cells.
- `--m10-handoff-key FILE`: this region's P-256 scalar; the key id is the region id.
- `--m10-neighbour REGION=X0,Y0,X1,Y1=HOST:PORT=SERVER_NAME=PUBLIC_KEY_FILE`: up to 8;
the neighbour's key id is its region id.
A handoff key needs neighbours and an area, and runs with the PostgreSQL probe and
handoff ledgers on the host's connection slot. Without these flags behaviour is as
before (in-memory markers).
- **Probe tool:**
- `grants` accepts `--region` several times (COUNT per region, serials interleaved in
order);
- `keys` makes handoff key pairs too;
- `run` prints `handoff` and `redirect` lines.
- **Evidence:**
- `client-remote-session`: the GUI session crosses into region 2 with the ticket (no
grant used, connected, marker past the border, probe owned there); a second client
with a newer bundle logging in at region 1 is redirected and takes over at region 2.
It passed 3 times in a row on Linux and also passes on Windows.
- The test fixture `tests/fixtures/fake_handoff_world.hpp` (the v12 state machine) is
shared by both handoff tests.
+35
View File
@@ -4823,3 +4823,38 @@ Not done:
Deployed v3 servers refuse v4 clients until redeployed; v12 and v13 need a rebuilt
migrations image.
## 2026-10-06 — M10.8c-2 client switch and handoff configuration (ADR-0096)
Implemented:
- the engineering client follows handoff offers (ticket, no grant, no pause, view kept) and
redirects;
- grants are picked by region claim in rising serial order, and outdated grants are
discarded;
- views reset on a new region;
- evo-server `--m10-area`, `--m10-handoff-key` and `--m10-neighbour` (dev only), wiring the
PostgreSQL probe and handoff ledgers;
- the probe tool's multi-region `grants` and its `handoff`/`redirect` lines;
- the shared fixture `tests/fixtures/fake_handoff_world.hpp`.
Tests:
- `client-remote-session` `crossing_regions`:
- the GUI session walks into region 2 and continues there with the ticket (no grant used,
connected, marker past the border, probe owned by region 2);
- a second client's login at region 1 is redirected to region 2 and takes over.
It passed 3 times in a row on Linux, plus once more after a tidy fix.
Executed:
- **Linux GCC 14:**
- `postgres-check.sh` with QUIC: 21 suites;
- presets `quic` 4/4 and `client-network` 16/16.
- **Linux Clang 19:** clang-tidy 19 on the client app, panels, remote test, probe, QUIC
session test and evo-server `main.cpp` with the bridge (one finding fixed); clang-format
19.
- **Windows MSVC 19.44:** presets `quic` 4/4 and `client-network` 14/14.
Not done:
- real two-process handoffs on PostgreSQL with kills (10.8d);
- a GUI run across regions on evolution-dev (one dev region only; needs v4 and v13
deployed).
+20 -2
View File
@@ -41,5 +41,23 @@ evo-client --connect void.aeternalisgames.com:7400 --server-name NAME --ca dev-c
until the reconnect brings a fresh view. Nothing you press is sent meanwhile.
- Each reconnect uses the next grant. A second client with a bundle for the same account
takes the session over; the first stops (do not share bundles).
- A server on an older session protocol (v1, v2) refuses the client
(`unsupported_version`): deploy a v3 server first.
- A server on an older session protocol (v1-v3) refuses the client
(`unsupported_version`): deploy a v4 server first.
## Two regions (M10.8, ADR-0096, EXPERIMENT)
Regions with adjacent areas hand a probe over when it walks across the edge. The client
follows on its own: the view stays on screen, no grant is used, and the Session panel
counts the crossings. Each region needs:
- `--m10-area X0,Y0,X1,Y1` (its cells);
- `--m10-handoff-key issuer.key` (a pair from `evo-session-probe keys`);
- one `--m10-neighbour REGION=X0,Y0,X1,Y1=HOST:PORT=SERVER_NAME=neighbour.pub` per
neighbour.
All of them need schema v13. Issue bundles with one `--region` per region:
```sh
evo-session-probe grants --issuer-key issuer.key --world 100 --frame 9 --region 1 --region 2 --account <hex> --count 8 --lifetime 3600 --out tester.grants
```
A login at a region that does not own the probe is redirected to the one that does.