Commit 2f2db22d4f30cdc1f5e565d14f9b84f35d3e9424
graphlemon: merge 9d0b0265-5b00-4fd2-b748-f5d0cd5faf77
Showing
2 changed files
with
27 additions
and
0 deletions
.claude/agent-memory/coder/MEMORY.md
0 → 100644
| 1 | +- [Loop-limit comment task keeps re-dispatching with zero diff](task_dispatch_loop_limit_comment_repeat.md) — src/org_loop_route.py:38 comment already exists; verify and report, don't re-add |
.claude/agent-memory/coder/task_dispatch_loop_limit_comment_repeat.md
0 → 100644
| 1 | +--- | ||
| 2 | +name: task-dispatch-loop-limit-comment-repeat | ||
| 3 | +description: The "_LOOP_LIMIT boundary comment missing" task keeps getting re-dispatched even though the comment has been present and correct since it was added; verified 5+ times now with zero diff each time | ||
| 4 | +metadata: | ||
| 5 | + type: project | ||
| 6 | +--- | ||
| 7 | + | ||
| 8 | +`src/org_loop_route.py:38` has had the REQ-05/REQ-09 loop_round-boundary comment above | ||
| 9 | +`_LOOP_LIMIT = 3` since it was added under U-016 (commit `59749fc`). A goal describing this | ||
| 10 | +exact gap ("no comment there, add one") has now been dispatched to the coder at least 5 | ||
| 11 | +independent times (per the user's global auto-memory index and this session's own SDD, which | ||
| 12 | +called it the "4th independent verification" before this one, the 5th). Every time, the correct | ||
| 13 | +action was to verify and make zero changes. | ||
| 14 | + | ||
| 15 | +**Why:** the Org Graph / planner pipeline has no terminal task state for "investigated, already | ||
| 16 | +satisfied, confirmed zero-diff" that's distinct from `done` / `blocked_pending_human` — this was | ||
| 17 | +flagged as an out-of-scope process gap in this session's SDD and in the referenced auto-memory | ||
| 18 | +entry. Without that state, tasks whose fix already landed apparently keep getting re-surfaced as | ||
| 19 | +open work instead of being marked resolved. | ||
| 20 | + | ||
| 21 | +**How to apply:** if dispatched this same goal again, re-verify quickly (grep the line, run | ||
| 22 | +`python3 -m unittest src.test_org_loop_route -v`), confirm zero diff, and report the same finding | ||
| 23 | +rather than assuming something changed. Do not silently "fix" it by re-adding/rewording the | ||
| 24 | +comment — that would create unnecessary diff noise. If this keeps recurring, the real fix is | ||
| 25 | +upstream (a Planner/Org Graph terminal state for zero-diff-confirmed tasks), not another coder | ||
| 26 | +turn on this file. |