[v0.2] Replace internal phase labels with versioned capability terminology - #145
Merged
Conversation
Replace milestone phase labels (M4-M14) in crate code and doc comments with the concrete issue references or capability names they pointed at, per #140. No code symbols, APIs, or identifiers change; only prose and comments.
Replace phase labels (M5, M11, M12, M13, M14) in living docs and README with capability names, issue references, and the normative #134 roadmap, per #140. Verbatim commit-subject quotes in SPEC-99 keep their historical record; excluded lanes (docs/adr, architecture, licensing, docs README) are untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #140 (implementation lane; QA/merge decisions remain).
Sweep scope
Removed internal phase-number planning labels (M4–M14, "milestone M…") from active/living material where they served as the roadmap model. Historical record (git history, closed PR/issue threads, commit-subject quotes, archival scripts/fixtures) is untouched.
What was replaced, where
d30736c): code/doc comments in allcrates/*— phase labels replaced with the concrete issue references (e.g.#97,#98,#117,#128–#131) or capability names they pointed at ("safe-edit transaction contract", "wright-benchharness", "OPY support matrix", "declared P0 surface"). No code symbols, APIs, identifiers, or test behavior changed; only prose/comments.f9432e7):docs/ostw/compatibility-baseline.md— "M13 Investigation" reframed as the OSTW reference/corpus/support investigation ([M13 investigation] Establish OSTW reference, corpus, licensing, and semantic support baseline #113); section headers and "post-M13 reassessment" → roadmap reassessment; decomposition A–E phase identifiers kept (defined in the same doc).docs/embedding.md,docs/language-services.md— M14 → issue refs ([M14 foundation] Make source-edit transactions project- and frontend-aware #128–[M14 language services] Converge LSP rename on the shared semantic refactoring contract #131).docs/compatibility.md,docs/compatibility/upstream-references.md— "M13 investigation" → "OSTW reference investigation ([M13 investigation] Establish OSTW reference, corpus, licensing, and semantic support baseline #113)"; "M11 evidence set" → "OverPy compatibility evidence set".docs/specs/SPEC-99-stability-rules.md— doc-owned M12 labels removed; verbatim commit-subject quotes ((M12)atc5b46f3/a54433b) kept as historical record.README.md— M13 status/foundation labels → capability language ("native OSTW frontend", "native frontend & HIR lowering baseline").CONTRIBUTING.md— one convention bullet: new issues/PRs/living docs use capability/issue/version terminology, Roadmap to v1.0: stable Workshop tooling platform #134 is the normative roadmap.crates/wright-driver|language|lsp|ostw|consumer,docs/embedding.md,docs/language-services.md,tests/; all occurrences were replaced above as normal follow-up. Historical PR/commit record untouched.Exclusions (owned by #136 / PR #144 — NOT touched, left as follow-up)
docs/adr/*,docs/architecture.md(contains "M13" references),docs/licensing.md,docs/README.md(M10/M11/M13 references) — per lane boundary.crates/wright-workshop/src/catalog/data/catalog.json("M5 support matrix" provenance strings in catalog data),scripts/m11-inventory.py/scripts/acquire-corpus.py/compatibility/README.md/adapter/test/adapter.test.js(historical acquisition-tooling and fixture provenance).Acceptance criteria mapping
rg '\bM[0-9]+\b'over crates/ and non-excluded docs/ (only historical commit quotes and out-of-lane files remain). ✓AGENTS.md; convention bullet added inCONTRIBUTING.md. ✓CONTRIBUTING.md. ✓Validation
cargo fmt --check— passcargo clippy --workspace --all-targets -- -D warnings— passcargo test --workspace --all-targets— pass (55 test binaries, 0 failures)git diff --check— pass