fix(mcp): rename wire fields to contract names before dispatch

[bjohas]

Summary

The MCP wire schema (generated from apps/cli operation params) exposes the PARAM_FLAG_OVERRIDES renames commentId → id and parentCommentId → parentId. The contract validator on the receiving side still expects the canonical names, but the MCP dispatch path passes args through raw with no inverse rename — so superdoc_comment actions delete / get / update fail with comments.<action> commentId must be a non-empty string even when callers follow the documented schema.

The CLI handles this in extractInvokeInput() (apps/cli/src/lib/invoke-input.ts PARAM_RENAMES). This PR mirrors that translation for the MCP path: a small applyParamRenames helper in a standalone module, applied in executeOperation right before api.invoke.

Repro (before this fix)

1. Open a doc with at least one comment via superdoc_open.
2. superdoc_comment action:"list" — returns comments with valid ids.
3. superdoc_comment action:"delete" id:"<that-id>" — fails with comments.delete commentId must be a non-empty string.

action:"create" and action:"list" are unaffected (they don't take a comment id).

Affected operations

Operation	Wire field	Contract field
comments.create	parentId	parentCommentId
comments.patch (update)	id	commentId
comments.delete	id	commentId
comments.get	id	commentId
getNodeById	id	nodeId

Changes

• New apps/mcp/src/tools/param-renames.ts — rename map + applyParamRenames helper. Mirrors the CLI's PARAM_RENAMES; comment in the file points to it.
• apps/mcp/src/tools/intent.ts — executeOperation now wraps input with applyParamRenames(opId, input) before api.invoke.
• New apps/mcp/src/__tests__/intent-param-renames.test.ts — 7 unit tests.

Test plan

• bun test apps/mcp/src/__tests__/intent-param-renames.test.ts — 7 pass / 0 fail.
• bun build apps/mcp/src/tools/param-renames.ts --target=node — transpiles clean.
• CI to type-check the full MCP app.
• Manual end-to-end: superdoc_comment action:"delete" against a doc that round-trips through list.

Notes

• The duplication between this module and the CLI's PARAM_RENAMES is intentional for now — the rename table is small (5 entries across 4 operations) and stable. A follow-up could promote it to a shared location, ideally driven by codegen so both the wire schema and the inverse map come from a single source.
• Alternative considered: change the wire schema to use the canonical contract names (commentId, parentCommentId, nodeId) directly. Cleaner but a breaking change for any caller relying on the current short names.

[caio-pizzol]

@bjohas thanks for the PR :) good fix and the tests cover the renames cleanly.

two small things inline.

[caio-pizzol]

count's off (map has 5 entries) and the em-dash trips our style rule.

Suggested change

	* mirror — kept in lockstep by hand. Three operations are affected today
	* mirror, kept in lockstep by hand. Five operations are affected today
	* (comments.delete, comments.get, comments.patch, comments.create's
	* parentId, and getNodeById's id), so duplication is small.

[caio-pizzol]

input gets renamed (id → commentId) but the response goes back as-is, so MCP clients see commentId in the body even though their input uses id. probably fine since the agent reads it as text, but is the asymmetry intentional? worth a line in the PR body, or a follow-up if it should be inverted on the way out too.