Stage the bundled computer-use discovery skill exclusively for supported macOS runtimes. - Gate Claude and Grok session skill resolution and staging by platform. - Install the Hermes discovery skill on Darwin while preserving user overrides and non-Darwin suppression. - Document runtime discovery behavior, add coverage, and add a minor release changeset. Files changed: .../darwin-only-computer-use-skill-staging.md | 7 + docs/computer-use.md | 10 +- .../custom-provider-routes-hermes-additive.test.ts | 2 +- .../src/__tests__/skill-loader.test.ts | 197 +++++++++++++++++++++ .../src/skill-loader.ts | 145 ++++++++++----- .../src/__tests__/skill-loader.test.ts | 51 +++++- .../fusion-plugin-grok-runtime/src/skill-loader.ts | 145 ++++++++++----- .../src/__tests__/fusion-skill-install.test.ts | 62 ++++++- .../src/__tests__/index.test.ts | 37 +++- .../src/fusion-skill-install.ts | 151 ++++++++-------- plugins/fusion-plugin-hermes-runtime/src/index.ts | 21 ++- 11 files changed, 649 insertions(+), 179 deletions(-) Fusion-Task-Id: FN-8986 Fusion-Task-Lineage: 373d558a-1d0a-4737-99be-f53189a9aeaf Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
Claude Runtime Plugin
fusion-plugin-claude-runtime exposes Claude Code as Fusion runtime claude and CLI provider claude-cli. It communicates through Agent Client Protocol (ACP), preserving streaming updates, tool calls, and multi-turn sessions.
The plugin uses the pinned claude-code-cli-acp bridge (0.1.1). CLI packaging stages its reviewed launcher beside the bundled plugin, while the published @runfusion/fusion dependency installs the matching optional native bridge for the operator's OS and CPU. The runtime never falls back to a same-named executable on PATH.
This is additive to Fusion's experimental pi-claude-cli Route A. Route A remains available; selecting the claude runtime explicitly selects this first-class ACP transport.
Fusion custom-tools bridge
The fusion-custom-tools MCP server launches mcp-schema-server.cjs beside the loaded bridge module. It is kept beside src/ for source loading and copied beside dist/ by pnpm build; do not remove that postbuild copy or dist-loaded sessions will fail initialize with handshake failed: connection closed: initialize response.
When requested Fusion tools cannot start their bridge, the adapter emits FUSION_TOOL_BRIDGE_FAILED: mcp-schema-server-missing or FUSION_TOOL_BRIDGE_FAILED: bridge-start-failed, omits the unusable MCP entry, and the engine stores only the fixed outcome and tool count in session:runtime-resolved run audit metadata.