Record cellular probe readiness
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s

This commit is contained in:
dingo
2026-10-11 01:23:32 -04:00
parent 108879d2fc
commit b77d98cdcd
3 changed files with 36 additions and 0 deletions
+7
View File
@@ -374,6 +374,13 @@ scoped change before starting the next segment.
startup, controls, scope limits and the human feedback needed to decide
whether the cellular loop merits further investment. It is ready for use
after CI confirms the v8 server/client build.
- Readiness update (2026-10-11): the maintainer reports that the Git checks
passed, `evo-region` is running, and the client connects. This is operator
confirmation of checks and connectivity; it does not establish that the v8
cellular path was selected or that life creation, movement, feeding and the
on-screen perception work in a hands-on session. Those outcomes and the
exploratory notes remain the 11.3e exit evidence. The 11.4 mutation expansion
stays behind that probe so its feedback can affect the next design decisions.
## Exit boundary
+17
View File
@@ -6520,3 +6520,20 @@ pending in CI.
The M11.3 cellular probe checklist was added for the first human session. It
does not count as live-region or usability evidence; those results must be
recorded after the operator confirms CI and runs the dev-region probe.
## 2026-10-11 — M11.3e deployment readiness report
The maintainer reports that the Git checks passed, the development `evo-region`
is up, and the client can connect. This is recorded as operator confirmation;
the CI run and checked revision were not independently available through the
current tools. A connection alone does not confirm the v8 cellular mode,
allocator-backed first life, movement, feeding, owner perception, or the human
playtest observations.
The local `build/client-network/evo-client.exe` predates the v8 client changes.
The Windows `client-network` build still stalls at Ninja's glob recheck. Running
the generated `VerifyGlobs.cmake` directly under both installed CMake versions
completed with no source-list mismatch, but did not resolve the Ninja hang. No
fresh client binary or local live cellular probe is claimed. The next gate is
the maintainer's short session using [the probe checklist](../playtests/M11_3_CELLULAR_PROBE.md);
11.4 remains gated on its feedback.