library install --format fusion: mirror the web Export's Fusion lane

Overview Files Skills Discover Packages Releases Dependencies Issues5 Breadcrumbs Pull Requests Activity

Open feature request

Colby Knox · 1mo ago

From the wiki thread's handoff after Cloud Libraries shipped. library install is KiCad-only today; the web Export's Fusion flow could be mirrored: stage the .lbr, fusion_open_lbr, the 3D bind with the runId poll, and the addin_restart_required ask (fusion-web-control documents the verb contracts). Same acceptance discipline as #39: verify against a live connected desktop running Fusion, both the clean path and addin_restart_required. Not urgent.

1 Reply

Colby Knox · 1mo ago

Re-scoped after checking the actual verb surfaces (Colby's routing question was right). The KiCad lane was clean ONLY because kicad-bridge owns the whole recipe as ONE composite verb (kicad_install_library_bundle: unpack, install, both lib tables, capture proof, restart contract) and the CLI is just stage + one call. Fusion has NO composite: the web Export hand-orchestrates a multi-verb lane (fusion_create_library / fusion_plan_library_import / fusion_build_library_3d / fusion_prove_result, runId polling, addin_restart_required) in webcontrol.js. Mirroring that orchestration here would duplicate the bridge's recipe knowledge in a second place that rots when the bridge evolves.

So this issue is BLOCKED on a fusion-bridge composite verb (fusion_install_library_bundle or similar) owning the recipe end to end, filed on the fusion bridge's tracker. Once that exists, this becomes the same thin shape as --format kicad: export, stage, one verb call, render the result and the restart ask. (Also found while probing: fusion_describe currently crashes bridge-side, filed alongside.)