fix: use macros to ensure request/response symmetry

[bolinfest]

Manually curating protocol-ts/src/lib.rs was error-prone, as expected. I finally asked Codex to write some Rust macros so we can ensure that:

• For every variant of ClientRequest and ServerRequest, there is an associated params and response type.
• All response types are included automatically in the output of codex generate-ts.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

[chatgpt-codex-connector]

Generate server method strings in PascalCase

The new server_request_definitions! macro derives the method constants with stringify!([<$variant:camel>]), which produces values like "ApplyPatchApproval". These strings are used in OutgoingMessageSender::send_request to populate the JSON‑RPC method field, but the ServerRequest enum is declared with #[serde(rename_all = "camelCase")], meaning clients expect method names such as "applyPatchApproval". Sending PascalCase names will cause clients and generated TS bindings to fail to match the request variants, so approval prompts will no longer be recognized.

Useful? React with 👍 / 👎.