Commit 6eb24998598236506503453fc7fad2b5c6dbf84d
1 parent
2b9b9a90
graphlemon: real agent-memory updates from self-hosting investigation runs
Showing
2 changed files
with
9 additions
and
2 deletions
.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) — off-by-one fix AND the REQ-05/REQ-09 comment above _LOOP_LIMIT are both already present 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 | name: project-loop-round-bug-already-fixed | 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 is also already present — don't plan either as an open item without re-verifying first |
| 4 | metadata: | 4 | metadata: |
| 5 | type: project | 5 | type: project |
| 6 | --- | 6 | --- |
| @@ -10,6 +10,13 @@ As of 2026-08-02, `src/org_loop_route.py:102` already reads | @@ -10,6 +10,13 @@ As of 2026-08-02, `src/org_loop_route.py:102` already reads | ||
| 10 | regression test covering exactly the loop_round=3 boundary: | 10 | regression test covering exactly the loop_round=3 boundary: |
| 11 | `src/test_org_loop_route.py::LoopLimitTest::test_third_route_attempt_at_limit_blocks_and_raises`. | 11 | `src/test_org_loop_route.py::LoopLimitTest::test_third_route_attempt_at_limit_blocks_and_raises`. |
| 12 | 12 | ||
| 13 | +As of 2026-08-03 (re-verified), the line directly above `_LOOP_LIMIT = 3` (currently line 38) also | ||
| 14 | +already reads: | ||
| 15 | +`# REQ-05/REQ-09 (docs/sdd/06-验收与测试锚点.md) loop_round boundary: loop_round >= _LOOP_LIMIT forces task.status -> blocked_pending_human.` | ||
| 16 | +i.e. a follow-up request to "add a one-line clarifying comment above `_LOOP_LIMIT = 3` citing | ||
| 17 | +REQ-05/REQ-09" is *also* already satisfied verbatim in substance. Two independent asks about this | ||
| 18 | +same three-line region of the file have both turned out to be already-done on inspection. | ||
| 19 | + | ||
| 13 | **Why:** `docs/self-development-feasibility.md` §"场景" uses "fix the loop_round off-by-one | 20 | **Why:** `docs/self-development-feasibility.md` §"场景" uses "fix the loop_round off-by-one |
| 14 | (`loop_round > 3` should be `loop_round >= 3`)" as the canonical illustrative example goal for | 21 | (`loop_round > 3` should be `loop_round >= 3`)" as the canonical illustrative example goal for |
| 15 | graphlemon's self-hosting/self-modification demo, and this exact string is hardcoded as the goal | 22 | graphlemon's self-hosting/self-modification demo, and this exact string is hardcoded as the goal |