Add primitive life calls to the session client
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (postgres) (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 2m43s
Foundation / checks (network) (push) Canceled after 39s
Foundation / checks (client) (push) Canceled after 2m49s

This commit is contained in:
dingo
2026-10-10 20:52:32 -04:00
parent 0bb8b50c9c
commit 3277b8f3cd
7 changed files with 193 additions and 56 deletions
+5 -3
View File
@@ -124,9 +124,11 @@ Local checks do not close ADR-0097's reference-worker qualification.
requires durable account control and accepts v5 only, while other region
listeners remain v4-only. Life requests are tied to the admitted session,
current epoch and authenticated account-control generation, then call the
primitive host; query calls its read-only path. The QUIC contract test covers
v5 Hello, Welcome, durable-generation binding, receipt and outcome. Runtime
process/PostgreSQL qualification remains pending CI.
primitive host; query calls its read-only path. The session client and headless
probe have opt-in v5 request/query calls; v4 remains the default, and primitive
v5 refuses the M10 action/movement/interest path. QUIC contract tests cover v5
Hello, Welcome, durable-generation binding, receipt, outcome and read-only query.
Runtime process/PostgreSQL qualification remains pending CI.
- Cross-region owner routing and reconnect-to-existing-life are not complete.
The accepted v5 outcome has no owner-region/address field, while the delivery
row requires routing. The host can identify a different reservation owner but
+14
View File
@@ -5799,3 +5799,17 @@ full `evo-server` compilation and real PostgreSQL process results await CI.
Cross-region routing remains incomplete because the accepted v5 outcome does not
carry an owner region/address; see the delivery plan. No deployed world was provisioned
or changed.
## 2026-10-10 — M11.2d-6 client and probe callers (CI pending)
`RegionSessionClientConfig` now selects v4 or v5 explicitly (v4 default). The client
encodes Hello and stream calls in its selected version, collects primitive-life
receipts/outcomes, and exposes create/query methods only for v5. M10 movement, action,
and interest methods are unavailable in v5. `evo-session-probe` accepts `--protocol v5`,
`--new-life ID` and `--life-query ID`, prints replies, retries unresolved exact requests,
and rejects combinations with M10 actions or movement options. The QUIC session test
now exercises these client APIs end to end with a durable-control fake.
Targeted MSVC Release/NDEBUG compilation of the modified session client, QUIC test and
probe, manual relink of the test/probe, and `ctest --preset quic` passed (5/5). Formatting
and `git diff --check` passed. Full server/process/PostgreSQL qualification remains in CI.