Fusion - the Fusion 360 Bridge

@@ -0,0 +1,74 @@+---+name: fusion-publishing+description: DEVELOPER-only. USE WHEN publishing the fusion-bridge package, cutting a bridge release, or adding/updating a user skill - the full adom-wiki ritual and the two traps that silently strand work (skills not globbed in page.json never install for users; adompkg is DEAD). Trigger words - publish fusion bridge, cut fusion release, ship a skill, skill not installing, adompkg, adom-wiki pkg publish, release ritual, page.json files.+user-invocable: false+---++# Publishing the fusion-bridge: the adom-wiki ritual (and the two silent traps)++## ⛔ Trap 1: adompkg is DEAD. Everything is adom-wiki now.++`adompkg` and every wiki-v1/v2 slug host are deprecated and gone (John, 2026-08-23: "there is+no such thing as adompkg anymore, its all done via adom-wiki"). The old CLI may still appear+to work as a shim - do not use it. The verbs:++| Task | Command |+|---|---|+| Publish the package | `adom-wiki pkg publish` (from the repo dir) |+| Bump the manifest version | `adom-wiki pkg version` (or edit page.json+package.json in lockstep) |+| Pre-publish lint | `adom-wiki pkg lint` |+| Upload a bridge release zip | `adom-wiki release upload adom/fusion-bridge <ver> <zip> --platform windows --arch x64` |+| Push source files | `adom-wiki repo push adom/fusion-bridge --files <...> -m "<msg>"` |+| User installs | `adom-wiki pkg install adom/fusion-bridge` |++## ⛔ Trap 2: a skill in skills/ does NOT ship unless it is GLOBBED in page.json++`page.json`'s `files` array is the package content list. A user-tier skill ships ONLY if+`skills/<name>/**` appears there. This bit us live (2026-08-23): FIVE skills sat on disk and+in the wiki repo - including `fusion-autodesk-signin`, which SHIPPED skills told the agent to+load - and no user ever received them, because nobody added the globs. Writing the skill and+pushing the repo is NOT publishing it.++**The check, run it before every publish:**+```python+import json, os+fl = json.load(open('page.json'))['files']+shipped = {g.split('/')[1] for g in fl if g.startswith('skills/')}+missing = [d for d in os.listdir('skills') if d not in shipped]+print('ON DISK but NOT shipped:', missing or 'none')   # must be 'none' (or deliberate)+```++## The full release ritual (both channels, in order)++The bridge has TWO delivery channels that move together:+- **runtime zip** (server.py/add-in/handlers, listed in `tools/release-files.txt`) -> delivered+  by `bridge_install` on each box. Skills are NOT in this zip.+- **package** (SKILL.md, skills/ tier, docs, installers, per page.json `files`) -> delivered by+  `adom-wiki pkg install` / user updates. Skills ship ONLY here.++1. Edit source. `python3 -c "import ast; ast.parse(open('server.py').read())"` ++   `python3 tools/shadow_check.py server.py` (0 findings required).+2. Bump `BRIDGE_VERSION` + `bridge.json` (bridge ver) AND `page.json` + `package.json`+   (pkg ver) - they track separately but always move together in a release.+3. Build the zip from `tools/release-files.txt` (python zipfile; 59 files, MISSING must be none).+4. `adom-wiki release upload adom/fusion-bridge <bridgever> <zip> --platform windows --arch x64`+5. Update `adom-bridge-fusion-manifest.json`: version, url, sha256, size.+6. `git commit` (wiki is canonical, git is history).+7. `adom-wiki repo push adom/fusion-bridge --files <changed files> -m "..."`+8. Run the Trap-2 skill-glob check above.+9. `adom-wiki pkg publish`+10. `bridge_install {"manifestUrl":"https://wiki.adom.inc/api/v1/pages/fusion-bridge/files/adom-bridge-fusion-manifest.json","force":true}`+    - server.py changes respawn on the next verb (NO Fusion restart); add-in changes ALSO need+      the Roaming deploy with Fusion closed (see CLAUDE.md deploy section).+11. Verify the changed behavior live (call the verb, check the new field/hint).++## Skill tiers (wiki three-tier layout)++- `skills/` = USER tier: ships + installs for every user, IF globbed (Trap 2).+- `dev-skills/` = DEV tier: source-only, maintainers read it in the repo, never installs.+- `publish-skills/` = PUBLISH tier: source-only, publishing workflows.++When you write or materially update a USER skill: add the glob (if new), bump pkg version,+`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).

@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.164",+  "version": "1.9.165",   "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,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.164",+  "version": "1.9.165",   "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": {@@ -11,6 +11,10 @@     "uninstall": "./uninstall.sh"   },   "tags": [+    "ab",+    "bridge",+    "fusion",+    "desktop-app",     "fusion360",     "autodesk",     "cad",@@ -53,7 +57,11 @@     "skills/fusion-multiprofile-signin/**",     "dock.json",     "docs/img/dock-fusion.svg",-    "skills/fusion-dashboard/**"+    "skills/fusion-dashboard/**",+    "skills/fusion-dark-mode/**",+    "skills/fusion-file-search/**",+    "skills/fusion-mcp-and-preferences/**",+    "skills/fusion-web-export/**"   ],   "discovery_triggers": [     "drive fusion 360",@@ -71,7 +79,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.",@@ -100,9 +111,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