Fusion - the Fusion 360 Bridge

@@ -31,10 +31,18 @@ Short version below, full detail in each guide.  ## The demo: one verb, a whole guided tour (`fusion_demo`) +> **Tour mode** (`fusion_demo {"mode": "tour"}`): the ASYNC showcase for progress-bar+> front-ends - walks symbol, footprint, device view, 3D package off the bundled sample+> library (plus project/schematic/2D/3D via `fusion_make_test_project` by default, or a+> cloud design when `query` names one), reports `{percent, stepLabel, elapsedSec,+> estimatedSec}` via `fusion_demo_progress`, and the final poll carries the screenshot+> gallery (`shots: [{title, image}]`). Background by default. The staged onboarding flow+> below remains bare `fusion_demo {}`.+ New to this? Run **one verb** and watch:  ```bash-adom-bridge-cli fusion_demo '{}'+adom-bridge fusion_demo '{}' ```  `fusion_demo` takes a first-time user from nothing to a real board. It launches Fusion, **finishes@@ -60,6 +68,48 @@ continues without it. To demo a specific design: `fusion_demo '{"query":"BQ25792  Playbook for the AI running it: the bundled **fusion-demo** skill. +## The wiki-to-EE circle: one verb per content type (NEW in 1.9.9-1.9.26)++The Web Control demo's contract: every electronics content type a wiki component page+implies, one first-class verb each, ALL background (your foreground is never touched):++| Content | Verb |+|---|---|+| Library | `fusion_open_lbr {"filePath": "C:/....lbr"}` |+| Symbol | `fusion_show_symbol {"name": "<deviceset>"}` (library open, or pass `libraryPath`) |+| Footprint | `fusion_show_footprint {"name": "..."}` |+| 3D chip | `fusion_show_3d_package {"name": "...", "libraryPath": "...", "stepPath": "C:/....step"}` |+| Project | `fusion_make_test_project {"libraryPath": "..."}` |+| Schematic | `fusion_show_schematic {}` |+| 2D board | `fusion_show_2d_board {}` |+| 3D board | `fusion_show_3d_board {}` |++**Bare-artifact wrapping**: `fusion_show_symbol` / `fusion_show_footprint` also accept a+raw `<symbol>` / `<package>` XML fragment (`symbolXml` / `packageXml`) - the bridge+generates a minimal wrapper library around it so a one-off artifact shows properly in+the Library Manager. Single-artifact libraries (symbol-only, footprint-only) are valid;+a 3D-only library parses but has nothing to display (a 3D binding needs a package).++**`fusion_make_test_project`** is the from-scratch answer for "a customer only has a+component page": it generates a minimal test circuit (the part + a generated 330R series+resistor, routed on a small board) as real EAGLE .sch/.brd server-side and imports both+DIALOG-FREE via `Document.newDesignFromLocal`. No cloud, no sign-in. After it, the+schematic/2D/3D verbs work on the result - and if the source library carries a 3D+binding, the generated board's element gets `package3d_urn`, so the 3D PCB renders the+REAL component model, not a generic extrusion.++**The correct library (3D rendering in the Content Manager)**: mint a real cloud URN+with `fusion_make_3d_package` (returns `wip_urn`; needs a signed-in session - the ONE+cloud-dependent step in the circle), bind it into the `.lbr`'s `<packages3d>`, reopen.+Autodesk's thumbnail service lags ~2-3 min behind a fresh mint. A one-call+`fusion_bind_library_3d` wrapper is planned.++**Background etiquette (hard contract)**: every verb above runs in the background - the+envelope denies Fusion's self-activation grabs, yields to real user input (it never+fights the human), keystrokes go via PostMessage, and native modal dialogs are banned+from automation. The user can keep typing in other threads the whole time. Pass+`foreground: true` on any window-raising verb when the user explicitly wants to watch.+ ## Component library manager - the Adom basic parts library  The bridge builds and opens full EAGLE-format component libraries in Fusion's library editor. Below:@@ -87,7 +137,7 @@ package + laser-etched marking + STEP export, in ONE call, a few seconds per par ![0603 chip with 103 etched](screenshots/epg-0603-103.png)  ```bash-adom-bridge-cli fusion_generate_package '{+adom-bridge fusion_generate_package '{   "type": "soic",   "params": {"DPins": 8, "D": 4.9, "E": 6.0, "E1": 3.9, "e": 1.27, "A": 1.6, "A1": 0.1, "b": 0.41, "L": 0.84},   "etch": "LM358\nADOM-A",@@ -148,9 +198,9 @@ verbs reprimand via `_hint` if you open a non-project file. One verb each, straight from the open board:  ```bash-adom-bridge-cli fusion_export_gerbers '{"outputPath": "C:/tmp/gerbers"}'   # JLCPCB-ready CAM job-adom-bridge-cli fusion_export_bom     '{"outputPath": "C:/tmp/bom.csv"}'   # grouped by value+package-adom-bridge-cli fusion_export_cpl     '{"outputPath": "C:/tmp/cpl.csv"}'   # pick-and-place centroids+adom-bridge fusion_export_gerbers '{"outputPath": "C:/tmp/gerbers"}'   # JLCPCB-ready CAM job+adom-bridge fusion_export_bom     '{"outputPath": "C:/tmp/bom.csv"}'   # grouped by value+package+adom-bridge fusion_export_cpl     '{"outputPath": "C:/tmp/cpl.csv"}'   # pick-and-place centroids ```  Plus mechanical exports: STEP / IGES / STL / 3MF / USDZ / OBJ / DXF / DWG. Long exports return@@ -162,8 +212,8 @@ The bridge ships manufacturer rule files + CAM jobs in `resources/` and loads th board, so DRC matches what the fab checks:  ```bash-adom-bridge-cli fusion_load_design_rules '{"ruleFile": "JLCPCB-2layer.dru"}'-adom-bridge-cli fusion_set_design_rules  '{"rules": {"minClearance": 0.127}}'   # ad-hoc tweaks+adom-bridge fusion_load_design_rules '{"ruleFile": "JLCPCB-2layer.dru"}'+adom-bridge fusion_set_design_rules  '{"rules": {"minClearance": 0.127}}'   # ad-hoc tweaks ```  Included: JLCPCB 2-layer + 4-layer DRU rules, the matching Gerber CAM jobs (used by@@ -376,7 +426,7 @@ tab), never inside the artifact streamed to every user's machine. ## Install (via Adom Bridge)  ```bash-adom-bridge-cli bridge_install '{"manifestUrl": "https://wiki.adom.inc/api/v1/pages/fusion-bridge/files/adom-bridge-fusion-manifest.json"}'+adom-bridge bridge_install '{"manifestUrl": "https://wiki.adom.inc/api/v1/pages/fusion-bridge/files/adom-bridge-fusion-manifest.json"}' adom-wiki pkg install adom/fusion-bridge   # the skills pack for your AI ```