fix(modules): tighten uptime-kuma strict-v2 outcome #300

Merged

pdurlej merged 1 commit from codex/f3/uptime-kuma-strict-v2 into main

2026-05-16 13:24:17 +02:00

codex commented

2026-05-16 13:10:36 +02:00

Collaborator

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

Canary Context Pack

Product story

The first F3 uptime-kuma stateful smoke reached plan/apply safely, but final health failed because the module manifest did not pass strict-v2 length rules. This PR fixes that metadata blocker without changing runtime behavior.

What changed

Shortened spec.intent.user_facing_outcome for uptime-kuma while preserving the important operator-facing facts: Tailnet UI, manual monitor setup/history, experimental state, and no production monitors.

Why it changed

F3 run API 1230 / UI #970 produced backup, eligible F3 scope, in-sync plan, no-op apply, and healthy container. The only failure was strict-v2 manifest validation in platformctl health.

Files touched

modules/uptime-kuma/module.yaml

Relevant context

F3 stateful no-op gate merged in #299.
Backup exists: /opt/pdurlej-platform/backups/uptime-kuma-20260516T110754Z.tar.gz mode 0600.
Run #970 artifact confirms no-op apply and health failure reason.

Runtime evidence

backup-before-apply.sh uptime-kuma completed and archived home-platform_uptime_kuma_data.
Run API 1230, UI #970: plan in-sync, apply noop, container home-platform-uptime-kuma-1 still healthy.
Health failed only on spec/intent/user_facing_outcome too long.

Known constraints

This PR does not retry F3 itself. After merge, Codex will run a fresh backup-before and retry the F3 workflow dispatch.

Explicit out-of-scope

No runtime mutation.
No health endpoint change.
No backup/restore logic change.

Requested decision

Merge so F3 uptime-kuma can be retried through the already-merged stateful no-op gate.

Merge blockers

uptime-kuma must pass strict-v2.
No runtime fields should change.

Spec sources read

modules/uptime-kuma/module.yaml - failing manifest field and F3 target.
scripts/cutover/README.md - F3 first-target guidance.
Artifact from run API 1230 - failure evidence.

Verification

uv run --project control-plane python -m platformctl validate --strict-v2 modules/uptime-kuma/module.yaml -> ok
uv run --project control-plane pytest control-plane/platformctl/tests/test_forgejo_ci_scripts_contract.py control-plane/platformctl/tests/test_health_phase3.py -> 50 passed
git diff --check

Refs: #142, #299

Canary status: missing - fire canary 3+3 manually before merge ## Canary Context Pack ### Product story The first F3 `uptime-kuma` stateful smoke reached plan/apply safely, but final health failed because the module manifest did not pass strict-v2 length rules. This PR fixes that metadata blocker without changing runtime behavior. ### What changed Shortened `spec.intent.user_facing_outcome` for `uptime-kuma` while preserving the important operator-facing facts: Tailnet UI, manual monitor setup/history, experimental state, and no production monitors. ### Why it changed F3 run API `1230` / UI `#970` produced backup, eligible F3 scope, in-sync plan, no-op apply, and healthy container. The only failure was strict-v2 manifest validation in `platformctl health`. ### Files touched - `modules/uptime-kuma/module.yaml` ### Relevant context - F3 stateful no-op gate merged in #299. - Backup exists: `/opt/pdurlej-platform/backups/uptime-kuma-20260516T110754Z.tar.gz` mode `0600`. - Run #970 artifact confirms no-op apply and health failure reason. ### Runtime evidence - `backup-before-apply.sh uptime-kuma` completed and archived `home-platform_uptime_kuma_data`. - Run API `1230`, UI `#970`: plan `in-sync`, apply `noop`, container `home-platform-uptime-kuma-1` still healthy. - Health failed only on `spec/intent/user_facing_outcome` too long. ### Known constraints This PR does not retry F3 itself. After merge, Codex will run a fresh backup-before and retry the F3 workflow dispatch. ### Explicit out-of-scope - No runtime mutation. - No health endpoint change. - No backup/restore logic change. ### Requested decision Merge so F3 `uptime-kuma` can be retried through the already-merged stateful no-op gate. ### Merge blockers - `uptime-kuma` must pass strict-v2. - No runtime fields should change. ## Spec sources read - `modules/uptime-kuma/module.yaml` - failing manifest field and F3 target. - `scripts/cutover/README.md` - F3 first-target guidance. - Artifact from run API `1230` - failure evidence. ## Verification - `uv run --project control-plane python -m platformctl validate --strict-v2 modules/uptime-kuma/module.yaml` -> ok - `uv run --project control-plane pytest control-plane/platformctl/tests/test_forgejo_ci_scripts_contract.py control-plane/platformctl/tests/test_health_phase3.py` -> 50 passed - `git diff --check` Refs: #142, #299

codex added 1 commit

2026-05-16 13:10:36 +02:00

fix(modules): tighten uptime-kuma strict-v2 outcome

base-is-main / guard (pull_request) Successful in 1s

Details

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

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 19s

Details

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