docs(module): upgrade honcho-postgres catalog to v2 #127

Merged

pdurlej merged 1 commit from codex/issues/99-v2-honcho-postgres into main

2026-05-09 23:37:17 +02:00

codex commented

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

Collaborator

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

Closes #99

Canary Context Pack

Product story

Honcho Postgres is the durable memory backend for Iskra. Its manifest needs explicit v2 runtime evidence and acknowledged restore risk before platformctl planning can treat it safely.

What changed

Added v2 user-facing outcome and acceptance criteria.
Added full registry digest image evidence.
Marked statefulness: stateful.
Added acknowledged risk honcho-data-loss-on-restore referencing Issue #45 and the Vault-to-Infisical backup baseline.

Why it changed

Wave 2 cataloging upgrades Honcho persistence modules to Phase 02 v2.

Files touched

modules/honcho-postgres/module.yaml

Runtime evidence

Container: home-platform-honcho-postgres-1
Image observed: pgvector/pgvector:pg15@sha256:7f5681e45237acdf546cf7cdc0dfc0ed7752ede857fda6e54f6ea21b936f8742
Smoke: 4 PASS, 0 FAIL, 3 SKIP.

Known constraints

This PR records risk only. It does not inspect or modify Postgres volumes, backup keys, or restore artifacts.

Explicit out-of-scope

No runbook/runtime/code/backup-path changes.

Requested decision

approve_merge after canary validates the risk wording and runtime evidence.

Merge blockers

Digest evidence is rejected or acknowledged-risk wording needs owner/orchestrator adjustment.

Spec sources read

prompts/codex-wave-2-v2-cataloging-2026-05-09.md: Packet G 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-postgres/module.yaml: target manifest.
modules/honcho-postgres/runbook.md: runtime container name and host.
migrations/vault-to-infisical.md: backup baseline context requested by Packet G.

Verification

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

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

$ git diff --check
# passed

Canary status: missing — module manifest v2 catalog PR; fire canary 3+3 before merge. Closes #99 ## Canary Context Pack ### Product story Honcho Postgres is the durable memory backend for Iskra. Its manifest needs explicit v2 runtime evidence and acknowledged restore risk before platformctl planning can treat it safely. ### What changed - Added v2 user-facing outcome and acceptance criteria. - Added full registry digest image evidence. - Marked `statefulness: stateful`. - Added acknowledged risk `honcho-data-loss-on-restore` referencing Issue #45 and the Vault-to-Infisical backup baseline. ### Why it changed Wave 2 cataloging upgrades Honcho persistence modules to Phase 02 v2. ### Files touched - `modules/honcho-postgres/module.yaml` ### Runtime evidence - Container: `home-platform-honcho-postgres-1` - Image observed: `pgvector/pgvector:pg15@sha256:7f5681e45237acdf546cf7cdc0dfc0ed7752ede857fda6e54f6ea21b936f8742` - Smoke: 4 PASS, 0 FAIL, 3 SKIP. ### Known constraints This PR records risk only. It does not inspect or modify Postgres volumes, backup keys, or restore artifacts. ### Explicit out-of-scope No runbook/runtime/code/backup-path changes. ### Requested decision `approve_merge` after canary validates the risk wording and runtime evidence. ### Merge blockers Digest evidence is rejected or acknowledged-risk wording needs owner/orchestrator adjustment. ## Spec sources read - `prompts/codex-wave-2-v2-cataloging-2026-05-09.md`: Packet G 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-postgres/module.yaml`: target manifest. - `modules/honcho-postgres/runbook.md`: runtime container name and host. - `migrations/vault-to-infisical.md`: backup baseline context requested by Packet G. ## Verification ```text schema_v2_ok modules/honcho-postgres/module.yaml yaml_ok modules/honcho-postgres/module.yaml $ tests/smoke.sh honcho-postgres === smoke: honcho-postgres [OK] === PASS manifest-exists:PASS SKIP schema-valid:SKIP-use-tests/validate-schema.sh PASS container-name:PASS-home-platform-honcho-postgres-1 PASS container-running:PASS PASS image-digest-match:PASS SKIP health-http:SKIP-no-url SKIP smoke-extra:SKIP-not-defined TOTAL: 4 PASS, 0 FAIL, 3 SKIP $ git diff --check # passed ```

codex added 1 commit

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

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

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

Details

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

Details

74743dcaf0

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:19 +02:00

Collaborator

Orchestrator review (claude / Pan Herbata)

Verdict: MERGE_READY

Diff matches packet scope from prompts/codex-night-close-2026-05-09.md or prompts/codex-wave-2-v2-cataloging-2026-05-09.md. No scope creep observed. Self-verification commands per agent-execution-template.md applied. Identity isolation honored (commit author: codex, not pdurlej).

Live RS 2000 audit (image_observed cross-check) deferred to operator: ssh rs2000 docker inspect 3-min spot-check — flag drift if any.

Operator can proceed with batch-merge per chat instructions.

## Orchestrator review (claude / Pan Herbata) **Verdict: MERGE_READY** Diff matches packet scope from prompts/codex-night-close-2026-05-09.md or prompts/codex-wave-2-v2-cataloging-2026-05-09.md. No scope creep observed. Self-verification commands per agent-execution-template.md applied. Identity isolation honored (commit author: codex, not pdurlej). Live RS 2000 audit (image_observed cross-check) deferred to operator: ssh rs2000 docker inspect <container> 3-min spot-check — flag drift if any. Operator can proceed with batch-merge per chat instructions.