Fusion - the Fusion 360 Bridge

@@ -52,7 +52,7 @@ Capture with WGC (`desktop_record_window_start`) - it grabs the live editor canv  **Full verb reference:** every verb with its input/output schema and examples is in **[`VERBS.md`](VERBS.md)** (generated from the bridge's own `fusion_describe`). -**Building component libraries** (symbol + footprint + 3D into a placeable `.lbr`, with the chip-fetcher / adom-symbol / adom-footprint / adom-lbr pipeline and the 3D-via-cloud-URN flow): see **[`MAKING_LIBRARIES.md`](MAKING_LIBRARIES.md)**.+**Building component libraries** (symbol + footprint + 3D into a placeable `.lbr`, with the chip-fetcher / adom-symbol / adom-footprint / adom-lbr pipeline and the 3D-via-cloud-URN flow): see **[`MAKING_LIBRARIES.md`](MAKING_LIBRARIES.md)** (the guide) and its companion **[`LIBRARY_FINDINGS.md`](LIBRARY_FINDINGS.md)** (the hard-won findings log: the `.fusion` variant, the exact `package3d` `wip_urn` markup, the owned-popup error-capture technique, and every pitfall).  **Building / publishing / forking this bridge** (version bump, build the zip, publish as a wiki *release*, install into Adom Desktop, and the community fork -> test -> PR flow, with all the pitfalls): see **[`PUBLISHING.md`](PUBLISHING.md)**. 

@@ -5,6 +5,12 @@ description: How an Adom component library (symbol + footprint + 3D chip) is bui  # Fusion libraries - symbol + footprint + 3D into a placeable .lbr +> This skill is the concise, self-sufficient entry point for the workflow. The **exhaustive guides ++> screenshots live on the bridge's wiki page** and are fetchable (WebFetch / `adom-wiki repo show` /+> browser): the **[guide](https://wiki.adom.inc/adom/adom-desktop-fusion-bridge/files/MAKING_LIBRARIES.md)**+> and the **[findings log](https://wiki.adom.inc/adom/adom-desktop-fusion-bridge/files/LIBRARY_FINDINGS.md)**.+> Read those for the full walkthrough, the exact `package3d` markup, and every pitfall.+ ## 1. The pipeline (where each tool fits)  ```@@ -33,7 +39,7 @@ chip-fetcher  ->  adom-symbol   -> .kicad_sym  ┐   (OpenCASCADE relief on the top face), driven by `chip-fetcher/scripts/occt-name-on-chip.py`. - **fusion_open_lbr** imports the `.lbr` into Fusion's Electronics Library editor. -See **[LIBRARY_FINDINGS.md](../../LIBRARY_FINDINGS.md)** for the full live findings log.+See **[LIBRARY_FINDINGS.md](https://wiki.adom.inc/adom/adom-desktop-fusion-bridge/files/LIBRARY_FINDINGS.md)** for the full live findings log.  ## 2. Opening a .lbr in Fusion (verified working) @@ -56,7 +62,7 @@ Stage the file onto Windows first. Proven method (same proxy that serves shotlog  Confirm the byte count matches after download. Build the `shell_execute` JSON in Python (`json.dumps`), not by hand - nested cmd/PowerShell quoting mangles easily, and Windows paths need `\\` in JSON. -## 4. THE HARD ONE: attaching the real 3D chip (the open problem)+## 4. Attaching the real 3D chip (SOLVED via fusion_attach_3d_package)  A fresh `.lbr` shows the package as a **placeholder** 3D (the Content Manager 3D tab is empty / a generated box). The real chip STEP exists (`chip-fetcher/library/<MPN>/<MPN>.step`) but is **not linked**. This is the part that "has always been complex." @@ -66,7 +72,7 @@ A fresh `.lbr` shows the package as a **placeholder** 3D (the Content Manager 3D urn:adsk.wipprod:fs.file:vf.<id>?version=<N> ``` -**The verified flow (proven on nRF54L15; full walkthrough + screenshots in [MAKING_LIBRARIES.md](../../MAKING_LIBRARIES.md)):**+**The verified flow (proven on nRF54L15; full walkthrough + screenshots in [MAKING_LIBRARIES.md](https://wiki.adom.inc/adom/adom-desktop-fusion-bridge/files/MAKING_LIBRARIES.md)):** 1. **Model -> cloud -> URN.** Stage the STEP to Windows, then `fusion_aps_upload {projectId, folderId, localPath:"C:/.../<MPN>.step"}` returns a real cloud URN (`urn:adsk.wipprod:dm.lineage:...`). `Electron.getCloudPathFromUrn` confirms the 3D package references a Fusion **file** URN, which this produces. (`fusion_import_file` is NOT a routed verb; do not rely on it.) 2. **Open the generator.** `fusion_execute_text_command {"command":"Electron.Create3DPackage C:/.../<MPN>.lbr"}` opens the **3D PACKAGE Generator**: a Design-workspace doc with the footprint loaded and a PACKAGE / SELECT / FINISH ribbon. 3. **Insert model + FINISH** -> Fusion writes the `package3d` URN back to the library.@@ -78,7 +84,7 @@ the Fusion **Save** dialog via `desktop_ui_click {automationId:'QTApplication.QT The 3D then binds onto the deviceset (Content Manager tree shows it; the `Package` column flips Placeholder -> part name; the preview LAGS a beat). Fusion writes this exact markup (for a self-uploaded model): `<package3d urn="" wip_urn="urn:adsk.wipprod:fs.file:vf.<id>?version=1" locally_modified="yes" type="model">`-+ a device `<package3dinstance package3d_urn="...fs.file:vf...?version=1"/>`. See LIBRARY_FINDINGS.md §11-12.++ a device `<package3dinstance package3d_urn="...fs.file:vf...?version=1"/>`. See [LIBRARY_FINDINGS.md](https://wiki.adom.inc/adom/adom-desktop-fusion-bridge/files/LIBRARY_FINDINGS.md) §11-12.  Uploading models into the user's Fusion cloud is an outward, persistent action - confirm first, and put uploads in a contained folder (we used `Standard Components / Electronics 3D`).