宜博 / lemongraph

Commit d4537c6e012fe1ae9d3cae0f1d363ca12b1a77d4

Authored by graphlemon
1 parent 4b42a1e9

graphlemon: auto-commit uncommitted changes for 7dd4ce06-846e-4712-8e34-809c1289… 

…3203-main-checkout-drift
Inline Side-by-side
Showing 2 changed files with 25 additions and 0 deletions
.claude/agent-memory/planner/MEMORY.md
  View file @d4537c6
1 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 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 3 - [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
  4 +- [deploy_health_check.py HTTP-timeout comment missing](project_deploy_health_check_http_timeout_comment_missing.md) — HEALTH_CHECK_HTTP_TIMEOUT (line 26) has no comment directly above it, unlike its sibling STARTUP_TIMEOUT; distinct open fact, don't conflate the two
... ...
.claude/agent-memory/planner/project_deploy_health_check_http_timeout_comment_missing.md 0 → 100644
  View file @d4537c6
  1 +---
  2 +name: project-deploy-health-check-http-timeout-comment-missing
  3 +description: HEALTH_CHECK_HTTP_TIMEOUT (line 26) in supervisor/deploy_health_check.py has no comment directly above it -- distinct from the already-resolved HEALTH_CHECK_STARTUP_TIMEOUT case
  4 +metadata:
  5 + type: project
  6 +---
  7 +
  8 +As of 2026-08-03, `supervisor/deploy_health_check.py` line 24 has the comment
  9 +`# MVP engineering estimate per 05 §5.9 -- needs real-world calibration, not an authoritative constant.`
  10 +directly above line 25 (`HEALTH_CHECK_STARTUP_TIMEOUT = 30`) only. Line 26
  11 +(`HEALTH_CHECK_HTTP_TIMEOUT = 10`) has line 25's *code* directly above it, not a
  12 +comment of its own -- so a literal "comment directly above HEALTH_CHECK_HTTP_TIMEOUT"
  13 +check reads as NOT satisfied, even though the module docstring (lines 1-11) and
  14 +line 24's comment both already narratively cover all three MVP timeout constants.
  15 +
  16 +**Why:** [[project_deploy_health_check_startup_timeout_comment_missing]] tracked the
  17 +same file's `HEALTH_CHECK_STARTUP_TIMEOUT` case, which resolved 2026-08-03 -- easy to
  18 +conflate the two constants and wrongly assume this one is also resolved just because
  19 +they live three lines apart in the same block.
  20 +
  21 +**How to apply:** Treat this as a separate, still-open fact until a comment appears
  22 +directly above line 26 specifically. Per established precedent, PL does not self-edit
  23 +even a one-line comment -- package as a Unit for Code Agent and re-verify by reading
  24 +the file before re-flagging or closing.
... ...