Commit edd483314460bd89f78ece44c76f75eb9a4b7352

Authored by graphlemon
1 parent 2b9b9a90

graphlemon: auto-commit uncommitted worktree changes for 044315ed-c80e-4866-a582-92efda9e9315

.claude/agent-memory/planner/MEMORY.md
1   -- [loop_round bug already fixed](project_loop_round_bug_already_fixed.md) — canonical self-hosting demo "bug" is already fixed + regression-tested in src/org_loop_route.py, re-verify before replanning it as open
  1 +- [loop_round bug already fixed](project_loop_round_bug_already_fixed.md) — demo "bug" fix + its REQ-05/REQ-09 comment above _LOOP_LIMIT are both already in src/org_loop_route.py; re-verify before replanning either as open
... ...
.claude/agent-memory/planner/project_loop_round_bug_already_fixed.md
1 1 ---
2 2 name: project-loop-round-bug-already-fixed
3   -description: The canonical self-hosting demo bug ("loop_round > 3 should be >= 3") is already fixed in src/org_loop_route.py with regression coverage — don't plan it as an open defect without re-verifying first
  3 +description: The canonical self-hosting demo bug ("loop_round > 3 should be >= 3") is already fixed in src/org_loop_route.py with regression coverage, AND the REQ-05/REQ-09 explanatory comment above _LOOP_LIMIT already exists too — don't plan either as an open item without re-verifying first
4 4 metadata:
5 5 type: project
6 6 ---
... ... @@ -25,3 +25,11 @@ still open — it may have been fixed between conversations, or the request may
25 25 the *planning process* (e.g. via the self-hosting E2E harness) rather than asking for a real code
26 26 change. Surface "already fixed, has regression coverage" as a first-class BRD finding rather than
27 27 silently manufacturing a fix for a non-existent defect.
  28 +
  29 +**Update 2026-08-03:** the documentation follow-up ("add a one-line comment above `_LOOP_LIMIT = 3`
  30 +explaining the REQ-05/REQ-09 loop_round boundary") is also already done. As of this date,
  31 +`src/org_loop_route.py:38` reads exactly `# REQ-05/REQ-09 (docs/sdd/06-验收与测试锚点.md)
  32 +loop_round boundary: loop_round >= _LOOP_LIMIT forces task.status -> blocked_pending_human.`
  33 +directly above line 39's `_LOOP_LIMIT = 3`. If asked again to add this comment, re-verify the file
  34 +first instead of trusting "no comment there" in the goal description, and do not duplicate/re-add
  35 +a comment that already exists.
... ...