pdurlej/platform

Fork 0

docs(module): upgrade honcho-api catalog to v2 #125

Merged

pdurlej merged 1 commit from codex/issues/97-v2-honcho-api into main

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

codex commented

2026-05-09 00:59:43 +02:00

Collaborator

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

Closes #97

Canary Context Pack

Product story

Honcho API is the stable memory API for Iskra and operator tooling. Moving the manifest to v2 makes its user outcome, runtime image evidence, and statelessness explicit for Phase 03 planning.

What changed

Added v2 intent outcome and acceptance criteria.
Added runtime image audit fields from RS2000 evidence.
Marked statefulness: stateless.

Why it changed

Wave 2 cataloging requires Honcho core modules to carry v2 audit fields before broader platformctl planning work.

Files touched

modules/honcho-api/module.yaml

Relevant context

prompts/codex-wave-2-v2-cataloging-2026-05-09.md Packet E.
AGENTS.md Phase 02 v2 field contract.
modules/honcho-api/runbook.md container name and host.

Runtime evidence

Container: home-platform-honcho-api-1
Runtime image: home-platform-honcho:3.0.6
Image build: local; no registry RepoDigest available, so smoke skips digest comparison as local/no-digest.
Smoke: 4 PASS, 0 FAIL, 3 SKIP.

Known constraints

The prompt's exact container RepoDigests command is not valid for this local image; Docker reports no registry digest for home-platform-honcho:3.0.6. The manifest therefore follows the existing schema allowance for local builds: image ref without digest, image_build: local, image_digest_pinned_in_compose: false.

Explicit out-of-scope

No runbook changes.
No runtime changes or restarts.
No Honcho API behavior changes.

Requested decision

approve_merge after canary confirms local-build image evidence is acceptable.

Merge blockers

Reviewer requires registry digest for local Honcho images despite current schema allowance.
Smoke result is considered insufficient for API acceptance criteria.

Spec sources read

prompts/codex-wave-2-v2-cataloging-2026-05-09.md: Packet E 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: v2-compatible runtime field definitions.
schema/module.schema.v2.json: v2 extension schema.
modules/honcho-api/module.yaml: target manifest.
modules/honcho-api/runbook.md: runtime container name and host.

Verification

$ python3.13 -c "import yaml; yaml.safe_load(open('modules/honcho-api/module.yaml')); print('yaml_ok modules/honcho-api/module.yaml')"
yaml_ok modules/honcho-api/module.yaml

$ python3.13 <yaml+jsonschema v2 validator>
schema_v2_ok modules/honcho-api/module.yaml

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

$ git diff --check
# passed

Test plan

Confirm local-build image handling is acceptable for Honcho API.
Confirm the user-facing outcome matches Honcho's memory API role.

Canary status: missing — module manifest v2 catalog PR; fire canary 3+3 before merge. Closes #97 ## Canary Context Pack ### Product story Honcho API is the stable memory API for Iskra and operator tooling. Moving the manifest to v2 makes its user outcome, runtime image evidence, and statelessness explicit for Phase 03 planning. ### What changed - Added v2 intent outcome and acceptance criteria. - Added runtime image audit fields from RS2000 evidence. - Marked `statefulness: stateless`. ### Why it changed Wave 2 cataloging requires Honcho core modules to carry v2 audit fields before broader platformctl planning work. ### Files touched - `modules/honcho-api/module.yaml` ### Relevant context - `prompts/codex-wave-2-v2-cataloging-2026-05-09.md` Packet E. - `AGENTS.md` Phase 02 v2 field contract. - `modules/honcho-api/runbook.md` container name and host. ### Runtime evidence - Container: `home-platform-honcho-api-1` - Runtime image: `home-platform-honcho:3.0.6` - Image build: local; no registry RepoDigest available, so smoke skips digest comparison as local/no-digest. - Smoke: 4 PASS, 0 FAIL, 3 SKIP. ### Known constraints The prompt's exact container `RepoDigests` command is not valid for this local image; Docker reports no registry digest for `home-platform-honcho:3.0.6`. The manifest therefore follows the existing schema allowance for local builds: image ref without digest, `image_build: local`, `image_digest_pinned_in_compose: false`. ### Explicit out-of-scope - No runbook changes. - No runtime changes or restarts. - No Honcho API behavior changes. ### Requested decision `approve_merge` after canary confirms local-build image evidence is acceptable. ### Merge blockers - Reviewer requires registry digest for local Honcho images despite current schema allowance. - Smoke result is considered insufficient for API acceptance criteria. ## Spec sources read - `prompts/codex-wave-2-v2-cataloging-2026-05-09.md`: Packet E 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`: v2-compatible runtime field definitions. - `schema/module.schema.v2.json`: v2 extension schema. - `modules/honcho-api/module.yaml`: target manifest. - `modules/honcho-api/runbook.md`: runtime container name and host. ## Verification ```text $ python3.13 -c "import yaml; yaml.safe_load(open('modules/honcho-api/module.yaml')); print('yaml_ok modules/honcho-api/module.yaml')" yaml_ok modules/honcho-api/module.yaml $ python3.13 <yaml+jsonschema v2 validator> schema_v2_ok modules/honcho-api/module.yaml $ tests/smoke.sh honcho-api === smoke: honcho-api [OK] === PASS manifest-exists:PASS SKIP schema-valid:SKIP-use-tests/validate-schema.sh PASS container-name:PASS-home-platform-honcho-api-1 PASS container-running:PASS SKIP image-digest-match:SKIP-no-digest-in-manifest PASS health-http:PASS-200 SKIP smoke-extra:SKIP-not-defined TOTAL: 4 PASS, 0 FAIL, 3 SKIP $ git diff --check # passed ``` ## Test plan - [ ] Confirm local-build image handling is acceptable for Honcho API. - [ ] Confirm the user-facing outcome matches Honcho's memory API role.

codex added 1 commit

2026-05-09 00:59:43 +02:00

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

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

Details

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

Details

be299e7873

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).