Fusion - the Fusion 360 Bridge

@@ -16,12 +16,19 @@ done echo "Installed adom-desktop-fusion-bridge skills: $(ls "$PKG_DIR/skills" 2>/dev/null | tr '\n' ' ')"  # The Dashboard CLI (the bridge's Launch Page server) - first container-side bridge-# binary (the three-artifact pattern: bridge zip -> ab, THIS pkg -> container, page media).-if [ -f "$PKG_DIR/bin/fusion-dashboard" ]; then-  DEST=""-  if [ -w /usr/local/bin ]; then DEST=/usr/local/bin-  else mkdir -p "$HOME/.local/bin"; DEST="$HOME/.local/bin"; fi-  cp "$PKG_DIR/bin/fusion-dashboard" "$DEST/fusion-dashboard"+# 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.42"+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+else mkdir -p "$HOME/.local/bin"; DEST="$HOME/.local/bin"; fi+if curl -fsSL -o "$DEST/fusion-dashboard.tmp" "$DASH_URL"; then+  mv "$DEST/fusion-dashboard.tmp" "$DEST/fusion-dashboard"   chmod +x "$DEST/fusion-dashboard"   echo "Installed fusion-dashboard CLI -> $DEST/fusion-dashboard ($("$DEST/fusion-dashboard" health 2>/dev/null || echo 'installed'))"+else+  rm -f "$DEST/fusion-dashboard.tmp"+  echo "WARN: fusion-dashboard download failed ($DASH_URL) - the Dashboard is unavailable until 'adom-wiki pkg update' retries it" fi

@@ -54,7 +54,6 @@     "skills/pcb-stackup/**",     "skills/fusion-demo/**",     "skills/fusion-multiprofile-signin/**",-    "bin/fusion-dashboard",     "dock.json",     "docs/img/dock-fusion.svg",     "skills/fusion-dashboard/**"

@@ -5,6 +5,8 @@ description: The Fusion bridge's Dashboard (Launch Page) - a web app showing LED  # fusion-dashboard - the bridge's Launch Page +Parent skill: adom-desktop-fusion-bridge (the fusion-bridge page skill).+ A Rust CLI in THIS container serving the Dashboard web app. Status comes from shelling `adom-bridge` (the bridge stays the single source of truth); every API response carries `_hint` fields telling you what to automate next.