micro--go-micro
Asim Aslam
85374c6401
An assessment of the last 100 commits found ~45% were pure "refresh planner priorities" bookkeeping and much of the rest was thrashing on one weak provider (AtlasCloud text-tool-call repair) and guarding docs the loop already wrote — motion, not progress. Two prompt-policy fixes: PLANNER (planner.md): - Default to NOT committing. Post the assessment and close the issue; open a PRIORITIES.md PR ONLY when the change is MATERIAL (top item changes, an item is added/removed, or a top item's issue closed). No PRs for reorders below the top, reword, or "keep it current" — that churn was the loop's #1 waste. - Add a diminishing-returns guard: don't queue the Nth doc-guard or the Nth robustness workaround for an already-tolerated class; mark exhausted areas needs-human and rank real-headroom capability instead. TRIAGE (triage.md): - Cap the AtlasCloud/plan-delegate tail-chase: another instance of a class the agent already tolerates is NOT filed as a routine patch — comment "recurred — capped" and, if worth more, needs-human. Real regressions (lint/tests/ govulncheck on master) and genuinely new defects still get filed. Prompt-only; reversible. Steers the loop toward outcomes over busy-work. Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL Co-authored-by: Claude <noreply@anthropic.com>