[CI] Already-done issues in batch waste pipeline cycles — batch triage should detect prior-commit implementations

[akaszubski]

Problem

In the batch of 21 issues (20260521-214143), two issues were ALREADY-DONE:

• _call_claude_p_judge: pass cwd=Path.home() to subprocess.run to avoid project context bleed #1064: _call_claude_p_judge cwd=Path.home() — implemented in prior commit a7875d5
• _call_claude_p_judge: strip markdown code fences from envelope.result before json.loads #1065: _call_claude_p_judge code-fence stripping — implemented in prior commit b57513a

Both issues remained OPEN on GitHub despite being implemented. The batch triage step processed them, found them already done, and skipped the pipeline — but only after reading the issue and checking. This wasted coordinator cycles and adds noise to the batch log.

Root Cause

When a fix is committed without closing the issue (e.g., during a prior batch that hit a different error), the issue stays open. The batch triage currently doesn't check whether the issue's referenced code already implements the described behavior.

Suggested Fix

Add an "already-done" pre-check to the batch triage step:

1. For each issue, extract the specific symbol/function/file references from the issue body
2. Run git log --oneline --all -S "search_term" to check if a commit already implements it
3. If a matching commit exists AND it's in the main branch ancestry → mark as ALREADY-DONE and skip
4. Auto-close the issue with a comment referencing the implementing commit

Alternatively: after each /implement run, enforce that all referenced issues are closed (existing STEP 8 requirement) — the gap is enforcement, not detection.

Also worth noting: The "already-done" check should be part of the STEP B2 pre-flight in implement.md batch mode, not just an opportunistic discovery mid-batch.

Plugin Version: 3.50.0 (f6f264c)

---

Filed automatically by continuous-improvement-analyst

[akaszubski]

Implemented in 82e1985 (cluster E — batch mode improvements).