pdurlej/platform

Fork 0

ops(honcho): reconcile 3.0.6 runtime image #776

Merged

pdurlej merged 1 commit from codex/issues/731-honcho-306-reconcile into main

2026-06-10 22:15:24 +02:00

codex commented

2026-06-10 22:12:24 +02:00

Collaborator

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

Canary Context Pack

Product story

Honcho should not leave the operator guessing whether repo state or runtime state is true. Issue #731 asked to either land the declared 3.0.6 runtime or revert the declaration; runtime was reconciled to the declared local image and the manifests now record that evidence.

What changed

Updated honcho-api and honcho-deriver observed image metadata from home-platform-honcho:3.0.3 to home-platform-honcho:3.0.6.
Added state/reports/honcho-306-runtime-reconcile-2026-06-10.md with root cause, runtime evidence, rollback, and follow-up.

Why it changed

compose/apps/compose.yaml and honcho-api artifact metadata already pointed at home-platform-honcho:3.0.6, but live containers were still on 3.0.3 because /opt/pdurlej-platform/runtime/compose.env had a stale HONCHO_IMAGE=home-platform-honcho:3.0.3 override.

Files touched

modules/honcho-api/module.yaml
modules/honcho-deriver/module.yaml
state/reports/honcho-306-runtime-reconcile-2026-06-10.md

Relevant context

Issue #731: ops(honcho): honcho-api 3.0.6 declared but 3.0.3 live - land or revert
compose/apps/compose.yaml Honcho services default to ${HONCHO_IMAGE:-home-platform-honcho:3.0.6}.
Local build schema permits tag-only image_observed for image_build: local; local image ID is recorded in the report as evidence, not as a fake registry digest.

Runtime evidence

Runtime env now reports HONCHO_IMAGE=home-platform-honcho:3.0.6.
home-platform-honcho-api-1: home-platform-honcho:3.0.6, running, healthy.
home-platform-honcho-deriver-1: home-platform-honcho:3.0.6, running, healthy.
Both containers inspected with image ID sha256:1d843c9f83136be5651589d60bfe07d4ea114f7e1b0c95a088d6c226c09e9bd7.
https://honcho.pdurlej.com/openapi.json returned HTTP 200.
home-platform-honcho-postgres-1 and home-platform-honcho-redis-1 were not recreated.

Known constraints

The runtime override still exists and is now aligned to 3.0.6. Ollama red-team advisory flagged that explicit override as a future drift footgun; the report records this as follow-up rather than mutating more runtime state in this PR.

Explicit out-of-scope

Removing HONCHO_IMAGE from runtime env.
Changing Honcho source/build provenance.
Database migrations, queue inspection, message/content inspection, secret changes, public exposure changes, or merge/automerge.

Requested decision

Approve that the repo-observed image metadata and reconcile report match the verified live runtime state.

Merge blockers

Any regression in Honcho API/deriver container health.
Evidence that 3.0.6 is not the intended local image for this issue.
Any secret/runtime content accidentally present in the report.

Spec sources read

Issue #731 body and labels: target scope and acceptance.
modules/honcho-api/module.yaml: declared artifact and observed runtime metadata.
modules/honcho-deriver/module.yaml: observed runtime metadata for paired worker.
compose/apps/compose.yaml: Honcho service image default and runtime env interaction.
schema/module.schema.json: image_observed format for local builds.
state/reports/honcho-qwen-runtime-reconcile-2026-06-04.md: local report style and evidence boundaries.

Verification

UV_CACHE_DIR=/private/tmp/uv-cache uv run --project control-plane platformctl validate modules/honcho-api/module.yaml --json
UV_CACHE_DIR=/private/tmp/uv-cache uv run --project control-plane platformctl validate modules/honcho-deriver/module.yaml --json
git diff --cached --check
Runtime inspect/smoke evidence recorded above and in the report.

Closes #731

