diff --git a/.claude/agent-memory/planner/MEMORY.md b/.claude/agent-memory/planner/MEMORY.md
index a3a7971..c34a7ff 100644
--- a/.claude/agent-memory/planner/MEMORY.md
+++ b/.claude/agent-memory/planner/MEMORY.md
@@ -1,3 +1,4 @@
 - [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: 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
+- [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
diff --git a/.claude/agent-memory/planner/project_deploy_health_check_http_timeout_comment_missing.md b/.claude/agent-memory/planner/project_deploy_health_check_http_timeout_comment_missing.md
new file mode 100644
index 0000000..31eb5b5
--- /dev/null
+++ b/.claude/agent-memory/planner/project_deploy_health_check_http_timeout_comment_missing.md
@@ -0,0 +1,24 @@
+---
+name: project-deploy-health-check-http-timeout-comment-missing
+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
+metadata:
+  type: project
+---
+
+As of 2026-08-03, `supervisor/deploy_health_check.py` line 24 has the comment
+`# MVP engineering estimate per 05 §5.9 -- needs real-world calibration, not an authoritative constant.`
+directly above line 25 (`HEALTH_CHECK_STARTUP_TIMEOUT = 30`) only. Line 26
+(`HEALTH_CHECK_HTTP_TIMEOUT = 10`) has line 25's *code* directly above it, not a
+comment of its own -- so a literal "comment directly above HEALTH_CHECK_HTTP_TIMEOUT"
+check reads as NOT satisfied, even though the module docstring (lines 1-11) and
+line 24's comment both already narratively cover all three MVP timeout constants.
+
+**Why:** [[project_deploy_health_check_startup_timeout_comment_missing]] tracked the
+same file's `HEALTH_CHECK_STARTUP_TIMEOUT` case, which resolved 2026-08-03 -- easy to
+conflate the two constants and wrongly assume this one is also resolved just because
+they live three lines apart in the same block.
+
+**How to apply:** Treat this as a separate, still-open fact until a comment appears
+directly above line 26 specifically. Per established precedent, PL does not self-edit
+even a one-line comment -- package as a Unit for Code Agent and re-verify by reading
+the file before re-flagging or closing.