[github-actions]

Changepacks

devup-mcp@0.20.1 → 0.21.0 - Cargo.toml

Minor

• Offer /devup-retro when devup-mcp work is complete: the final completion report ends with one question in the user's language ("작업이 완료되었습니다. 지금까지 진행한 내용을 개선하기 위해 /devup-retro 를 실행할까요?"). The rule is contract identifier offer-devup-retro-in-final-report (developmentContract v5) and is stated in delivery-quality, the devfive-frontend, devup and devup-implementation-plan skills and the usage guide; results that mark completion (runtime-audit completion reportAllowed, screen-plan status reportAllowed, stack-diff zero drift on every layer) carry nextSuggestedAction with the ready message and the invocation that works in the workspace. Never on intermediate or failing results, never run unasked.
• Add the /devup-retro command: a session retrospective that lists the follow-up prompts the user had to write after devup-mcp's work, classifies each by the surface that should have prevented it, asks the user to confirm, and then prints ready-to-paste improvement prompts (optionally saved as .feedback records). Ships as the devup-retro skill (Claude Code /devup-retro, OpenCode command file), as an MCP prompt of the same name for workspaces without the skill, and with a read-only devup_skills action retro that returns the installed build, this process's devup-mcp call log with timestamps, the surface list and the .feedback folder state.
• Make restrained entrance/transition motion a default delivery item (animation reference, contract, entrance-motion validation rules, reveal re-entry audit), accept same-file static consts such as keyframes names in css()/globalCss()/keyframes(), and validate tokens per app against the nearest devup.json while reporting unresolved files as unverified. Reveal audits also measure trigger position and opt-in fast-scroll, reload, history, image, focus and progress-sync scenarios; the shipped motion runtime no longer hides content already on screen; a located sourceName selects the theme for a single tsx.
• Entrance and transition motion is now Devup UI static keyframes instead of a script-driven or framer-motion entrance: exports ship Reveal.tsx (keyframes on a view timeline, with staggered groups and progress lines), the shared motion runtime only marks state for browsers without view timelines, and the animation guide, contract and behaviorPlan name the keyframes form. devup_ui_validate reads keyframes and CSS scroll-timeline usage in every entrance rule (ssr-hidden-reveal, reveal-replays, reveal-moves-background, stagger-too-long, motion-without-reduced-motion) and adds entrance-uses-motion-library, entrance-on-static-content and entrance-per-element. devup_runtime_audit reveal checks measure scroll-linked and timed entrances, run every scenario by default (adding bfcache, client-nav, reduced-motion, no-script and stagger bounds), report not-applicable and unverified instead of passing what was not observed, and ingest returns motionEvidence per candidate at mobile and desktop widths. The export reply moves standing prose to the guide, restoring the contract identifiers renamed earlier and leaving over 1 KiB of headroom under the 15 KiB budget. A single tsx at a monorepo root is matched to its owning app's devup.json from an absolute or partial sourceName or by its text.

Patch

• Open a blended negative-z decoration's stacking context on the ancestor that paints its backdrop, so multiply decorations inside a transparent wrapper composite against the gradient instead of turning white.
• Keep Korean word boundaries with textWrap pretty, reset generated heading margins, keep extra-fill asset paths distinct, label missing-only devupJson as additions-only, flag hidden component masters, and report on-disk facts for every asset output path.