docs(w8): close uptime-kuma runtime pilot #516

Merged

pdurlej merged 1 commit from codex/w8-uptime-kuma-runtime-closeout into main

2026-05-27 08:36:53 +02:00

codex commented

2026-05-27 08:27:06 +02:00

Collaborator

Canary status: missing — rely on required Forgejo checks and included runtime evidence before merge

Canary Context Pack

Product story

W8 should finish as a small, real module-upgrade wave: metadata readiness, a reversible runtime pilot, and clear evidence of what happened. The operator should not have to reconstruct runtime state from chat scrollback.

What changed

Records the successful Uptime Kuma runtime pilot from 2.1.3 to 2.3.2.
Updates modules/uptime-kuma observed runtime metadata and runbook evidence.
Updates the W8.2 upgrade packet from planned/no-runtime to completed runtime pilot.
Adds a W8 closeout note for #389.

Why it changed

The runtime pilot was approved with w8-uptime-kuma-runtime-approved, executed on RS2000, and verified green. Repo state now needs to match live state.

Files touched

modules/uptime-kuma/module.yaml
modules/uptime-kuma/runbook.md
state/cycle/W8-uptime-kuma-upgrade-packet.md
state/cycle/W8-module-upgrade-closeout.md

Relevant context

W8 plan and parent issue #389.
Prior W8 PRs #509, #510, #511, #512, #513.
Uptime Kuma module manifest/runbook.

Runtime evidence

Backup: /opt/pdurlej-platform/backups/uptime-kuma-20260527T061854Z.tar.gz, 14765 bytes, sha256 c398d97f4b649b85c21bc6496a6a67bdca20acdb9bbae72a3dfa6325907c13ce.
Runtime env: UPTIME_KUMA_IMAGE=louislam/uptime-kuma:2.3.2.
Container: home-platform-uptime-kuma-1, running, Docker health healthy.
Image id: sha256:612463db04fa08c7910c8f776e034c6d9958ebf47ea58fd9ac0a7e14203243ef.
Tailnet smoke: /health returned HTTP 200 via Tailscale IP override.
Unhealthy containers: 0.

Known constraints

Uptime Kuma remains tag-only in compose env and runs as root/default. It remains tailnet-only. Forgejo upgrade is explicitly deferred to W8.final.

Explicit out-of-scope

No further runtime mutation, no Forgejo upgrade, no broad module upgrade, no digest pinning in compose, no public exposure change.

Requested decision

Merge after required checks are green.

Merge blockers

Schema validation failure, contradicted runtime evidence, or unexpected change outside the closeout scope.

Spec sources read

modules/uptime-kuma/module.yaml — observed runtime metadata to update.
modules/uptime-kuma/runbook.md — operator runbook evidence to update.
state/cycle/W8-uptime-kuma-upgrade-packet.md — W8.2 packet to close after pilot.
state/cycle/W8-module-upgrade-closeout.md — new closeout artifact.

Verification

PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json → exitCode 0.
curl --resolve uptime.pdurlej.com:443:100.110.188.20 https://uptime.pdurlej.com/health → HTTP 200.
ssh rs2000 docker inspect home-platform-uptime-kuma-1 → running/healthy on louislam/uptime-kuma:2.3.2.
ssh rs2000 docker ps --filter health=unhealthy → 0 containers.

Closes #389

Canary status: missing — rely on required Forgejo checks and included runtime evidence before merge ## Canary Context Pack ### Product story W8 should finish as a small, real module-upgrade wave: metadata readiness, a reversible runtime pilot, and clear evidence of what happened. The operator should not have to reconstruct runtime state from chat scrollback. ### What changed - Records the successful Uptime Kuma runtime pilot from `2.1.3` to `2.3.2`. - Updates `modules/uptime-kuma` observed runtime metadata and runbook evidence. - Updates the W8.2 upgrade packet from planned/no-runtime to completed runtime pilot. - Adds a W8 closeout note for #389. ### Why it changed The runtime pilot was approved with `w8-uptime-kuma-runtime-approved`, executed on RS2000, and verified green. Repo state now needs to match live state. ### Files touched - `modules/uptime-kuma/module.yaml` - `modules/uptime-kuma/runbook.md` - `state/cycle/W8-uptime-kuma-upgrade-packet.md` - `state/cycle/W8-module-upgrade-closeout.md` ### Relevant context - W8 plan and parent issue #389. - Prior W8 PRs #509, #510, #511, #512, #513. - Uptime Kuma module manifest/runbook. ### Runtime evidence - Backup: `/opt/pdurlej-platform/backups/uptime-kuma-20260527T061854Z.tar.gz`, 14765 bytes, sha256 `c398d97f4b649b85c21bc6496a6a67bdca20acdb9bbae72a3dfa6325907c13ce`. - Runtime env: `UPTIME_KUMA_IMAGE=louislam/uptime-kuma:2.3.2`. - Container: `home-platform-uptime-kuma-1`, `running`, Docker health `healthy`. - Image id: `sha256:612463db04fa08c7910c8f776e034c6d9958ebf47ea58fd9ac0a7e14203243ef`. - Tailnet smoke: `/health` returned HTTP 200 via Tailscale IP override. - Unhealthy containers: 0. ### Known constraints Uptime Kuma remains tag-only in compose env and runs as root/default. It remains tailnet-only. Forgejo upgrade is explicitly deferred to W8.final. ### Explicit out-of-scope No further runtime mutation, no Forgejo upgrade, no broad module upgrade, no digest pinning in compose, no public exposure change. ### Requested decision Merge after required checks are green. ### Merge blockers Schema validation failure, contradicted runtime evidence, or unexpected change outside the closeout scope. ## Spec sources read - `modules/uptime-kuma/module.yaml` — observed runtime metadata to update. - `modules/uptime-kuma/runbook.md` — operator runbook evidence to update. - `state/cycle/W8-uptime-kuma-upgrade-packet.md` — W8.2 packet to close after pilot. - `state/cycle/W8-module-upgrade-closeout.md` — new closeout artifact. ## Verification - `PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json` → exitCode 0. - `curl --resolve uptime.pdurlej.com:443:100.110.188.20 https://uptime.pdurlej.com/health` → HTTP 200. - `ssh rs2000 docker inspect home-platform-uptime-kuma-1` → running/healthy on `louislam/uptime-kuma:2.3.2`. - `ssh rs2000 docker ps --filter health=unhealthy` → 0 containers. Closes #389

codex added 1 commit

2026-05-27 08:27:06 +02:00

docs(w8): close uptime-kuma runtime pilot

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

Details

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

Details

patchwarden-client-dry-run / 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 24s