mosaicstack/stack
25
0 Fork 1
Code Issues 403 Pull Requests 13 Packages Projects Releases 15 Wiki Activity

row 250 (Vikunja #450): README lists R13 for cohort.test.mjs (sage-2082)

Browse Source
This commit is contained in:
jason.woltje committed 2026-10-21 14:14:17 -05:00
1 parent 156dce5193
commit e9cfd92f89
2 files changed
+6 -5
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

agents/gizmoduck/work/queue-250/BUILD.md
+5 -4
View File
@@ -78,11 +78,12 @@ was false. Now an `events()` answer that isn't `ok` is returned as it is, with t
- K15 already covers a stop, as opposed to a release, with `events` unavailable: the shim gone, the file
mode 000, or `engine` missing, each ending `uncertain` with its reason.
## Follow-up outside the files owned
## File added beyond the brief
packages/conversation/README.md:599 lists "R1–R3, R5–R12" for cohort.test.mjs. With R13 that should
read "R1–R3, R5–R13". The README isn't in the brief's files, so I left it.
packages/conversation/README.md:599 listed "R1–R3, R5–R12" for cohort.test.mjs. With R13 it now reads
"R1–R3, R5–R13". The brief's files don't include the README. Sage added it to this row in sage-2082.
## Runs
None yet. They need Sage's slot.
None yet. They need Sage's slot. Sage's sage-2082 says the run is on the pushed candidate in a clean
worktree, and that it adds the control-board suite whole, so it counts as the gate run.
packages/conversation/README.md
+1 -1
View File
@@ -596,7 +596,7 @@ no prompt:
| `claim.test.mjs` | W1–W17, W20, G1–G3: the writer claim, crash barriers, the guard |
| `races.test.mjs` | H1–H4, H9–H23: takeover, Interrupt and force stop, retries, incarnations |
| `turns.test.mjs` | N1–N25, N24b: the turn tracker against the fake engine's Pi behaviors; the engine seal and environment |
| `cohort.test.mjs` | K1–K19, R1–R3, R5–R12, E1–E6: scopes, force stop, proofs, recovery, eligibility, the scope's environment, scope release and its retry after a crash, the engine-exit stop (needs a systemd user manager) |
| `cohort.test.mjs` | K1–K19, R1–R3, R5–R13, E1–E6: scopes, force stop, proofs, recovery, eligibility, the scope's environment, scope release and its retry after a crash, the engine-exit stop (needs a systemd user manager) |
| `flows.test.mjs` | S1–S7, P3, E1–E7, the terminal, and a CHAT-01 schema check of every record produced |
| `smoke.test.mjs` | the pinned Pi binary, as above |