Phase workflow + active phase navigation.
| Phase | Name | Status | Doc |
|---|---|---|---|
| 1 | SDL2 Core Bindings + Harvesting | DONE | retired (code + git history are canonical) |
| 2 | CI/CD & Packaging | IN PROGRESS | phase-2-adaptation-plan.md |
| X | Build-Host Modernization | DONE | ../decisions/2026-05-05-target-centric-build-host.md |
| 3 | SDL2 Complete (samples, meta-package, first prerelease) | PLANNED | plan.md roadmap |
| 4 | Binding Auto-Generation | PLANNED | phase-4-binding-autogen.md |
| 5 | SDL3 Support | PLANNED | phase-5-sdl3-support.md |
One phase is active:
Phase 2: CI/CD & Packaging. Core surface is landed (release.yml + Cake build host + tools.cs). The remaining tail lives in phase-2-adaptation-plan.md: nuget.org promotion (PD-7), release-recovery playbook (PD-8), and the four scope-assumption gaps surfaced in the 2026-05-01 tag-push rehearsals.
Closed stream: Phase X / Build-Host Modernization. Closed 2026-05-10. Current build-host architecture is captured by ../decisions/2026-05-05-target-centric-build-host.md and ../decisions/2026-05-12-build-host-data-layer.md. Durable practice lives in ../knowledge-base/testing-guidelines.md and ../knowledge-base/extraction-guidelines.md. Migration-era notes were retired after test-infrastructure consolidation.
PLANNED → IN PROGRESS → DONE
↓
(can pause → resume)
A phase is DONE when its exit criteria are met. Phases can pause and resume (Phase 2 did, after a ~10-month hiatus).
A planned phase document stays in phases/ only if it carries design-level content that plan.md cannot absorb:
- Alternative analysis tables (e.g., "CppAst vs ClangSharp vs c2ffi" in Phase 4)
- Pipeline / topology diagrams specific to the phase
- Vendor availability matrices (e.g., SDL3 per-library vcpkg availability + features + blockers in Phase 5)
- Known-blocker catalogs that
plan.mdrotation cannot hold
If the doc drifts into a roadmap-brief copy of plan.md, it retires. The test re-applies at each phase activation.
- Catching up: start with phase-2-adaptation-plan.md for the Phase 2 tail.
- Day-to-day: active phase doc +
plan.md. - Planning ahead: phase-4-binding-autogen.md, phase-5-sdl3-support.md. Don't start detailed design work until the phase activates.