Merge roadmap status — pls4all ⤳ nirs4all-methods unification¶
This directory ships the status reports and procedures produced during the M0–M17 merge sprint. Each subdirectory carries the work-product of its phase (analysis, reconciliation, gate evidence, follow-up plan).
Phase |
Status |
Doc |
|---|---|---|
M0 |
✅ done |
|
M1 |
✅ done |
|
M2 |
✅ done |
(in commit |
M2.5 |
✅ done |
|
M3 |
✅ done |
|
M4 |
🟡 scaffold + recipe |
|
M5 |
🟡 script ready, deferred |
|
M6 |
🟡 stubs only |
(in commit |
M7+M8 |
🟡 partial |
|
M9–M11 |
🟡 scaffolds |
(in commit |
M12 |
⚪ deferred |
— |
M13 |
🟡 donor bindings lifted; secondary refresh deferred |
(in commit |
M14 |
✅ done |
(in commit |
M15 |
🟡 scaffold |
(in commit |
M16 |
📄 procedure documented |
|
M17 |
📄 procedure documented |
For the verification report (what actually works end-to-end), see VERIFICATION_REPORT.md.
For the master roadmap (rationale, target tree, parity strategy, subset
machinery), see MERGE_ROADMAP.md.
How the M-numbers map to phases¶
The numbering follows MERGE_ROADMAP.md §9 (the 17-phase work
breakdown). M2.5 is the common-core unification that the v0 draft
missed — added during Codex review.
Convention¶
Each phase committed at least one git commit on
merge/import-donor. Status docs above are post-execution reports.
Commits referenced in the table land the actual deliverables; status
docs explain the deliverable, what gate it satisfies, and what is
deferred.
Open items not blocking v1.0.0-rc1¶
(see M17/M17_RELEASE_V1.md preflight checklist)
M4 full extraction (stubs + recipe ready; execution gated by M5+M6)
M5+M6 ABI rename + header reorganisation (paired focused session)
M7+M8 unified runner + dashboard wiring
M9+M10+M11 package activation (vendored-source build via catalog/scripts/render_subset.py)
M11 CRAN cleanup pass (existing 1 WARNING + 4 NOTEs)
M13 secondary binding refresh after M5 lands
M15 cibuildwheel matrix activation (currently gated
if: false)
These ship in a v1.1.0 follow-up release pass per the roadmap budget.