Summary
docs/memory/architecture.md lists the backend health endpoint as /api/health, but the actual served path is /health.
Verification
$ curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8000/health
200
$ curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8000/api/health
404
The OpenAPI spec also confirms /health (no /api/ prefix) is the correct path.
Fix
In docs/memory/architecture.md, update the row under "Auth, Users & MCP" that reads:
| GET | `/api/health` | Health check |
Replace with:
| GET | `/health` | Health check |
(Or move it out of the auth section entirely — it's not auth-related.)
How this surfaced
Caught during local Trinity smoke verification while running PR #553 (issue #67 — design system tokens). The verification used the architecture-documented endpoint and got a 404; falling back to /health worked.
Severity
P3 — pure documentation drift, no functional impact. Worth filing because /validate-architecture should ideally catch this, and it's the kind of thing new contributors would trip over.
Summary
docs/memory/architecture.mdlists the backend health endpoint as/api/health, but the actual served path is/health.Verification
The OpenAPI spec also confirms
/health(no/api/prefix) is the correct path.Fix
In
docs/memory/architecture.md, update the row under "Auth, Users & MCP" that reads:Replace with:
(Or move it out of the auth section entirely — it's not auth-related.)
How this surfaced
Caught during local Trinity smoke verification while running PR #553 (issue #67 — design system tokens). The verification used the architecture-documented endpoint and got a 404; falling back to
/healthworked.Severity
P3 — pure documentation drift, no functional impact. Worth filing because
/validate-architectureshould ideally catch this, and it's the kind of thing new contributors would trip over.