state(roadmap): consolidate current platform milestones #386

Merged

pdurlej merged 1 commit from codex/roadmap/current-platform-milestones into main

2026-05-19 08:52:21 +02:00

codex commented

2026-05-19 08:45:06 +02:00

Collaborator

Canary status: missing - roadmap/state-only PR; rely on required Forgejo checks before merge

Canary Context Pack

Product story

The operator needs one visible, current platform roadmap instead of several overlapping historical plans (Phase 01-06, F1/F2/F3, cutoff soak, Honcho closeout, ADR-0020/21/22). Forgejo milestones should become the communication layer for stages and tasks.

What changed

Added state/roadmap/current-platform-roadmap.md as the active durable roadmap.
Updated state/STATUS_NOW.md to point at the roadmap and milestone train.
Created Forgejo milestones 01 through 09 and assigned existing open issues into the new buckets.

Why it changed

After ADR-0022 merged, the old plans no longer explain the true next sequence. This PR consolidates them and makes milestones the operator-facing stage board.

Files touched

state/roadmap/current-platform-roadmap.md
state/STATUS_NOW.md

Relevant context

ADR-0020: post-soak cleanup and modularization boundary
ADR-0021: DDD bounded contexts
ADR-0022: module source/release boundaries
Issue #384: ProgramBench-style agent-readiness audit
Current RS2000 cutoff/F3 evidence in state/STATUS_NOW.md

Runtime evidence

No production mutation. Forgejo planning mutation only: milestones created and existing issues assigned.

Known constraints

Milestones are planning state. They do not authorize production mutation, destructive cleanup, broad upgrades, repo splits, or embedding migration.

Explicit out-of-scope

Creating all follow-up meta issues if Forgejo API is unavailable
Running cleanup or DR commands
Closing stale issues
Changing module schema
Starting module upgrades

Requested decision

Approve the roadmap as the new planning source of truth and use Forgejo milestones for the next platform phase.

Merge blockers

Block if the milestone order misrepresents operator priorities, if old plans should remain active, or if any milestone groups unsafe work before DR/metadata gates.

Spec sources read

state/STATUS_NOW.md - current operator state
state/cutover/rs2000-control-plane-cutoff.md - cutoff contract
state/cutover/rs2000-post-soak-legacy-cleanup.md - post-soak cleanup plan
state/cutover/honcho-closeout-plan.md - Honcho closeout state
decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md - cleanup/modularization decision
decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md - internal bounded-context plan
decisions/0022-module-source-and-release-boundaries.md - source/artifact boundary plan
Forgejo open issues and milestones via API

Refs #384.

Canary status: missing - roadmap/state-only PR; rely on required Forgejo checks before merge ## Canary Context Pack ### Product story The operator needs one visible, current platform roadmap instead of several overlapping historical plans (Phase 01-06, F1/F2/F3, cutoff soak, Honcho closeout, ADR-0020/21/22). Forgejo milestones should become the communication layer for stages and tasks. ### What changed - Added `state/roadmap/current-platform-roadmap.md` as the active durable roadmap. - Updated `state/STATUS_NOW.md` to point at the roadmap and milestone train. - Created Forgejo milestones `01` through `09` and assigned existing open issues into the new buckets. ### Why it changed After ADR-0022 merged, the old plans no longer explain the true next sequence. This PR consolidates them and makes milestones the operator-facing stage board. ### Files touched - `state/roadmap/current-platform-roadmap.md` - `state/STATUS_NOW.md` ### Relevant context - ADR-0020: post-soak cleanup and modularization boundary - ADR-0021: DDD bounded contexts - ADR-0022: module source/release boundaries - Issue #384: ProgramBench-style agent-readiness audit - Current RS2000 cutoff/F3 evidence in `state/STATUS_NOW.md` ### Runtime evidence No production mutation. Forgejo planning mutation only: milestones created and existing issues assigned. ### Known constraints Milestones are planning state. They do not authorize production mutation, destructive cleanup, broad upgrades, repo splits, or embedding migration. ### Explicit out-of-scope - Creating all follow-up meta issues if Forgejo API is unavailable - Running cleanup or DR commands - Closing stale issues - Changing module schema - Starting module upgrades ### Requested decision Approve the roadmap as the new planning source of truth and use Forgejo milestones for the next platform phase. ### Merge blockers Block if the milestone order misrepresents operator priorities, if old plans should remain active, or if any milestone groups unsafe work before DR/metadata gates. ## Spec sources read - `state/STATUS_NOW.md` - current operator state - `state/cutover/rs2000-control-plane-cutoff.md` - cutoff contract - `state/cutover/rs2000-post-soak-legacy-cleanup.md` - post-soak cleanup plan - `state/cutover/honcho-closeout-plan.md` - Honcho closeout state - `decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md` - cleanup/modularization decision - `decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md` - internal bounded-context plan - `decisions/0022-module-source-and-release-boundaries.md` - source/artifact boundary plan - Forgejo open issues and milestones via API Refs #384.

codex added 1 commit

2026-05-19 08:45:07 +02:00

state(roadmap): consolidate platform milestones

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 19s