fix(modules): keep mirotalk-sfu strict-v2 valid #258

Merged
pdurlej merged 1 commit from codex/cutover/mirotalk-sfu-strict-v2 into main 2026-05-13 18:27:08 +02:00
Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

F1.5 corrected target mirotalk-sfu is stateless and safe for a no-op smoke, but strict-v2 validation was blocked by an overlong user-facing outcome string. This PR makes the manifest validate without changing runtime truth.

What changed

  • Shortened spec.intent.user_facing_outcome for mirotalk-sfu.
  • No runtime, exposure, health, image, statefulness, or dependency fields changed.

Why it changed

platformctl validate --strict-v2 modules/mirotalk-sfu/module.yaml failed because the outcome exceeded the schema length limit.

Files touched

  • modules/mirotalk-sfu/module.yaml

Relevant context

  • Issue #142 cutover lane
  • Pan Herbatka F1.5 correction: mirotalk-sfu is a verified stateless target
  • Prior dashboard smoke run #621 / API #757

Runtime evidence

No runtime mutation in this PR. Existing module/runbook classify mirotalk-sfu as stateless with no volumes.

Known constraints

  • This PR only unblocks strict-v2 validation before no-op smoke.
  • Smoke is still separate and will run only after this lands on main.

Explicit out-of-scope

  • No production apply.
  • No compose changes.
  • No exposure policy change.
  • No stateful work.

Requested decision

Merge so Codex can resume F1.5 mirotalk-sfu no-op smoke.

Merge blockers

  • Strict-v2 validation fails.
  • Review finds the shortened outcome lost material operator meaning.

Spec sources read

  • modules/mirotalk-sfu/module.yaml — changed manifest.
  • modules/mirotalk-sfu/runbook.md — confirmed stateless/no volumes context.
  • prompts/codex-f1.5-hardening-f2-2026-05-13.md plus inline correction — target selection and procedure.

Verification

/tmp/platformctl-test-venv/bin/python -m platformctl validate --strict-v2 modules/mirotalk-sfu/module.yaml
/tmp/platformctl-test-venv/bin/pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_health_phase3.py -q

Result: strict-v2 validation OK; 25 passed.

Refs #142

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story F1.5 corrected target `mirotalk-sfu` is stateless and safe for a no-op smoke, but strict-v2 validation was blocked by an overlong user-facing outcome string. This PR makes the manifest validate without changing runtime truth. ### What changed - Shortened `spec.intent.user_facing_outcome` for `mirotalk-sfu`. - No runtime, exposure, health, image, statefulness, or dependency fields changed. ### Why it changed `platformctl validate --strict-v2 modules/mirotalk-sfu/module.yaml` failed because the outcome exceeded the schema length limit. ### Files touched - `modules/mirotalk-sfu/module.yaml` ### Relevant context - Issue #142 cutover lane - Pan Herbatka F1.5 correction: `mirotalk-sfu` is a verified stateless target - Prior dashboard smoke run #621 / API #757 ### Runtime evidence No runtime mutation in this PR. Existing module/runbook classify `mirotalk-sfu` as stateless with no volumes. ### Known constraints - This PR only unblocks strict-v2 validation before no-op smoke. - Smoke is still separate and will run only after this lands on `main`. ### Explicit out-of-scope - No production apply. - No compose changes. - No exposure policy change. - No stateful work. ### Requested decision Merge so Codex can resume F1.5 `mirotalk-sfu` no-op smoke. ### Merge blockers - Strict-v2 validation fails. - Review finds the shortened outcome lost material operator meaning. ## Spec sources read - `modules/mirotalk-sfu/module.yaml` — changed manifest. - `modules/mirotalk-sfu/runbook.md` — confirmed stateless/no volumes context. - `prompts/codex-f1.5-hardening-f2-2026-05-13.md` plus inline correction — target selection and procedure. ## Verification ```bash /tmp/platformctl-test-venv/bin/python -m platformctl validate --strict-v2 modules/mirotalk-sfu/module.yaml /tmp/platformctl-test-venv/bin/pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_health_phase3.py -q ``` Result: strict-v2 validation OK; 25 passed. Refs #142
fix(modules): keep mirotalk-sfu strict-v2 valid
All checks were successful
canary-required / collect-diff (pull_request) Successful in 4s
platformctl plan / auto-apply scope (pull_request) Successful in 19s
canary-required / canary (pull_request) Successful in 13s
base-is-main / guard (pull_request) Successful in 1s
c2b8633c7b
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!258
No description provided.