Fusion - the Fusion 360 Bridge

@@ -1 +1 @@-1.9.261\ No newline at end of file+1.9.262\ No newline at end of file

@@ -5,11 +5,16 @@ Fusion, **you own and maintain this code.** You write it, version it, publish it Stop treating bridge problems as someone else's. (This file exists because an AI repeatedly forgot all of this and filed its own bridge bugs as "adom-desktop" requests. Don't.) -## You vs adom-bridge (AD) core - the boundary+## You vs adom-bridge (ab) core - the boundary -- **AD core owns:** the `adom-bridge` CLI, the relay / command passthrough, bridge lifecycle+**Naming (John, 2026-08-29):** the host app is **Adom Bridge, "ab"**. "Adom Desktop" and "AD" are the+retired names; do not use them in prose, hints, skills or issues. Identifiers such as `_ad_call`,+`ad_client.py` and the repo folder keep their old spelling on purpose (renaming buys nothing and risks+breakage).++- **ab core owns:** the `adom-bridge` CLI, the relay / command passthrough, bridge lifecycle   (`bridge_install` / streaming the bridge from the wiki into `…\bridges-cache\fusion360`), and the-  core `desktop_*` verbs. That's it. AD just **hosts and loads** this bridge.+  core `desktop_*` verbs. That's it. ab just **hosts and loads** this bridge. - **YOU (this bridge) own:** every `fusion_*` verb and its response `_hint`s, the **APS** integration   (auth/config/quota - see below), the **Fusion add-in** code AND **deploying it into Fusion**, the   `SKILL.md` + bundled `skills/`, and the edit → publish → reinstall loop.@@ -60,17 +65,17 @@ page's own issues (ab watches those).  ## Map of what you manage -- `server.py` - bridge server / verb router (talks to AD's relay, proxies to the add-in). **On start+- `server.py` - bridge server / verb router (talks to ab's relay, proxies to the add-in). **On start   it calls `install_addin()`** to deploy the add-in (see deploy below). - `aps.py` - the **entire APS** implementation: PKCE OAuth, token store, server-indexed cloud search,   never-charge cap. **All APS is yours** (the `fusion_aps_*` verbs + `fusion_search_cloud_files` /-  `fusion_walk_cloud_tree`). NOTE: port **8910 is AD's vestigial "native" APS** - NOT yours; this-  bridge uses **8917/8918/8920** and steers around it. The bare `aps_status` (8910) is that AD stub,+  `fusion_walk_cloud_tree`). NOTE: port **8910 is ab's vestigial "native" APS** - NOT yours; this+  bridge uses **8917/8918/8920** and steers around it. The bare `aps_status` (8910) is that ab stub,   not this bridge's `fusion_aps_status`. - `addin/AdomBridge/` - the add-in that runs **inside Fusion**: `AdomBridge.py`, `http_server.py`,   `commands/*.py` (cloud_documents, open_electronics_file, electronics, export, modeling,   manufacturing, screenshot, document_info, parameters, …).-- `describe.py` - the `fusion_describe` self-describe catalog (AD's Verbs tab).+- `describe.py` - the `fusion_describe` self-describe catalog (ab's Verbs tab). - `handlers/` - close / recovery / dialog-classify / UI / open_design. - `skills/` - bundled skills you ship: `fusion-aps-search`, `fusion-aps-signin`, `fusion-bridge-dev`,   `fusion-onboarding`. `resources/` - JLCPCB CAM jobs, Adom DRU rules, the layer-detect ULP.@@ -92,7 +97,7 @@ fusion_start); runOnStartup does the rest. The exact, watched-it-happen release 1. **`bridge_install {"manifestUrl": ".../adom-bridge-fusion-manifest.json"}`** - streams the new zip    into the CACHE via `method: in_place_merge`. Updates the cache ONLY; it does NOT touch Fusion's    AddIns dir. (Pass `"force": true` to re-merge when the version already bumped.)-   Do NOT manually `bridge_kill` - `bridge_install`'s own output says "AD reaps + respawns it from the+   Do NOT manually `bridge_kill` - `bridge_install`'s own output says "ab reaps + respawns it from the    new cache on the next call (no manual kill needed)," so the bridge SERVER (new server.py/describe.py)    reloads automatically on the next verb. (Running `bridge_kill` here is pointless.) 2. **`fusion_stop`** (graceful; `fusion_kill` if it is wedged) - REQUIRED. Fusion holds the add-in files@@ -101,13 +106,13 @@ fusion_start); runOnStartup does the rest. The exact, watched-it-happen release 3. Deploy the add-in into Roaming. Two ways:    - **(intended)** Run the cache's `install_addin.py`: `shell_execute` -> `cd <cache>\fusion360 &&      python install_addin.py`. It prints `Updated: commands\cloud_documents.py ...`.-   - **⚠️ TRAP (hit 2026-06-29): `python`/`py` are NOT on the box's shell PATH.** AD spawns the bridge+   - **⚠️ TRAP (hit 2026-06-29): `python`/`py` are NOT on the box's shell PATH.** ab spawns the bridge      with its OWN python, so `python install_addin.py` via `shell_execute` returns "Python was not      found" / errors with empty output (same Windows-Store-alias stub that makes a bridge fail to-     respawn). (AD >=1.9.63 PROVISIONS Python itself - a system install if one is on PATH, else a+     respawn). (ab >=1.9.63 PROVISIONS Python itself - a system install if one is on PATH, else a      portable no-UAC python-build-standalone copy under `~/.adom/adom-runtimes/python-<ver>/`, pinned      to 3.12.13 - and spawns `server.py` by ABSOLUTE PATH from it. So the bridge-SPAWN case is fully-     handled by AD; NEVER bootstrap/download your own Python. Check runtime state anytime with AD's+     handled by ab; NEVER bootstrap/download your own Python. Check runtime state anytime with ab's      `runtimes` verb (`state ∈ absent|installing|ready|failed`). But a bare `python` you invoke      yourself via `shell_execute` still won't resolve, so the file-copy deploy below remains the way.)      `cmd /c copy` and `robocopy` also fight you on the spaces in `Adom Bridge` / `Autodesk

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "fusion360",-  "version": "1.9.261",-  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.261/adom-bridge-fusion-v1.9.261.zip",-  "sha256": "266bcc4dc5a62f4dd5a72da0a08315b74365c31eb73b3f9e079aa9ef6901c079",-  "size": 554558,+  "version": "1.9.262",+  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.262/adom-bridge-fusion-v1.9.262.zip",+  "sha256": "322d4aee01e4522fed0ce6adeda757b7b353142b4435f10536118d428ba164b0",+  "size": 554511,   "verbPrefixes": [     "fusion_"   ],

