Fusion - the Fusion 360 Bridge

@@ -16,6 +16,14 @@ all of this and filed its own bridge bugs as "adom-desktop" requests. Don't.) - So: a `fusion_*` verb behaves wrong, a hint is missing, APS misbehaves, the add-in is stale → it's   **your code**, fix it here and republish. It is NOT an adom-bridge request. +## Where to TALK to ab (learned the hard way, 2026-08-17)++**The adom/adom-bridge-sdk repo is DEPRECATED as a discussion venue** - the SDK moved INTO the+main `adom/adom-bridge` repo (its skills ship in that pkg: `adom-bridge-sdk*`), and the ab thread+does not watch the old repo's issues. Two of this bridge's posts sat unread there. File EVERY+SDK/cross-bridge ask on **adom/adom-bridge** issues; bridge-specific dialogue stays on this+page's own issues (ab watches those).+ ## Map of what you manage  - `server.py` - bridge server / verb router (talks to AD's relay, proxies to the add-in). **On start

@@ -124,5 +124,6 @@ fusion-dashboard status                                 # one-shot JSON (the LED  ## SDK evangelism -ab's Bridge SDK gets this pattern as "the container binary facet" - filed on the ab/SDK-threads so kicad-bridge can mimic. Keep the contract doc in sync when the CLI grows.+ab's Bridge SDK gets this pattern as "the container binary facet" - filed as adom/adom-bridge#81+(⚠ NOT adom-bridge-sdk: that repo is a dead letterbox, the SDK lives in the main adom/adom-bridge+repo now) so kicad-bridge can mimic. Keep the contract doc in sync when the CLI grows.