fix(honcho): align catalog image with runtime #374

Merged

pdurlej merged 1 commit from codex/honcho-runtime-image-catalog-fix into main

2026-05-18 18:41:19 +02:00

codex commented

2026-05-18 18:35:16 +02:00

Collaborator

Canary status: missing - module manifest catalog-only fix; rely on required Forgejo checks before merge

Canary Context Pack

Product story

Honcho Gemma/Ollama closeout needs a no-op auto-apply smoke. The smoke correctly stopped because module manifests claimed home-platform-honcho:3.0.6 while RS2000 is actively running and rendering home-platform-honcho:3.0.3 through HONCHO_IMAGE in runtime compose env.

What changed

Aligned modules/honcho-api/module.yaml and modules/honcho-deriver/module.yaml image_observed fields to the active RS2000 runtime image home-platform-honcho:3.0.3 and refreshed the audit timestamp.

Why it changed

This is a catalog correction, not an app upgrade. The active compose render on RS2000 resolves both Honcho services to home-platform-honcho:3.0.3; platformctl was comparing against stale manifest claims and blocking the no-op smoke.

Files touched

modules/honcho-api/module.yaml
modules/honcho-deriver/module.yaml

Relevant context

H1 Honcho provider-secret bridge smoke after #373 stopped at plan phase with image drift.
RS2000 active env has HONCHO_IMAGE=home-platform-honcho:3.0.3.
docker compose config on RS2000 renders both honcho-api and honcho-deriver as home-platform-honcho:3.0.3.

Runtime evidence

home-platform-honcho-api-1 home-platform-honcho:3.0.3 Up ... healthy
home-platform-honcho-deriver-1 home-platform-honcho:3.0.3 Up ... healthy
Rendered compose on RS2000 shows image: home-platform-honcho:3.0.3 for both services.
Failed smoke run: platformctl-auto-apply.yml run index 1373, pickup 1s, stopped before apply on plan drift only.

Known constraints

No production restart, compose change, image rebuild, or upgrade is included. The compose default remains out of scope because runtime desired state currently comes from the active env override.

Explicit out-of-scope

Upgrading Honcho to home-platform-honcho:3.0.6.
Changing compose defaults.
Changing Gemma/Ollama provider behavior.
Closing #359 before a successful post-fix smoke.

Requested decision

Merge this catalog correction so the Honcho no-op smoke can be retried against the actual RS2000 runtime.

Merge blockers

Evidence that 3.0.6 is intentionally the active desired runtime image today.
Any failing validation/check indicating the manifest shape regressed.

Spec sources read

modules/honcho-api/module.yaml - field corrected.
modules/honcho-deriver/module.yaml - field corrected.
compose/apps/compose.yaml - verified service image default and env override behavior.
state/cutover/honcho-closeout-plan.md - verified H1 smoke context.

Validation

control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/honcho-api/module.yaml - pass.
control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/honcho-deriver/module.yaml - pass.
control-plane/.venv/bin/python -m pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_plan_phase3.py control-plane/platformctl/tests/test_apply_phase3.py -q - 65 passed.

Canary status: missing - module manifest catalog-only fix; rely on required Forgejo checks before merge ## Canary Context Pack ### Product story Honcho Gemma/Ollama closeout needs a no-op auto-apply smoke. The smoke correctly stopped because module manifests claimed `home-platform-honcho:3.0.6` while RS2000 is actively running and rendering `home-platform-honcho:3.0.3` through `HONCHO_IMAGE` in runtime compose env. ### What changed Aligned `modules/honcho-api/module.yaml` and `modules/honcho-deriver/module.yaml` `image_observed` fields to the active RS2000 runtime image `home-platform-honcho:3.0.3` and refreshed the audit timestamp. ### Why it changed This is a catalog correction, not an app upgrade. The active compose render on RS2000 resolves both Honcho services to `home-platform-honcho:3.0.3`; platformctl was comparing against stale manifest claims and blocking the no-op smoke. ### Files touched - `modules/honcho-api/module.yaml` - `modules/honcho-deriver/module.yaml` ### Relevant context - H1 Honcho provider-secret bridge smoke after #373 stopped at plan phase with image drift. - RS2000 active env has `HONCHO_IMAGE=home-platform-honcho:3.0.3`. - `docker compose config` on RS2000 renders both `honcho-api` and `honcho-deriver` as `home-platform-honcho:3.0.3`. ### Runtime evidence - `home-platform-honcho-api-1 home-platform-honcho:3.0.3 Up ... healthy` - `home-platform-honcho-deriver-1 home-platform-honcho:3.0.3 Up ... healthy` - Rendered compose on RS2000 shows `image: home-platform-honcho:3.0.3` for both services. - Failed smoke run: `platformctl-auto-apply.yml` run index 1373, pickup 1s, stopped before apply on plan drift only. ### Known constraints No production restart, compose change, image rebuild, or upgrade is included. The compose default remains out of scope because runtime desired state currently comes from the active env override. ### Explicit out-of-scope - Upgrading Honcho to `home-platform-honcho:3.0.6`. - Changing compose defaults. - Changing Gemma/Ollama provider behavior. - Closing #359 before a successful post-fix smoke. ### Requested decision Merge this catalog correction so the Honcho no-op smoke can be retried against the actual RS2000 runtime. ### Merge blockers - Evidence that `3.0.6` is intentionally the active desired runtime image today. - Any failing validation/check indicating the manifest shape regressed. ## Spec sources read - `modules/honcho-api/module.yaml` - field corrected. - `modules/honcho-deriver/module.yaml` - field corrected. - `compose/apps/compose.yaml` - verified service image default and env override behavior. - `state/cutover/honcho-closeout-plan.md` - verified H1 smoke context. ## Validation - `control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/honcho-api/module.yaml` - pass. - `control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/honcho-deriver/module.yaml` - pass. - `control-plane/.venv/bin/python -m pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_plan_phase3.py control-plane/platformctl/tests/test_apply_phase3.py -q` - 65 passed.

codex added 1 commit

2026-05-18 18:35:16 +02:00

fix(honcho): align catalog image with runtime

base-is-main / guard (pull_request) Successful in 2s

Details

canary-required / collect-diff (pull_request) Successful in 5s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 3s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 19s

Details

canary-required / canary (pull_request) Successful in 14s