Fusion - the Fusion 360 Bridge

@@ -1 +1 @@-1.6.7\ No newline at end of file+1.6.8\ No newline at end of file

@@ -3,6 +3,22 @@ All notable changes to the Adom Desktop Fusion 360 bridge, newest first. Canonical: https://wiki.adom.inc/adom/adom-desktop-fusion-bridge · GitHub backup: `adom-inc/adom-desktop-fusion-bridge` +## 1.6.8 - 2026-06-30++- **Stale add-in is no longer a SILENT failure (fixes #55, Drew's report).** The add-in now REPORTS+  its version (`AdomBridge.manifest` → `/health` + `/status`), and the bridge compares it to the+  version it bundles. `fusion_readiness` and `fusion_addin_status` now return `addinVersion` /+  `expectedAddinVersion` / `addinStale` (+ a re-sync `_hint`), and any add-in command the running+  add-in is too old to know (e.g. `open_by_urn`, which silently broke `fusion_aps_open` for Drew) now+  comes back with `errorCode:"addin_stale"` and the exact fix (`fusion_stop` then `fusion_start` to+  re-sync from cache with Fusion closed). Add-in manifest bumped 1.0.2 → 1.0.3.+- **Bridge-SDK re-audit against the updated SDK.** (1) `bridge.json` `verbs[]` re-synced to the+  authoritative `fusion_describe` catalog (was stale: 40 → 53 verbs; added the library/3D + board ++  app-state verbs; `statusVerb` `fusion_get_app_state` is now listed; dropped the dead+  `fusion_apply_instapcb_rules`). (2) The USER skill's cold-start section now encodes all **8** SDK+  conventions (was 5), led by an `errorCode` response→meaning→action table (incl. the new+  `addin_stale` row) and the reuse-don't-relaunch + surface-`_hint`-verbatim conventions.+ ## 1.6.7 - 2026-06-30  - **AD 1.9.63 alignment (discussion #57).** (1) The bridge HTTP server now honors **`ADOM_BIND_HOST`**

@@ -14,22 +14,31 @@ adom-desktop fusion_<action> '<json_args>'  The leading `fusion_` routes to the Fusion plugin; `<action>` is the plugin-side name. -## Read this before you panic (cold-start + conventions)+## FIRST-TIME / COLD-START — read before you panic -1. **Check readiness first, don't launch blindly.** Call **`fusion_readiness`** (or AD's-   `bridge_readiness`) - it reports `installed` / `running` / `ready` WITHOUT launching anything.-   `installed:false` → the user needs Fusion (see [fusion-onboarding](skills/fusion-onboarding/SKILL.md));-   AD **detects** Fusion (never installs it) and **provisions Python itself** (a portable no-UAC-   3.12.13 runtime if none is on PATH - never bootstrap your own; check AD's `runtimes` verb for-   state). `running:false` → `fusion_start` (it blocks until the add-in is ready). `ready:true` → drive.-2. **A long op that "times out" at ~60s is usually STILL RUNNING server-side** (the relay caps the-   request, not the work). Verify by artifacts (the saved file / screenshots), don't blindly retry.-3. **Never fly blind past a dialog.** Mutating verbs return a dialog array; analyze it and dismiss in-   the BACKGROUND (`fusion_close_window`, never `fusion_send_key`/Escape which steals focus). See-   [fusion-driving](skills/fusion-driving/SKILL.md).-4. **Never write files to a shared cloud ROOT.** Uploads default to an `Adom AI Workspace` folder; see-   [fusion-cloud-hygiene](skills/fusion-cloud-hygiene/SKILL.md).-5. Read each verb's `_hint` in its OUTPUT - it tells you the next step.+A fresh laptop may not have Fusion running (or may run a stale add-in). That is EXPECTED, not defeat.+Branch on the stable `errorCode`, never the prose:++| response (`errorCode`) | what it means | what you do |+|---|---|---|+| `ready:true` (fusion_readiness) | Fusion up + add-in current | drive |+| `running:false` / `fusion_not_running` | installed, not launched | `fusion_start` (blocks until the add-in is ready), retry |+| `installed:false` | no Fusion host app | [fusion-onboarding](skills/fusion-onboarding/SKILL.md); AD DETECTS Fusion (never installs it) |+| `addinStale:true` / `addin_stale` | Fusion runs an OLD add-in that never re-synced (silent-failure risk) | `fusion_stop` then `fusion_start` — the bridge re-syncs the add-in from cache on start (Fusion must be CLOSED) |+| `blockingDialogs:[…]` | a modal is blocking the add-in | dismiss in the BACKGROUND, then the op auto-resumes |++**Runtime note:** AD **provisions Python itself** (a portable no-UAC 3.12.13 runtime if none is on PATH — the bridge never bootstraps its own; check AD's `runtimes` verb). You never install Python.++## The 8 conventions (from the Bridge SDK)++1. **Poll readiness, don't launch blindly.** `fusion_readiness` (or AD's `bridge_readiness`) is read-only — it reports `installed`/`running`/`ready`/`addinStale` WITHOUT launching anything. Loop: readiness → act on the row above → drive.+2. **`fusion_readiness` is the standardized cold-start probe.** (Fusion is a detected HOST APP with no heavy download, so there's no `prewarm` step — readiness is the whole gate.)+3. **Core verbs live in the table below; `fusion_describe '{}'` is the full machine-readable catalog.** Read the table to act fast; hit `describe` for completeness — don't guess a verb.+4. **Background by default — don't disrupt the user.** This bridge drives the AI's workspace, not the user's screen. Dismiss dialogs in the BACKGROUND (`fusion_close_window`, never `fusion_send_key`/Escape, which steals focus); only foreground to SHOW the user something. See [fusion-driving](skills/fusion-driving/SKILL.md).+5. **`ok:true` is not enough — verify.** A long op that "times out" at ~60s is usually STILL RUNNING server-side (the relay caps the request, not the work). Verify by artifacts (the saved file / a screenshot / `fusion_get_app_state`), don't blindly retry.+6. **Reuse the running Fusion, don't relaunch.** Fusion is a singleton — `fusion_readiness` before `fusion_start` (especially after a compaction); if it's already `ready`, just drive. Relaunching churns state.+7. **Surface `_hint` verbatim + branch on `errorCode`.** Every verb returns an actionable `_hint`; relay it to the user unchanged and key your logic off the stable `errorCode`, not the prose.+8. **Never write files to a shared cloud ROOT.** Uploads default to an `Adom AI Workspace` folder; see [fusion-cloud-hygiene](skills/fusion-cloud-hygiene/SKILL.md).  ## [!] Electronics PCBs: ALWAYS open the PROJECT file (never the schematic / board / 3D) 

