Fusion - the Fusion 360 Bridge

@@ -481,3 +481,40 @@ Any browser window WE open for OAuth is ours to close. Do not assume the flow cl  Same discipline applies to captions: `desktop_caption` auto-clears, but if you ever pass `persist:true` YOU must hide it.++### Is there a CLI to sign Fusion in? (investigated 2026-07-22 - answer: effectively no)++John asked whether Fusion auth can be triggered from a command line instead of its GUI, which+would remove the whole click-the-Sign-In-button problem. Investigated on the real machine.++**What is actually running** (via `process_list {nameFilter}` - `commandLine` is populated there+even when `shell_execute`/`run_script` are dead, which is how this was found):++```+IdentityService.exe+IdentityUpdateService.exe+AdskIdentityManager.exe --process_name Autodesk.IDSDK.DefaultProcess-v2 \+                        --server_name  Autodesk.IDSDK.DefaultServer-v2+   (in <webdeploy>/production/<hash>/Autodesk Identity Manager/)+Fusion360.exe          (in <webdeploy>/production/<hash>/)+FusionLauncher.exe+```++**Conclusion: no.** `AdskIdentityManager.exe` DOES take flags, but they are **plumbing, not auth+commands**: they name the IPC channel (`--process_name` / `--server_name`) that the Identity SDK+broker listens on. It is a long-running local IPC server; Fusion is its CLIENT and asks it to do+the login over that channel. There is no `--login` / `--user` / `--token` surface, and the+resulting tokens go into a DPAPI-encrypted store (app entropy), so you cannot write one in either.++**What IS command-line reachable: the last mile.** The `autodesk://` protocol handler is what+returns the token to a waiting Fusion, and protocol handlers are invocable by URL. So the final+browser click ("Open Product") is in principle replaceable by firing the `autodesk://` callback+directly. NOT yet verified live - do not claim it works until someone tests it.++**So the practical answer stays: drive the GUI, but drive it in the BACKGROUND.** Fusion's Sign In+button is UIA-invokable, so no foreground is needed anyway (see the sign-in section above). That+already solves the annoyance a CLI would have solved.++**Bonus finding:** two `webdeploy/production/<hash>` dirs were live at once - `Fusion360.exe` from+one hash and `FusionLauncher.exe` from another. Per this repo's own notes Fusion NEVER prunes old+builds, so a dir count is NOT an update signal. Use `fusion_update_in_progress()`.