Fusion - the Fusion 360 Bridge

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

@@ -1169,8 +1169,20 @@ fn serve(port: u16, target: String, ai_thread: String, print_url: bool) {         last_launch_note: Mutex::new(std::collections::HashMap::new()),     });     if print_url {-        // Hydrogen dock await:url contract - the proxied URL a webview can reach.-        println!("http://127.0.0.1:{}/", port);+        // Hydrogen dock await:url contract - the URL a webview can ACTUALLY REACH.+        //+        // The comment here used to say "the proxied URL" while printing loopback (page+        // issue #37). A dock webview renders OUTSIDE this container, so 127.0.0.1 is not+        // its loopback - it resolves to the viewer's own machine and the dock navigates to+        // nothing. code-server publishes the mapping we need as VSCODE_PROXY_URI, e.g.+        // https://<workspace>.adom.cloud/proxy/{{port}}/ - substitute the port and print+        // that. Loopback stays as the fallback for a genuinely local run, where it is right.+        let url = std::env::var("VSCODE_PROXY_URI")+            .ok()+            .filter(|u| u.contains("{{port}}"))+            .map(|u| u.replace("{{port}}", &port.to_string()))+            .unwrap_or_else(|| format!("http://127.0.0.1:{}/", port));+        println!("{}", url);     }     ok(&format!("fusion-dashboard v{} serving on port {} (target {})", VERSION, port,         if app.target.is_empty() { "auto" } else { &app.target }));

@@ -1,18 +1,25 @@ {   "dock_manifest": "1.1.0",-  "webview": { "title": "Fusion Dashboard", "favicon": "docs/img/dock-fusion.svg" },+  "webview": {+    "title": "Fusion Dashboard",+    "favicon": "docs/img/dock-fusion.svg"+  },   "launch": {     "mode": "container_command",     "console": "show",     "steps": [-      { "label": "Installing the Fusion bridge",+      {+        "label": "Installing the Fusion bridge",         "run": "adom-wiki pkg install adom/fusion-bridge",-        "skip_if": "command -v fusion-dashboard",-        "timeout_seconds": 180 },-      { "label": "Starting the Fusion Dashboard",-        "run": "fusion-dashboard serve --print-url",+        "skip_if": "sh -c 'PATH=\"$HOME/.local/bin:$PATH\"; command -v fusion-dashboard'",+        "timeout_seconds": 180+      },+      {+        "label": "Starting the Fusion Dashboard",+        "run": "sh -c 'PATH=\"$HOME/.local/bin:$PATH\"; exec fusion-dashboard serve --print-url'",         "await": "url",-        "timeout_seconds": 60 }+        "timeout_seconds": 60+      }     ],     "on_ready": "navigate_placeholder",     "ai": {@@ -23,4 +30,4 @@       "typed": false     }   }-}+}\ No newline at end of file

@@ -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.101"+DASH_VERSION="1.9.102" 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@@ -30,6 +30,17 @@ 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'))"+  # SAY IT WHEN THE BINARY IS INSTALLED BUT INVISIBLE (page issue #37). /usr/local/bin is+  # not writable in a workspace container, so we land in ~/.local/bin - which is NOT on+  # PATH in a clean process. The install then "succeeds" while `command -v fusion-dashboard`+  # reports nothing, which is exactly how the Hydrogen dock step failed on every real+  # machine while passing on the dev box (where the binary had been placed by hand).+  if ! command -v fusion-dashboard >/dev/null 2>&1; then+    echo "NOTE: $DEST is not on PATH, so 'fusion-dashboard' will not resolve by name."+    echo "      Run it as $DEST/fusion-dashboard, or add to your shell profile:"+    echo "        export PATH=\"\$HOME/.local/bin:\$PATH\""+    echo "      (dock.json already resolves it this way, so the Hydrogen dock is unaffected.)"+  fi 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"

@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.101",+  "version": "1.9.102",   "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,16 +1,20 @@ {   "slug": "fusion-bridge",-  "version": "1.9.101",+  "version": "1.9.102",   "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": {-    "adom/adom-desktop": "*"+    "adom/adom-desktop": "^1.9.0"   },   "scripts": {     "install": "./install.sh",     "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