hazo_ui 4.10.0 → 5.1.1

package/CHANGE_LOG.md

@@ -5,7 +5,58 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## v4.10.0 (2026-07-09)
+## v5.1.0 (2026-07-10)
+
+### New
+- **`HazoUiKanban` card editor: `richtext` field type** — `editorFields` now
+  accepts `type: 'richtext'`, which renders the package's existing
+  `HazoUiRte` (`hazo_ui_rte`) in place of a plain text input. No new
+  dependency — TipTap was already required by this package. Binds to a
+  string HTML key on the item; `on_change` writes `RteOutput.html` back
+  into the draft. As with `select`/`checkbox`, `required` gating is not
+  honored for `richtext` (an "empty" RTE still emits `<p></p>`, not `""`).
+  Auto-detected fields are unaffected — `richtext` is opt-in via
+  `editorFields` only.
+- **`HazoUiKanban`: double-click to open the card editor** — double-clicking
+  a card now opens the same editor as the pencil icon, gated by the same
+  `showEdit`/`onEditRequest` props (no new prop). PointerSensor's 5px drag
+  activation distance means this doesn't interfere with drag-and-drop.
+
+## v5.0.0 (2026-07-09)
+
+### BREAKING — theming rehomed onto hazo_theme
+hazo_ui no longer owns theme tokens, a Tailwind preset, or its own theme
+provider — `hazo_theme` is now the single source, and is a **required** peer
+dependency (was optional).
+
+- **Removed exports:** `./styles.css` and `./tailwind-preset` package exports
+  are gone (`dist/styles.css`, `tailwind.preset.js` no longer ship). Import
+  `hazo_theme/theme.css` (+ optionally a `hazo_theme/themes/<name>.css` brand
+  palette) in your app's globals instead of `hazo_ui/styles.css`.
+- **`useTheme()` return shape changed:** `{ theme, setTheme, resolvedTheme,
+  toggleTheme }` → `{ mode, setMode, resolvedMode, toggleMode, themeSet,
+  setThemeSet }`. `HazoThemeProvider`'s `defaultTheme` prop is now
+  `defaultMode`; add `defaultThemeSet` to opt into a shipped brand palette.
+  `Theme`/`ThemeProviderProps`/`ThemeContextValue` types are removed — use
+  `ThemeMode`/`HazoThemeProviderProps`/`HazoThemeContextValue` from
+  `hazo_theme/client` (re-exported from the `hazo_ui` root).
+- **New export:** `ThemeSetPicker`, re-exported from `hazo_theme/client`,
+  lets consumers switch between shipped theme-sets (`indigo-sunset`,
+  `ops-dark`, `soft-studio`, ...) at runtime.
+- **Persisted-preference reset (one-time):** the localStorage key changed
+  from `"theme"` to `"hazo-theme"` (with `-mode`/`-set` suffixes), so a
+  user's saved theme choice resets to `"system"` once after upgrading.
+- **hazo_ui's own kanban tokens deleted** (`--hazo-kanban-*` in
+  `src/styles/globals.css`) — now sourced from `hazo_theme`'s Tier-1 tokens
+  (`hazo_theme@^0.2.0`), same values, zero visual change, but consumers
+  MUST import `hazo_theme/theme.css` for kanban components to render with
+  the intended colors (previously baked into `hazo_ui`'s own CSS).
+- **Migration:** bump to `hazo_theme@^0.2.0` (now required, not optional),
+  swap `hazo_ui/styles.css` → `hazo_theme/theme.css` in your globals, and
+  update any `useTheme()`/`HazoThemeProvider` call sites for the
+  `theme`→`mode` rename.
+
+## Unreleased
 
 ### New
 - **`Logo`, `AppHeader`, `AppFooter` chrome components** (framework-neutral,

package/README.md

@@ -216,8 +216,6 @@ The following components support both global config and prop-level color overrid
 
 - **[Theme Kit](#theme-kit-v490)** (v4.9.0) - SSR-safe dark/light theme using the shadcn `.dark`-class convention: `HazoThemeProvider`, `useTheme`, `ThemeToggle`, and a no-flash `ThemeScript`. Persists the chosen mode to `localStorage` and resolves `"system"` against the OS preference.
 
-- **[Chrome Components](#chrome-components-v4100)** (v4.10.0) - `Logo`, `AppHeader`, and `AppFooter` — framework-neutral header/footer/logo pieces that consume hazo_theme's `BrandIdentity` contract and its `footer-public-*`/`footer-app-*` chrome tokens. Every admin-configurable `<a href>` inside them runs through the new `safeHref()` scheme allowlist.
-
 ### State Primitives (v2.10.0)
 
 Lightweight, opinionated components for the four ubiquitous async states: **loading**, **empty**, **error**, and **success**.
@@ -252,46 +250,6 @@ SSR-safe dark/light theme using the shadcn `.dark`-class convention (toggles a `
 
 **Exports:** `HazoThemeProvider`, `useTheme`, `ThemeToggle`, `ThemeScript` and types `Theme`, `ThemeProviderProps`, `ThemeContextValue`, `ThemeScriptProps`, `ThemeToggleProps`.
 
-### Chrome Components (v4.10.0)
-
-`Logo`, `AppHeader`, and `AppFooter` — framework-neutral chrome pieces that consume hazo_theme's
-`BrandIdentity` (type-only import; `hazo_theme` stays an optional peer) plus its
-`footer-public-*`/`footer-app-*` chrome tokens (import `hazo_theme/theme.css` for the tokens to
-resolve).
-
-```tsx
-import { AppHeader, AppFooter } from 'hazo_ui';
-import type { BrandIdentity } from 'hazo_theme';
-
-const identity: BrandIdentity = {
-  logoUrl: '/brand/logo.svg',
-  appTitle: 'Acme',
-  footer: { app: { copyright: '© 2026 Acme Inc.' } },
-};
-
-function Shell({ children }: { children: React.ReactNode }) {
-  return (
-    <>
-      <AppHeader identity={identity} homeHref="/" actions={<UserMenu />} />
-      {children}
-      <AppFooter variant="app" identity={identity} />
-    </>
-  );
-}
-```
-
-- `Logo({ logoUrl?, logoUrlDark?, appTitle?, href?, height?, className?, imgClassName? })` — logo
-  image (swaps light/dark variants via `dark:hidden`/`dark:block`) or text fallback.
-- `AppHeader({ identity?, homeHref?, navItems?, actions?, className? })` — `bg-navbar` header bar.
-- `AppFooter({ variant: 'public' | 'app', footer?, identity?, className? })` — `'app'` renders a
-  thin copyright/link strip (`bg-footer-app`); `'public'` renders a taller multi-column footer with
-  a brand row and social links (`bg-footer-public`).
-- **`safeHref(url?: string): string | undefined`** — also exported standalone from the package
-  root. Allows `http://`, `https://`, `mailto:`, and same-origin `/path` hrefs; returns `undefined`
-  for anything else (`javascript:`, `data:`, protocol-relative `//host`, …). Used internally by
-  every chrome-component `<a href>` sink; reach for it directly when rendering admin-configurable
-  links elsewhere.
-
 ```tsx
 // app/layout.tsx
 import { HazoThemeProvider, ThemeScript } from 'hazo_ui';
@@ -3749,12 +3707,19 @@ on hover/focus). Clicking it opens a `HazoUiDialog` editor:
 
 Field types: `text`, `textarea`, `select`, `number`, `checkbox`,
 `priority` (a select pre-populated with `editorPriorities` —
-defaults to `["P0","P1","P2","P3"]`).
+defaults to `["P0","P1","P2","P3"]`), `status` (a select pre-populated
+from `columns`, bound to `columnKey`), and `richtext` (renders the
+package's `HazoUiRte` rich text editor — binds to a string HTML key;
+`required` gating is not honored for this type, same as `select`/
+`checkbox`).
 
 If you don't pass `editorFields`, the library auto-detects all
 string-valued fields on the item (except `id`, `columnKey`, `priority`)
 and renders each as a text input with a humanized label.
 
+Besides the pencil icon, **double-clicking a card** also opens the
+editor — same `onCardSave`/`editorFields` config, no extra prop needed.
+
 #### Custom form via renderCardEditor
 
 When the declarative config isn't enough, replace the dialog body