← Commit history

v1.6.39: dev skill core-goal (AI runs everything, never punt to user)

John Lauer ·25c1d414cc ·3mo ago ·parent dd0feba
5 files changed +38−7
BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.6.38\ No newline at end of file+1.6.39\ No newline at end of file
CHANGELOG.md+8
@@ -3,6 +3,14 @@ All notable changes to the Adom Desktop Fusion 360 bridge, newest first. Canonical: https://wiki.adom.inc/adom/adom-desktop-fusion-bridge · GitHub backup: `adom-inc/adom-desktop-fusion-bridge` +## 1.6.39 - 2026-07-06++- **Dev skill: added THE CORE GOAL** (John) - the entire reason this bridge exists is for the AI to+  run EVERYTHING so the user never does anything manual. Never ask the user to click/close/sign-in;+  the only acceptable walls are UAC/elevation and a password/2FA we must not enter. Any flow that+  still needs the user is the next bug to fix in the bridge, not the user's job. Reinforces detecting+  + handling state deterministically in code, not via the AI following skills.+ ## 1.6.38 - 2026-07-06  - **Deterministic, process-based detection of the seat/licensing dialog** (John: track state in CODE,
adom-bridge-fusion-manifest.json+5−5
@@ -1,13 +1,13 @@ {   "manifest_version": 1,   "name": "fusion360",-  "version": "1.6.38",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-fusion-bridge/1.6.38/adom-bridge-fusion-v1.6.38.zip",-  "sha256": "9d224d1ce06beffb8962bcb69df6a6389e60b16f2b2bbf9e73c1a357311a0840",-  "size": 339225,+  "version": "1.6.39",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-fusion-bridge/1.6.39/adom-bridge-fusion-v1.6.39.zip",+  "sha256": "5df9ca5388a850cd77291bd4fba74e2124205e36b492a0e1fa2f736de436ca4e",+  "size": 340095,   "verbPrefixes": [     "fusion_"   ],   "healthEndpoint": "/status",-  "released_at": "2026-07-06T12:09:09Z"+  "released_at": "2026-07-06T12:17:21Z" }
bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "fusion360",   "displayName": "Autodesk Fusion 360",-  "version": "1.6.38",+  "version": "1.6.39",   "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/adom-desktop-fusion-bridge",   "author": "Adom Inc.",
skills/fusion-bridge-dev/SKILL.md+23
@@ -5,6 +5,29 @@ description: How to develop, version, and PUBLISH the Adom Desktop Fusion 360 br  # Fusion bridge — dev + publish workflow +## ★ THE CORE GOAL: the AI runs EVERYTHING so the user never has to (why this bridge exists)++The entire reason adom-desktop and its bridges exist is so that **the AI drives the whole flow+end to end and the user does nothing manual** (John, 2026-07-06). This bridge is a FAILURE any time+it punts a step back to the user. That means the code + verbs must automate, on their own:+**install → launch (background) → Autodesk sign-in → seat/licensing conflicts → every startup dialog+→ recovery/update prompts → the actual work (open/model/export).**++- **NEVER ask the user to do something manually** - not "click Continue", not "sign in yourself",+  not "close that dialog". The ONLY acceptable exceptions are a true hard wall the OS forbids us to+  cross: a **UAC/elevation** prompt, or a **password/2FA** you must not enter for them. Everything+  else you AUTOMATE. If you catch yourself about to ask the user to click/close/choose something,+  that is a bug in this bridge - fix the bridge so it does it.+- **Detect and handle state in CODE, deterministically** - do NOT rely on the AI noticing a dialog+  and following a skill (the AI is unreliable at that). Hard signals (add-in round-trip, owning+  process, window size, `family_windows()`), not titles or vibes. See the background-launch state+  machine + `find_licensing_dialog()`.+- When something can't yet be fully automated (e.g. a browser OAuth handoff), the goal is still to+  push automation as far as it goes and shrink the manual part to zero over time - not to hand it back.++Hold every change to this bar: does it move the bridge toward "the user does nothing"? If a flow+still needs the user, that's the next thing to fix, not the user's job.+ ## ⛔ Background-launch invariant: NEVER steal the user's foreground (HARD RULE)  The bridge runs on a machine the **user is actively working on**. Anything this bridge launches or