Defer Droid CLI validation and discovery so startup no longer spawns or hangs on droid. - Register the Droid provider without boot-time validation or model discovery side effects. - Trigger CLI validation only when a Droid stream starts and expose explicit model discovery. - Add regression coverage for non-interactive droid process spawning and startup probe behavior. - Add a patch changeset for the published Fusion CLI package. Files changed: .changeset/fn-6911-droid-cli-no-boot-spawn.md | 5 ++ .../commands/__tests__/droid-cli-extension.test.ts | 15 +++- packages/droid-cli/index.ts | 33 ++++---- packages/droid-cli/src/__tests__/index.test.ts | 90 +++++++++------------- .../src/__tests__/discover-models.test.ts | 7 +- .../src/__tests__/probe.test.ts | 8 ++ .../src/__tests__/process-manager.test.ts | 74 ++++++++++++++++++ .../src/__tests__/startup-probes.test.ts | 5 +- 8 files changed, 160 insertions(+), 77 deletions(-) Fusion-Task-Id: FN-6911 Fusion-Task-Lineage: ef4bc3df-bfe8-416a-b701-64f752faea30
@fusion/droid-cli
Compatibility-shim package for Fusion's Droid integration extension entrypoint.
Runtime/provider internals live in:
@fusion-plugin-examples/droid-runtime(plugins/fusion-plugin-droid-runtime)
This package preserves the historical pi extension entrypoint and wires runtime helpers into the real extension surface (registerProvider, session_start tool activation, model discovery, and MCP handoff) so existing imports continue to work.
Testing boundary
packages/droid-cli/src/__tests__/index.test.tsowns integration coverage for this shim entrypoint (index.ts) and verifies provider registration and wiring behavior.- Runtime internals (
streamViaCli, CLI process handling, MCP schema generation, parsing, etc.) remain covered in the plugin package tests underplugins/fusion-plugin-droid-runtime.