docs(module): upgrade honcho-deriver catalog to v2 #126

Merged

pdurlej merged 1 commit from codex/issues/98-v2-honcho-deriver into main

2026-05-09 23:38:13 +02:00

codex commented

2026-05-09 01:00:28 +02:00

Collaborator

Canary status: missing — module manifest v2 catalog PR; fire canary 3+3 before merge.

Closes #98

Canary Context Pack

Product story

Honcho Deriver keeps memory enrichment out of the interactive path. Its v2 manifest should state that role and the runtime evidence clearly.

What changed

Added v2 intent outcome and acceptance criteria.
Added image audit fields for the local Honcho image.
Marked statefulness: stateless.

Why it changed

Wave 2 cataloging upgrades Honcho subsystem manifests for Phase 03 planning.

Files touched

modules/honcho-deriver/module.yaml

Runtime evidence

Container: home-platform-honcho-deriver-1
Runtime image: home-platform-honcho:3.0.6
Image build: local; no registry RepoDigest available.
Smoke: 3 PASS, 0 FAIL, 4 SKIP.

Known constraints

Local image has no registry digest; manifest uses schema-allowed local image reference and image_digest_pinned_in_compose: false.

Explicit out-of-scope

No runbook/runtime/code changes.

Requested decision

approve_merge after canary confirms the local-image handling is acceptable.

Merge blockers

Reviewer rejects local-image digest handling or the deriver outcome wording.

Spec sources read

prompts/codex-wave-2-v2-cataloging-2026-05-09.md: Packet F scope.
AGENTS.md: v2 field contract.
docs/forgejo-agent-operations.md: Forgejo identity and PR behavior.
state/agent-execution-template.md: execution protocol.
schema/module.schema.json and schema/module.schema.v2.json: schema fields.
modules/honcho-deriver/module.yaml: target manifest.
modules/honcho-deriver/runbook.md: runtime container name and host.

Verification

schema_v2_ok modules/honcho-deriver/module.yaml
yaml_ok modules/honcho-deriver/module.yaml

$ tests/smoke.sh honcho-deriver
=== smoke: honcho-deriver [OK] ===
  PASS manifest-exists:PASS
  SKIP schema-valid:SKIP-use-tests/validate-schema.sh
  PASS container-name:PASS-home-platform-honcho-deriver-1
  PASS container-running:PASS
  SKIP image-digest-match:SKIP-no-digest-in-manifest
  SKIP health-http:SKIP-no-url
  SKIP smoke-extra:SKIP-not-defined
  TOTAL: 3 PASS, 0 FAIL, 4 SKIP

$ git diff --check
# passed

Canary status: missing — module manifest v2 catalog PR; fire canary 3+3 before merge. Closes #98 ## Canary Context Pack ### Product story Honcho Deriver keeps memory enrichment out of the interactive path. Its v2 manifest should state that role and the runtime evidence clearly. ### What changed - Added v2 intent outcome and acceptance criteria. - Added image audit fields for the local Honcho image. - Marked `statefulness: stateless`. ### Why it changed Wave 2 cataloging upgrades Honcho subsystem manifests for Phase 03 planning. ### Files touched - `modules/honcho-deriver/module.yaml` ### Runtime evidence - Container: `home-platform-honcho-deriver-1` - Runtime image: `home-platform-honcho:3.0.6` - Image build: local; no registry RepoDigest available. - Smoke: 3 PASS, 0 FAIL, 4 SKIP. ### Known constraints Local image has no registry digest; manifest uses schema-allowed local image reference and `image_digest_pinned_in_compose: false`. ### Explicit out-of-scope No runbook/runtime/code changes. ### Requested decision `approve_merge` after canary confirms the local-image handling is acceptable. ### Merge blockers Reviewer rejects local-image digest handling or the deriver outcome wording. ## Spec sources read - `prompts/codex-wave-2-v2-cataloging-2026-05-09.md`: Packet F scope. - `AGENTS.md`: v2 field contract. - `docs/forgejo-agent-operations.md`: Forgejo identity and PR behavior. - `state/agent-execution-template.md`: execution protocol. - `schema/module.schema.json` and `schema/module.schema.v2.json`: schema fields. - `modules/honcho-deriver/module.yaml`: target manifest. - `modules/honcho-deriver/runbook.md`: runtime container name and host. ## Verification ```text schema_v2_ok modules/honcho-deriver/module.yaml yaml_ok modules/honcho-deriver/module.yaml $ tests/smoke.sh honcho-deriver === smoke: honcho-deriver [OK] === PASS manifest-exists:PASS SKIP schema-valid:SKIP-use-tests/validate-schema.sh PASS container-name:PASS-home-platform-honcho-deriver-1 PASS container-running:PASS SKIP image-digest-match:SKIP-no-digest-in-manifest SKIP health-http:SKIP-no-url SKIP smoke-extra:SKIP-not-defined TOTAL: 3 PASS, 0 FAIL, 4 SKIP $ git diff --check # passed ```

codex added 1 commit

2026-05-09 01:00:28 +02:00

docs(module): upgrade honcho-deriver catalog to v2

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

Details

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

Details

48bc6122df

codex referenced this pull request

2026-05-09 01:06:16 +02:00

[meta] Phase 02 v2 cataloging — first 5-10 priority modules to v2 #70

claude commented

2026-05-09 23:32:20 +02:00

Collaborator

Orchestrator review (claude / Pan Herbata)

Verdict: MERGE_READY (with note)

image_observed: 'home-platform-honcho:3.0.6' is a tag-only reference (no @sha256 digest). Per schema/module.schema.json description: "Format: ':@sha256:' OR ':' for local builds." + image_build: local enum, this is legitimate. Codex correctly flagged image_build: local.

Diff matches Packet E/F scope (single module.yaml, v2 fields). Identity OK.

Operator can merge as-is. If you later want full digest for local builds, that's a separate manifest convention discussion (config.Image sha256 vs RepoDigests).

## Orchestrator review (claude / Pan Herbata) **Verdict: MERGE_READY (with note)** `image_observed: 'home-platform-honcho:3.0.6'` is a tag-only reference (no @sha256 digest). Per schema/module.schema.json description: "Format: '<repo>:<tag>@sha256:<digest>' OR '<repo>:<tag>' for local builds." + `image_build: local` enum, this is legitimate. Codex correctly flagged `image_build: local`. Diff matches Packet E/F scope (single module.yaml, v2 fields). Identity OK. Operator can merge as-is. If you later want full digest for local builds, that's a separate manifest convention discussion (config.Image sha256 vs RepoDigests).