90e8a10608
## Summary Full Suite after #2291: shards 1–3 green; shard 4 failed CLI suites with: `Failed to resolve entry for package "@fusion-plugin-examples/claude-runtime"` from `dashboard/src/runtime-provider-probes.ts` under the CLI vitest package lane. - Add `plugins/fusion-plugin-claude-runtime/src/probes-entry.ts` (probe + model discovery only) - Alias `@fusion-plugin-examples/claude-runtime` to that entry in CLI vitest config (same class as Cursor/Grok/OMP source aliases, but avoids ACP index load) ## Test plan - [x] Local: vitest-workspace-resolution, task-steer, extension-task-tools - [ ] PR gate - [ ] Post-merge Full Suite green <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved CLI resolution for Claude runtime diagnostics and provider model discovery. * Prevented unnecessary runtime dependencies from affecting CLI test execution. * **Refactor** * Added a lightweight entry point for accessing Claude binary checks and provider model discovery. <!-- end of auto-generated comment: release notes by coderabbit.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.