Fusion - the Fusion 360 Bridge

@@ -132,6 +132,17 @@ Not the janitor three minutes later. Not the next open tripping over it. Inside The janitor and the sentinel remain as BACKSTOPS for docs dirtied by crashed runs or other routes - but if they ever fire for a live verb's document, that verb has a bug. +### Closes must wait for the Hub upload to drain (John caught it live, 2026-08-21)++Create3DPackage / cloud saveAs uploads continue AFTER the API call returns. A close issued+while they run raises "Packages are being uploaded to your Fusion Hub... you will lose+these changes" - a modal that blocks the main thread AND whose default-looking button+destroys the upload. `app.hasActiveJobs` is the deterministic signal. Every bridge-issued+close (`_close_bridge_doc_verified`, prove's f3d close) polls it to False (cap 120s) BEFORE+closing, and DEFERS rather than closes when it will not drain. If the modal appears anyway,+the answer is ALWAYS No (work-preserving: cancels the close, loses nothing) - the dispatch+chokepoint auto-answers it, and the gated close retries after the drain. Never Yes.+ ## Checklist for a new verb that drives the UI  1. Can it prompt? List every dialog it could raise, then remove each cause.