The new `@modelcontextprotocol/codemod` package is added to the publish workflow but ships with no `README.md`, while every other published package in the repo (client, server, middleware/*) has one. The PR description's CLI usage, programmatic API, and transform table won't be visible on the npm package page — worth adding a `packages/codemod/README.md` before this lands (npm auto-includes README regardless of the `files` array, so no `package.json` change is needed).

When the second handler param is destructured directly in the signature (e.g., `async (request, { signal, authInfo }) => {...}`), `extraParam.getName()` returns the binding-pattern text `'{ signal, authInfo }'`, which fails the `=== 'extra'` check at line 47 and silently `continue`s with no diagnostic. This is internally inconsistent with the body-level destructuring case (lines 74-88), which *does* push a 'Manual refactoring required' warning for the same situation. Consider adding `if (Node.is

`rewriteExportDeclarations` only calls `exp.setModuleSpecifier(targetPackage)` and never inspects `mapping.renamedSymbols`, so a barrel re-export like `export { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js'` becomes `export { StreamableHTTPServerTransport } from '@modelcontextprotocol/node'` — which doesn't export that name (TS2305), with no diagnostic. Iterate `exp.getNamedExports()` and emit `{ NodeStreamableHTTPServerTransport as StreamableHTTPServe