docs: move v1.1.0 migration guidance to dedicated file

[kargnas]

Summary

• move the v1.1.0 ToolInterface migration instructions into docs/migrations/v1.1.0-tool-interface-migration.md
• replace the README section with a concise summary that links to the dedicated migration guide

Testing

• not run

---

https://chatgpt.com/codex/tasks/task_e_68eb5ecdb9648321b548dfd160325d5c

[claude]

Code Review: Migration Documentation Refactor

Summary

This PR successfully extracts the verbose v1.1.0 migration instructions from README.md into a dedicated migration guide. This is a positive change that improves documentation maintainability and readability.

Strengths

1. Documentation Organization - Excellent separation of concerns with clear directory structure (docs/migrations/)
2. Content Quality - Well-structured guide with clear sections and accurate code examples
3. Consistency - Follows CLAUDE.md guidance about documentation updates

Suggestions for Improvement

1. Line 30 mentions messageType() defaults to ProcessMessageType::SSE. Consider clarifying if this is correct given the package now recommends Streamable HTTP as primary transport.

2. Consider adding notes about when to use ProcessMessageType::HTTP vs SSE, and the messageType() deprecation in favor of isStreaming() (v1.3.0+)

3. Verify the relative link works: docs/migrations/v1.1.0-tool-interface-migration.md - Consider using absolute GitHub URL for reliability

4. README mentions "May 2025" but current date is October 2025. Verify this date reference is correct.

Technical Review

• Code Quality: N/A (documentation only)
• Security: No concerns
• Performance: No impact
• Testing: Consider verifying documentation links
• Breaking Changes: None introduced

Recommendation

APPROVE with minor suggestions. This is a clean documentation refactor that improves project structure. The 146 line deletion from README.md while adding 115 lines in a dedicated guide is excellent documentation debt reduction.

Checklist Before Merge

• Verify relative link works on GitHub
• Consider clarifying default ProcessMessageType recommendation
• Optional: Update or remove the May 2025 date reference