@@ -45,12 +45,12 @@ APS_BASE = "https://developer.api.autodesk.com" AUTH_URL = f"{APS_BASE}/authentication/v2/authorize" TOKEN_URL = f"{APS_BASE}/authentication/v2/token" -# Fixed callback — MUST match the registered APS app exactly. 8910 is AD-native+# Fixed callback — MUST match the registered APS app exactly. 8910 is ab-native # APS's port; the bridge uses its own so the two never collide. # Fixed callback ports — tried in order at sign-in; the FIRST free one is bound. # All of these (× localhost AND 127.0.0.1) are registered on the APS app, so a # port collision on any user's machine just falls through to the next — no failed-# sign-ins. 8917 avoids AD's own APS on 8910; all verified free + outside Windows'+# sign-ins. 8917 avoids ab's own APS on 8910; all verified free + outside Windows' # reserved/excluded ranges (5357, 27339, 50000-50059) on a real box. REDIRECT_PORTS = [8917, 8918, 8920] REDIRECT_PATH = "/fusion-aps/callback"@@ -84,7 +84,7 @@ APS_REQUIRED_HINT = (     "⛔ NEVER enumerate cloud files via app.data (dataProjects/dataFiles) in fusion_run_modeling_script: "     "the DEPRECATED method holds Fusion's main thread for minutes, times out, and locks the app. "     "AUTO-RECOVER APS instead: (1) NOT configured? The org Client ID is a PUBLIC PKCE id - pull it from a "-    "peer that has it: read ~/.adom/fusion-aps/config.json (key 'client_id') off another AD desktop (adom-"+    "peer that has it: read ~/.adom/fusion-aps/config.json (key 'client_id') off another ab desktop (adom-"     "desktop status lists them) via shell_execute/pull_file, then fusion_aps_set_client_id {clientId}. "     "(2) fusion_aps_signin -> open the returned authUrl in the user's REAL browser with a warm Autodesk "     "session; INSTALL + USE the adom-browser-extension (nbrowser/ABE, https://wiki.adom.inc/adom/adom-"@@ -252,7 +252,7 @@ _ABE_UPSELL = ("OPTIONAL, offer it: installing the Adom browser extension lets m   def _ad(verb: str, args: dict, timeout: int = 60) -> dict:-    """Call an AD verb from aps.py. Lazy-imports server (which imports us) so there is no+    """Call an ab verb from aps.py. Lazy-imports server (which imports us) so there is no     circular import at module load. Never raises."""     try:         import server as _s@@ -793,7 +793,7 @@ def _aps_user_info() -> dict:   def handle_status(args: dict) -> dict:-    # NOTE: AD's relay only forwards output/data/success/error/_hint to the+    # NOTE: ab's relay only forwards output/data/success/error/_hint to the     # cloud caller — every structured field MUST live under `data`.     client_id = get_client_id()     tok = _load_tokens()

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "fusion360",   "displayName": "Autodesk Fusion 360",-  "version": "1.9.261",+  "version": "1.9.262",   "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.",

