Skip to content

chore: add --verbose near-miss reporting to eligible_backlog.py - #529

Open
essentialbit wants to merge 9 commits into
mainfrom
tooling/eligible-backlog-near-miss-verbose-20260727
Open

chore: add --verbose near-miss reporting to eligible_backlog.py#529
essentialbit wants to merge 9 commits into
mainfrom
tooling/eligible-backlog-near-miss-verbose-20260727

Conversation

@essentialbit

Copy link
Copy Markdown
Owner

Summary

  • eligible_backlog.py has printed [] for 6+ cycles with no visibility into why (below-threshold consensus / risk:high / already-referenced) — self-directed tooling gap, not tied to any FSI feature proposal (precedent in fredai memory: this class doesn't need consensus/outcome-recording).
  • New --verbose flag returns {"eligible": [...], "near_misses": [...]}, where near_misses are non-risk:high, unreferenced proposals sorted by consensus descending. Default (no flag) behavior/output unchanged.

Test plan

  • ast.parse syntax check
  • python3 scripts/eligible_backlog.py (no flag) still returns [], matching pre-change behavior
  • python3 scripts/eligible_backlog.py --verbose returns real near-miss data from the live open-proposal backlog

Saifodius and others added 9 commits July 27, 2026 01:55
Eligible backlog has printed [] for 6+ cycles running with zero visibility
into why (below-threshold consensus vs risk:high vs already-referenced) —
each cycle re-derived that reasoning by hand instead of a quick check.
--verbose now surfaces the non-risk:high, unreferenced candidates sorted
by consensus descending. Default (no flag) output is unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant