From 70f05579aa4b3e0a2e99d95cf9ec4e16edfbb553 Mon Sep 17 00:00:00 2001 From: graphlemon Date: Mon, 3 Aug 2026 00:48:26 +0800 Subject: [PATCH] graphlemon: auto-commit uncommitted worktree changes for 64673231-c2e5-4160-9840-426fae66fe8d --- .claude/agent-memory/planner/MEMORY.md | 1 + .claude/agent-memory/planner/project_scheduler_busy_timeout_comment_missing.md | 25 +++++++++++++++++++++++++ 2 files changed, 26 insertions(+), 0 deletions(-) create mode 100644 .claude/agent-memory/planner/project_scheduler_busy_timeout_comment_missing.md diff --git a/.claude/agent-memory/planner/MEMORY.md b/.claude/agent-memory/planner/MEMORY.md index 28d03db..14340e3 100644 --- a/.claude/agent-memory/planner/MEMORY.md +++ b/.claude/agent-memory/planner/MEMORY.md @@ -1 +1,2 @@ - [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 +- [scheduler.py busy-timeout comment missing](project_scheduler_busy_timeout_comment_missing.md) — as of 2026-08-03 _BUSY_TIMEOUT_MS (scheduler.py:78) has no inline comment; PL does not self-edit, packages as a Unit for Code Agent diff --git a/.claude/agent-memory/planner/project_scheduler_busy_timeout_comment_missing.md b/.claude/agent-memory/planner/project_scheduler_busy_timeout_comment_missing.md new file mode 100644 index 0000000..f909032 --- /dev/null +++ b/.claude/agent-memory/planner/project_scheduler_busy_timeout_comment_missing.md @@ -0,0 +1,25 @@ +--- +name: project-scheduler-busy-timeout-comment-missing +description: src/scheduler.py's _BUSY_TIMEOUT_MS constant has no comment directly above it as of 2026-08-03; the rationale only lives in the module docstring, far above the constant. +metadata: + type: project +--- + +As of 2026-08-03, `src/scheduler.py` line 78 (`_BUSY_TIMEOUT_MS = 30000`) has no comment +directly above it. The rationale for the 30s value ("concurrent sqlite writers on the shared +db file should retry instead of raising 'database is locked'") exists only inside the module +docstring (lines 21-28), not adjacent to the constant itself. + +**Why:** A user/orchestrator request asked to verify this and, if missing, add exactly one +inline comment line above the constant. This is a source-code edit, which falls outside the +Planning Agent role (SOUL.md: "不写业务代码，不替 Code Agent 实现"). Response was to write a +BRD documenting the gap as a one-line Development Unit for a Code Agent to implement, rather +than editing `src/scheduler.py` directly — even though the change is trivial. + +**How to apply:** If asked again to "check for X comment/fix and edit if missing" as part of a +"write a BRD" request, do the read-only investigation, report the fact, and package any actual +code change as a requirement/acceptance criterion for Code Agent — do not perform the Edit +myself. This mirrors [[project_loop_round_bug_already_fixed]]'s pattern of quick verification +asks embedded in planning requests; the difference here is the fact was "not yet fixed" rather +than "already fixed," so the correct BRD is a genuine (if tiny) actionable requirement instead +of a no-op report. -- libgit2 0.21.4