fix: resolve claude-runtime probe source for CLI full-suite (#2292)

## 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 -->

plugins/fusion-plugin-claude-runtime/src/probes-entry.ts

@@ -0,0 +1,10 @@
+/*
+FNXC:CliTests 2026-07-18-09:15:
+Thin entry for dashboard runtime-provider-probes and CLI vitest source aliases.
+Importing the full plugin index pulls ACP/runtime-adapter (and @agentclientprotocol/sdk)
+which is not required for binary probe / model discovery and fails full-suite CLI
+resolution when dist/ is absent or ACP deps are not on the CLI resolver path.
+*/
+export { probeClaudeBinary } from "./probe.js";
+export type { ClaudeBinaryStatus } from "./types.js";
+export { discoverClaudeProviderModels } from "./provider.js";