Three root causes behind CI run 28695362549 failures: 1. droid-cli: 8 tests fail with 'Failed to resolve entry for @fusion-plugin-examples/droid-runtime'. The droid-cli vitest config had no source alias for the droid-runtime plugin, so Vite tried to resolve non-existent dist/ exports. 2. CLI: multiple tests fail with 'Failed to resolve entry for @fusion-plugin-examples/roadmap'. The CLI vitest config was missing source aliases for the roadmap plugin (., /server, /roadmap-suggestions). 3. CLI: 73 bin.test.ts tests fail with 'No runTaskImportFromGitLab export is defined on the ../commands/task.js mock'. The GitLab import command was added to bin.ts and task.ts but the bin.test.ts mock was not updated to include the new export.
@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.