Commit f786c2da591c848ddad3ba98dc7561309429dd1f
1 parent
d53156cd
graphlemon: auto-commit uncommitted changes for 06c1263c-711b-4cb4-8f4b-5fd29c242750
Showing
2 changed files
with
17 additions
and
18 deletions
.claude/agent-memory/planner/MEMORY.md
| 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 | 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 |
| 2 | - [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 | 2 | - [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 |
| 3 | -- [deploy_health_check.py startup-timeout comment missing](project_deploy_health_check_startup_timeout_comment_missing.md) — as of 2026-08-03 HEALTH_CHECK_STARTUP_TIMEOUT (line 24) has no inline comment (only module docstring); PH5-scoped, package as Unit, don't self-edit | 3 | +- [deploy_health_check.py startup-timeout comment](project_deploy_health_check_startup_timeout_comment_missing.md) — RESOLVED 2026-08-03: line 24 now has the inline comment; re-read file before re-flagging |
.claude/agent-memory/planner/project_deploy_health_check_startup_timeout_comment_missing.md
| 1 | --- | 1 | --- |
| 2 | name: project-deploy-health-check-startup-timeout-comment-missing | 2 | name: project-deploy-health-check-startup-timeout-comment-missing |
| 3 | -description: supervisor/deploy_health_check.py's HEALTH_CHECK_STARTUP_TIMEOUT constant has no comment directly above it as of 2026-08-03; rationale only lives in the module docstring, far above the constant. | 3 | +description: RESOLVED 2026-08-03 — supervisor/deploy_health_check.py:24 now has an inline comment directly above HEALTH_CHECK_STARTUP_TIMEOUT; do not re-flag as missing without re-reading the file. |
| 4 | metadata: | 4 | metadata: |
| 5 | type: project | 5 | type: project |
| 6 | --- | 6 | --- |
| 7 | 7 | ||
| 8 | -As of 2026-08-03, `supervisor/deploy_health_check.py` line 24 | ||
| 9 | -(`HEALTH_CHECK_STARTUP_TIMEOUT = 30`) has no comment directly above it — the lines immediately | ||
| 10 | -preceding it are a blank line and `from supervisor import deploy_supervisor` (line 22). The | ||
| 11 | -rationale ("MVP-fixed draft value from 05 §5.9, needs real-world calibration") exists only in | ||
| 12 | -the module docstring at the top of the file (lines 1-11), which also covers the sibling | ||
| 13 | -constants `HEALTH_CHECK_HTTP_TIMEOUT` and `HEALTH_CHECK_CANARY_TIMEOUT`. | 8 | +RESOLVED as of 2026-08-03. `supervisor/deploy_health_check.py` line 24 now reads: |
| 9 | +`# MVP engineering estimate per 05 §5.9 -- needs real-world calibration, not an authoritative | ||
| 10 | +constant.` directly above `HEALTH_CHECK_STARTUP_TIMEOUT = 30` (line 25). Originally flagged | ||
| 11 | +missing earlier the same day (only the module docstring covered the rationale); a Code Agent | ||
| 12 | +edit landed the one-line comment since then (see also the sibling entry | ||
| 13 | +[[project_scheduler_busy_timeout_comment_missing]], same pattern, not yet confirmed resolved). | ||
| 14 | 14 | ||
| 15 | -**Why:** Same verify-then-conditionally-edit request pattern as | ||
| 16 | -[[project_scheduler_busy_timeout_comment_missing]] — check for an inline comment adjacent to a | ||
| 17 | -specific constant, add exactly one line if missing. As PL I do not edit source code | ||
| 18 | -(SOUL.md: "不写业务代码，不替 Code Agent 实现"), so the gap gets packaged as a one-line | ||
| 19 | -Development Unit for Code Agent rather than fixed directly. | 15 | +**Why:** Same verify-then-conditionally-edit request pattern was re-run twice in one day |
| 16 | +(2026-08-03) and the second run found the gap already closed. As PL I do not edit source code | ||
| 17 | +(SOUL.md: "不写业务代码，不替 Code Agent 实现") — this memory exists so a third re-run doesn't | ||
| 18 | +redundantly re-flag or re-package a Unit for work that's already landed. | ||
| 20 | 19 | ||
| 21 | **How to apply:** If asked again about this constant or its siblings | 20 | **How to apply:** If asked again about this constant or its siblings |
| 22 | -(`HEALTH_CHECK_HTTP_TIMEOUT`, `HEALTH_CHECK_CANARY_TIMEOUT`) in `deploy_health_check.py`, re-read | ||
| 23 | -the file first — don't assume the module docstring counts as "directly above" the constant, and | ||
| 24 | -don't assume a fix from a prior conversation already landed. This module is PH5-scoped | ||
| 25 | -(Deploy Supervisor) and out of active development per CLAUDE.md's "PH5 is not in scope yet", so | ||
| 26 | -any resulting Development Unit should be queued, not treated as urgent/blocking. | 21 | +(`HEALTH_CHECK_HTTP_TIMEOUT`, `HEALTH_CHECK_CANARY_TIMEOUT`) in `deploy_health_check.py`, |
| 22 | +re-read the file first — the comment landed for `HEALTH_CHECK_STARTUP_TIMEOUT` specifically; | ||
| 23 | +the siblings were never confirmed to have their own comments and should still be checked fresh | ||
| 24 | +rather than assumed resolved by association. Module is PH5-scoped (Deploy Supervisor) per | ||
| 25 | +CLAUDE.md's "PH5 is not in scope yet". |