Allow cellular spawn and actions together
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (checks) (push) Failing after 39s
Foundation / checks (ecs) (push) Successful in 1m58s
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 (postgres) (push) Canceled after 5s
Foundation / checks (client) (push) Canceled after 2m19s
Foundation / checks (network) (push) Canceled after 1m43s

This commit is contained in:
dingo
2026-10-11 00:52:51 -04:00
parent 704ce0f2c8
commit 9c84c8f5b4
5 changed files with 65 additions and 3 deletions
+12
View File
@@ -6452,3 +6452,15 @@ The focused session-batch executable was manually compiled and run with GCC
sanitizers and CI are pending. The existing unrelated initializer warning in
`cellular_region_step.cpp:29` is demoted for these manual builds. This builder
is not yet wired into an `evo-server` cellular tick loop.
## 2026-10-11 — M11.3d-7k v5/v7 session admission
The region session host can now admit v5 life requests and v7 cellular actions
in the same configuration. A v5 connection remains v5; a v7 connection carries
reliable cellular actions. The QUIC session test covers both clients logged in
at one host and confirms a spawn response plus a carried cellular action.
GCC 13.2 strict-warning syntax checks pass for `region_sessions.cpp` and
`tests/quic_sessions.cpp`; `git diff --check` passes. QUIC runtime tests, the
full network preset, and CI remain pending. No wire layout changed in this
subsection.