← Commit history
BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.13.78\ No newline at end of file+1.13.79\ No newline at end of file
CHANGELOG.md+4
@@ -3,6 +3,10 @@ All notable changes to the Adom Bridge Fusion 360 bridge, newest first. Canonical: https://wiki.adom.inc/adom/fusion-bridge ยท GitHub backup: `adom-inc/fusion-bridge` +## 1.13.79 (2026-11-05)++Typed reads for assembly planning (PR #42 by Drew Owens). `assembly_layout` lists one scope's visible parts (path, name, component, grounded, children, a root-space box in mm) with the scope's joints, as-built joints and rigid groups as part paths; it is journaled. `ray_cast` casts batches of rays at named occurrences in their own coordinates and answers `[index, distance]` nearest first; it stays out of the journal, stops at `budgetSeconds` or 1 MiB, and says how many it `cast` so the caller sends the rest. A planner no longer needs raw modeling scripts for either. Add-in 1.0.38: Fusion needs one restart.+ ## 1.13.78 (2026-11-05)  CAM jobs come out as asked (PR #41 by Drew Owens). The FANUC program number and comment are the ones you give (every program was O1001), and the file lands in `post.folder` (a backslash path was ignored and the file went to Fusion's own NC folder; one that still does is moved and flagged `movedFromFusionFolder`). New strategies: 2D adaptive, 2D pocket, 2D contour, drill cycles (drill, peck, chip break with `peckDepthMm`) and pocket clearing. Setups take `stock` (relative box, fixed box or stock bodies) and `wcs`, read back in model mm. Tools come from any sample or local library or the document by type, description, flutes and nearest diameter; `cam_tools` filters by description and diameter. Every operation reports its real status (generated, empty, error, outdated, suppressed, not_generated) with Fusion's warnings and machining time, and the job does not post while an operation lacks a toolpath. A document without CAM opens Manufacture once and goes back to your workspace. Add-in 1.0.37: Fusion needs one restart.
addin/AdomBridge/AdomBridge.manifest+1−1
@@ -6,7 +6,7 @@     "description": {         "": "Adom Desktop Conduit bridge add-in. Exposes a localhost HTTP API for external automation of Fusion 360."     },-    "version": "1.0.37",+    "version": "1.0.38",     "runOnStartup": true,     "supportedOS": "windows" }\ No newline at end of file
bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "fusion360",   "displayName": "Autodesk Fusion 360",-  "version": "1.13.78",+  "version": "1.13.79",   "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.lock+1−1
@@ -4,7 +4,7 @@ version = 4  [[package]] name = "fusion-dashboard"-version = "1.13.78"+version = "1.13.79" dependencies = [  "serde_json", ]
dashboard/Cargo.toml+1−1
@@ -1,6 +1,6 @@ [package] name = "fusion-dashboard"-version = "1.13.78"+version = "1.13.79" 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.13.78"+DASH_VERSION="1.13.79" 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.13.78",+  "version": "1.13.79",   "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+2−2
@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.13.78",+  "version": "1.13.79",   "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": {@@ -152,4 +152,4 @@   "confirmed_user_skills": [     "fusion-design-efficiency"   ]-}\ No newline at end of file+}
rust/Cargo.lock+5−5
@@ -19,7 +19,7 @@ dependencies = [  [[package]] name = "adom-fusion-bridge"-version = "1.13.78"+version = "1.13.79" dependencies = [  "adom-eda-checks",  "base64",@@ -299,7 +299,7 @@ dependencies = [  [[package]] name = "fusion-core"-version = "1.13.78"+version = "1.13.79" dependencies = [  "serde",  "serde_json",@@ -310,7 +310,7 @@ dependencies = [  [[package]] name = "fusion-lbr"-version = "1.13.78"+version = "1.13.79" dependencies = [  "regex",  "roxmltree",@@ -322,14 +322,14 @@ dependencies = [  [[package]] name = "fusion-os-mac"-version = "1.13.78"+version = "1.13.79" dependencies = [  "fusion-core", ]  [[package]] name = "fusion-os-win"-version = "1.13.78"+version = "1.13.79" dependencies = [  "fusion-core",  "windows-sys 0.59.0",
rust/Cargo.toml+1−1
@@ -4,7 +4,7 @@ members = ["core", "lbr", "os-win", "os-mac", "bridge"]  # One version for the whole bridge, in lockstep with BRIDGE_VERSION (tools/release.sh bumps both). [workspace.package]-version = "1.13.78"+version = "1.13.79" edition = "2021" license = "MIT"