Document the first cellular playtest
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 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
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:15:27 -04:00
parent 1bba54ebd8
commit 108879d2fc
3 changed files with 59 additions and 0 deletions
+4
View File
@@ -370,6 +370,10 @@ scoped change before starting the next segment.
markers, lists their exact perceived stocks, and lets the player select a
patch for continuous feeding. The client build and live-region probe still
need verification before this segment can be called playable.
- 11.3e-4: [the probe checklist](../playtests/M11_3_CELLULAR_PROBE.md) records
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.
## Exit boundary
+4
View File
@@ -6516,3 +6516,7 @@ result. It is not counted as a build or test result. QUIC runtime, PostgreSQL
CI, and the real-region player probe remain pending. `clang-format` is not
installed in this Windows environment, so formatting validation is also
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.