Update Versions

[github-actions]

Changepacks

devup-mcp@0.9.0 → 0.10.0 - crates/devup-mcp/Cargo.toml

Minor

• Four places said work had been done that had not been, and one place made a caller chase a failure that could not be retried. devup_ui_validate reported file-placement against Next.js files whose default export the framework requires - app/layout.tsx without one is a build error, so the advice could not be taken, and because the finding is a warning it failed strict: true on a correct application; not-found.tsx collected two findings for the same reason. The page-name rule judged every component in a route file rather than the one the route renders, so a correct export default function NoticePage was reported for its own PageContent helper, and one-component-per-file then asked for that helper to be moved somewhere the file-placement rule forbids - leaving src/components/ as the only destination for a component used by one route. At a monorepo root theme_for_validation took the first devup.json the sorted scan found, so apps/front code was validated against apps/admin's theme and its real tokens came back as unknown-token errors suggesting the other package's token as the fix; it now refuses to choose and returns candidateProjectRoots naming the projectRoot that selects each. A call with neither tsx nor files validated the empty string and answered ok: true, okReason: "clean" about code never sent, and is now refused; clean itself is split so clean-unverified-tokens says a $token reference existed but no theme was resolved to check it against. Tokens inside css()/globalCss()/keyframes() were invisible to the token check, so an unknown one there passed in silence. On the Figma side a Section whose candidate menu exceeded the plugin transport was refused outright, returning nothing for a menu that was merely long and reproducing the same refusal on every retry because the ceiling follows the Section's size; it now surrenders text previews first, then shortens from the end under the same projectionTruncated the traversal and candidate caps already raise, and allScreens still refuses a truncated index rather than pretending to be whole. Of the twenty-five codes the plugin scripts throw only two carry a JSON payload, so the rest arrived as pluginCode: null with generic advice; the code is now read from the message for all of them, and the two that name a caller-fixable condition are mapped - a missing node or page reached callers as -32603 INTERNAL_ERROR when the README promises the JSON-RPC code alone separates "fix the arguments" from "stop and report", which is the most common mistake there is. The placement contract now carries the collected parent's fill, because learning that the desktop frame behind an app screen was #E6EDE6 otherwise took a second Figma acquisition for a colour the capture already held. Finally, a new self_update module keeps the binary current without anyone tending it: the existing release check now fetches the published asset for the platform, proves it by running --self-check on it, and renames it into place - never touching the running image, so the stdio pipe the host already holds is never at risk, and the next start is the one that differs. It stands down where it is not the owner of its install, and reports which mechanism is in force under server.updateAvailable.autoUpdate.