Fusion - the Fusion 360 Bridge

@@ -7,10 +7,13 @@ all of this and filed its own bridge bugs as "adom-desktop" requests. Don't.)  ## You vs adom-bridge (ab) core - the boundary -**Naming (John, 2026-08-29):** the host app is **Adom Bridge, "ab"**. "Adom Desktop" and "AD" are the-retired names; do not use them in prose, hints, skills or issues. Identifiers such as `_ad_call`,-`ad_client.py` and the repo folder keep their old spelling on purpose (renaming buys nothing and risks-breakage).+**Naming (John, 2026-08-29, tightened 2026-09-01):** the host app is **Adom Bridge, "ab"**. "Adom+Desktop" and "AD" are the retired names; do not use them in prose, hints, skills or issues. The+2026-08-29 exception that kept `_ad_call`, `ad_client.py` and the `adom-desktop-fusion-bridge` folder+is REVERSED: John (2026-09-01) - "make sure there's no more remnants of ad or adom-desktop naming."+The Rust port ships the purge (census + targets in the roadmap: 86 `_ad_call`, 59 `ad_client`,+70 `adom-desktop`), and a CI grep fails the build on any remnant. Until the rename lands, do not ADD+new uses of the old identifiers; write `ab` in everything new.  - **ab core owns:** the `adom-bridge` CLI, the relay / command passthrough, bridge lifecycle   (`bridge_install` / streaming the bridge from the wiki into `…\bridges-cache\fusion360`), and the