Fusion - the Fusion 360 Bridge

@@ -1 +1 @@-1.9.224\ No newline at end of file+1.9.225\ No newline at end of file

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "fusion360",-  "version": "1.9.224",-  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.224/adom-bridge-fusion-v1.9.224.zip",-  "sha256": "c3d6751cfda363538d20794f9abf4c15b3d2f501efabe48b3bf49578401b7305",-  "size": 518156,+  "version": "1.9.225",+  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.225/adom-bridge-fusion-v1.9.225.zip",+  "sha256": "e62305a19d4ea8757a7a5b7568af54649afdbb3f33e28ce2aa8985bfd180d971",+  "size": 518157,   "verbPrefixes": [     "fusion_"   ],

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "fusion360",   "displayName": "Autodesk Fusion 360",-  "version": "1.9.224",+  "version": "1.9.225",   "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.",

@@ -4,7 +4,7 @@ version = 4  [[package]] name = "fusion-dashboard"-version = "1.9.224"+version = "1.9.225" dependencies = [  "serde_json", ]

@@ -1,6 +1,6 @@ [package] name = "fusion-dashboard"-version = "1.9.224"+version = "1.9.225" edition = "2021"  [dependencies]

@@ -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.224"+DASH_VERSION="1.9.225" 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

@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.224",+  "version": "1.9.225",   "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": {

@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.224",+  "version": "1.9.225",   "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",@@ -75,7 +79,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.",@@ -104,9 +111,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+  ]+}

@@ -220,16 +220,71 @@ adom-wiki release upload "$REPO" "$VERSION" "$DASH_BIN" --platform linux --arch echo "  both assets uploaded"  # --- 7. commit + push the source (repo layer) --------------------------------------------+# ⛔ NEVER CLOBBER SOMEONE ELSE'S WORK ON THE PAGE (John, 2026-08-27: "colby might have+# made changes... so don't conflict"). This push overwrites an explicit file list with our+# LOCAL copies. If anyone merges a PR into the page repo, or edits it directly, and we push+# without looking, their change is silently reverted and the merge button lied to them.+# Colby has PR #58 open and Oliver has #34/#38 - the moment one merges, this is live.+# So: remember the page head we last pushed, and if the page has moved since by someone+# other than us, STOP and make a human look.+step "Page-repo conflict check"+HEAD_FILE=".release-page-head"+PAGE_HEAD=$(adom-wiki repo log "$REPO" --json 2>/dev/null | python3 -c "+import sys,json+try:+    d=json.load(sys.stdin); x=d.get('data') or d+    cs=x.get('commits') or x.get('log') or []+    print(cs[0].get('hash','') if cs else '')+except Exception: print('')" 2>/dev/null)+if [ -z "$PAGE_HEAD" ]; then+  echo "  WARNING: could not read the page head - pushing blind is how we would clobber a merge"+  [ "${RELEASE_FORCE:-0}" = "1" ] || die "refusing to push without knowing the page head. Retry, or RELEASE_FORCE=1 once you have checked the page yourself."+elif [ -f "$HEAD_FILE" ] && [ "$(cat "$HEAD_FILE")" != "$PAGE_HEAD" ]; then+  LAST_MSG=$(adom-wiki repo log "$REPO" --json 2>/dev/null | python3 -c "+import sys,json+try:+    d=json.load(sys.stdin); x=d.get('data') or d+    cs=x.get('commits') or x.get('log') or []+    print((cs[0].get('message') or '').splitlines()[0][:80] if cs else '')+except Exception: print('')" 2>/dev/null)+  echo "  page moved since our last push: $LAST_MSG"+  case "$LAST_MSG" in+    "Publish "*|"Update "*) echo "  (our own release pattern - continuing)" ;;+    *) die "the page repo changed since our last push (\"$LAST_MSG\") - someone merged a PR or edited it. PULL those changes into this tree FIRST, or this push reverts them. RELEASE_FORCE=1 only once you have confirmed there is nothing to lose." ;;+  esac+else+  echo "  page head unchanged since our last push"+fi+ step "Commit + repo push" git add -A git commit -q -m "release $VERSION (lockstep): bridge + dashboard + package all at $VERSION  Co-Authored-By: Claude Opus 4.8 <[email protected]>" || echo "  (nothing to commit)"-adom-wiki repo push "$REPO" --files server.py fusion_detect.py BRIDGE_VERSION bridge.json \-  page.json package.json "$MANIFEST" dashboard/src/main.rs dashboard/Cargo.toml dashboard/Cargo.lock \-  dashboard/ui/index.html dockbar.json handlers/dismiss_recovery.py handlers/dialog_classify.py \-  install.sh --json 2>/dev/null | ok_check || die "repo push FAILED"+# THE LIST WAS INCOMPLETE, AND HAD BEEN FOR MONTHS. Oliver reported it in PR #34 back in+# July - "the page-repo server.py is behind the shipped release" - and he was being kind:+# describe.py (the verb catalog the AI reads), the WHOLE addin/ tree, and skills/ were+# never pushed at all. So anyone reading the page, or opening a PR against it, was working+# from source that did not match what shipped. That is why his PR needed a reconciliation+# section. Push what we actually ship.+PUSH_FILES="server.py fusion_detect.py describe.py timings.py aps.py install_addin.py \+  BRIDGE_VERSION bridge.json page.json package.json $MANIFEST \+  dashboard/src/main.rs dashboard/Cargo.toml dashboard/Cargo.lock dashboard/ui/index.html \+  dockbar.json install.sh"+for f in handlers/*.py addin/AdomBridge/*.py addin/AdomBridge/commands/*.py \+         addin/AdomBridge/*.manifest skills/*/SKILL.md tools/release.sh CLAUDE.md; do+  [ -f "$f" ] && PUSH_FILES="$PUSH_FILES $f"+done+echo "  pushing $(echo $PUSH_FILES | wc -w) files"+adom-wiki repo push "$REPO" --files $PUSH_FILES --json 2>/dev/null | ok_check || die "repo push FAILED" echo "  pushed"+adom-wiki repo log "$REPO" --json 2>/dev/null | python3 -c "+import sys,json+try:+    d=json.load(sys.stdin); x=d.get('data') or d+    cs=x.get('commits') or x.get('log') or []+    open('.release-page-head','w').write(cs[0].get('hash','') if cs else '')+except Exception: pass" 2>/dev/null || true  # --- 8. publish the PACKAGE, CHECKED (the step the old flow forgot) ----------------------- step "Publishing package"