docs(minio-init): prepare W8 pilot packet #504

Merged

pdurlej merged 1 commit from codex/w8-minio-init-pilot into main

2026-05-26 10:52:18 +02:00

codex commented

2026-05-26 09:49:16 +02:00

Collaborator

Canary status: missing — full required checks must pass before merge

Canary Context Pack

Product story

W8 needs a safe first module-upgrade pilot. For minio-init, the right pilot is not a fake version bump: upstream currently shows the existing minio/mc tag as latest, so this PR records the digest/evidence packet and keeps runtime untouched.

What changed

Added desired spec.artifact.digest for modules/minio-init/module.yaml.
Added state/cycle/W8-minio-init-pilot.md with the W8.1 packet.
Linked the packet from state/cycle/W8-module-upgrade-prep.md.

Why it changed

#501 confirmed minio-init is the correct W8.1 first candidate. #502 needed a concrete packet with old/current digest, upstream tag evidence, smoke contract, rollback, and no-runtime-mutation scope.

Files touched

modules/minio-init/module.yaml
state/cycle/W8-minio-init-pilot.md
state/cycle/W8-module-upgrade-prep.md

Relevant context

#389
#501 / PR #503
#502
ADR-0022 source/artifact boundaries

Runtime evidence

No runtime mutation. Repo/local read-only checks:

curl -fsSL 'https://registry.hub.docker.com/v2/repositories/minio/mc/tags?page_size=20&ordering=last_updated' | jq -r '.results[] | [.name,.last_updated] | @tsv' | sed -n '1,20p'
docker buildx imagetools inspect minio/mc:RELEASE.2025-08-13T08-35-41Z-cpuv1
PYTHONPATH=control-plane python3 -m platformctl.cli validate minio-init --json
PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json
PYTHONPATH=control-plane python3 -m platformctl.cli update-report minio-init --json
git diff --cached --check

Results: current tag is still newest in Docker Hub listing; manifest-list digest verified; validate minio-init OK; validate all exit=0 failures=0; update-report shows the desired digest.

Known constraints

This PR is metadata/evidence only. It does not request apply, recreate, restart, backup, or a live bucket smoke.

Explicit out-of-scope

platformctl apply
docker compose up minio-init
minio service changes
runtime bucket mutation
Forgejo/core upgrade work

Requested decision

Merge the metadata/evidence packet, not a runtime change.

Merge blockers

If reviewers require a real version bump, block: there is no newer upstream tag in the checked Docker Hub listing.
If this is interpreted as production apply approval, block: runtime execution remains a later operator-gated action.

Spec sources read

modules/minio-init/module.yaml
modules/minio-init/runbook.md
state/cycle/W8-readiness-2026-05-26.md
state/cycle/W8-module-upgrade-prep.md
decisions/0022-module-source-and-release-boundaries.md
schema/module.schema.json
schema/module.schema.md

Closes #502

Canary status: missing — full required checks must pass before merge ## Canary Context Pack ### Product story W8 needs a safe first module-upgrade pilot. For `minio-init`, the right pilot is not a fake version bump: upstream currently shows the existing `minio/mc` tag as latest, so this PR records the digest/evidence packet and keeps runtime untouched. ### What changed - Added desired `spec.artifact.digest` for `modules/minio-init/module.yaml`. - Added `state/cycle/W8-minio-init-pilot.md` with the W8.1 packet. - Linked the packet from `state/cycle/W8-module-upgrade-prep.md`. ### Why it changed #501 confirmed `minio-init` is the correct W8.1 first candidate. #502 needed a concrete packet with old/current digest, upstream tag evidence, smoke contract, rollback, and no-runtime-mutation scope. ### Files touched - `modules/minio-init/module.yaml` - `state/cycle/W8-minio-init-pilot.md` - `state/cycle/W8-module-upgrade-prep.md` ### Relevant context - #389 - #501 / PR #503 - #502 - ADR-0022 source/artifact boundaries ### Runtime evidence No runtime mutation. Repo/local read-only checks: ```bash curl -fsSL 'https://registry.hub.docker.com/v2/repositories/minio/mc/tags?page_size=20&ordering=last_updated' | jq -r '.results[] | [.name,.last_updated] | @tsv' | sed -n '1,20p' docker buildx imagetools inspect minio/mc:RELEASE.2025-08-13T08-35-41Z-cpuv1 PYTHONPATH=control-plane python3 -m platformctl.cli validate minio-init --json PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json PYTHONPATH=control-plane python3 -m platformctl.cli update-report minio-init --json git diff --cached --check ``` Results: current tag is still newest in Docker Hub listing; manifest-list digest verified; `validate minio-init` OK; `validate all` exit=0 failures=0; update-report shows the desired digest. ### Known constraints This PR is metadata/evidence only. It does not request apply, recreate, restart, backup, or a live bucket smoke. ### Explicit out-of-scope - `platformctl apply` - `docker compose up minio-init` - `minio` service changes - runtime bucket mutation - Forgejo/core upgrade work ### Requested decision Merge the metadata/evidence packet, not a runtime change. ### Merge blockers - If reviewers require a real version bump, block: there is no newer upstream tag in the checked Docker Hub listing. - If this is interpreted as production apply approval, block: runtime execution remains a later operator-gated action. ## Spec sources read - `modules/minio-init/module.yaml` - `modules/minio-init/runbook.md` - `state/cycle/W8-readiness-2026-05-26.md` - `state/cycle/W8-module-upgrade-prep.md` - `decisions/0022-module-source-and-release-boundaries.md` - `schema/module.schema.json` - `schema/module.schema.md` Closes #502

codex added 1 commit

2026-05-26 09:49:16 +02:00

docs(minio-init): prepare W8 pilot packet

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

Details

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

Details

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

Details

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

Details

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