fix(modules): shorten Umami outcome for strict-v2 #281

Merged
pdurlej merged 1 commit from codex/f2/umami-strict-v2-outcome into main 2026-05-14 11:47:21 +02:00
Collaborator

Canary status: missing — not fired because F2 batch hit 2/3 watchdog restarts; avoid triggering more deploy-host jobs before operator decision.

Canary Context Pack

Product story

F2 ramp should only smoke modules that already pass strict-v2 validation. During the 2026-05-14 F2 batch, Umami was the next target after two green smokes, but strict-v2 rejected its manifest before runtime smoke.

What changed

Shortened spec.intent.user_facing_outcome in modules/umami/module.yaml to fit the v2 strict schema limit. Detailed context remains in the existing acknowledged risks.

Why it changed

The previous prose exceeded the strict-v2 max length and blocked the Umami no-op smoke.

Files touched

  • modules/umami/module.yaml

Relevant context

  • Issue #142 F2 ramp continuation
  • PR #280 dispatch: prompts/codex-f2-ramp-continuation-2026-05-14.md
  • #260 watchdog observations during this same batch

Runtime evidence

No runtime mutation and no workflow_dispatch in this PR. F2 batch was stopped before a third watchdog restart.

Known constraints

This does not change Umami runtime behavior, exposure, secrets, health checks, or compose config.

Explicit out-of-scope

No Umami smoke. No deploy-runner fix. No changes to acknowledged risks.

Requested decision

Merge after operator/orchestrator accepts that this is a metadata-only strict-v2 unblocker.

Merge blockers

Any schema validation failure or concern that the shortened operator outcome loses required product context.

Spec sources read

  • prompts/codex-f2-ramp-continuation-2026-05-14.md — dispatch for this batch
  • modules/umami/module.yaml — failing manifest
  • schema/module.schema.v2.json — strict-v2 limit source, indirectly via validator output

Validation

  • uv run --project control-plane python -m platformctl.cli validate --strict-v2 modules/umami/module.yaml — pass
  • uv run --project control-plane --extra dev pytest control-plane/platformctl/tests/test_validate.py -q — 6 passed

Refs #142
Refs #260

Canary status: missing — not fired because F2 batch hit 2/3 watchdog restarts; avoid triggering more deploy-host jobs before operator decision. ## Canary Context Pack ### Product story F2 ramp should only smoke modules that already pass strict-v2 validation. During the 2026-05-14 F2 batch, Umami was the next target after two green smokes, but strict-v2 rejected its manifest before runtime smoke. ### What changed Shortened `spec.intent.user_facing_outcome` in `modules/umami/module.yaml` to fit the v2 strict schema limit. Detailed context remains in the existing acknowledged risks. ### Why it changed The previous prose exceeded the strict-v2 max length and blocked the Umami no-op smoke. ### Files touched - `modules/umami/module.yaml` ### Relevant context - Issue #142 F2 ramp continuation - PR #280 dispatch: `prompts/codex-f2-ramp-continuation-2026-05-14.md` - #260 watchdog observations during this same batch ### Runtime evidence No runtime mutation and no workflow_dispatch in this PR. F2 batch was stopped before a third watchdog restart. ### Known constraints This does not change Umami runtime behavior, exposure, secrets, health checks, or compose config. ### Explicit out-of-scope No Umami smoke. No deploy-runner fix. No changes to acknowledged risks. ### Requested decision Merge after operator/orchestrator accepts that this is a metadata-only strict-v2 unblocker. ### Merge blockers Any schema validation failure or concern that the shortened operator outcome loses required product context. ## Spec sources read - `prompts/codex-f2-ramp-continuation-2026-05-14.md` — dispatch for this batch - `modules/umami/module.yaml` — failing manifest - `schema/module.schema.v2.json` — strict-v2 limit source, indirectly via validator output ## Validation - `uv run --project control-plane python -m platformctl.cli validate --strict-v2 modules/umami/module.yaml` — pass - `uv run --project control-plane --extra dev pytest control-plane/platformctl/tests/test_validate.py -q` — 6 passed Refs #142 Refs #260
fix(modules): shorten umami outcome for strict-v2
All checks were successful
canary-required / collect-diff (pull_request) Successful in 5s
platformctl plan / auto-apply scope (pull_request) Successful in 20s
base-is-main / guard (pull_request) Successful in 1s
canary-required / canary (pull_request) Successful in 14s
97c1d7790e
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!281
No description provided.