docs(w8): record module upgrade readiness #503

Merged

Iskra merged 1 commit from codex/w8-readiness-inventory into main

2026-05-26 09:41:54 +02:00

codex commented

2026-05-26 09:39:07 +02:00

Collaborator

Canary status: missing — rely on required Forgejo checks before merge

Canary Context Pack

Product story

W8 should start with a boring, inspectable readiness packet instead of broad module upgrades. This lets agents choose upgrade candidates from metadata and rollback evidence, not from vibes.

What changed

Added state/cycle/W8-readiness-2026-05-26.md with the current repo-only update readiness snapshot.
Linked that artifact from state/cycle/W8-module-upgrade-prep.md.

Why it changed

#389 needed child W8.0 evidence before W8.1 minio-init can become a real pilot packet.

Files touched

state/cycle/W8-readiness-2026-05-26.md
state/cycle/W8-module-upgrade-prep.md

Relevant context

#389
#501
ADR-0022 source/artifact boundaries
Current W8 module upgrade prep artifact

Runtime evidence

No runtime mutation. Repo-only commands:

PYTHONPATH=control-plane python3 -m platformctl.cli update-report --json
PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json

Results: update report OK; validation exit=0 failures=0; git diff --check passed.

Known constraints

This PR does not upgrade any module and does not request production apply/recreate.

Explicit out-of-scope

Runtime mutation
Service restart/recreate
Image/tag/digest changes
Forgejo/core upgrade execution

Requested decision

Merge as W8.0 readiness evidence.

Merge blockers

Any claim that this PR changes runtime or widens W8 beyond readiness should block merge.

Spec sources read

state/cycle/W8-module-upgrade-prep.md
state/roadmap/current-platform-roadmap.md
decisions/0022-module-source-and-release-boundaries.md
modules/minio-init/module.yaml
.forgejo/issue_template/atomic_task.md

Closes #501

Canary status: missing — rely on required Forgejo checks before merge ## Canary Context Pack ### Product story W8 should start with a boring, inspectable readiness packet instead of broad module upgrades. This lets agents choose upgrade candidates from metadata and rollback evidence, not from vibes. ### What changed - Added `state/cycle/W8-readiness-2026-05-26.md` with the current repo-only update readiness snapshot. - Linked that artifact from `state/cycle/W8-module-upgrade-prep.md`. ### Why it changed #389 needed child W8.0 evidence before W8.1 `minio-init` can become a real pilot packet. ### Files touched - `state/cycle/W8-readiness-2026-05-26.md` - `state/cycle/W8-module-upgrade-prep.md` ### Relevant context - #389 - #501 - ADR-0022 source/artifact boundaries - Current W8 module upgrade prep artifact ### Runtime evidence No runtime mutation. Repo-only commands: ```bash PYTHONPATH=control-plane python3 -m platformctl.cli update-report --json PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json ``` Results: update report OK; validation `exit=0 failures=0`; `git diff --check` passed. ### Known constraints This PR does not upgrade any module and does not request production apply/recreate. ### Explicit out-of-scope - Runtime mutation - Service restart/recreate - Image/tag/digest changes - Forgejo/core upgrade execution ### Requested decision Merge as W8.0 readiness evidence. ### Merge blockers Any claim that this PR changes runtime or widens W8 beyond readiness should block merge. ## Spec sources read - `state/cycle/W8-module-upgrade-prep.md` - `state/roadmap/current-platform-roadmap.md` - `decisions/0022-module-source-and-release-boundaries.md` - `modules/minio-init/module.yaml` - `.forgejo/issue_template/atomic_task.md` Closes #501

codex added 1 commit

2026-05-26 09:39:07 +02:00

docs(w8): record module upgrade readiness

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

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Has been skipped

Details

patchwarden-client-dry-run / dry-run (pull_request) Successful in 21s

Details

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