Handle custom tool use similarly to MCP tools for ipc schema purposes

[jr]

The tool name field is an enum, but custom tool names are dynamic. Follow the MCP tool pattern of just tracking all the custom tools in a single bucket.

---

Important

Custom tools are now tracked as custom_tool for usage and error recording, similar to MCP tools, with tests added for validation.

• Behavior:
  • Custom tools are now recorded as custom_tool in presentAssistantMessage.ts, similar to MCP tools.
  • Custom tool errors are recorded with the name custom_tool.
  • Partial tool blocks are not recorded.
• Tests:
  • Added presentAssistantMessage-custom-tool.spec.ts to test custom tool usage and error recording.
  • Tests cover scenarios with enabled/disabled experiments and partial blocks.
• Misc:
  • Added custom_tool to toolNames in tool.ts and TOOL_DISPLAY_NAMES in tools.ts.

^{This description was created by for a582f9b. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found. The PR correctly handles custom tools similarly to MCP tools by tracking them in a single "custom_tool" bucket for IPC schema purposes.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}