Update Versions

[github-actions]

Changepacks

devup-mcp@0.11.0 → 0.12.0 - crates/devup-mcp/Cargo.toml

Minor

• An agent asked for one screen with the Devup Bridge plugin attached and serving, was told status: "disconnected" by devup_figma_auth - a word that described only the OAuth path - and asked its user to log in. Pressing on, devup_figma_export without a url was refused as "url or artifactId is required" with no next step, so it invented /design/bridge/bridge; the plugin, which could not report its own file key, served it because it was the only one attached, and the answer reported source.kind: "direct" and the invented key as the file's. Connectivity is now path-aware: status (and the login/logout answers) report connected, activePath (bridge, direct or null), both paths with the files attached plugins have open - file name, current page and selection, which the plugin now reports on attach and on every change - and a nextAction; top-level disconnected is left only for when neither path can serve, and doctor is the same report plus reference data. With exactly one plugin attached, devup_figma_export, devup_figma_search and devup_figma_explore take no url: they read the plugin's file, export and explore start from the node selected in Figma, and frameIds without url name frames in it. figma-bridge://current[?node-id=] is the official placeholder where a link is still needed, and every link devup-mcp hands back for a file whose key is unknown uses it. With no plugin or several, the refusal carries a nextAction listing the ways forward - run the plugin, log in and pass a link, or pick one of the attached files. Answers the plugin served say source.kind: "bridge" with bridgePort, fileName, pageName and bridgeReads, and source.fileKey is only ever the key the plugin reported: null with a reason when it reported none, and a key the request carried is reported apart as requestedFileKey. A plugin that could not report its key is routed by a connection-scoped key that never reaches the direct path and never appears in an answer. Plugins are now tracked per connection, so two keyless plugins no longer collapse into one slot, with the second's registration erased when the first disconnects. login warns rather than blocks when a bridge is attached. The auth tool description, the server instructions (rule 1a) and devup://guide/usage now state the connection order: bridge, then direct.