feat(modules): catalog agaria-postgres v2 #152

Merged

pdurlej merged 1 commit from codex/issues/142-v2-agaria-postgres into main

2026-05-10 01:15:58 +02:00

codex commented

2026-05-10 00:59:23 +02:00

Collaborator

Canary status: missing — modules PR; fire canary 3+3 before merge

Canary Context Pack

Product story

Phase 2 needs enough real modules at v2 to make Phase 3 control-plane work credible. This PR catalogs agaria-postgres from live RS 2000 evidence without changing runtime.

What changed

Added Phase 02 v2 intent fields to modules/agaria-postgres/module.yaml.
Recorded live image observation postgres:16-alpine@sha256:4e6e670bb069649261c9c18031f0aded7bb249a5b6664ddec29c013a89310d50.
Set spec.runtime.statefulness: stateful from the observed mounts/runtime shape.
Added non-critical data-store metadata where this module owns persistent local state.

Why it changed

Cutover Flight Phase 2 needs to move pdurlej/platform toward the 30+ v2 module gate before platformctl plan/apply/health becomes the operational path.

Files touched

modules/agaria-postgres/module.yaml

Relevant context

Tracking lane #142
prompts/codex-cutover-flight/dispatch.md
prompts/codex-cutover-flight/phase-2-finish.md
AGENTS.md Phase 02 v2 requirements

Runtime evidence

Sanitized read-only RS 2000 evidence:

container: agaria-postgres
running: True; health: healthy
image_ref: postgres:16-alpine
repo_digest: postgres@sha256:4e6e670bb069649261c9c18031f0aded7bb249a5b6664ddec29c013a89310d50
image_build: registry
exposure label: none/internal by compose context
mounts: /var/lib/postgresql/data:volume:rw:infra_postgres_data
secret env key names only: POSTGRES_PASSWORD

Known constraints

This PR is manifest-only. It does not redeploy, mutate compose, read secret values, or change the runtime exposure boundary.

Explicit out-of-scope

Runtime mutation or deploy
Compose migration from the legacy salvage worktree
Secret delivery changes
Canary execution and merge

Requested decision

Approve this as one Phase 2 module-cataloging slice if the manifest matches the sanitized runtime evidence.

Merge blockers

Runtime image evidence does not match image_observed.
Statefulness classification contradicts observed mounts.
Any reviewer finds a hidden security-sensitive scope expansion.

Verification

PYTHONPATH=control-plane python3 -m platformctl.tools.validate_module modules/agaria-postgres/module.yaml -> ✓ YAML parsed (no duplicates); ✓ schema v2 valid
PYTHONPATH=control-plane python3 -m pytest tests/test_l4_verify.py -q --tb=short -k 'agaria-postgres or yaml_syntax_valid' -> 92 passed, 235 deselected in 2.22s
tests/smoke.sh agaria-postgres -> TOTAL: 4 PASS, 0 FAIL, 3 SKIP
git diff --check -> passed

Spec sources read

docs/forgejo-agent-operations.md - Forgejo identity/API contract
prompts/codex-cutover-flight/dispatch.md - flight-level constraints
prompts/codex-cutover-flight/phase-2-finish.md - Phase 2 packet contract
modules/agaria-postgres/module.yaml - edited manifest
modules/agaria-postgres/runbook.md - container/runtime context
schema/module.schema.v2.json and schema/module.schema.json - v2/runtime field constraints
AGENTS.md - Phase 02 current-phase requirements and PR/canary rules

Part of #142

Canary status: missing — modules PR; fire canary 3+3 before merge ## Canary Context Pack ### Product story Phase 2 needs enough real modules at v2 to make Phase 3 control-plane work credible. This PR catalogs `agaria-postgres` from live RS 2000 evidence without changing runtime. ### What changed - Added Phase 02 v2 intent fields to `modules/agaria-postgres/module.yaml`. - Recorded live image observation `postgres:16-alpine@sha256:4e6e670bb069649261c9c18031f0aded7bb249a5b6664ddec29c013a89310d50`. - Set `spec.runtime.statefulness: stateful` from the observed mounts/runtime shape. - Added non-critical data-store metadata where this module owns persistent local state. ### Why it changed Cutover Flight Phase 2 needs to move `pdurlej/platform` toward the 30+ v2 module gate before platformctl plan/apply/health becomes the operational path. ### Files touched - `modules/agaria-postgres/module.yaml` ### Relevant context - Tracking lane #142 - `prompts/codex-cutover-flight/dispatch.md` - `prompts/codex-cutover-flight/phase-2-finish.md` - AGENTS.md Phase 02 v2 requirements ### Runtime evidence Sanitized read-only RS 2000 evidence: - container: `agaria-postgres` - running: `True`; health: `healthy` - image_ref: `postgres:16-alpine` - repo_digest: `postgres@sha256:4e6e670bb069649261c9c18031f0aded7bb249a5b6664ddec29c013a89310d50` - image_build: `registry` - exposure label: `none/internal by compose context` - mounts: `/var/lib/postgresql/data:volume:rw:infra_postgres_data` - secret env key names only: `POSTGRES_PASSWORD` ### Known constraints This PR is manifest-only. It does not redeploy, mutate compose, read secret values, or change the runtime exposure boundary. ### Explicit out-of-scope - Runtime mutation or deploy - Compose migration from the legacy salvage worktree - Secret delivery changes - Canary execution and merge ### Requested decision Approve this as one Phase 2 module-cataloging slice if the manifest matches the sanitized runtime evidence. ### Merge blockers - Runtime image evidence does not match `image_observed`. - Statefulness classification contradicts observed mounts. - Any reviewer finds a hidden security-sensitive scope expansion. ## Verification - `PYTHONPATH=control-plane python3 -m platformctl.tools.validate_module modules/agaria-postgres/module.yaml` -> ✓ YAML parsed (no duplicates); ✓ schema v2 valid - `PYTHONPATH=control-plane python3 -m pytest tests/test_l4_verify.py -q --tb=short -k 'agaria-postgres or yaml_syntax_valid'` -> 92 passed, 235 deselected in 2.22s - `tests/smoke.sh agaria-postgres` -> TOTAL: 4 PASS, 0 FAIL, 3 SKIP - `git diff --check` -> passed ## Spec sources read - `docs/forgejo-agent-operations.md` - Forgejo identity/API contract - `prompts/codex-cutover-flight/dispatch.md` - flight-level constraints - `prompts/codex-cutover-flight/phase-2-finish.md` - Phase 2 packet contract - `modules/agaria-postgres/module.yaml` - edited manifest - `modules/agaria-postgres/runbook.md` - container/runtime context - `schema/module.schema.v2.json` and `schema/module.schema.json` - v2/runtime field constraints - `AGENTS.md` - Phase 02 current-phase requirements and PR/canary rules Part of #142

codex added 1 commit

2026-05-10 00:59:23 +02:00

feat(modules): catalog agaria-postgres v2

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

Details

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

Details

41fa2290fb

codex referenced this pull request

2026-05-10 01:00:14 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142