Canary status: missing - fire canary 3+3 manually before merge ## Canary Context Pack ### Product story Honcho should not leave the operator guessing whether repo state or runtime state is true. Issue #731 asked to either land the declared 3.0.6 runtime or revert the declaration; runtime was reconciled to the declared local image and the manifests now record that evidence. ### What changed - Updated `honcho-api` and `honcho-deriver` observed image metadata from `home-platform-honcho:3.0.3` to `home-platform-honcho:3.0.6`. - Added `state/reports/honcho-306-runtime-reconcile-2026-06-10.md` with root cause, runtime evidence, rollback, and follow-up. ### Why it changed `compose/apps/compose.yaml` and `honcho-api` artifact metadata already pointed at `home-platform-honcho:3.0.6`, but live containers were still on 3.0.3 because `/opt/pdurlej-platform/runtime/compose.env` had a stale `HONCHO_IMAGE=home-platform-honcho:3.0.3` override. ### Files touched - `modules/honcho-api/module.yaml` - `modules/honcho-deriver/module.yaml` - `state/reports/honcho-306-runtime-reconcile-2026-06-10.md` ### Relevant context - Issue #731: `ops(honcho): honcho-api 3.0.6 declared but 3.0.3 live - land or revert` - `compose/apps/compose.yaml` Honcho services default to `${HONCHO_IMAGE:-home-platform-honcho:3.0.6}`. - Local build schema permits tag-only `image_observed` for `image_build: local`; local image ID is recorded in the report as evidence, not as a fake registry digest. ### Runtime evidence - Runtime env now reports `HONCHO_IMAGE=home-platform-honcho:3.0.6`. - `home-platform-honcho-api-1`: `home-platform-honcho:3.0.6`, running, healthy. - `home-platform-honcho-deriver-1`: `home-platform-honcho:3.0.6`, running, healthy. - Both containers inspected with image ID `sha256:1d843c9f83136be5651589d60bfe07d4ea114f7e1b0c95a088d6c226c09e9bd7`. - `https://honcho.pdurlej.com/openapi.json` returned HTTP 200. - `home-platform-honcho-postgres-1` and `home-platform-honcho-redis-1` were not recreated. ### Known constraints The runtime override still exists and is now aligned to 3.0.6. Ollama red-team advisory flagged that explicit override as a future drift footgun; the report records this as follow-up rather than mutating more runtime state in this PR. ### Explicit out-of-scope - Removing `HONCHO_IMAGE` from runtime env. - Changing Honcho source/build provenance. - Database migrations, queue inspection, message/content inspection, secret changes, public exposure changes, or merge/automerge. ### Requested decision Approve that the repo-observed image metadata and reconcile report match the verified live runtime state. ### Merge blockers - Any regression in Honcho API/deriver container health. - Evidence that 3.0.6 is not the intended local image for this issue. - Any secret/runtime content accidentally present in the report. ## Spec sources read - Issue #731 body and labels: target scope and acceptance. - `modules/honcho-api/module.yaml`: declared artifact and observed runtime metadata. - `modules/honcho-deriver/module.yaml`: observed runtime metadata for paired worker. - `compose/apps/compose.yaml`: Honcho service image default and runtime env interaction. - `schema/module.schema.json`: `image_observed` format for local builds. - `state/reports/honcho-qwen-runtime-reconcile-2026-06-04.md`: local report style and evidence boundaries. ## Verification - `UV_CACHE_DIR=/private/tmp/uv-cache uv run --project control-plane platformctl validate modules/honcho-api/module.yaml --json` - `UV_CACHE_DIR=/private/tmp/uv-cache uv run --project control-plane platformctl validate modules/honcho-deriver/module.yaml --json` - `git diff --cached --check` - Runtime inspect/smoke evidence recorded above and in the report. Closes #731

codex added the

labels

2026-06-10 22:12:24 +02:00

codex added 1 commit

2026-06-10 22:12:24 +02:00

ops(honcho): reconcile 3.0.6 runtime image

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

Details

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

Details

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

Details

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

Details

canary-required / canary (pull_request) Has been skipped

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / dry-run (pull_request) Successful in 19s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 1m53s

Details

22786ec67b

pdurlej merged commit a8235434f0 into main

2026-06-10 22:15:24 +02:00

pdurlej deleted branch codex/issues/731-honcho-306-reconcile

2026-06-10 22:15:24 +02:00

pdurlej referenced this pull request from a commit

2026-06-10 22:15:25 +02:00

Merge pull request 'ops(honcho): reconcile 3.0.6 runtime image' (#776) from codex/issues/731-honcho-306-reconcile into main

codex referenced this pull request

2026-06-10 22:27:38 +02:00

ops(honcho): codify 3.0.9 host-ops runtime #777

patchwarden commented

2026-06-10 22:28:16 +02:00

First-time contributor

Patchwarden PR sanity

Status: eligible_sanity_clean
PR: 776
Commit: 22786ec67b59de2bf7a97dd200b8b1d89b3d808f
Security-sensitive label: missing
Authority: advisory model review plus deterministic blockers only
3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

`global-glm` / `glm-5.1:cloud`

Status: ok
Verdict: OK
Findings: none

`global-deepseek` / `deepseek-v4-pro:cloud`

Status: ok
Verdict: OK
Findings: none

`redteam` / `kimi-k2.6:cloud`

Status: ok
Verdict: OK
Findings: none

Policy notes

GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
Auto-merge is not enabled here.

# Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `776` - Commit: `22786ec67b59de2bf7a97dd200b8b1d89b3d808f` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.