84830595f2
Remove blocking execSync validation paths from CLI process managers while preserving async probe coverage. - Drop synchronous Claude and Droid CLI presence/auth validators from process managers. - Keep async spawn-based validation as the sole probing path for session startup. - Replace sync validator tests with execSync guard coverage for both CLI integrations. Files changed: .../droid-cli/src/__tests__/execsync-guard.test.ts | 17 ++++++++ .../src/__tests__/process-manager.test.ts | 46 +--------------------- .../src/__tests__/execsync-guard.test.ts | 14 +++++++ .../src/__tests__/process-manager.test.ts | 46 +--------------------- .../pi-claude-cli/src/__tests__/provider.test.ts | 1 - packages/pi-claude-cli/src/process-manager.ts | 44 +++------------------ .../src/process-manager.ts | 43 +++----------------- 7 files changed, 45 insertions(+), 166 deletions(-) Fusion-Task-Id: FN-6485 Fusion-Task-Lineage: e3f0f656-3445-4672-b597-a811924137e9
@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.