Fusion - the Fusion 360 Bridge

@@ -223,6 +223,24 @@ Earlier versions used hardcoded port `8773` for the bridge and `8774` for the in - The add-in v1.0.2 ships a stale-lock watchdog in `http_server.py`: if a command holds the main-thread lock longer than `per_command_timeout + 30s` (e.g. Fusion's native cloud SDK wedges on a slow API call), the watchdog force-releases so subsequent commands work without restarting Fusion. The wedged command is orphaned but no longer blocks everything else. - The `searchComplete` contract (see above) prevents false-negative reporting on capped/skipped searches. Always check `data.searchComplete` before telling the user "file not found". +## How this bridge is packaged + delivered (3 artifacts)++This bridge is ONE wiki page (`wiki.adom.inc/adom/adom-desktop-fusion-bridge`) that ships **three things**:++1. **The page git repo** — the ONE source of truth (all source, `skills/`, the docs, `page.json`, and the+   bridge manifest). Edit + push here.+2. **The Release zip + the bridge manifest** (`adom-bridge-fusion-manifest.json`) — what **adom-desktop**+   consumes on `bridge_install`: the manifest tells adom-desktop who this bridge is (name, version, the+   Release-zip URL, sha256, size, verb prefixes, health), and it streams that zip into its bridge cache.+3. **The adom-wiki skills pkg** (`adom-wiki pkg install adom/adom-desktop-fusion-bridge`) — **skills only**.+   It deploys these skills into a container's `~/.claude/skills/` so the AI knows how to drive this bridge+   and Fusion.++**Install handshake:** when an AI has adom-desktop install this bridge, adom-desktop installs the Release+AND tells the AI to `adom-wiki pkg install` this pkg — so the container gets all these skills. An AI can+also install the pkg itself; then the skills **auto-update** via the pkg mechanism (the goal). Full detail++ the publish ritual + the hero-relink reminder: the **`fusion-bridge-dev`** skill.+ ## Related  - **`fusion-aps-search`** + **`fusion-aps-signin`** — APS fast-search reasoning + the AI-driven one-time setup (bundled in this repo's `skills/`).

@@ -13,6 +13,48 @@ is AD's vestigial native APS, this bridge uses 8917), the add-in code AND its de the SKILL.md, the publish loop. A `fusion_*` bug is a bug in THIS repo: fix it here and republish, never as an adom-desktop discussion ask. (See the repo `CLAUDE.md`.) +## Your wiki structure: ONE page, THREE artifacts (know this cold)++You are a single wiki page (`wiki.adom.inc/adom/adom-desktop-fusion-bridge`) that ships **three distinct+things**, each with a different consumer:++1. **The page git repo — the ONE source of truth.** Everything lives here: `server.py`, `aps.py`,+   `addin/`, `handlers/`, `skills/`, the `*.md` docs, **`page.json`** (the skills-pkg manifest), and+   **`adom-bridge-fusion-manifest.json`** (the bridge manifest). Edit here, push here (+ GitHub backup).++2. **The Release (the zip) + the bridge manifest — consumed by ADOM-DESKTOP on `bridge_install`.**+   - The **Release zip** (`adom-bridge-fusion-v<ver>.zip`, uploaded via `adom-wiki release upload`) is the+     BUILT bridge (server + add-in). Binaries/zips are **Releases, NEVER git** (`*.zip` is gitignored and+     `repo push` silently skips it — see PUBLISHING.md).+   - The **bridge manifest** (`adom-bridge-fusion-manifest.json`, text, in git) tells adom-desktop **who you+     are**: name, version, the `url` pointing at the Release zip, `sha256`, `size`, verb prefixes, health+     endpoint. adom-desktop streams that zip by URL into its bridge cache and hash-verifies it.++3. **The adom-wiki pkg (`adom-wiki pkg install adom/adom-desktop-fusion-bridge`) — NOTHING BUT SKILLS.**+   It gives a user's container the skills to know how to talk to YOU and to Fusion. `page.json` is its+   manifest; `install.sh` copies the top-level `SKILL.md` + every `skills/*/` into `~/.claude/skills/`.+   **No binaries belong in this pkg** — that's what the Release is for.++### The install handshake (how a container gets your skills)+- An AI asks adom-desktop to install you → adom-desktop installs the **Release** (via the manifest) AND+  **tells the AI to `adom-wiki pkg install` your pkg** → the container gets ALL your skills.+- An AI may also `adom-wiki pkg install` you on its own. Then your skills **auto-update via the pkg+  mechanism** on every refresh. **THAT is the goal** — your skills always current, everywhere.++### The hero gets unlinked — re-check it+You have a hero we worked hard on (`screenshots/hero.png`, declared in `page.json`). **The wiki sometimes+UNLINKS it after certain updates (e.g. a `pkg publish`).** Every so often, verify `page.json` still+declares the hero and the page still shows it; **re-link it if it dropped.** TODO: file a bug to the+`adom/wiki` discussion about the hero getting unlinked on updates.++### Your STANDING JOB: document EVERY verb in skills+The skills pkg must document **absolutely every verb you support** — a **core skill** + **sub-skills** for+the extra areas. For each verb capture: what it does, **why** it exists, **when** to use it, why it's+**valuable**, and its **pitfalls**. Walk `fusion_describe` / `VERBS.md` and ensure each verb has skill+coverage. **Constantly refine and expand** — this is never "done." (Current coverage: fusion-electronics,+fusion-libraries, fusion-eagle-commands, fusion-aps-search/signin, fusion-onboarding; the full per-verb+sweep is ongoing.)+ ## How the add-in actually deploys (VERIFIED by shipping v1.5.1, 2026-06-28) Fusion loads the add-in from `%APPDATA%\Roaming\Autodesk\Autodesk Fusion[ 360]\API\AddIns\AdomBridge\`, NOT from this repo or the cache. `install_addin.py` (`_sync_directory`) copies `addin/AdomBridge` there.