Milestones
List view
## Outcome The carpaccio runs after the delivery, from Align to Closing, delete nothing outside their folders, and they keep each proof that they cite. Each verdict applies to the commit that merges. Each layer of a stack holds its own fixes. Each Story that a Land step leaves open is reported with its PR. Each message arrives during the turn, and the Chef closes a mixed batch with no exceptional decision. ## Epics by Rank 1. Epic 27 (#810): a cleanup deletes only what its thread created, in a recoverable way, and each cited proof survives the cleanup 2. Epic 29 (#812): a review verdict or a Verify proof names the commit that it covers, and it covers the code that will merge 3. Epic 30 (#813): an agent restacks and lands a stack, and it leaves no branch, message line or Story behind 4. Epic 32 (#814): on T3, a message between threads arrives during the turn and is easy to find. Its receipt is recorded with no ambiguity 5. Epic 31 (#815): the Chef closes a mixed batch with no exceptional decision, and `just check` verifies its status model 6. Epic 60 (#979): the carpaccio runs after the M2 delivery prove the M2 outcome ## Done when - The Stories of the five Epics are merged on `main` of pascalandy/skills, and `just check --sweep` answers `{"ok":true}` on `main`, including the `brigade-carpaccio` line (Epic 31) - The shared check occurs after the delivery. The audit covers the carpaccio runs after the last merge. It continues until each case below occurred at least one time. For each case, the audit cites the run, its final Detail and the trace that proves the case: - A cleanup at the end of a run: the proof read again in the PR (#797) - A PR that cites a Verify proof: the head that the verdict covers (#716, #802) - A fix that changes a Verify input after a Verify proof: the Verify proof run again after this fix (#782) - A restack of a stack with two or more layers: the ancestry of the layers (#781) - A Land step that merges a PR in the lower layer: the reported pair of PR and Story (#794) - A Chef answer during the turn of a Cook: the recorded receipt (#784) - A mixed batch with a `queued_after_merge` slot: the closing with no "exceptional decision" (#785) A case that did not occur yet stays pending, and the Milestone stays open - No retro of these runs reports one of these failures: - A deletion outside a folder - A cited proof that was deleted - A verdict on a different commit - A stack branch that is behind - A Story that stays open after `MERGED` with no report that names its PR - A message that stays `queued` - An exceptional decision of the Chef The audit starts from the issue links that each retro of these runs recorded (step 2 of Closing, Retros of the Head Chef). The audit reads the linked issues in all states. `gh issue list -R pascalandy/skills --state all --limit 500 --search "created:<start>..<end of the last run>"` is a cross-check: the audit also reads an issue of the window that is not in the recorded links - Closing the five Epics is not sufficient: the audit above, with its links, is the proof ## Boundaries and dependencies - Outside the Milestone: Epic 28 (proof of a stack on macOS and Linux, fleet tool), Epic 33 (questions to Pascal), Epics 34 to 38. They are delivered separately - The `arancini` and `bisque` routes stay frozen. Each change to brigade targets `carpaccio` - Dependencies between the Epics of the Milestone: #653 (Epic 30) waits for #802 (Epic 29), because they change two adjacent lines of `opening-a-pr.md`. #785 (Epic 31) waits for #796 (Epic 32), which adds a link to the same line `chef-closing.md:7`. No other link connects these Epics - No open product decision The grooming of 2026-10-24 rewrote this description in English. Apart from item 6 and the query with no label filter, the rewrite changes the wording only. by Opus-5.5 via Claude Code
No due date•5/6 issues closed