feat(app-server): add ThreadItem::DynamicToolCall

[owenlin0]

Previously, clients would call thread/start with dynamic_tools set, and when a model invokes a dynamic tool, it would just make the server->client item/tool/call request and wait for the client's response to complete the tool call. This works, but it doesn't have an item/started or item/completed event.

Now we are doing this:

• [new] emit item/started with DynamicToolCall populated with the call arguments
• send an item/tool/call server request
• [new] once the client responds, emit item/completed with DynamicToolCall populated with the response.

Also, with persistExtendedHistory: true, dynamic tool calls are now reconstructable in thread/read and thread/resume as ThreadItem::DynamicToolCall.

[owenlin0]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f0e1279e24

ℹ️ 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[owenlin0]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

codex/codex-rs/mcp-server/src/codex_tool_runner.rs

Line 365 in 7d8b969

| EventMsg::DynamicToolCallRequest(_)

Handle DynamicToolCallResponse in codex_tool_runner match

Add EventMsg::DynamicToolCallResponse to the large match in run_codex_tool_session. This commit introduces a new EventMsg variant, but this exhaustive match still enumerates DynamicToolCallRequest only. Building codex-mcp-server against the updated codex-protocol will fail with a non-exhaustive pattern error.

ℹ️ 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".