@@ -6,7 +6,7 @@     "description": {         "": "Adom Desktop Conduit bridge add-in. Exposes a localhost HTTP API for external automation of Fusion 360."     },-    "version": "1.0.2",+    "version": "1.0.3",     "runOnStartup": true,     "supportedOS": "windows" }

@@ -20,6 +20,7 @@ Threading model: """  import json+import os import threading import time import uuid@@ -31,6 +32,21 @@ from .commands.cloud_documents import get_walk_progress  PORT = 8774 +# Add-in version — read from the sibling manifest so /health + /status can+# REPORT it. The bridge compares this against the version it bundles to catch a+# STALE add-in (issue #55: an old Roaming add-in that never re-synced from the+# bridge cache, which made fusion_aps_open fail SILENTLY). Sourced from the+# manifest so a single bump is the source of truth (no hardcode to drift).+def _read_addin_version():+    try:+        mf = os.path.join(os.path.dirname(__file__), "AdomBridge.manifest")+        with open(mf, "r", encoding="utf-8") as f:+            return (json.load(f) or {}).get("version", "unknown")+    except Exception:+        return "unknown"++ADDIN_VERSION = _read_addin_version()+ _server = None _server_thread = None _custom_event_id = None@@ -256,6 +272,7 @@ class AdomBridgeHandler(BaseHTTPRequestHandler):             self._respond(200, {                 "status": "ok",                 "addin": "AdomBridge",+                "version": ADDIN_VERSION,                 "port": PORT,                 "main_thread": main_status,                 "main_thread_locked": main_lock_held,@@ -274,6 +291,7 @@ class AdomBridgeHandler(BaseHTTPRequestHandler):                 elapsed = round(time.time() - busy["started_at"], 1)                 resp = {                     "busy": True,+                    "version": ADDIN_VERSION,                     "busyCommand": busy["command"],                     "elapsedSeconds": elapsed,                     "requestId": busy["request_id"],@@ -295,7 +313,7 @@ class AdomBridgeHandler(BaseHTTPRequestHandler):                     )                 self._respond(200, resp)             else:-                self._respond(200, {"busy": False})+                self._respond(200, {"busy": False, "version": ADDIN_VERSION})         else:             self._respond(404, {"error": "Not found"}) 

@@ -1,13 +1,13 @@ {   "manifest_version": 1,   "name": "fusion360",-  "version": "1.6.7",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-fusion-bridge/1.6.7/adom-bridge-fusion-v1.6.7.zip",-  "sha256": "c9aa67c269f6da763d08ded74a33eb5e120a5e1894eed2989964793a892613ee",-  "size": 294279,+  "version": "1.6.8",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-fusion-bridge/1.6.8/adom-bridge-fusion-v1.6.8.zip",+  "sha256": "9dc5bed4d8a7db0dbdc7fc4863c42d12b95b0747e9081dbb8ebd4cb6661428da",+  "size": 297014,   "verbPrefixes": [     "fusion_"   ],   "healthEndpoint": "/status",-  "released_at": "2026-06-30T16:30:00Z"+  "released_at": "2026-06-30T17:15:00Z" }\ No newline at end of file

@@ -1,6 +1,6 @@ {   "slug": "adom-desktop-fusion-bridge",-  "version": "1.6.8",+  "version": "1.6.9",   "type": "app",   "description": "Drive Autodesk Fusion 360 from the cloud via Adom Desktop: launch Fusion, electronics board layout, design rules, exports (STEP/IGES/STL/3MF/USDZ/OBJ/DXF/DWG/Gerbers/BOM/CPL), fast APS server-indexed cloud search with browse/recent/versions, cloud download/upload and folder creation, and in-app parametric modeling. Never-charge: APS calls are capped to the free tier.",   "dependencies": {},