chore: update tasty to 2.10.0 and eslint-plugin-tasty to 0.11.1, apply migrations

[tenphi]

Describe changes

Bumps @tenphi/tasty 2.8.0 → 2.11.0 and @tenphi/eslint-plugin-tasty 0.6.2 → 0.11.2, and applies every migration those versions make safe.

The plugin bump on its own was clean: .oxlintrc.json enumerates rules explicitly, so the eight rules added across 0.7–0.9 were never activated. Enabling them surfaced 231 findings. I checked each by running the real tasty style handlers and diffing the emitted CSS rather than trusting the rule message — which mattered, because most were wrong. That audit produced three upstream PRs, and this PR is the result of applying what came back:

Upstream	What it fixed
eslint-plugin-tasty#26	flex mapping was backwards; prefer-directional-shorthand dropped real values
tasty#244	Added single-corner radius modifiers and the inset dock modifier — the two forms that had no lossless target
eslint-plugin-tasty#28 + #30	Extended the rule to radius/fade/border; fixed dock failing validation
tasty#246	dock takes a second value for the spanned sides
eslint-plugin-tasty#32	Stopped linting DOM inline-style objects as tasty styles

Every change here is CSS-equivalent, verified per-state for the state-map cases. The only textual difference in output is two min-height: 0px → 0.

Applied

Rule	Change
prefer-custom-property-syntax	currentColor → #current, transparent → #clear, var(--disabled-opacity) → $disabled-opacity
prefer-hide	display: 'none' state maps → display + inverted boolean hide map
prefer-shorthand-property	min/max → positional width/height; backgroundColor → fill; backgroundImage → image; gridAutoFlow → flow
prefer-directional-shorthand	4-value margin/padding → directional form; radius → single corner; inset → dock
no-raw-color-values	Tabs fade stops → #black / #black.0
consistent-token-usage	raw px → 3x / 1x

Notes on the ones that weren't mechanical:

• hide migration (Modal, Tray, Popover, CopyPasteBlock) — hide: true overrides display and hide: false is inert, so the unmounted-wins-over-entered precedence is preserved. Verified by diffing the full rule set, not just declarations.
• positional dimensions — the grammar is 1 value = base, 2 = min/max, 3 = min/base/max. Tree and InlineInput had a minHeight/minWidth next to a conflicting width/height state map; those are merged into one property. Worth a look in review: Tree's old minHeight: 0 was overriding the fixed min so the tree could shrink below $tree-height, and '0 $tree-height $tree-height' keeps that (plain fixed $tree-height would have pinned it).
• radius / inset collapses — these are the seven findings the earlier plugin version had to leave alone because no correct rewrite existed. radius: '0 0 4px 0' → '4px bottom-right', inset: 'auto 0 0 0' → '0 bottom dock'. Slider's range states keep their 4-value form: their offsets are unequal, so no directional or dock form exists for them, and the rule correctly leaves them alone.

Incidental bug fix

Placeholder had fill: '#dark.10' and backgroundColor: '#dark.15' — both compile to background-color. backgroundColor won regardless of source order, so the fill line was dead code. Removed it; rendering is unchanged. The rename is what exposed it as a duplicate key.

One rule left disabled

Every rule in the plugin's recommended set is now enabled except prefer-shorthand-property, which still emits 141 findings whose suggestions change runtime behaviour. Verified failure modes:

• top/right/bottom/left → inset (110) — {top:'1x'} emits top: 8px, but {inset:'1x top'} emits inset: 8px auto auto auto, resetting the other three sides. These are first-class tasty styles, not raw CSS.
• outlineOffset → outline (11) — with no sibling outline, {outline:'/ 1bw'} emits outline: 1px solid var(--outline-color), inventing a visible outline and dropping the offset.
• borderTop etc. → border (6) — sets all four sides, zeroing the other three.
• paddingRight/paddingBottom → padding (2) — clobbers the sibling base padding.
• fontFamily → font (1) — font: 'inherit' appends the sans fallback stack.
• fontSize/lineHeight/fontWeight/textTransform → preset (10) — preset is a bundle (family + size + weight + line-height + letter-spacing), not a rename, which is why the hints are literally preset: '...'.

That count is down from 141: eslint-plugin-tasty#32 removed 7 false positives where the plugin was linting plain DOM inline-style objects as tasty — 5 from the setStyle() object in src/utils/ResizeSensor.ts, plus hostStyle: CSSProperties in WidgetHost and baseStyle: Record<string, string> in Layout. The remaining 134 are all genuine, so the rule stays off.

Checklist

• Pipeline is passed
• Tests are passed successfully — 997 passed, 1 skipped (51 files); pnpm lint clean; Chromatic reports 905 stories unchanged
• Tests are added — none; this is a refactor with no behaviour change, and every rewrite was verified CSS-equivalent against the tasty handlers
• Changeset(s) is(are) added — patch, covering the dependency updates and the style reformatting
• Commit message follows commit guidelines

Closes: N/A

Other information

tsc reports 11 errors on this branch — identical to main (verified by stashing), all in files this PR does not touch (CommandMenu.stories.tsx, caretPosition.ts, CommandTextArea.tsx, Tooltip.stories.tsx).

Note @tenphi/tasty is pinned exactly (2.11.0) per the repo's update-tasty convention. Plugin 0.11.2 or newer is required: 0.11.0 shipped an auto-fix whose output its own valid-value rule rejected (#30), and 0.11.2 carries the inline-style detection fix (#32).

🤖 Generated with Claude Code

---

Note

Medium Risk
Wide touch on overlay visibility, flex sizing (Tree, InlineInput), and layout tokens; regressions would be visual only but could affect modals, trees, and inline editing if any rewrite were not truly CSS-equivalent.

Overview
Upgrades @tenphi/tasty to 2.11.0 and @tenphi/eslint-plugin-tasty to 0.11.2, turns on additional tasty lint rules in .oxlintrc.json (including stricter no-nested-selector and several prefer-* / consistency rules), and rewrites component tasty styles to satisfy them.

The source changes are style-definition refactors only—tokens like #current / #clear, hide instead of display: none state maps on overlays (Modal, Tray, Popover), directional margin / padding / radius / inset dock, positional width / height, and related longhand moves (fill, image, flow). Placeholder drops a duplicate fill that was overridden by backgroundColor. No public API changes; the changeset states emitted CSS is equivalent and Chromatic is unchanged.

^{Reviewed by Cursor Bugbot for commit 794a27a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

🦋 Changeset detected

Latest commit: 794a27a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@cube-dev/ui-kit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cube-ui-kit	Ready	Preview, Comment	Jul 29, 2026 12:31pm

[github-actions]

📦 NPM canary release

Deployed canary version 0.0.0-canary-92dda5a.

[github-actions]

🏋️ Size limit report

Name	Size	Passed?
All	434.03 KB (+0.1% 🔺)	Yes 🎉
Tree shaking (just a Button)	114.87 KB (+0.44% 🔺)	Yes 🎉

---

Click here if you want to find out what is changed in this build

[github-actions]

🧪 Storybook is successfully deployed!

• 👀 Review changes: https://www.chromatic.com/build?appId=626ee6db91d1c8004a912249&number=3609
• 👨‍🎨 Preview storybook: https://626ee6db91d1c8004a912249-bztfukkcxf.chromatic.com/