v0.4.2: Framework update: request IDs on errors, argument repair

Framework update: request IDs on errors, argument repair

• Framework @cyanheads/mcp-ts-core ^0.13.6 → ^0.13.14 — tool error results carry data.requestId and end with request <id> (0.13.10); stack traces, request context, and rootCause no longer reach client error data (0.13.7, 0.13.8, 0.13.13); numeric or boolean strings and null optional values in arguments are repaired before validation (0.13.9, 0.13.14)
• The -32602 argument rejection is bounded in size (0.13.14); ctx.log lines reach the client only at or above MCP_LOG_LEVEL, with sensitive fields masked (0.13.11)
• Tool handlers no longer forward ctx.recoveryFor(...); the same recovery hints still reach clients through the framework's declared-recovery fill (0.13.10)
• server.json npm entries launch through npx, and the HTTP entry sets MCP_TRANSPORT_TYPE to http (0.13.11)
• Docker image installs production dependencies in a deps stage on the build platform and drops unused musl native bindings (0.13.10, 0.13.11)
• .env.example and the README document the new logging, payload-logging, OTLP, and resumability variables
• Bundle and ignore files: .mcpbignore additions, .env* ignore rules, !dist/*.mcpb in files, manifest.json author; CodeQL runs one job per language; README badges; framework skills and scripts synced to 0.13.14
• Dependencies pino-pretty ^13.1.3 → ^13.2.0; dev: @biomejs/biome ^2.5.14 → ^2.5.15, @socketsecurity/bun-security-scanner ^1.1.2 → ^1.1.3, @types/node ^26.6.2 → ^26.6.4, ignore ^7.0.9 → ^7.0.12, tsc-alias ^1.9.5 → ^1.9.7, vitest ^5.0.1 → ^5.0.3; Bun 1.4.0 → 1.4.2

CHANGELOG v0.4.2 · release PR #75