hazo_ui 6.10.0 → 6.11.2

package/CHANGE_LOG.md

@@ -5,6 +5,129 @@ 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).
 
+## v6.11.2 (2026-09-01)
+
+### Fixed — `hazo_state` peer dependency range never resolved
+
+`peerDependencies.hazo_state` was `^0.5.0`, but `hazo_state` never published a
+0.5.x release on the registry (its version history jumps `0.4.0` → `0.6.0`
+directly). Any fresh install of `hazo_ui` requiring registry resolution of
+this peer range failed with `ETARGET`. Only symbol used from `hazo_state` is
+the `StateLevel` type, unchanged since `0.4.0`, so the range is corrected to
+`^0.6.0` with no consumer-facing behavior change.
+
+## v6.11.1 (2026-08-25)
+
+### Added — `data-lane-key` on `HazoUiKanban` swimlane hooks
+
+`KanbanColumn` already exposes `data-column-key` on its shell so a consumer
+can style/select one column via CSS (`cls_hazo_kanban_column[data-column-key='...']`,
+pubsos's own board chrome). Lanes had no equivalent — the per-lane row
+wrapper, heading and collapsed strip carried only the shared
+`cls_hazo_kanban_lane*` hooks, with no way to target one specific lane (e.g.
+a "Marked Items" lane that should read louder than an ordinary tag lane)
+without matching on lane title text. `data-lane-key={lane.key}` is now on
+the lane row wrapper (`cls_hazo_kanban_lane`), the heading
+(`cls_hazo_kanban_lane_head`) and the collapsed strip
+(`cls_hazo_kanban_lane_strip`) — same attribute name and placement pattern
+as the column hook.
+
+## v6.11.0 (2026-08-24)
+
+### Added — `LocalePicker` + `createPackageT` i18n infrastructure (FR-030)
+
+First of the i18n-prerequisite work for the still-unbuilt `hazo_i18n`
+package (see `00.lib/design/PRD-hazo_i18n.md`, §2.1 / §11 / §16.3).
+`hazo_i18n` is headless by design, so the locale picker component lives
+here; `hazo_ui` also starts routing its own ~150 baked-in English strings
+through an i18n bridge instead of hardcoding them. Everything in this
+release works identically whether `hazo_i18n` is installed or not —
+**an English-only consumer sees zero change** (same text, same markup, same
+`en-US` number/currency formatting).
+
+- **New `<LocalePicker>`** (`hazo_ui` and the slim `hazo_ui/locale-picker`
+  entry) — a standard language-switcher dropdown, purely prop-driven, no
+  `hazo_i18n` dependency:
+  ```tsx
+  <LocalePicker
+    variant="dropdown"       // "dropdown" | "inline" | "compact"
+    show="auto"              // "auto" (renders null below 2 locales) | "always" | "never"
+    display="native"         // "native" | "native+code" | "code"
+    flags={false}
+    alternates={{ en: "https://x.com/", de: "https://x.com/de" }}
+  />
+  ```
+  Built on the same Radix `DropdownMenu`/`DropdownMenuRadioGroup` primitives
+  as `src/components/ui/dropdown-menu.tsx`. Every option is a real `<a href>`
+  (via Radix `asChild`), not a JS-only click handler, so it stays crawlable
+  and middle-click-openable — options can only ever point at URLs present in
+  the `alternates` map (the same map a consumer already builds for `<head>`
+  hreflang). Native language names come from `Intl.DisplayNames`,
+  instantiated per-language in that language's own locale, so German shows
+  "Deutsch" and Swedish shows "svenska" — never an English name. `flags:
+  true` renders inline SVG (a small embedded set for common locales, a
+  generic globe icon otherwise) — **never emoji**, since Segoe UI Emoji ships
+  no regional-indicator glyphs and flag emoji render as broken letter-boxes
+  on Windows Chrome/Edge. `lang={code}` is set on both the trigger and each
+  option.
+
+- **New `createPackageT(namespace, fallbackCatalog)`**
+  (`src/lib/create_package_t.ts`) — the i18n bridge every `hazo_*` package
+  will eventually adopt for its own strings. Probes for `hazo_i18n` once via
+  `optional_import("hazo_i18n")` from `hazo_core/client` (the same
+  optional-peer pattern used elsewhere in this package); the returned `t()`
+  delegates to `hazo_i18n`'s translator when present and resolvable, and
+  otherwise looks up the key in the bundled fallback catalog with simple
+  `{{var}}` interpolation. Pure function, no React dependency. Also exports
+  `resolvePackageLocale(defaultLocale)`, used by the table's number
+  formatting (see below) — it only ever overrides the default when
+  `hazo_i18n` exposes a synchronous, SSR/CSR-identical locale getter, and
+  falls back to the static default otherwise, so it can never introduce a
+  hydration mismatch.
+
+- **`src/locales/en.json`** — the bundled English catalog, ~69 keys covering
+  the four files below.
+
+- **Wired `t()` into the four files that hold 55%+ of this package's
+  translatable strings** (per the FR's own survey):
+  `hazo_ui_table/index.tsx` (pagination: "Showing X–Y of Z", Prev/Next +
+  their aria-labels, search placeholder, sort tooltip, empty/no-results/error
+  states), `hazo_ui_rte/toolbar/toolbar.tsx` (all 28 `tooltip=` values —
+  Bold, Italic, Undo, Align left, etc. — popover body copy is deferred, not
+  in scope), `hazo_ui_rte/types.ts` (new `get_translated_block_types()`
+  helper for the block-type dropdown's 9 labels; `BLOCK_TYPES` itself is
+  unchanged for any direct consumer), and
+  `hazo_ui_multi_filter_dialog/index.tsx` (dialog title/description,
+  field-input placeholders, On/Off, Active filters tooltip, footer buttons,
+  ~21 keys total). Every existing `labels`/default-prop override
+  (`HazoUiTableProps.empty`/`.noResults`, `booleanLabels`, the dialog's
+  `title`/`description`, etc.) still takes precedence over `t()` — verified
+  by regression tests. The remaining ~40 strings across the rest of the
+  package are explicitly deferred to `hazo_i18n`'s own creation.
+
+- **Number-locale threading** — `hazo_ui_table`'s `DEFAULT_NUMBER_LOCALE`
+  pin now resolves through `resolvePackageLocale("en-US")` instead of a bare
+  constant. **Behavior for everyone without `hazo_i18n` installed is
+  unchanged** (still pinned to `"en-US"`, still hydration-safe by
+  construction); this only starts mattering once `hazo_i18n` exists and
+  exposes a synchronous locale getter. Date formatting (`date-fns`'s
+  `"MMM d, yyyy"` pattern in the table and the filter dialog) is unchanged —
+  deferred, since locale-aware date formatting needs a `date-fns/locale`
+  import per BCP-47 code, out of scope for this pass.
+
+- **`hazo_i18n` added as an optional peer** (`peerDependencies` +
+  `peerDependenciesMeta.hazo_i18n.optional: true`) — it doesn't exist on npm
+  yet, so this is forward-declaration; `optional_import` means a missing or
+  unpublished `hazo_i18n` never breaks `npm install` or the build.
+
+- **New test infrastructure** — this package had no unit test runner before
+  this release. Added `jest.config.cjs` (ESM + ts-jest + jsdom, mirrors
+  `hazo_theme`'s config) and `npm run test`; 32 tests across 4 files cover
+  `createPackageT`'s fallback/interpolation/delegation behavior,
+  `LocalePicker`'s auto-hide/real-`<a>`/flag/no-emoji/precedence rules, the
+  table's translated-catalog wiring and empty/noResults override precedence,
+  and an SSR-vs-CSR hydration-safety check for formatted currency.
+
 ## v6.10.0 (2026-08-15)
 
 ### Added — `HazoUiKanban.renderColumnHeaderExtra`