@usetheo/ui 0.6.1-next.0 → 0.6.2-next.0

package/dist/styles.css

@@ -27,6 +27,31 @@
     border-color: hsl(var(--border));
   }
 
+  /* Tailwind v4 preflight regression compensation —
+   * v4 intentionally dropped the `button { cursor: pointer }` rule
+   * (https://tailwindcss.com/docs/upgrade-guide#default-button-cursor)
+   * so every native <button> renders with the default arrow cursor.
+   *
+   * Library authors are expected to opt in explicitly per button. The
+   * Violet Forge `<Button>` primitive does so (see its CVA). For the
+   * dozens of native <button> elements composites render directly,
+   * we restore the v3 behavior here — scoped to *interactive* buttons:
+   *
+   *   - `:not(:disabled)` skips the HTML `disabled` attribute path
+   *     (browser already shows `cursor: default` for disabled, but the
+   *     rule below stays explicit for clarity).
+   *   - `:not([aria-disabled="true"])` skips the ARIA-disabled path
+   *     (where the button stays focusable but acts as no-op).
+   *
+   * This is an EXPLICIT opt-in by the library author for consumers who
+   * imported `@usetheo/ui/styles.css` — it does NOT alter Tailwind's
+   * global preflight, only this stylesheet's @layer base.
+   */
+  button:not(:disabled):not([aria-disabled="true"]),
+  [role="button"]:not([aria-disabled="true"]) {
+    cursor: pointer;
+  }
+
   html {
     font-family: var(--font-body);
     -webkit-font-smoothing: antialiased;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usetheo/ui",
-  "version": "0.6.1-next.0",
+  "version": "0.6.2-next.0",
   "description": "Theo UI — framework-agnostic React component library with the Violet Forge design system. Focused on AI-agent interfaces, cloud dashboards, and developer-tooling surfaces.",
   "license": "Apache-2.0",
   "type": "module",