Two shipped features — Rename change-annotations (#70/#133) and Inlay Hints/F23 (#43) — were never added to the roadmap/feature index in LSP-IDE-Support-Overview.md, and that doc's cross-client capability story (the §7-style matrices, e.g. which of VS / VS Code / Rider get which behavior) hasn't been updated to include either. See docs/AsBuilt-Reconciliation-Reminder.md §3.
Work
Depends on the reconciliation content landing in Feature-Designs.md first (#134, #135) for consistent framing, but can be done independently if roadmap-only changes are wanted sooner.
Two shipped features — Rename change-annotations (#70/#133) and Inlay Hints/F23 (#43) — were never added to the roadmap/feature index in
LSP-IDE-Support-Overview.md, and that doc's cross-client capability story (the §7-style matrices, e.g. which of VS / VS Code / Rider get which behavior) hasn't been updated to include either. See docs/AsBuilt-Reconciliation-Reminder.md §3.Work
LSP-IDE-Support-Overview.md: add both features to the feature index / phase roadmap (assign F-numbers if the F-series convention continues — Inlay Hints is already informally "F23" in commit messages).LSP-IDE-Support-Overview.md: update the cross-client capability story in the release-strategy section — Rename annotations: VS Code/Rider get the annotated preview, VS stays on theChangesfallback (nochangeAnnotationSupport); Inlay Hints: per the plan's Phase-0 capability verification.Depends on the reconciliation content landing in Feature-Designs.md first (#134, #135) for consistent framing, but can be done independently if roadmap-only changes are wanted sooner.