Milestones
List view
Ordered queue, most severe first. Take them in this order unless something newer outranks them. 1. #669 - a team's roster is silently emptied when the journal is present but unreadable: the fold sees no events, json_set builds a valid document from the config it could read, the non-empty guard passes, and the write commits. rc=0, nothing on stderr, membership gone. Present on integration/remote now. Outranks the rest: the others lose or misreport messages, this one destroys identity. 2. #637 - check-inbox.sh stamps messages read per team inside the loop but emits output only after it. Under `set -euo pipefail` a later team's failure aborts before anything is emitted, so already-stamped messages are never delivered and never re-offered. Irreversible loss on the delivery path, present in v1.1.13. 3. #658 - main carries its own fix for the same defect as #637, and it is inert: it emits the decision JSON and then exits non-zero, which the hook runtimes read as a failed hook and discard. It delivers nothing on exactly the path that was broken. This is the version that ships. 4. #595 - the process-lifecycle bats tests flake on main itself, a different test each time. This does not make a green run false; it makes a red run meaningless, which trains everyone to re-run until green - and that is how a real failure gets re-run away. The merge gate rests on this signal. 5. #625 - despawn reports status=ok for a member it did not tear down, then deletes the placement record that the `--force` it recommends would need. A third defect in reset.sh leaves the registration behind even after a successful --force. 6. #553 - install.sh --cmd repoints the shared Codex shim. 7. #599 - install.sh --update updates whichever install sorts first and misreports which one it touched. 4 and 5 are the same file. Take them together rather than in parallel. 8. #373 - atomic message consumption: duplicate delivery and inject-failure loss. Same axis as item 1 but carries a design change; close 1 first. 9. #645 - Codex CLI 0.147.0 on Windows cannot record the role session. Same family as #608. 10. #647 - spawn.sh waits for a readiness sentinel that a `mode: off` project can never produce.
No due date•4/10 issues closed