@@ -4,7 +4,7 @@ version = 4  [[package]] name = "fusion-dashboard"-version = "1.9.261"+version = "1.9.262" dependencies = [  "serde_json", ]

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

@@ -1,9 +1,9 @@-"""fusion_describe — self-describe the bridge's verb surface for Adom Desktop.+"""fusion_describe — self-describe the bridge's verb surface for Adom Bridge. -AD v1.9.23+ added a Verbs tab to each bridge's detail pop-out (lists verbs,-expands each for its I/O + timeout + status schema, with an inline runner). AD+ab v1.9.23+ added a Verbs tab to each bridge's detail pop-out (lists verbs,+expands each for its I/O + timeout + status schema, with an inline runner). ab does NOT hardcode a cloud-owned bridge's verbs, so the bridge must self-describe.-AD POSTs {command:"describe", args:{}} and caches the result at ~/.adom/bridge-verbs/.+ab POSTs {command:"describe", args:{}} and caches the result at ~/.adom/bridge-verbs/.  Each entry: name, summary, input, output, timeoutSeconds, statusVerb, longRunning, example. Keep this in step with the actual handlers as verbs are added.@@ -27,7 +27,7 @@ _T = [      {"hwnd": "required int (the dialog window)"}, {"success": "bool"}, 30, None, False, {"hwnd": 123456}),     ("fusion_get_app_state", "Current app state: running, active document, workspace, isElectronics. The poll/status verb for long-running calls.",      {}, {"activeDocument": "str", "activeWorkspace": "str", "isElectronics": "bool"}, 20, None, False, {}),-    ("fusion_readiness", "FAST readiness check (does NOT launch Fusion): is the Fusion host app installed + running + the bridge ready to drive? AD DETECTS Fusion (never installs it) via bridge.json 'detect', and auto-installs Python if missing (AD >=1.9.47). Call this before driving Fusion; if installed-but-not-running, fusion_start. SELF-HEALS the seat/licensing dialog (background UIA + screenshot-verify) whenever it detects one. Pairs with AD's bridge_readiness.",+    ("fusion_readiness", "FAST readiness check (does NOT launch Fusion): is the Fusion host app installed + running + the bridge ready to drive? ab DETECTS Fusion (never installs it) via bridge.json 'detect', and auto-installs Python if missing (ab >=1.9.47). Call this before driving Fusion; if installed-but-not-running, fusion_start. SELF-HEALS the seat/licensing dialog (background UIA + screenshot-verify) whenever it detects one. Pairs with ab's bridge_readiness.",      {}, {"installed": "bool", "running": "bool", "ready": "bool", "hostApp": "str", "bridgeVersion": "str"}, 15, None, False, {}),      ("fusion_new_electronics_from_eagle", "Import a legacy EAGLE .sch (+ paired .brd) into a NEW Fusion electronics design so the parts INSTANTIATE (schematic + populated board, lands in the PCB editor). The ONLY way to author a board from EAGLE source: Document.newDesignFromLocal opens the schematic editor but does NOT instantiate parts, and the Fusion-native .fsch/.fbrd container is opaque binary you can't build offline. This fires Fusion's own ImportSCHAndBRDCmd and drives BOTH native Open dialogs (the .sch then the .brd) in the BACKGROUND via desktop_ui_click by accessible name (no foreground). Stage both files to Windows first (send_files). After: fusion_show_2d_board, RATSNEST + 'AUTO ;' to autoroute, fusion_show_3d_board for 3D.",@@ -35,7 +35,7 @@ _T = [      {"success": "bool", "imported": "list"}, 200, None, False,      {"schPath": "C:/Users/me/adom-lib/MyBoard.sch", "brdPath": "C:/Users/me/adom-lib/MyBoard.brd"}), -    ("fusion_notify_owner", "LAST-RESORT human escalation: toast the user's MAIN computer (fans out cross-AD to every peer on the relay, so it reaches them even when this bridge runs on an unattended VM). ONLY for true human walls - password/2FA entry, UAC elevation, a physical step. Exhaust programmatic options first (UIA background clicks, seat auto-resolve, warm-SSO sign-in). After sending, WAIT and poll fusion_readiness; do not re-toast within a few minutes.",+    ("fusion_notify_owner", "LAST-RESORT human escalation: toast the user's MAIN computer (fans out cross-ab to every peer on the relay, so it reaches them even when this bridge runs on an unattended VM). ONLY for true human walls - password/2FA entry, UAC elevation, a physical step. Exhaust programmatic options first (UIA background clicks, seat auto-resolve, warm-SSO sign-in). After sending, WAIT and poll fusion_readiness; do not re-toast within a few minutes.",      {"title": "optional str", "body": "required str", "level": "optional str info|warning|error"},      {"success": "bool", "targets": "list"}, 20, None, False,      {"title": "Fusion needs you", "body": "Please complete the Autodesk 2FA prompt on winvm - everything else is done."}),@@ -138,7 +138,7 @@ _T = [     ("fusion_attach_3d_package", "LOW-LEVEL primitive: attaches ONE model to ONE package. Prefer fusion_create_library with parts[]. Attach a real 3D chip model to a library package, end to end: opens the .lbr (library active), runs Electron.Create3DPackage to enter the Package3DEnvironment showing the footprint, imports the STEP + auto-orients it flat on the footprint, then executes Package3DStop (FINISH). This BINDS the 3D onto the deviceset (Content Manager shows the 3D nested under the package; the Packages 'Package' column flips Placeholder->part-name). ONE desktop-side step remains: Fusion pops a modal Save dialog (an OWNED popup) - the response _hint gives the exact desktop_ui_click to confirm it. AFTER: re-grab desktop_screenshot_window and check ownedPopupCount for errors; the 3D preview LAGS a beat before showing the real chip. Both paths (filePath/modelPath) are WINDOWS paths - stage from the container first.",      {"filePath": "required str (.lbr WINDOWS path C:/...)", "modelPath": "required str (.step WINDOWS path C:/...)", "packageName": "optional str"},      {"success": "bool", "savePending": "bool", "data": "{steps}", "_hint": "the Save-dialog click + verify steps"}, 240, _STATUS, True, {"filePath": "C:/Users/<user>/adom-lib/ADS8588SIPM.fusion.lbr", "modelPath": "C:/Users/<user>/adom-lib/ADS8588SIPM.step", "packageName": "ADS8588SIPM"}),-    ("fusion_install_fusion", "Install Fusion 360 FOR the user - downloads Autodesk's official Client Downloader and streams the free trial silently, with NO shell_execute and NO AD approval gate (runs inside the trusted bridge). Elevation-aware: --globalinstall when admin, PER-USER otherwise (a non-elevated globalinstall dies silently on UAC - learned live). Returns promptly; poll fusion_readiness (reports installing:true) until installed:true, then fusion_start. Declared as detect.installVerb so AD's bridge_readiness recommends it.",+    ("fusion_install_fusion", "Install Fusion 360 FOR the user - downloads Autodesk's official Client Downloader and streams the free trial silently, with NO shell_execute and NO ab approval gate (runs inside the trusted bridge). Elevation-aware: --globalinstall when admin, PER-USER otherwise (a non-elevated globalinstall dies silently on UAC - learned live). Returns promptly; poll fusion_readiness (reports installing:true) until installed:true, then fusion_start. Declared as detect.installVerb so ab's bridge_readiness recommends it.",      {}, {"success": "bool", "installing": "bool", "alreadyInstalled": "bool?", "mode": "globalinstall|per-user", "statusVerb": "str"}, 90, _STATUS, True, {}),     ("fusion_generate_package", "Generate an IPC-7351-compliant parametric 3D package via Fusion's BUILT-IN ElectronicsPackageGenerator (EPG) - ~50 package families (chip/soic/qfn/qfp/bga/sot23/dfn/melf/ecap/crystal/headers/...), each a few seconds, ZERO GUI. Optionally LASER-ETCH a marking (MPN / '103') into the body top as REAL cut geometry (survives STEP), and export STEP in the same call - the royalty-free, license-clean path to a whole component library (our own generated output, not vendor models). Proven live: 0603 + '103' etch + STEP in ~2s.",      {"type": "required str (EPG family, e.g. chip|soic|qfn|qfp|bga|sot23|dfn2|melf|ecap|crystal|header_straight - see supportedTypes in the error for the full list)", "params": "optional dict (generator dims in MM by default, e.g. chip: {D,E,A,L,L1}; soic: {A,A1,b,D,E,E1,e,L,DPins}; omitted keys use EPG defaults)", "unitsCm": "optional bool (params already EPG-native cm)", "etch": "optional str (marking text on the chip top: MPN / '103'; multi-line with newline, e.g. MPN+variant - laid along the LONGEST face axis)", "etchStyle": "optional str raised|engraved (default raised = thin WHITE positive extrude, silkscreen-style contrast; engraved = sunken cut)", "etchDepthMm": "optional float (marking height/depth, default 0.03)", "etchHeightMm": "optional float (text height; default auto-fit: top-5%-band face, 10% margin, width-aware)", "outputStep": "optional str (WINDOWS path; exports STEP incl. the marking)"},@@ -182,7 +182,7 @@ _T = [     ("fusion_import_step", "Import a STEP/.stp (or other native-importable) file into a NEW Fusion design via the native import API. The open-electronics hints redirect .step here. (Was implemented but missing from this catalog until the verb suite's reverse-drift check caught it, 2026-08-14.)", {"filePath": "required str (WINDOWS path C:/...; stage from container first)"}, {"success": "bool", "documentName": "str"}, 300, None, True, {"filePath": "C:/Temp/part.step"}),      # ── Catalog completion (2026-08-14): 14 verbs that were LIVE but undescribed, caught by-    # the verb suite's reverse drift check. An undescribed verb is invisible to AD's Verbs+    # the verb suite's reverse drift check. An undescribed verb is invisible to ab's Verbs     # tab and to every caller reading fusion_describe - never let these drift again.     ("fusion_open_cloud_file", "Open a CLOUD file by name (the front door to every design flow). PCB/ELECTRONICS NAV RULE: open the electronics DESIGN document (EcadDesignProductType), never a child .brd/.sch/3D directly - then switch views with fusion_show_schematic / fusion_show_2d_board / fusion_show_3d_board. LONG-RUNNING: fire it, then poll fusion_get_app_state until activeDocument matches (cloud opens on electronics designs take 1-3 min). A crash-recovery modal can block the open - fusion_dismiss_blocking_dialogs.", {"fileName": "required str", "projectName": "optional str (defaults to active project)", "folderPath": "optional str"}, {"success": "bool", "documentName": "str"}, 240, "fusion_get_app_state", True, {"fileName": "BQ25792", "projectName": "Main"}),     ("fusion_open_design", "Open a LOCAL design file (routes through the add-in import). Prefer cloud flows (fusion_open_cloud_file) for team designs; this is for local .f3d/.step style files.", {"filePath": "required str (WINDOWS path)"}, {"success": "bool"}, 240, None, True, {"filePath": "C:/Temp/part.f3d"}),@@ -296,7 +296,7 @@ _T = [      60, None, False, {"dryRun": True}),      # ── Self-describe ──────────────────────────────────────────────────────-    ("fusion_describe", "Self-describe every verb the bridge exposes (this list) for AD's Verbs tab + runner.",+    ("fusion_describe", "Self-describe every verb the bridge exposes (this list) for ab's Verbs tab + runner.",      {}, {"success": "bool", "verbs": "[{name,summary,input,output,timeoutSeconds,statusVerb,longRunning,example}]"}, 20, None, False, {}), ] @@ -321,8 +321,8 @@ def _verbs():  def handle_describe(args: dict) -> dict:     verbs = _verbs()-    # `verbs` at the TOP LEVEL is what AD's Verbs tab reads from the raw /command-    # response. AD's relay strips non-standard top-level fields on the CLI proxy+    # `verbs` at the TOP LEVEL is what ab's Verbs tab reads from the raw /command+    # response. ab's relay strips non-standard top-level fields on the CLI proxy     # path, so we ALSO nest under `data` (which the relay forwards) for CLI/debug.     return {         "success": True,

@@ -72,7 +72,7 @@ _callbacks = [] # Guard windll so this module imports on non-Windows hosts (galliaApril smoke # tests, macOS). The Win32-only functions below are never reached off-Windows — # detect_fusion() short-circuits to installed:False — but the bridge must still-# boot + serve /status on any platform AD spawns it on.+# boot + serve /status on any platform ab spawns it on. user32 = ctypes.windll.user32 if hasattr(ctypes, "windll") else None  @@ -332,7 +332,7 @@ def _has_fusion_process() -> bool:         creationflags = 0x08000000 if hasattr(subprocess, "CREATE_NO_WINDOW") else 0         if hasattr(subprocess, "CREATE_NO_WINDOW"):             creationflags = subprocess.CREATE_NO_WINDOW-        # stdin=DEVNULL is load-bearing: AD spawns the bridge console-less ++        # stdin=DEVNULL is load-bearing: ab spawns the bridge console-less +         # detached, so the inherited stdin handle is invalid. Without an explicit         # DEVNULL, this child can block on a dead handle and deadlock the probe —         # the exact failure mode that bit the KiCad bridge.@@ -786,7 +786,7 @@ def _popen_fusion_background(exe_path: str):     ⚠ THE #50 ROOT CAUSE (proven by process parentage on AdomLapper, 2026-08-23):     Fusion360.exe <- FusionLauncher.exe <- python (this bridge) <- adom-bridge.exe.     Fusion was a CHILD of the bridge, so every bridge reap - each `bridge_install` of a-    release, AD's supervisor respawn (adom-bridge #61), the idle reaper - killed Fusion+    release, ab's supervisor respawn (adom-bridge #61), the idle reaper - killed Fusion     with it. Seven releases shipped during a 20-part build matrix = seven dead Fusions,     every one mid-chain, every one a 'clean exit' with no crash artifact. @@ -1139,7 +1139,7 @@ def ensure_fusion_running(fusion_info: dict, wait_addin: bool = False) -> dict |         _set_min_animate(0)         # Launch MINIMIZED + NOT ACTIVATED (STARTUPINFO). DEVNULL on all three std         # streams + CREATE_NO_WINDOW: the bridge is a detached, console-less child of-        # AD, so inherited handles are invalid.+        # ab, so inherited handles are invalid.         _popen_fusion_background(exe_path)         # Reactive backstop via the refcounted envelope (minimize mode: splash/seat         # windows vanish rather than being demoted). The envelope restores the user's

@@ -6,8 +6,8 @@ glance; the same signal belongs on FUSION's button whenever this bridge drives i THE LESSON (stolen from pup, who paid for it first - src/server.js): an in-bridge ITaskbarList3::SetOverlayIcon is IN-PROCESS-ONLY. The COM call returns S_OK cross-process and the shell silently ignores it (verified live here too: badge never-rendered). The working path is AD-core's `desktop_taskbar` verb (AD >=1.9.106): hand-it the badge PNG as base64 and AD paints the overlay natively, cross-process.+rendered). The working path is AD-core's `desktop_taskbar` verb (ab >=1.9.106): hand+it the badge PNG as base64 and ab paints the overlay natively, cross-process.      set:   desktop_taskbar {hwnd, overlay: {icon: <b64 png>, tooltip}}     clear: desktop_taskbar {hwnd, overlay: {badge: "none"}}

@@ -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.261"+DASH_VERSION="1.9.262" 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

@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.261",+  "version": "1.9.262",   "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.261",+  "version": "1.9.262",   "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",@@ -75,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.",@@ -104,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+  ]+}

@@ -11,7 +11,7 @@ part is Autodesk's **email OTP**, which **expires fast** — the user may walk a cup of coffee"), so you must **monitor** the flow and turn the code around in seconds.  All browser steps use the native-browser extension verbs (`nbrowser_*`) against the-AD-connected laptop: `adom-bridge --target <laptop> nbrowser_* '{...}'`.+ab-connected laptop: `adom-bridge --target <laptop> nbrowser_* '{...}'`.  ## Working principles (non-negotiable) @@ -39,7 +39,7 @@ AD-connected laptop: `adom-bridge --target <laptop> nbrowser_* '{...}'`.    `sessionId`** in every `nbrowser_eval/type/click`. The extension **refuses to drive PWA /    installed-app windows** (e.g. "Hydrogen - Chat") and `nbrowser_eval` defaults to the    foreground tab — which is often the wrong (PWA) window.-4. **Foreground it with `desktop_bring_to_front`** (the AD verb) so the user can see/act on+4. **Foreground it with `desktop_bring_to_front`** (the ab verb) so the user can see/act on    the login. `nbrowser_focus_window` is NOT implemented. 5. **Proactively use adom-google.** Autodesk emails the OTP — you can read it via the    `adom-google` Gmail API passthrough. If adom-google isn't set up, TELL the user it exists@@ -285,7 +285,7 @@ This whole flow was driven live and works. Replicate it per org: 3. The bridge's **monthly hard cap** (fails closed). Card on file = identity verification only.  ## Port choice for the callback-Check availability LIVE on the box (no AD verb exists): `python` bind-test on 127.0.0.1 ++Check availability LIVE on the box (no ab verb exists): `python` bind-test on 127.0.0.1 + `netsh int ipv4 show excludedportrange protocol=tcp`. 8917/8918/8920 verified free + outside Windows reserved ranges (5357, 27339, 50000-50059). The box runs ~67 listeners — don't assume. 

@@ -63,7 +63,7 @@ On the Autodesk sign-in page (`signin.autodesk.com/?flowId=...`): click **"Conti ## Step 5 — Escalate the secret step (never type it) `fusion_notify_owner {title:"Fusion sign-in needs you", body:"On <box> Fusion is at the Google password step for <email>. Please enter your password/2FA in the open browser; I'll finish once-you're in."}`. It toasts the user's MAIN computer, fanning out cross-AD so it reaches them even though+you're in."}`. It toasts the user's MAIN computer, fanning out cross-ab so it reaches them even though this bridge runs on an unattended VM. Then WAIT and poll `fusion_readiness`; do not re-toast for a few minutes. (The user may instead remote into the box and type it — either way you take over after.) 

@@ -95,13 +95,13 @@ ways to get the array, in order of preference:    enforces this" below.) 2. **`fusion_screenshot_all`** - captures the main window PLUS every Qt dialog window as separate    shots, and returns the list of saved paths. Read each.-3. **`desktop_screenshot_window {"hwnd": <fusion-hwnd>}`** (AD core) - returns `screenshots[]` and+3. **`desktop_screenshot_window {"hwnd": <fusion-hwnd>}`** (ab core) - returns `screenshots[]` and    **`ownedPopupCount`**. `ownedPopupCount > 0` means dialogs are stacked on the window. Read the    shots. Get the hwnd from `fusion_window_info` (its `hwnd` field) or `desktop_find_window    {"titleContains":"Autodesk Fusion"}`.  **To actually SEE a shot - mind WHERE it lands:**-- AD core `desktop_screenshot_window {hwnd}` saves the PNG **into your container** (e.g.+- ab core `desktop_screenshot_window {hwnd}` saves the PNG **into your container** (e.g.   `/tmp/adom-desktop-screenshots/`) - Read it directly. - The bridge's own captures (the auto `dialogArray[].screenshot` paths and `fusion_screenshot_all`)   are saved on the **Windows box** (`C:/tmp/conduit-screenshots/`). To see one, either re-capture that

@@ -87,7 +87,7 @@ pipeline: anchor to MP pins -> optional silk bake -> gold pins -> dedup/flatten/ prune -> Draco), so the same board comes out **~465 KB / ~31 draw calls, auto-anchored**. ALWAYS use this for a component page's `component.parts.model_3d` - never a raw STEP->GLB. -Two verbs, because a big board tessellates for minutes (longer than the AD relay's ~60s+Two verbs, because a big board tessellates for minutes (longer than the ab relay's ~60s request timeout), so it is submit-then-poll, never one long blocking call:  ```

@@ -103,7 +103,7 @@ Two things bite after the profile fix works: ## ⭐ THE PROVEN APPROACH (John's directive, 2026-08-22) - DO NOT over-automate this  After hours of trying to fully automate the desktop sign-in, John's ruling is: **trigger the sign-in,-then put up an AD CAPTION asking the USER to complete it in the browser window that just opened, and+then put up an ab CAPTION asking the USER to complete it in the browser window that just opened, and STOP. Do not try to automate the browser-side auth or the protocol handoff.** The exact flow:  1. **If switching accounts:** sign the current user out first (reset the shared Autodesk identity, see@@ -117,7 +117,7 @@ STOP. Do not try to automate the browser-side auth or the protocol handoff.** Th 3. **Detect the browser auth window** (you CAN): `Get-Process chrome|msedge | Where MainWindowTitle -match    "Sign in - Autodesk"` gives its hwnd, and `nbrowser_list_tabs {profile}` shows which profile+tab holds    the `signin.autodesk.com` flow.-4. **Put an AD caption on that browser window asking the user to finish**, then poll and STOP automating:+4. **Put an ab caption on that browser window asking the user to finish**, then poll and STOP automating:    `desktop_caption {hwnd:<auth window>, text:"Please finish signing in as <email> here", subtext:"Adom    will detect when it completes"}`. Do NOT drive the page, do NOT reopen the flow elsewhere, do NOT click    the protocol dialog. John completes it by hand.

@@ -15,18 +15,18 @@ All laptop steps run via `adom-bridge --target <laptop> shell_execute` / `run_sc `send_files`. Drive the user's own machine; don't ask them to do steps you can do.  ## Step 0 — Check readiness (fast, never launches Fusion)-Call **`fusion_readiness`** (or AD's **`bridge_readiness`**) FIRST - it reports `installed` / `running`+Call **`fusion_readiness`** (or ab's **`bridge_readiness`**) FIRST - it reports `installed` / `running` / `ready` without launching anything: - `installed:false` → onboard (the steps below). - `installed:true, running:false` → **no onboarding needed**, just `fusion_start`, then drive. - `ready:true` → drive Fusion directly. -NOTE (AD >=1.9.63): AD **DETECTS** the Fusion host app (via the bridge.json `detect` block - the+NOTE (ab >=1.9.63): ab **DETECTS** the Fusion host app (via the bridge.json `detect` block - the `%LOCALAPPDATA%\Autodesk\webdeploy\production\*\FusionLauncher.exe` path) but **NEVER installs it** --Fusion is the user's host app. AD also **provisions Python itself** - a system install if one is on+Fusion is the user's host app. ab also **provisions Python itself** - a system install if one is on PATH, else a portable, no-UAC python-build-standalone copy (pinned 3.12.13) under `~/.adom/adom-runtimes/` - and spawns the bridge from it by absolute path. So **never** download or-bootstrap Python here; the user sees no UAC prompt for a runtime (check state with AD's `runtimes`+bootstrap Python here; the user sees no UAC prompt for a runtime (check state with ab's `runtimes` verb). Onboarding is only about Fusion itself + the Autodesk login + deploying the add-in.  ## Step 1 — Download the Fusion installer@@ -99,11 +99,11 @@ auth tab must be in nbrowser's window; if Fusion opened a different Edge window, path above.  > **NOTIFY only when you truly can't proceed.** The sign-in is something you should AUTOMATE, not-> punt. Reserve an AD **`notify_user`** toast for a genuine wall (a UAC/elevation prompt, a+> punt. Reserve an ab **`notify_user`** toast for a genuine wall (a UAC/elevation prompt, a > `--globalinstall` consent, license acceptance, or a 2FA/password step you must not auto-fill).-> As of **AD 1.9.84** `notify_user` works directly over the bridge's direct API — you don't relay a+> As of **ab 1.9.84** `notify_user` works directly over the bridge's direct API — you don't relay a > payload to the AI anymore. **If the bridge runs UNATTENDED (e.g. on a VM) and the user is on-> another machine, add a cross-AD `target`** (a peer clientName from the `targets` verb, or `"all"`)+> another machine, add a cross-ab `target`** (a peer clientName from the `targets` verb, or `"all"`) > so the toast lands where they actually are. The bridge already fires this itself for a seat/ > licensing DECISION dialog (a true wall) — see `notifyDelivered` in the launch response.