21 lines
1.7 KiB
Markdown
21 lines
1.7 KiB
Markdown
# Stability skip count
|
|
|
|
This count asks one question: would skipping stability round 2 have skipped a round that blocked, where round 1's findings each asked only that a named mutant be killed or a named failing test pass?
|
|
It ran on 2026-11-12, over loop-claude's archive in `~/.claude/loop-claude-transcripts/`. `docs/decisions.md` → `review: a fix for a 🔴 reruns the pass that found it…` records what was decided from it, and `skills/larv-review/SKILL.md` §3 → "Re-entry" → "Mechanical answers" holds the rule.
|
|
|
|
## Terms
|
|
|
|
- **Report:** a stability-reviewer run in the archive, with the round number its launch names.
|
|
- **Report before:** the previous report in the same archived cycle.
|
|
- **Mechanical:** a finding that asks only that a named mutant be killed or a named failing test pass.
|
|
|
|
## Method
|
|
|
|
`python3 -I stability-skip-count/count.py` prints the totals, then each report of round 2 or later whose report before held a 🔴 and had every 🔴 and 🟡 line match mutant or test-failure wording, with that report's opening line and the report before's findings. The match casts wide; reading each printed round by hand decides which are mechanical. It reads only reports begun before its `UNTIL`, so a rerun on this machine prints the same counts. It needs the archive, which only the machine that ran the cycles holds.
|
|
|
|
## Results
|
|
|
|
- 326 reports of round 2 or later, from 13 projects; 81 open with BLOCK.
|
|
- 5 reports before matched, and the round 2 after each of the 5 approved, so no BLOCK falls in a round the skip could skip.
|
|
- Read by hand, 1 of the 5 is mechanical: fejkdata, 2026-11-04, a pin test that fails. The other 4 matched on wording alone: a test's structure, a workflow condition, a failing type check and a missed timing target.
|