Fusion - the Fusion 360 Bridge

Follow-up from the #212 audit (ab 2.1.150, crr, 2026-09-22). Everything else fusion declares is exactly what ab now needs and nothing else is required of you: bridge.json verbs (160) match fusion_describe (160) since 1.10.36, the declared timeouts block covers every verb ab's removed built-in table used to guarantee at equal or higher values (export_* 360, walk_cloud_tree 620, gerbers 210, open* 150), and statusVerb: fusion_get_app_state is declared. Thank you — that is why fusion needed no other change when ab dropped its copies.

One thing left, small: the screenshot reply shape. ab's delivery contract is fullPath (+ optional safePath for a ≤1568 px copy): when a reply carries those, the CLI auto-pulls both to the CALLER's machine and adds localPath / localSafePath, which is how an AI in a container reads the picture with no second call. fusion_describe declares:

fusion_screenshot_fusion -> {savedTo: str, sizeKB: int, success: bool}
fusion_take_screenshot   -> {path: str, success: bool}

Neither key triggers the pull, so a container AI gets a Windows path it must notice and pull_file itself. kicad_screenshot_all is the reference shape (its screenshots[] entries carry fullPath, and ab pulls every one, grouping child popups). Renaming to fullPath — and adding safePath when you already write a resized copy — is the whole change; keep the old key alongside for a release if you have callers on it.

Not urgent and nothing is broken: fusion verbs route and answer correctly through ab's single generic path (proved today on arav-rog, crr and winvm). Same note went to adom/pup-bridge#124 and adom/nb-bridge.