Add M10.5b snapshot wiring: sessions, evo-server, client and probe
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (client) (push) Successful in 12m40s
Foundation / checks (network) (push) Successful in 11m27s
Foundation / checks (tsan) (push) Successful in 8m6s
Foundation / checks (checks) (push) Successful in 31m54s
Foundation / checks (postgres) (push) Successful in 40m43s
Foundation / server-image (push) Successful in 25s
Foundation / postgres-tools (push) Successful in 1m2s
Foundation / image (push) Successful in 2m32s

RegionSessions owns the replication server: interest and acks per session, a
host-set default interest, and per-tick snapshots sized to each connection's
datagram limit. evo-server builds each interest's view from the region's own
habitat sites (default: the first site, radius 7). RegionSessionClient assembles,
acknowledges and presents snapshots and can change its interest; the probe prints
them. Loopback and real-process evidence. ADR-0093.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 10:47:47 -04:00
co-authored by Claude Opus 5.5
parent e640b6d3a3
commit 33e91458e7
15 changed files with 428 additions and 23 deletions
@@ -58,3 +58,26 @@ are ignored; malformed records, a slice mismatch or disagreeing chunk headers ar
are not needed at this size and are left for measurement (10.9).
- Wiring into RegionSessions, evo-server and the clients is 10.5b; until then v2 messages
exist but no server sends snapshots.
## M10.5b wiring (2026-10-06)
- **RegionSessions** owns the `ReplicationServer`: replication opens with Welcome and
closes with the session; `Interest` arrives on the stream, `SnapshotAck` as a datagram.
The host calls `replicate(tick, source)` once per simulated tick; each session's chunks
are sized to its connection's current datagram limit (no snapshot while the datagram
extension is not negotiated). A refused chunk leaves the snapshot unacknowledged.
- **Default interest:** until a client sends its own, a session has the interest the host
set: evo-server uses the region's first habitat site with radius 7, so a new session
sees the region at once. Clients learn the slice and square from the snapshot itself.
- **evo-server source:** for each distinct interest, the habitat sites of the square in
the slice are queried from the region's own stores (`query_environment`, all fields) and
copied through `present_environment`, the same read-only path as the M9 view; organisms
stay empty (no placed individuals). A failed query sends an empty source and logs once.
- **Client:** `RegionSessionClient` assembles and acknowledges snapshots, exposes the view
and validated presentations, sends `Interest`, and closes the session (protocol) on a
malformed or unpresentable snapshot. Chunks arriving before Welcome are dropped (the
channels are not ordered); the next tick resends.
- **Probe:** `--interest X,Y,Z,R` and `--snapshots N`; one `snapshot` line per applied
snapshot (tick, cells, organisms, bounding square, slice) and `snapshot-bytes`.
- Evidence: the test region's default interest holds one habitat site, so the process test
shows a one-cell view refreshed every tick (40 chunks, 8,888 bytes in 40 ticks); the
225-cell and 32-session figures come from synthetic sources.