diff --git a/.claude/agent-memory/planner/MEMORY.md b/.claude/agent-memory/planner/MEMORY.md
index 55274fd..28d03db 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) — 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
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..d666439 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 is also already present — don't plan either as an open item without re-verifying first
 metadata:
   type: project
 ---
@@ -10,6 +10,13 @@ As of 2026-08-02, `src/org_loop_route.py:102` already reads
 regression test covering exactly the loop_round=3 boundary:
 `src/test_org_loop_route.py::LoopLimitTest::test_third_route_attempt_at_limit_blocks_and_raises`.
 
+As of 2026-08-03 (re-verified), the line directly above `_LOOP_LIMIT = 3` (currently line 38) also
+already reads:
+`# REQ-05/REQ-09 (docs/sdd/06-验收与测试锚点.md) loop_round boundary: loop_round >= _LOOP_LIMIT forces task.status -> blocked_pending_human.`
+i.e. a follow-up request to "add a one-line clarifying comment above `_LOOP_LIMIT = 3` citing
+REQ-05/REQ-09" is *also* already satisfied verbatim in substance. Two independent asks about this
+same three-line region of the file have both turned out to be already-done on inspection.
+
 **Why:** `docs/self-development-feasibility.md` §"场景" uses "fix the loop_round off-by-one
 (`loop_round > 3` should be `loop_round >= 3`)" as the canonical illustrative example goal for
 graphlemon's self-hosting/self-modification demo, and this exact string is hardcoded as the goal