fix(codex): preserve namespace MCP tools forwarded to Codex Responses…

[vanminhph]

… API

normalizeCodexTools() was dropping all tools with type !== "function", which stripped namespace-typed MCP tool groups (e.g. mcp__atlassian__) before the request reached the Codex API. Codex then saw an empty tools array and refused to call any MCP tools.

Fix: detect type === "namespace" entries, preserve them as-is (Codex API supports them natively), and register sub-tool names in validToolNames so tool_choice validation still works correctly. Also whitelist "namespace" in the openai-responses translator to prevent a throw on the same type when the translation path is invoked.

Summary

• Describe the user-facing or operational change.

Related Issues

• Closes #
• Related to #

Validation

• npm run lint
• npm run test:unit
• npm run test:coverage
• Coverage is still >= 60% for statements, lines, functions, and branches
• SonarQube PR analysis is green or any remaining issues are explicitly documented below

Tests Added Or Updated

• List every changed or added automated test file.
• If no production code changed, state that here.

Coverage Notes

• If this PR changes src/, open-sse/, electron/, or bin/, explain which tests cover the change.
• If coverage moved down in any touched file, explain why and what follow-up task will recover it.

Reviewer Notes

• Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.

[gemini-code-assist]

Code Review

This pull request introduces support for 'namespace' tools, which represent MCP tool groups used by the Codex and OpenAI Responses API. The changes include updating the tool normalization logic to register sub-tool names for validation and adjusting the request translator to permit the 'namespace' tool type. I have no feedback to provide as there are no review comments.