ops(honcho): honcho-api 3.0.6 declared but 3.0.3 live — land or revert #731

New issue

Closed

opened 2026-06-05 14:45:48 +02:00 by claude · 0 comments

claude commented

2026-06-05 14:45:48 +02:00

Collaborator

From the 2026-06-05 deslop audit + a live rs2000 check (claude).

Finding (live-verified)

modules/honcho-api/module.yaml declares artifact.tag / source.ref = 3.0.6, but the running containers are 3.0.3:

home-platform-honcho-api-1      home-platform-honcho:3.0.3   Up 38h (healthy)
home-platform-honcho-deriver-1  home-platform-honcho:3.0.3   Up 38h (healthy)

So the 3.0.6 upgrade never landed on the host (criticality: core). Operator intent: "should be current" → most likely a partially-failed upgrade.

Fix (operator-gated — runtime, core DB-adjacent)

Investigate WHY 3.0.6 didn't land: does the home-platform-honcho:3.0.6 image actually exist (built/published)? Check the build/deploy logs for a failed apply.
If 3.0.6 is real + intended → deploy it (gated platformctl apply path), then re-audit so image_observed refreshes to 3.0.6.
If 3.0.6 was aspirational / the upgrade is abandoned → revert artifact.tag/source.ref to 3.0.3 to match reality.
Do NOT hand-edit image_observed — it is plan.py's drift-detection source of truth; it must only change via a real deploy + re-audit.

Acceptance

Manifest tag and live image_observed agree (both 3.0.6 after deploy, or both 3.0.3 after revert).
The decision (deploy vs revert) recorded with the root-cause of the failed upgrade.

Authored from the deslop audit (claude). Runtime apply = operator-gated; Codex authors, operator approves.

From the 2026-06-05 deslop audit + a live rs2000 check (claude). ## Finding (live-verified) `modules/honcho-api/module.yaml` declares `artifact.tag` / `source.ref` = **3.0.6**, but the running containers are **3.0.3**: ``` home-platform-honcho-api-1 home-platform-honcho:3.0.3 Up 38h (healthy) home-platform-honcho-deriver-1 home-platform-honcho:3.0.3 Up 38h (healthy) ``` So the 3.0.6 upgrade **never landed on the host** (criticality: core). Operator intent: "should be current" → most likely a partially-failed upgrade. ## Fix (operator-gated — runtime, core DB-adjacent) 1. Investigate WHY 3.0.6 didn't land: does the `home-platform-honcho:3.0.6` image actually exist (built/published)? Check the build/deploy logs for a failed apply. 2. If 3.0.6 is real + intended → **deploy it** (gated `platformctl apply` path), then re-audit so `image_observed` refreshes to 3.0.6. 3. If 3.0.6 was aspirational / the upgrade is abandoned → revert `artifact.tag`/`source.ref` to **3.0.3** to match reality. 4. **Do NOT hand-edit `image_observed`** — it is `plan.py`'s drift-detection source of truth; it must only change via a real deploy + re-audit. ## Acceptance - [ ] Manifest tag and live `image_observed` agree (both 3.0.6 after deploy, or both 3.0.3 after revert). - [ ] The decision (deploy vs revert) recorded with the root-cause of the failed upgrade. *Authored from the deslop audit (claude). Runtime apply = operator-gated; Codex authors, operator approves.*

Rows
Columns