← Commit history
BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.9.100+1.9.101
adom-bridge-fusion-manifest.json+4−4
@@ -1,10 +1,10 @@ {     "manifest_version": 1,     "name": "fusion360",-    "version": "1.9.100",-    "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.115/adom-bridge-fusion-v1.9.100.zip",-    "sha256": "c7b68d8f5a5af7311e3b66f5aa44e44c8bfd4bb9eaab2680cd0f085b3135f766",-    "size": 437937,+    "version": "1.9.101",+    "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.116/adom-bridge-fusion-v1.9.101.zip",+    "sha256": "d1fe69c2fc6e0a8e3307e9376217512f87e299ef73c29c117f43254827171479",+    "size": 438531,     "verbPrefixes": [         "fusion_"     ],
bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "fusion360",   "displayName": "Autodesk Fusion 360",-  "version": "1.9.100",+  "version": "1.9.101",   "description": "Drive Autodesk Fusion 360 from the cloud: 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 plus browse/recent/file-info/versions, cloud file download/upload and folder creation, and in-app parametric modeling (fusion_run_modeling_script). Never-charge: APS calls are capped to the free tier.",   "homepage": "https://wiki.adom.inc/adom/fusion-bridge",   "author": "Adom Inc.",
dashboard/Cargo.toml+1−1
@@ -1,6 +1,6 @@ [package] name = "fusion-dashboard"-version = "1.9.115"+version = "1.9.116" edition = "2021"  [dependencies]
install.sh+1−1
@@ -21,7 +21,7 @@ echo "Installed fusion-bridge skills: $(ls "$PKG_DIR/skills" 2>/dev/null | tr '\ # binary (the three-artifact pattern: bridge zip -> ab, THIS pkg -> container skills + # this download, page media -> wiki). Per the wiki's PKG_VS_RELEASE policy, binaries are # platform-tagged RELEASE assets, never tarball content - the installer fetches them.-DASH_VERSION="1.9.115"+DASH_VERSION="1.9.116" DASH_URL="https://wiki.adom.inc/download/adom/fusion-bridge/${DASH_VERSION}/fusion-dashboard" DEST="" if [ -w /usr/local/bin ]; then DEST=/usr/local/bin
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.115",+  "version": "1.9.116",   "type": "app",   "description": "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.",   "dependencies": {
page.json+10−7
@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.115",+  "version": "1.9.116",   "type": "app",   "description": "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.",   "dependencies": {@@ -11,6 +11,10 @@     "uninstall": "./uninstall.sh"   },   "tags": [+    "ab",+    "bridge",+    "fusion",+    "desktop-app",     "fusion360",     "autodesk",     "cad",@@ -70,7 +74,10 @@     "build a basic parts library",     "add a 3d model to a component",     "make a fusion 360 library with 3d",-    "set up the fusion bridge"+    "set up the fusion bridge",+    "fusion dashboard",+    "fusion status page",+    "open the fusion launch page"   ],   "discovery_pitch": "Use the Adom Bridge Fusion 360 bridge when the user wants to DRIVE Autodesk Fusion 360 from the cloud: open/search their team's Fusion cloud designs, lay out a PCB or do electronics, export STEP/IGES/STL/Gerbers/BOM, or build a component library with real rendering 3D. It runs Fusion on the user's own machine via Adom Bridge. NOT for web/browser/login/form-filling (that's the native-browser extension) and NOT for KiCad (that's the kicad bridge).",   "brief": "Drive Autodesk Fusion 360 from the cloud via Adom Bridge: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.",@@ -99,9 +106,5 @@       "label": "Part volume",       "prompt": "How much material does each printed part in this assembly use?"     }-  ],-  "author": {-    "name": "John Lauer",-    "email": "[email protected]"-  }+  ] }\ No newline at end of file
server.py+31−2
@@ -589,9 +589,38 @@ def _handle_launch(fusion_info: dict, args: dict) -> dict:         # DOCTRINE: the add-in only loads AT LAUNCH, so "running but no add-in" is not         # something more waiting can fix - it needs a restart, and the bridge performs it         # rather than returning a cheerful false positive. Fall through to the cold path.+        # ⛔ BUSY IS NOT MISSING - AND THIS PATH IS DESTRUCTIVE (page issue #41). The #39 fix+        # force-restarts when the add-in does not answer. But an add-in mid-way through a long+        # command does not answer EITHER, and a surface has measured 546s here. ab's loop read+        # an unparseable (busy) probe as "not running", called fusion_start, and this code+        # killed a perfectly healthy Fusion doing real work - destroying the very run it was+        # meant to rescue. 1.9.94 taught the not-responding path to check /status for busy; I+        # failed to apply it to the one path where being wrong DESTROYS something. Check first.+        _busy = None         if not addin_ok:-            print("[Fusion Bridge] warm start found NO add-in - restarting Fusion so it loads "-                  "(never reporting success with addinConnected:false, issue #39)")+            try:+                _st = _check_addin_status(timeout=3.0)+                _busy = _st if (_st and _st.get("busy")) else None+            except Exception:+                _busy = None+        if _busy:+            return {+                "success": False,+                "error": "Fusion is running and the add-in is BUSY with a long command - NOT "+                         "restarting it. Waiting is the remedy here, not a relaunch.",+                "errorCode": "fusion_addin_busy",+                "busyCommand": _busy.get("busyCommand"),+                "elapsedSeconds": _busy.get("elapsedSeconds"),+                "alreadyRunning": True,+                "startKind": "warm",+                "_hint": ("Do NOT call fusion_start again on this - it is exactly how a healthy "+                          "run gets killed. Poll fusion_readiness (it answers while the add-in "+                          "is busy) and compare elapsedSeconds against fusion_state.timings for "+                          "this machine; only past roughly 2x p90 is a restart justified."),+            }+        if not addin_ok:+            print("[Fusion Bridge] warm start found NO add-in and it is NOT busy - restarting "+                  "Fusion so the add-in loads (issue #39, guarded by the busy check from #41)")             try:                 handle_fusion_kill(fusion_info, {})   # a non-serving add-in will not close politely                 _t0.sleep(3)                          # brief settle; the launch below is what matters