Language migration friction — findings (2026)
Language migration friction — findings (2026)
Section titled “Language migration friction — findings (2026)”Probe charter
Section titled “Probe charter”Enumerate high-friction migrations (syntax retired in prose but still parse-correct, or documented in multiple places with conflicting status).
Evidence (2026-05-11)
Section titled “Evidence (2026-05-11)”- Retired surfaces table in root
AGENTS.mdvs ADRs such as ADR 028 — durability keywords remain parse-visible per durability-runtime-audit-2026.md. - React interop migrations centralized partially in phase5-react-interop-spec-2026.md.
Friction patterns
Section titled “Friction patterns”- Dual truth: Roadmap says “supported grammar,” runtime audit says “no scheduler” — contributors must read both.
- Scattered codemod names: Phase 3 (
id-strings) vs Phase 5 (drop-island) — hub doc reduces search cost (vox-language-migrations-ssot-2026.md). - IDE lag: VS Code extension deprecation (ADR 031) vs LSP-first workflow — migration messaging must stay synchronized.
Next steps
Section titled “Next steps”- Add CLI
--helpcross-links when codemods ship (reference/cli.md). - For each ADR that changes grammar, add a row to the migrations hub and a release note stub under
docs/news/when cutting versions.