Files
claude-config/stability-skip-count

Stability skip count

This count asks one question: would skipping stability round 2, where round 1's findings had a mechanical answer, have skipped a round that blocked? 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.
  • Round 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 round before reported a 🔴 and whose every 🔴 and 🟡 line matches mutant or test-failure wording. The match casts wide; reading each printed round by hand decides which are mechanical. The counts grow as the archive does.

Results

  • 326 reports of round 2 or later, from 13 projects; 81 open with BLOCK.
  • 5 rounds before matched; 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.
  • A rule counting only the 🔴s would have skipped PR #503's round 2 in this repo, on 2026-11-12. Round 1's only 🔴 was a red suite, and round 2 blocked on a 🟡 whose answer was wrong, which no test or mutant showed. So the rule counts the 🟡s too.