docs: add post-release stub and 0.6.4 entry

CHANGELOG.md

@@ -1,6 +1,14 @@
 # Changelog
 
 ## [Unreleased]
+- Nothing yet.
+
+## [0.6.4] - 2025-11-22
+### Runtime & CLI
+- Updated to `@modelcontextprotocol/sdk` 1.22.0; inline stdio test server now uses Zod schemas to remain compatible with the SDK’s JSON Schema conversion path.
+
+### Runtime
+- `listTools` now follows SDK pagination, looping through `nextCursor` so long catalogs return complete tool lists.
 
 ## [0.6.3] - 2025-11-22
 ### Runtime & CLI

docs/RELEASE.md

@@ -44,6 +44,7 @@
     - `mcporter-<version>.tgz.sha1` and `mcporter-<version>.tgz.sha256`
     Double-check the uploaded checksums match your local files.
 16. Tag the release (git tag v<version> && git push --tags).
+17. Post-tag housekeeping: add a fresh "Unreleased" stub to CHANGELOG.md (set to "- Nothing yet.") and start a new version section for the just-released patch if it isn’t already recorded.
 
 After the release is live, always update the Homebrew tap and re-verify both installers. That flow should be: