docs(w8): prepare staged module upgrade plan #466

Merged

pdurlej merged 1 commit from codex/w8-upgrade-prep into main

2026-05-25 01:01:17 +02:00

codex commented

2026-05-25 00:49:59 +02:00

Collaborator

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

Canary Context Pack

Product story

The platform is ready to think about module upgrades, but not by starting with Forgejo. This PR turns #389 into an actionable W8 staging plan: readiness first, low-blast pilot second, Forgejo later.

What changed

Added state/cycle/W8-module-upgrade-prep.md with W8.0/W8.1/W8.2/W8.3/W8.final sequencing.
Added state/roadmap/forgejo-upgrade-plan.md with Forgejo-specific preflight, backup, smoke, and rollback gates.
Updated issue #389 as the M09 coordination lane.

Why it changed

The operator wants to reach W8, but broad upgrades still need metadata and restore evidence. This makes the next step concrete without mutating production.

Files touched

state/cycle/W8-module-upgrade-prep.md
state/roadmap/forgejo-upgrade-plan.md

Relevant context

ADR-0022 requires source/artifact metadata and risk-based update policy.
W5 update report currently sees 88 modules, 6 with source/artifact metadata, 0 auto-pr candidates.
#389 is the M09 coordination issue and was updated to point at this plan.

Runtime evidence

None. Read-only platformctl update-report --json was run locally; no production or Forgejo runtime mutation.

Known constraints

This PR does not start upgrades. It explicitly defers Forgejo upgrade until after a W8 low-blast pilot and DR/restore stance.

Explicit out-of-scope

Changing any module image.
Running platformctl apply.
Creating backups or restarting services.
Upgrading Forgejo.

Requested decision

Merge to make W8 planning durable, then use #389 as the coordination lane for child issues.

Merge blockers

Plan accidentally allows broad/core upgrades before pilot evidence.
Forgejo upgrade becomes first W8 candidate.
Restore/rollback gates are omitted.

Spec sources read

decisions/0022-module-source-and-release-boundaries.md — update workflow and risk policy.
state/roadmap/current-platform-roadmap.md — current W0-W9 plan.
state/cycle/W5-modularity-foundation-output.md — metadata/update-report status.
Issue #389 — current M09 meta issue.

Tests

git diff --check
PYTHONPATH=control-plane python3 -m platformctl.cli update-report --json → ok=true, total modules 88, source/artifact metadata 6/6

Canary status: missing — rely on required Forgejo checks before merge ## Canary Context Pack ### Product story The platform is ready to think about module upgrades, but not by starting with Forgejo. This PR turns #389 into an actionable W8 staging plan: readiness first, low-blast pilot second, Forgejo later. ### What changed - Added `state/cycle/W8-module-upgrade-prep.md` with W8.0/W8.1/W8.2/W8.3/W8.final sequencing. - Added `state/roadmap/forgejo-upgrade-plan.md` with Forgejo-specific preflight, backup, smoke, and rollback gates. - Updated issue #389 as the M09 coordination lane. ### Why it changed The operator wants to reach W8, but broad upgrades still need metadata and restore evidence. This makes the next step concrete without mutating production. ### Files touched - `state/cycle/W8-module-upgrade-prep.md` - `state/roadmap/forgejo-upgrade-plan.md` ### Relevant context - ADR-0022 requires source/artifact metadata and risk-based update policy. - W5 update report currently sees 88 modules, 6 with source/artifact metadata, 0 auto-pr candidates. - #389 is the M09 coordination issue and was updated to point at this plan. ### Runtime evidence None. Read-only `platformctl update-report --json` was run locally; no production or Forgejo runtime mutation. ### Known constraints This PR does not start upgrades. It explicitly defers Forgejo upgrade until after a W8 low-blast pilot and DR/restore stance. ### Explicit out-of-scope - Changing any module image. - Running `platformctl apply`. - Creating backups or restarting services. - Upgrading Forgejo. ### Requested decision Merge to make W8 planning durable, then use #389 as the coordination lane for child issues. ### Merge blockers - Plan accidentally allows broad/core upgrades before pilot evidence. - Forgejo upgrade becomes first W8 candidate. - Restore/rollback gates are omitted. ## Spec sources read - `decisions/0022-module-source-and-release-boundaries.md` — update workflow and risk policy. - `state/roadmap/current-platform-roadmap.md` — current W0-W9 plan. - `state/cycle/W5-modularity-foundation-output.md` — metadata/update-report status. - Issue #389 — current M09 meta issue. ## Tests - `git diff --check` - `PYTHONPATH=control-plane python3 -m platformctl.cli update-report --json` → `ok=true`, total modules `88`, source/artifact metadata `6/6`

codex added 1 commit

2026-05-25 00:49:59 +02:00

docs(w8): prepare staged module upgrade plan

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

canary-required / canary (pull_request) Has been skipped

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 21s