fix(honcho): align api health probe with openapi readiness #362

Merged

pdurlej merged 1 commit from codex/honcho-api-openapi-health into main

2026-05-18 08:17:47 +02:00

codex commented

2026-05-18 08:15:11 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

Honcho API is healthy after the Ollama/Gemma deploy, but the manifest still pointed smoke/readiness at /health, which the current Honcho image does not expose. Future agents would read that as a false red signal.

What changed

Updated modules/honcho-api/module.yaml acceptance criteria and HTTP health URL from /health to /openapi.json.
Updated the Honcho Ollama switch runbook post-deploy verification line to match the real readiness endpoint.

Why it changed

Runtime evidence after recreating honcho-api showed Docker health is healthy and the container healthcheck itself probes /openapi.json. Tailnet GET /openapi.json returns HTTP 200, while GET /health returns 404.

Files touched

modules/honcho-api/module.yaml
runbooks/honcho-ollama-gemma-switch.md

Relevant context

Honcho API container healthcheck: urllib.request.urlopen('http://127.0.0.1:8000/openapi.json').
Post-deploy evidence: openapi.json HTTP 200; /health HTTP 404.

Runtime evidence

home-platform-honcho-api-1: running, Docker health healthy.
https://honcho.pdurlej.com/openapi.json over tailnet resolve: HTTP 200.
https://honcho.pdurlej.com/health: HTTP 404.

Known constraints

This is metadata/runbook alignment only. It does not change compose, containers, secrets, or runtime traffic.

Explicit out-of-scope

Adding a new /health endpoint to Honcho upstream.
Changing Honcho container healthcheck.
Re-running the Ollama deploy.

Requested decision

Merge to remove a false future smoke failure.

Merge blockers

If Honcho upstream restores a real /health endpoint and the compose healthcheck changes accordingly.

Spec sources read

modules/honcho-api/module.yaml — manifest health/acceptance contract.
runbooks/honcho-ollama-gemma-switch.md — post-deploy verification checklist.
Runtime Docker healthcheck and endpoint probes on RS2000.

Test Plan

control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/honcho-api/module.yaml
git diff --check
Runtime probe: /openapi.json HTTP 200, /health HTTP 404.

Commit: 9901369

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story Honcho API is healthy after the Ollama/Gemma deploy, but the manifest still pointed smoke/readiness at `/health`, which the current Honcho image does not expose. Future agents would read that as a false red signal. ### What changed - Updated `modules/honcho-api/module.yaml` acceptance criteria and HTTP health URL from `/health` to `/openapi.json`. - Updated the Honcho Ollama switch runbook post-deploy verification line to match the real readiness endpoint. ### Why it changed Runtime evidence after recreating `honcho-api` showed Docker health is healthy and the container healthcheck itself probes `/openapi.json`. Tailnet `GET /openapi.json` returns HTTP 200, while `GET /health` returns 404. ### Files touched - `modules/honcho-api/module.yaml` - `runbooks/honcho-ollama-gemma-switch.md` ### Relevant context - Honcho API container healthcheck: `urllib.request.urlopen('http://127.0.0.1:8000/openapi.json')`. - Post-deploy evidence: `openapi.json` HTTP 200; `/health` HTTP 404. ### Runtime evidence - `home-platform-honcho-api-1`: running, Docker health healthy. - `https://honcho.pdurlej.com/openapi.json` over tailnet resolve: HTTP 200. - `https://honcho.pdurlej.com/health`: HTTP 404. ### Known constraints This is metadata/runbook alignment only. It does not change compose, containers, secrets, or runtime traffic. ### Explicit out-of-scope - Adding a new `/health` endpoint to Honcho upstream. - Changing Honcho container healthcheck. - Re-running the Ollama deploy. ### Requested decision Merge to remove a false future smoke failure. ### Merge blockers - If Honcho upstream restores a real `/health` endpoint and the compose healthcheck changes accordingly. ## Spec sources read - `modules/honcho-api/module.yaml` — manifest health/acceptance contract. - `runbooks/honcho-ollama-gemma-switch.md` — post-deploy verification checklist. - Runtime Docker healthcheck and endpoint probes on RS2000. ## Test Plan - `control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/honcho-api/module.yaml` - `git diff --check` - Runtime probe: `/openapi.json` HTTP 200, `/health` HTTP 404. Commit: `9901369`

codex added 1 commit

2026-05-18 08:15:11 +02:00