Expand description
The local follow-up queue, and working it.
.spar/followups.md is what followups = "local" writes instead of filing
on the tracker. Until now nothing read it back, so a review’s out of scope
findings accumulated in a file with no way to act on them. spar followup
reads it, asks one agent whether each entry is still true of the code as it
is now, files the survivors, and hands them to the same pipeline spar run
uses, which means both agents still triage each one before anything is
implemented.
Most of the care here is in the parser, for one reason. An entry is written
as ## <title>, and review::issue_report writes that entry’s own sections
as ## Problem, ## Reproduction, ## Impact and ## Expected behavior,
at the same heading level. A real file had 25 ## lines and 5 entries, so a
naive split would file twenty issues, four of them titled “Impact”.
Structs§
Enums§
- Mode
- Where a run of
spar followupstops.
Functions§
- parse
- Split a note file into entries.
- run
- Read the queue, screen it, file what still holds, and take the filed entries out of the file.
- screen
- One agent’s verdict on every entry that fits in one prompt.
- wave
- The issue numbers a set of outcomes produced, deduplicated and in order.
- without
- The text with these entries removed, blank lines closed up at the seams.