[diegosouzapw]

Summary

• OpenCode Zen/Go chat-completions upstreams reject tool names longer than 64 characters (name must be at most 64 characters, got 68), which Claude Code MCP tool names routinely exceed. The registry-scoped tool-name alias only ran in DefaultExecutor; OpencodeExecutor extends BaseExecutor, so long names reached opencode.ai unchanged and the request failed with 400.
• Extract that alias step into a reusable helper and apply it to OpenCode (opencode, opencode-zen, opencode-go now declare toolNameMaxLength: 64). Aliases are restored in responses through the existing _toolNameMap path.

Attribution

Thanks to @MakdumIbrohim for the original implementation.

Changes

• open-sse/executors/toolNameLengthAlias.ts (new): applyToolNameLengthAliases(body, maxLength, normalize?) (pluggable normalizer, defaulting to the existing normalizeOpenAIToolNames; a missing or non-positive-integer limit is a no-op), applyRegistryToolNameLengthAliases(provider, body), and mergeToolNameAliases (copies any existing _toolNameMap, merges the new aliases, and keeps the map non-enumerable). It accepts other normalizers, so a surface with a different tool shape (for example a Responses-API 128-char cap) can reuse it.
• open-sse/executors/default.ts: the inline alias block is replaced by applyRegistryToolNameLengthAliases(this.provider, withDefaults). Outputs are unchanged; the NVIDIA suite passes as before.
• open-sse/executors/opencode.ts: transformRequest applies the helper as its last step, and only on the chat-completions surface. Claude and Responses surfaces are left alone.
• open-sse/config/providers/registry/opencode/{index,zen/index,go/index}.ts: toolNameMaxLength: 64.
• No new hashing code: aliases reuse normalizeOpenAIToolNames (prefix + _ + sha256-12, safe against collisions, consistent across tools, tool_choice, history tool_calls and role:"tool" names).

Test plan

• New tests/unit/opencode-tool-name-length.test.ts (TDD). Against the pre-port opencode executor and registry, 4 tests failed (registry flag, distinct aliases for two 68-char names sharing a 64-char prefix, consistent history/tool_choice aliasing, response restore). After the port:
  node --import tsx/esm --test tests/unit/opencode-tool-name-length.test.ts → ℹ tests 10 ℹ pass 10 ℹ fail 0
• Refactor neutrality: node --import tsx/esm --test tests/unit/nvidia-tool-compatibility-2840.test.ts → ℹ tests 7 ℹ pass 7 ℹ fail 0
• Every existing test referencing the changed files or symbols (143 files: executors/opencode.ts, executors/default.ts, registry/opencode, toolNameMaxLength, normalizeOpenAIToolNames): ℹ tests 1375 ℹ pass 1374 ℹ fail 1. The one failure was a concurrency-timing assertion in opencode-transient-rotation.test.ts ("both requests must be in flight simultaneously") that showed up under box load. Rerun in isolation: ℹ tests 11 ℹ pass 11 ℹ fail 0.
• npm run typecheck:core → exit 0
• npx eslint --suppressions-location config/quality/eslint-suppressions.json <changed files> → exit 0; npx prettier --check <changed files> → clean
• node scripts/check/check-pr-test-policy.mjs → Result: PASS; GITHUB_BASE_REF=release/v3.8.52 npm run check:test-masking → OK — 0 modificado(s) … sem enfraquecimento

⚠️ base-red inherited: #15306 — unit/vitest/integration/package-artifact gates on release/v3.8.52

[github-actions]

CI Coverage Report

• Coverage job: skipped
• PR test policy: success

Coverage artifact was not available for this run.