docs(migrations/v0.3.0): drop incorrect sdkx/tool/mcp reference [skip-tag]#86
Merged
Conversation
…-tag] The v0.3.0 migration guide listed `sdkx/tool/mcp` as a "new package landing alongside", but no such package was ever shipped — sdkx/tool/ contains only history, kanban, knowledge, and memory. MCP client / server support is queued as a follow-up workstream (separate from the v0.3.0 cutover); the doc shouldn't claim it landed. Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Summary
The v0.3.0 migration guide listed `sdkx/tool/mcp` under "New
`sdkx/tool/...` packages landing alongside", but no such package
was ever shipped. `sdkx/tool/` contains only `history`, `kanban`,
`knowledge`, and `memory`.
MCP client / server support is queued as a follow-up workstream
(separate from the v0.3.0 cutover); the doc shouldn't claim it landed.
Tagging
`[skip-tag]` (whole-workflow skip): docs-only change, no module
should pick up a new tag.
Test plan
`docs/migrations/v0.3.0.md`.
Made with Cursor