Fusion - the Fusion 360 Bridge

@@ -81,3 +81,23 @@ When you write or materially update a USER skill: add the glob (if new), bump pk `adom-wiki pkg publish` - in the SAME sitting. A skill that is written but not published is invisible to every Adom user, which defeats the entire point (John's standing rule: shared learnings go to the wiki so every user's agent gets them, not into private memory).++## ⛔ Trap 3: a DASHBOARD-only ship still needs `pkg publish` (repo push is NOT enough)++The dashboard binary version is wired into `install.sh` as `DASH_VERSION`, and `install.sh`+lives in the PACKAGE PAYLOAD. `adom-wiki repo push` updates the page's git repo (the Files+tab) but does NOT touch the published install payload, and `adom-wiki pkg install` reads the+PAYLOAD. So a dashboard ship that only does `release upload` + `repo push` leaves every+`pkg install` resolving the OLD `DASH_VERSION` -> the old dashboard binary. project-1d caught+this live twice (2026-08-23: install kept giving 1.9.153/1.9.157 after 1.9.157/1.9.158 were+"shipped"). After ANY dashboard binary ship you MUST also bump the pkg version+(page.json + package.json) and `adom-wiki pkg publish --org adom`.++**Dashboard ship checklist:** edit main.rs -> bump dashboard `Cargo.toml` version -> `cargo+build --release` -> `adom-wiki release upload adom/fusion-bridge <ver> <binary> --platform+linux --arch x64` -> bump `DASH_VERSION` in install.sh -> **bump page.json + package.json pkg+version** -> commit -> `adom-wiki repo push` -> **`adom-wiki pkg publish --org adom`** ->+VERIFY with a real clean install: `cd /tmp/x && adom-wiki pkg install adom/fusion-bridge`+then `grep DASH_VERSION adom_modules/adom/fusion-bridge/install.sh` must show the new version.+Never trust the `files/install.sh` HTTP endpoint for this - it serves the git repo, not the+payload.