From edd483314460bd89f78ece44c76f75eb9a4b7352 Mon Sep 17 00:00:00 2001 From: graphlemon Date: Mon, 3 Aug 2026 00:19:55 +0800 Subject: [PATCH] graphlemon: auto-commit uncommitted worktree changes for 044315ed-c80e-4866-a582-92efda9e9315 --- .claude/agent-memory/planner/MEMORY.md | 2 +- .claude/agent-memory/planner/project_loop_round_bug_already_fixed.md | 10 +++++++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/.claude/agent-memory/planner/MEMORY.md b/.claude/agent-memory/planner/MEMORY.md index 55274fd..63b18b4 100644 --- a/.claude/agent-memory/planner/MEMORY.md +++ b/.claude/agent-memory/planner/MEMORY.md @@ -1 +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 +- [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 diff --git a/.claude/agent-memory/planner/project_loop_round_bug_already_fixed.md b/.claude/agent-memory/planner/project_loop_round_bug_already_fixed.md index 227ae9f..58dc43b 100644 --- a/.claude/agent-memory/planner/project_loop_round_bug_already_fixed.md +++ b/.claude/agent-memory/planner/project_loop_round_bug_already_fixed.md @@ -1,6 +1,6 @@ --- name: project-loop-round-bug-already-fixed -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 +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 metadata: type: project --- @@ -25,3 +25,11 @@ still open — it may have been fixed between conversations, or the request may the *planning process* (e.g. via the self-hosting E2E harness) rather than asking for a real code change. Surface "already fixed, has regression coverage" as a first-class BRD finding rather than silently manufacturing a fix for a non-existent defect. + +**Update 2026-08-03:** the documentation follow-up ("add a one-line comment above `_LOOP_LIMIT = 3` +explaining the REQ-05/REQ-09 loop_round boundary") is also already done. As of this date, +`src/org_loop_route.py:38` reads exactly `# REQ-05/REQ-09 (docs/sdd/06-验收与测试锚点.md) +loop_round boundary: loop_round >= _LOOP_LIMIT forces task.status -> blocked_pending_human.` +directly above line 39's `_LOOP_LIMIT = 3`. If asked again to add this comment, re-verify the file +first instead of trusting "no comment there" in the goal description, and do not duplicate/re-add +a comment that already exists. -- libgit2 0.21.4