From b0799411caff1515658d33e7f7ffc8716be8f79b Mon Sep 17 00:00:00 2001 From: graphlemon Date: Mon, 3 Aug 2026 13:32:35 +0800 Subject: [PATCH] graphlemon: auto-commit uncommitted changes for 06c1263c-711b-4cb4-8f4b-5fd29c242750-main-checkout-drift --- .claude/agent-memory/planner/MEMORY.md | 2 +- .claude/agent-memory/planner/project_deploy_health_check_startup_timeout_comment_missing.md | 32 ++++++++++++++------------------ 2 files changed, 15 insertions(+), 19 deletions(-) diff --git a/.claude/agent-memory/planner/MEMORY.md b/.claude/agent-memory/planner/MEMORY.md index 6061057..a3a7971 100644 --- a/.claude/agent-memory/planner/MEMORY.md +++ b/.claude/agent-memory/planner/MEMORY.md @@ -1,3 +1,3 @@ - [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 -- [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 +- [deploy_health_check.py startup-timeout comment: RESOLVED](project_deploy_health_check_startup_timeout_comment_missing.md) — comment now present above HEALTH_CHECK_STARTUP_TIMEOUT (line 24); re-verify by reading file before re-flagging diff --git a/.claude/agent-memory/planner/project_deploy_health_check_startup_timeout_comment_missing.md b/.claude/agent-memory/planner/project_deploy_health_check_startup_timeout_comment_missing.md index 9dd7ea1..22f54c2 100644 --- a/.claude/agent-memory/planner/project_deploy_health_check_startup_timeout_comment_missing.md +++ b/.claude/agent-memory/planner/project_deploy_health_check_startup_timeout_comment_missing.md @@ -1,26 +1,22 @@ --- name: project-deploy-health-check-startup-timeout-comment-missing -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. +description: supervisor/deploy_health_check.py's HEALTH_CHECK_STARTUP_TIMEOUT constant — RESOLVED 2026-08-03, comment now present directly above it. metadata: type: project --- -As of 2026-08-03, `supervisor/deploy_health_check.py` line 24 -(`HEALTH_CHECK_STARTUP_TIMEOUT = 30`) has no comment directly above it — the lines immediately -preceding it are a blank line and `from supervisor import deploy_supervisor` (line 22). The -rationale ("MVP-fixed draft value from 05 §5.9, needs real-world calibration") exists only in -the module docstring at the top of the file (lines 1-11), which also covers the sibling -constants `HEALTH_CHECK_HTTP_TIMEOUT` and `HEALTH_CHECK_CANARY_TIMEOUT`. +RESOLVED as of 2026-08-03 (re-verified by direct file read same day): `supervisor/deploy_health_check.py` +line 24 now reads `# MVP engineering estimate per 05 §5.9 -- needs real-world calibration, not an +authoritative constant.` directly above `HEALTH_CHECK_STARTUP_TIMEOUT = 30` (line 25). -**Why:** Same verify-then-conditionally-edit request pattern as -[[project_scheduler_busy_timeout_comment_missing]] — check for an inline comment adjacent to a -specific constant, add exactly one line if missing. As PL I do not edit source code -(SOUL.md: "不写业务代码，不替 Code Agent 实现"), so the gap gets packaged as a one-line -Development Unit for Code Agent rather than fixed directly. +**History:** Earlier on 2026-08-03, this same check found the constant had no comment directly +above it (only the module docstring covered the rationale, far above the constant) and packaged +it as a one-line Development Unit for Code Agent rather than self-editing (SOUL.md: "不写业务代码， +不替 Code Agent 实现"). That Unit was executed later the same day; the edit landed. -**How to apply:** If asked again about this constant or its siblings -(`HEALTH_CHECK_HTTP_TIMEOUT`, `HEALTH_CHECK_CANARY_TIMEOUT`) in `deploy_health_check.py`, re-read -the file first — don't assume the module docstring counts as "directly above" the constant, and -don't assume a fix from a prior conversation already landed. This module is PH5-scoped -(Deploy Supervisor) and out of active development per CLAUDE.md's "PH5 is not in scope yet", so -any resulting Development Unit should be queued, not treated as urgent/blocking. +**How to apply:** If asked again about this constant or its siblings (`HEALTH_CHECK_HTTP_TIMEOUT`, +`HEALTH_CHECK_CANARY_TIMEOUT`, which still only have docstring-level coverage, not per-line +comments), re-read the file first — don't assume this memory's "resolved" status still holds +indefinitely, but also don't re-flag the startup-timeout comment as missing without checking. +This module is PH5-scoped (Deploy Supervisor) and out of active development per CLAUDE.md's +"PH5 is not in scope yet", so any resulting Development Unit should be queued, not urgent. -- libgit2 0.21.4