fix(f3): catalog infisical redis for stateful smoke #312

Merged
pdurlej merged 1 commit from codex/f3/infisical-redis-strict-v2 into main 2026-05-17 02:25:56 +02:00
Collaborator

Canary status: missing — module manifest change; rely on required Forgejo checks before merge

Canary Context Pack

Product story

F3 stateful smoke needs manifests to pass strict-v2 before any backup/apply gate. infisical-redis is part of the Infisical final-boss tranche and was blocked only by missing catalog metadata.

What changed

  • Added strict-v2 intent outcome and acceptance criteria for infisical-redis.
  • Added observed Redis image digest/audit metadata from live RS2000 runtime.
  • Recorded the Docker volume and Redis password reference.
  • Added an acknowledged state-loss risk for Redis AOF/RDB restore behavior.

Why it changed

The next RS2000 F3 tranche is infisical-redis then infisical. infisical already passed strict-v2; infisical-redis needed metadata before backup-before and workflow smoke.

Files touched

  • modules/infisical-redis/module.yaml

Runtime evidence

  • Live container: home-platform-infisical-redis-1 running/healthy on RS2000.
  • Image digest: redis:7.4.7-alpine@sha256:02f2cc4882f8bf87c79a220ac958f58c700bdec0dfb9b9ea61b62fb0e8f1bfcf.
  • Volume: home-platform_infisical_redis_data mounted at /data.

Known constraints

This PR does not run backup or smoke by itself. Runtime mutation remains gated by explicit backup-before and platformctl-auto-apply.yml F3 workflow.

Explicit out-of-scope

  • No compose changes.
  • No Infisical runtime restart.
  • No direct secret inspection.

Requested decision

Merge after checks. This unblocks the infisical-redis F3 backup/smoke.

Merge blockers

  • strict-v2 validation failure
  • workflow lint/schema failure

Spec sources read

  • modules/infisical-redis/module.yaml — target manifest
  • modules/honcho-redis/module.yaml — local Redis strict-v2 pattern
  • compose/apps/compose.yaml — live compose service/volume names
  • scripts/cutover/README.md — F3 class mapping

Verification

control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/infisical-redis/module.yaml
control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/infisical/module.yaml
control-plane/.venv/bin/pytest control-plane/platformctl/tests/test_validate.py -q
git diff --check

Refs: #142

Canary status: missing — module manifest change; rely on required Forgejo checks before merge ## Canary Context Pack ### Product story F3 stateful smoke needs manifests to pass strict-v2 before any backup/apply gate. `infisical-redis` is part of the Infisical final-boss tranche and was blocked only by missing catalog metadata. ### What changed - Added strict-v2 intent outcome and acceptance criteria for `infisical-redis`. - Added observed Redis image digest/audit metadata from live RS2000 runtime. - Recorded the Docker volume and Redis password reference. - Added an acknowledged state-loss risk for Redis AOF/RDB restore behavior. ### Why it changed The next RS2000 F3 tranche is `infisical-redis` then `infisical`. `infisical` already passed strict-v2; `infisical-redis` needed metadata before backup-before and workflow smoke. ### Files touched - `modules/infisical-redis/module.yaml` ### Runtime evidence - Live container: `home-platform-infisical-redis-1` running/healthy on RS2000. - Image digest: `redis:7.4.7-alpine@sha256:02f2cc4882f8bf87c79a220ac958f58c700bdec0dfb9b9ea61b62fb0e8f1bfcf`. - Volume: `home-platform_infisical_redis_data` mounted at `/data`. ### Known constraints This PR does not run backup or smoke by itself. Runtime mutation remains gated by explicit backup-before and `platformctl-auto-apply.yml` F3 workflow. ### Explicit out-of-scope - No compose changes. - No Infisical runtime restart. - No direct secret inspection. ### Requested decision Merge after checks. This unblocks the `infisical-redis` F3 backup/smoke. ### Merge blockers - strict-v2 validation failure - workflow lint/schema failure ## Spec sources read - `modules/infisical-redis/module.yaml` — target manifest - `modules/honcho-redis/module.yaml` — local Redis strict-v2 pattern - `compose/apps/compose.yaml` — live compose service/volume names - `scripts/cutover/README.md` — F3 class mapping ## Verification ```bash control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/infisical-redis/module.yaml control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/infisical/module.yaml control-plane/.venv/bin/pytest control-plane/platformctl/tests/test_validate.py -q git diff --check ``` Refs: #142
fix(f3): catalog infisical redis for stateful smoke
All checks were successful
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
platformctl plan / auto-apply scope (pull_request) Successful in 20s
canary-required / canary (pull_request) Successful in 12s
patchwarden-pr-sanity / sanity (pull_request) Successful in 20s
c6e3d8a6d4
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!312
No description provided.