2 Commits

Include renames

Author	SHA1	Message	Date
Omar SobhandClaude Opus 5	72ba4ba523	fix(ci): two runs stomped each other, and the logs blamed the tests ... Runs 490 and 491 both failed `test`. Neither failure was in the code. Runs 490 and 491 started 16 minutes apart and a full suite takes longer than that, so they overlapped. The first thing a run does is `docker rm -fv cm-ci-pg` — a name every run shared — so the newer run deleted the older run's database mid-suite. Both failed, and the failures read as test failures. Verified before changing anything: the exact CI command, on gw-04, against the same warm cargo volumes and a Postgres started exactly as CI starts it, passes on 128b423 — as do `npm ci`, `typecheck` and `vitest` on that host. The code was never the problem. - `concurrency: deploy-${{ gitea.ref }}` with cancel-in-progress, so runs on a ref serialize. A superseded run tests a commit that is no longer the tip; finishing it costs 20 minutes to learn something that no longer matters. - the test Postgres is named per run, so overlap cannot corrupt a run even if the concurrency guard is later removed. Impossible rather than unlikely. - `--shm-size=1g` on it. Docker defaults /dev/shm to 64MB and cm-testkit creates a database per test; Postgres exhausts its parallel-query segments mid-run and reports `could not resize shared memory segment` DURING MIGRATIONS, which reads like a schema fault. Hit locally on 2026-08-19; scripts/test-server.sh already carries the same flag. The lesson is the session's own: I twice inferred a cause from a red build without reading the failure — first node, then dash — and both were wrong. The answer came from running the job on the runner's own host. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-20 07:00:10 -07:00
Omar SobhandClaude Opus 5	b653dbfe72	docs: hand-off note for the next session ... Records the state of the tree, the one step not taken (the stream-json runtime image is built and never deployed, so no mission has confirmed tool.call rows end to end), the ordered next steps, the decisions that are the operator's, and what was deliberately left undone with reasons. Also records the two corrections made this session — "missions can't call tools" was wrong, and raw test counts are a bad coverage metric — because both were confidently stated here before being checked. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-20 05:24:43 -07:00