Fusion - the Fusion 360 Bridge

@@ -2,7 +2,7 @@  > **This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.** -Drive **Autodesk Fusion 360** from the cloud through [Adom Bridge](https://wiki.adom.inc/adom/adom-desktop):+Drive **Autodesk Fusion 360** from the cloud through [Adom Bridge](https://wiki.adom.inc/adom/adom-bridge): component libraries with real 3D, parametric IPC package generation with laser-etched markings, electronics board workflows, manufacturing exports (Gerbers/BOM/CPL), per-manufacturer design rules, and fast APS cloud-file search - all by asking your AI. Every verb returns a rich `_hint`, so a@@ -171,7 +171,7 @@ Included: JLCPCB 2-layer + 4-layer DRU rules, the matching Gerber CAM jobs (used  ## How the bridge talks to Fusion (architecture) -![Architecture: cloud AI to AD relay to bridge to add-in to Fusion](screenshots/architecture.svg)+![Architecture: cloud AI to ab relay to bridge to add-in to Fusion](screenshots/architecture.svg)  The bridge picks the right channel per task: @@ -185,7 +185,7 @@ The bridge picks the right channel per task:    (zoom/pan/select), and `run_modeling_script` for free-form CAD (this is how EPG packages and    laser markings are generated). 4. **Win32 / UIA side channel** - when the API can't reach it: background hwnd screenshots, WM_CLOSE-   dialog dismissal (no focus steal), SendInput keys/clicks, and AD core verbs+   dialog dismissal (no focus steal), SendInput keys/clicks, and ab core verbs    (`desktop_find_control` / `desktop_ui_click`). 5. **APS cloud** (`aps.py`) - fast server-indexed search + file ops at scale (below). @@ -267,7 +267,7 @@ precisely by lineage URN (never by name).  The AI does the whole setup - the user never gets handed a download link: -- **Detection first:** AD detects an existing Fusion via this bridge's `detect` paths - per-user+- **Detection first:** ab detects an existing Fusion via this bridge's `detect` paths - per-user   (`%LOCALAPPDATA%`) AND system-wide (`%ProgramFiles%`, from `--globalinstall`) webdeploy installs.   `fusion_readiness` / AD's `bridge_readiness` answer installed/running/ready without launching   anything.@@ -277,7 +277,7 @@ The AI does the whole setup - the user never gets handed a download link:   deploys the add-in. A **view-only trial** install is a first-class option for users who just need   to open and inspect designs. - **Never a manual step:** the bridge restarts Fusion itself (`fusion_stop`/`fusion_start`),-  installs the add-in to every add-in directory Fusion has ever used, and fires an AD toast the+  installs the add-in to every add-in directory Fusion has ever used, and fires an ab toast the   moment a step needs the user (sign-in, 2FA, license acceptance).  ## Full verb catalog@@ -294,7 +294,7 @@ _55 verbs._ - `fusion_get_app_state` - Current app state: running, active document, workspace, isElectronics - `fusion_readiness` - FAST readiness check (does NOT launch Fusion): is the Fusion host app installed + running + the bridge ready to drive? A - `fusion_new_electronics_from_eagle` - Import a legacy EAGLE .sch (+ paired .brd) into a NEW Fusion electronics design so the parts INSTANTIATE (schematic + po-- `fusion_notify_owner` - LAST-RESORT human escalation: toast the user's MAIN computer (fans out cross-AD to every peer on the relay, so it reache+- `fusion_notify_owner` - LAST-RESORT human escalation: toast the user's MAIN computer (fans out cross-ab to every peer on the relay, so it reache  **Cloud search & files (APS)** @@ -364,7 +364,7 @@ This page ships **two separate artifacts**, and it matters which one you want:  | Layer | What it is | Who installs it | Contents | Size | |---|---|---|---|---|-| **Wiki package** (`adom-wiki pkg install adom/fusion-bridge`) | **SKILLS ONLY** for a container's AI | your cloud/HD container | `SKILL.md` + `skills/**` (the AI playbooks: APS, driving, onboarding, cloud hygiene, molecule export, PCB stackup) | tiny, text |+| **Wiki package** (`adom-wiki pkg install adom/fusion-bridge`) | **SKILLS ONLY** for a container's AI | your cloud/ah container | `SKILL.md` + `skills/**` (the AI playbooks: APS, driving, onboarding, cloud hygiene, molecule export, PCB stackup) | tiny, text | | **Release zip** (`adom-bridge-fusion-v<ver>.zip`, pointed at by `adom-bridge-fusion-manifest.json`) | the **bridge RUNTIME** | Adom Bridge, via `bridge_install` | `server.py`, `aps.py`, `describe.py`, `handlers/`, the `AdomBridge` Fusion add-in, `resources/` | ~456 KB |  The package teaches your AI **how** to drive Fusion; the release zip is the code Adom Bridge runs on the machine where Fusion lives. Installing the package alone gives you skills with no bridge;@@ -380,7 +380,7 @@ adom-bridge-cli bridge_install '{"manifestUrl": "https://wiki.adom.inc/api/v1/pa adom-wiki pkg install adom/fusion-bridge   # the skills pack for your AI ``` -Auto-updates via `updateManifestUrl` (AD polls on launch + every 4h). 55 verbs -+Auto-updates via `updateManifestUrl` (ab polls on launch + every 4h). 55 verbs - `fusion_describe '{}'` returns the full machine-readable catalog. More demos:  <video controls width="100%" src="https://wiki.adom.inc/api/v1/pages/fusion-bridge/files/library2-3d-montage.mp4"></video>