docs(readme): mention make targets in README build/deploy section

[BluegReeno]

Summary

Issue #59 is a docs-only follow-up from PR #57: the root Makefile (deploy / verify / test targets) wasn't clearly surfaced in README.md. The README's "Develop & deploy" section showed make deploy once, inline, with no description and no pointer to the full runbook.

Changes

• README.md: replaced the single unlabeled make deploy line with a short bullet list naming all three canonical Makefile targets, descriptions copied verbatim from the Makefile's own ## comments:
  • make deploy — deploy hal-mcp + verify it answers
  • make verify — probe the live hal-mcp function (no redeploy)
  • make test — offline checks — deno type-check (both fns) + offline pytest (mirrors CI)
  • Added one pointer line to CLAUDE.md § Migrations & deploy and docs/operations.md for the full runbook.
• README-only change (+8/-3), no other file touched.

Validation

• Level 1 (static): grep -n "make deploy\|make verify\|make test\|Migrations & deploy" README.md → shows all three targets + runbook pointer (README.md:279-283)
• Level 3 (full suite): make test → exit 0, deno check clean on both edge functions, 157 passed / 17 deselected (pytest)
• Scope check: git show --stat HEAD confirms README.md only, +8/-3

Fixes #59

🤖 Generated with Claude Code

[BluegReeno]

🔍 Comprehensive PR Review

PR: #75
Reviewed by: 2 specialized agents (code-review, docs-impact) — error-handling, test-coverage, comment-quality were N/A for this docs-only diff
Date: 2026-07-25

---

Summary

Docs-only change (README.md, +8/-3) that surfaces the three root Makefile targets (deploy, verify, test) in the "Develop & deploy" section, per issue #59, with a pointer to the full runbook in CLAUDE.md and docs/operations.md. Both agents that ran independently verified the target descriptions match the Makefile's own ## comments verbatim, confirmed the CLAUDE.md cross-reference resolves, and found no scope violations or broken references.

Verdict: APPROVE

Severity	Count
🔴 CRITICAL	0
🟠 HIGH	0
🟡 MEDIUM	0
🟢 LOW	0

---

✅ What's Good

• Verbatim-copy discipline: all three make target descriptions match the Makefile's ## comments exactly, preventing README↔Makefile drift.
• Single source of truth preserved: only a one-line pointer to CLAUDE.md § "Migrations & deploy" and docs/operations.md was added — no duplicated runbook text.
• Scope discipline: Makefile, CLAUDE.md, and docs/operations.md left untouched per issue docs(readme): mention make targets in README build/deploy section #59's README-only scope; no speculative make help target added.
• Cross-reference integrity: the referenced CLAUDE.md heading (CLAUDE.md:66) still exists verbatim.

---

Next Steps

1. ✅ No CRITICAL or HIGH issues — nothing to auto-fix.
2. ✅ No MEDIUM issues requiring a decision.
3. 🎯 Ready to merge once the migration smoke-test CI check finishes and draft status is lifted.

---

Reviewed by Archon comprehensive-pr-review workflow
Artifacts: /Users/renaud/.archon/workspaces/BluegReeno/hal/artifacts/runs/1289c78a5264ca035fed7feae4f552fe/review/

[BluegReeno]

⚡ Self-Fix Report (Aggressive)

Status: COMPLETE
Pushed: N/A — no changes needed, nothing was pushed
Philosophy: Fix everything unless clearly a new concern

---

Fixes Applied (0 total)

Severity	Count
🔴 CRITICAL	0
🟠 HIGH	0
🟡 MEDIUM	0
🟢 LOW	0

All review dimensions that ran (code-review, docs-impact) returned zero findings and an APPROVE / NO_CHANGES_NEEDED verdict. error-handling, test-coverage, and comment-quality were correctly not produced — the PR is a docs-only +8/-3 change to README.md with no source, tests, or code comments touched.

---

Tests Added

(none — docs-only diff)

---

Skipped (0)

(none — all findings addressed, because there were none)

---

Suggested Follow-up Issues

(none)

---

Validation

N/A — no code changed, nothing to type-check/lint/test.

---

Self-fix by Archon · aggressive mode · no changes required, nothing pushed