Fusion - the Fusion 360 Bridge

@@ -11,10 +11,6 @@     "uninstall": "./uninstall.sh"   },   "tags": [-    "ab",-    "bridge",-    "fusion",-    "desktop-app",     "fusion360",     "autodesk",     "cad",@@ -79,10 +75,7 @@     "build a basic parts library",     "add a 3d model to a component",     "make a fusion 360 library with 3d",-    "set up the fusion bridge",-    "fusion dashboard",-    "fusion status page",-    "open the fusion launch page"+    "set up the fusion bridge"   ],   "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.",@@ -111,5 +104,9 @@       "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

@@ -72,6 +72,18 @@ echo "  gates OK" # this guard read a respawn-window "running: null" as "no" and shipped anyway (the 8th kill). # RULE NOW: a RUNNING Fusion means someone is using it -> refuse. UNKNOWN -> refuse. Only an # explicit running:false passes. RELEASE_FORCE=1 overrides, and you had better know why.+# ⛔ SCOPE: the guard exists because bridge_install REAPS THE BRIDGE and kills in-flight+# work. Publishing to the wiki does not touch anyone's Fusion, so gating a publish on+# Fusion's state protects nothing and blocks real work - it refused a dashboard-HTML+# release on 2026-08-27 purely because Fusion's parentage was undeterminable, with+# RELEASE_INSTALL unset so no install would have run at all. Guard the DANGEROUS step,+# not the whole script. (Bypassing with RELEASE_FORCE would have been the wrong fix: that+# flag is for when you have CONFIRMED nobody is driving Fusion, not for skipping a check+# that should not have applied.)+if [ "${RELEASE_INSTALL:-0}" != "1" ]; then+  echo "  guard SKIPPED - publish-only run (RELEASE_INSTALL is not 1, so nothing installs)"+  RELEASE_FORCE=1+fi step "Live-work guard on $BRIDGE_TARGET" _probe() { adom-bridge --ai-thread "$AITHREAD" --target "$BRIDGE_TARGET" "$1" '{}' 2>/dev/null \   | python3 -c "import sys,json