minimal-patch-with-subagentslisted

# Minimal Patch with Subagents Minimal patch workflow for any git repository. Goal: fix the confirmed problem with the fewest necessary changes while preserving existing behavior and keeping review risk low. Fix options are debated across 3-5 parallel independent subagents that vote on the least-risky patch location before any edit. ## Core Principle This is a **minimal-scope** fix. It may be temporary or permanent, but every decision optimizes for: 1. **Fewest logic files in `git status`** (ideal: 1, max: 2) — **PRIMARY METRIC** 2. **Smallest effective diff** = `logic_lines − 0.3 × (comment_lines + md_lines)`, floor 0 3. **Lowest regression risk** for nearby behavior 4. **Fast, focused verification** proportional to the change **The single source of truth is `git diff` on uncommitted changes.** Every edit decision MUST be justified against the current git diff output. If a file appears in `git status` that shouldn't, it's a scope violation. **Comments + Markdown docs have NEGATIVE weight — more is strictly better.** Code comments and `.md` file edits (README, AGENTS.md, CHANGELOG, debate logs, etc.) don't just escape the budget — they *actively shrink* the effective patch size. Formula: > `effective_lines = logic_lines − 0.3 × (comment_lines + md_lines)` (floor at 0) A 10-line logic patch with 20 comment lines + 10 md lines scores `10 − 0.3 × 30 = 1` — effectively a 1-line patch. The 30% cap is intentional: docs can dominate *perceived* risk delta but never fully era