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 d666439..221590f 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
@@ -32,3 +32,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.