@exxatdesignux/ui 0.3.0 → 0.4.1

package/template/docs/blueprints/page-header.md

@@ -89,7 +89,7 @@ ID token gets `font-mono tabular-nums`, the rest of the line stays sans.
 | `base` | Default — most routes | Title + actions only |
 | `object-home` | Lists / hubs with optional metrics + tabs **below** the header | Adds a count/freshness slot under the title |
 | `record-home` | Detail / record views | May expose a small detail row (label/value pairs) — keep ≤ 5 pairs |
-| `collaboration` | Shared hubs (Question bank, future) | Adds face rail + invite entry — see [`exxat-collaboration-access.mdc`](../../../.cursor/rules/exxat-collaboration-access.mdc) |
+| `collaboration` | Shared hubs (Library, future) | Adds face rail + invite entry — see [`exxat-collaboration-access.mdc`](../../../.cursor/rules/exxat-collaboration-access.mdc) |
 
 Pick **one** variant per header. Combining `collaboration` with
 `record-home` is allowed only when the record itself is a shareable
@@ -99,7 +99,7 @@ artifact (e.g. a question).
 
 | Framework | Component(s) | File |
 |---|---|---|
-| **React (this app)** | `PageHeader` (shell) + per-hub headers (composition) | [`apps/web/components/page-header.tsx`](../../components/page-header.tsx), `placements-page-header.tsx`, `team-page-header.tsx`, `question-bank-page-header.tsx` |
+| **React (this app)** | `PageHeader` (shell) + per-hub headers (composition) | [`apps/web/components/page-header.tsx`](../../components/page-header.tsx), [`apps/web/components/library-page-header.tsx`](../../components/library-page-header.tsx) |
 | Mobile | — | — |
 | Figma | — | — |
 
@@ -107,7 +107,7 @@ Reference hub-level compositions:
 
 - **Placements** — filled primary CTA `New placement` + `⋯` (Export, Customize…)
 - **Team** — same shape, count + freshness in subtitle
-- **Question bank** — `variant="collaboration"` + folder-scoped customize entry
+- **Library** — `variant="collaboration"` + folder-scoped customize entry
 
 ## 8. Do / Don't
 
@@ -124,7 +124,7 @@ Reference hub-level compositions:
 
 - [`apps/web/docs/data-views-pattern.md`](../data-views-pattern.md) — `PageHeader` in context of `ListPageTemplate`
 - [`apps/web/docs/collaboration-access-pattern.md`](../collaboration-access-pattern.md) — `variant="collaboration"`
-- [`apps/web/docs/question-bank-hub-header-pattern.md`](../question-bank-hub-header-pattern.md) — folder-scoped header
+- [`apps/web/docs/library-hub-header-pattern.md`](../library-hub-header-pattern.md) — folder-scoped header
 - [`.cursor/rules/exxat-collaboration-access.mdc`](../../../.cursor/rules/exxat-collaboration-access.mdc)
 - [`.cursor/rules/exxat-mono-ids.mdc`](../../../.cursor/rules/exxat-mono-ids.mdc)
 - [`apps/web/AGENTS.md`](../../AGENTS.md) §4.7, §6.2, §9

package/template/docs/collaboration-access-pattern.md

@@ -1,8 +1,8 @@
 # Collaboration & access pattern
 
-Shared UI for **who can access a hub** (face stack in the header) and **inviting people** (floating sheet). **Reference:** Question bank — `QuestionBankPageHeader`, `QuestionBankClient`, `InviteCollaboratorsDrawer`.
+Shared UI for **who can access a hub** (face stack in the header) and **inviting people** (floating sheet). **Reference:** Library — `LibraryPageHeader`, `LibraryClient`, `InviteCollaboratorsDrawer`.
 
-**Folder-scoped question bank:** When the library URL selects a folder (`?scope=folder&folderId=`), the same header **⋯ More** menu also exposes **Customize folder** (name / color / icon) via **`QuestionBankNewFolderSheet`** mounted on **`QuestionBankClient`** so it works on every view tab. See **`docs/question-bank-hub-header-pattern.md`** and **`.cursor/rules/exxat-question-bank-hub-header.mdc`**.
+**Folder-scoped library:** When the library URL selects a folder (`?scope=folder&folderId=`), the same header **⋯ More** menu also exposes **Customize folder** (name / color / icon) via **`LibraryNewFolderSheet`** mounted on **`LibraryClient`** so it works on every view tab. See **`docs/library-hub-header-pattern.md`** and **`.cursor/rules/exxat-library-hub-header.mdc`**.
 
 ## When to use
 
@@ -33,11 +33,11 @@ Shared UI for **who can access a hub** (face stack in the header) and **inviting
 
 ```tsx
 <CollaborationAccessFlow
-  initialCollaborators={QUESTION_BANK_HEADER_COLLABORATORS}
+  initialCollaborators={LIBRARY_HEADER_COLLABORATORS}
   resourceLabel={hubHeader.title}
 >
   {({ collaborators, openInvite }) => (
-    <QuestionBankPageHeader
+    <LibraryPageHeader
       variant="collaboration"
       title={hubHeader.title}
       questionCount={count}
@@ -100,9 +100,9 @@ Row order:
 | Hub flow | `components/collaboration-access-flow.tsx` |
 | Collaborator type | `components/page-header.tsx` (`PageHeaderCollaborator`) |
 | Invite sheet | `components/invite-collaborators-drawer.tsx` |
-| Entity header | `components/question-bank-page-header.tsx` |
-| Hub wiring | `components/question-bank-client.tsx` |
-| Demo roster | `lib/mock/question-bank-header-collaborators.ts` |
+| Entity header | `components/library-page-header.tsx` |
+| Hub wiring | `components/library-client.tsx` |
+| Demo roster | `lib/mock/library-header-collaborators.ts` |
 
 ## Checklist (new hub)
 

package/template/docs/component-selection-guide.md

@@ -56,7 +56,7 @@ primitive after asking the user
 | Export | Filled primary CTA + `⋯` → `ExportDrawer` |
 | Kanban view body | **`ListPageBoardCard`** + `ListPageBoardTemplate` ([`exxat-board-cards.mdc`](../../.cursor/rules/exxat-board-cards.mdc)) |
 | Folder / panel view body | **`FolderGridView`** / **`FinderPanelView`** wrapped in **`ListPageViewFrame`** ([`exxat-list-page-view-shells.mdc`](../../.cursor/rules/exxat-list-page-view-shells.mdc)) |
-| Dashboard view body | **`KeyMetrics variant="card"`** + chart sections from `data-view-dashboard-charts*.tsx` |
+| Dashboard view body | **`KeyMetrics variant="card"`** + a hub-specific chart section (reference: `library-dashboard-charts.tsx`) |
 | Nested scope nav (All / Mine / tree) | **`secondaryPanel`** + `PANELS` + `useAutoPanel` ([`exxat-primary-nav-secondary-panel.mdc`](../../.cursor/rules/exxat-primary-nav-secondary-panel.mdc)) |
 | Shared hub w/ invite | **`PageHeader` `variant="collaboration"`** + `InviteCollaboratorsDrawer` |
 | Dedicated search (empty `?q=` vs results) | **`DedicatedSearchLandingTemplate`** + **`DedicatedSearchResultsHeaderChrome`** |

package/template/docs/data-views-pattern.md

@@ -2,6 +2,8 @@
 
 > **Canonical rules for agents (MUST/MUST NOT, checklists):** [`AGENTS.md`](../AGENTS.md) in this package (including **§8 Accessibility**). This file is the long-form narrative; keep both aligned when patterns change.
 
+> **Scaling past ~2K rows:** see [`large-dataset-strategy.md`](./large-dataset-strategy.md) for pagination, server-mode upgrade path, and the virtualization follow-up.
+
 This document describes how list pages combine **views**, **toolbar** behavior, **filters**, **properties**, and **persistence** in this codebase.
 
 ## Reuse existing components (required)
@@ -10,18 +12,18 @@ This document describes how list pages combine **views**, **toolbar** behavior,
 
 | Need | Reuse | Where Placements uses it |
 | --- | --- | --- |
-| **View tabs** (table / list / board, lifecycle filters) | `ListPageTemplate` (`ViewTab`, `renderContent`, optional metrics + export) | `components/placements-client.tsx` + `components/templates/list-page.tsx` |
-| **Table shell** (search, filter bar, sort, grouping, columns, pagination) | `DataTable`, `DataTableToolbar`, `useTableState` | `components/data-table/`, `components/placements-table.tsx` |
-| **Properties drawer** (display, columns, filters, sort, view type tiles) | `TablePropertiesDrawer` from `@/components/table-properties` | `DrawerToolbar` / list–board shells in `placements-table.tsx` |
+| **View tabs** (table / list / board, lifecycle filters) | `ListPageTemplate` (`ViewTab`, `renderContent`, optional metrics + export) | `components/library-hub-client.tsx` + `components/templates/list-page.tsx` |
+| **Table shell** (search, filter bar, sort, grouping, columns, pagination) | `HubTable` → `DataTable`, `DataTableToolbar`, `useTableState` | `components/data-table/`, `components/data-views/hub-table.tsx`, `components/columns-showcase.tsx` |
+| **Properties drawer** (display, columns, filters, sort, view type tiles) | `TablePropertiesDrawer` from `@/components/table-properties` (auto-wired by `HubTable`) | `DrawerToolbar` / list–board shells in `library-table.tsx` |
 | **Board / list** | `PlacementsBoardView`, `PlacementListRowContent` (wrapped by `HubTable.renderListRow` → `DataRowList`) + same `useTableState` | `PlacementsTable` |
-| **Page header** (primary CTA + More ⋯ + export) | `PlacementsPageHeader` or `TeamPageHeader` | `components/placements-page-header.tsx`, `components/team-page-header.tsx` |
-| **Team page (primary template)** | `TeamClient` = `ListPageTemplate` + `KeyMetrics` + `TeamPageHeader` + `TeamTable` (same composition as `PlacementsClient`) | `components/team-client.tsx`, `lib/mock/team-kpi.ts` |
-| **Team roster** | `TeamTable` — `DataTable` + `useTableState` + `TablePropertiesDrawer`; list/board/dashboard read **`tableState.rows`** | `components/team-table.tsx` |
-| **Dashboard view (list tab)** | **`KeyMetrics`** (`variant="flat"` or `"card"`) — same KPI system as the template metrics strip; **do not** add ad-hoc `Card` grids for entity summaries | `TeamTable` dashboard branch, `lib/mock/team-kpi.ts` |
-| **List hub metrics strip** | **`KeyMetrics variant="flat"`** — transparent cells, OKLCH brand glow only, border hairlines (**no** grey panel) | **`docs/kpi-flat-band-pattern.md`**, Placements / Team / Question bank clients |
-| **Secondary panel chrome** | **`--secondary-panel-bg`** on **`NestedSecondaryPanelShell`** (lighter than sidebar, follows active product) | **`docs/shell-surface-elevation-pattern.md`**, Question bank |
+| **Page header** (primary CTA + More ⋯ + export) | Per-hub page header composing `PageHeader` + `ExportDrawer` button | `components/library-page-header.tsx` |
+| **Primary hub composition** | `*Client` = `ListPageTemplate` + `KeyMetrics` + `*PageHeader` + `*Table`. Reference: `LibraryHubClient`. | `components/library-hub-client.tsx`, `components/columns-client.tsx`, `components/tokens-themes-client.tsx` |
+| **Hub table body** | `HubTable` — wraps `DataTable` + `useTableState` + `TablePropertiesDrawer`; list / board / dashboard read **`tableState.rows`**. Pagination chrome is auto-mounted when the hub passes `pagination` + `onPaginationChange`. | `components/data-views/hub-table.tsx`, `components/library-table.tsx`, `components/columns-showcase.tsx` |
+| **Dashboard view (list tab)** | **`KeyMetrics`** (`variant="flat"` or `"card"`) — same KPI system as the template metrics strip; **do not** add ad-hoc `Card` grids for entity summaries. | `LibraryTable` dashboard branch, `components/library-dashboard-charts.tsx` |
+| **List hub metrics strip** | **`KeyMetrics variant="flat"`** — transparent cells, OKLCH brand glow only, border hairlines (**no** grey panel) | **`docs/kpi-flat-band-pattern.md`**, Placements / Team / Library clients |
+| **Secondary panel chrome** | **`--secondary-panel-bg`** on **`NestedSecondaryPanelShell`** (lighter than sidebar, follows active product) | **`docs/shell-surface-elevation-pattern.md`**, Library |
 | **Export** | `ExportDrawer` | `ListPageTemplate` export props; `PlacementsClient` |
-| **View body layout** (gutter + centered max-width for folder / icon / panel-style content) | **`ListPageViewFrame`** (`components/data-views/list-page-view-frame.tsx`, re-exported from `components/data-views`) | **`FolderGridView`** (uses the frame); **`QuestionBankOsFolderView`** — see **`AGENTS.md` §4.5** |
+| **View body layout** (gutter + centered max-width for folder / icon / panel-style content) | **`ListPageViewFrame`** (`components/data-views/list-page-view-frame.tsx`, re-exported from `components/data-views`) | **`FolderGridView`** (uses the frame); **`LibraryOsFolderView`** — see **`AGENTS.md` §4.5** |
 
 **Rules:** (1) Import and compose these components; pass **props** and **column defs** for your entity. (2) If something is missing, **extend the shared component** under `components/` (e.g. a new optional slot on `DataTableToolbar`) rather than copying markup into a single page. (3) Card-only or lightweight pages may use a smaller **Properties** sheet only when there is **no** table—otherwise use `TablePropertiesDrawer` with `DataTable` (see Team).
 
@@ -89,13 +91,13 @@ Non-table view branches (e.g. **folder** icon grid, **panel** finder, OS-style f
 - **Status (Team & Compliance)** — `lib/list-status-badges.ts` — single source for label strings + badge `className` tails for **table, list, and board**. Do **not** pair with `uppercase` on the Badge (labels are sentence case, aligned with Placements `BoardStatusBadge`).
 - **Owner initials** — `lib/initials-from-name.ts` when mock rows have a display name but no `initials` field.
 - **Shared column shell** — `components/data-views/list-page-board-template.tsx` — `ListPageBoardTemplate` + `ListPageBoardColumnDef<T>`: define columns with `filter` predicates, `renderCard`, `getRowKey`. Used by **Team** and **Compliance** boards; new hubs should start here before custom chrome.
-- **Placement card** — `components/data-views/placement-board-card.tsx` — `BoardPlacementCard` composes **`ListPageBoardCard`** parts with `ColumnDef<Placement>` and lifecycle layout helpers from `lib/placement-board-card-layout.ts`. Placements keeps richer column headers (search, menus); still uses the same primitives.
+- **Library board** — `components/library-board-view.tsx` — composes **`ListPageBoardCard`** parts with `BoardCardTwoLineBlock` for the body and `ListHubStatusBadge` for the status row. Use this as the reference for any new domain board card.
 - New entities should add their own card component that composes **`ListPageBoardCard`** + primitives rather than duplicating column scroll/layout or ad-hoc card chrome.
 
 ## Dashboard view (list pages)
 
-- **Reuse the dashboard chart bundle** — `components/dashboard-report-charts.tsx` — `DashboardReportCharts`: flat `KeyMetrics` + middle chart section + period comparison `KeyMetrics` card. **`ChartsOverview`** (placement-themed demo gallery) is the default middle section for `/dashboard` and **Placements**. **Team** passes **`chartsSection={<TeamDashboardChartsSection members={tableState.rows} />}`** so charts reflect roster data, not placements. List hubs use `ListPageDashboardCharts` (`metricsSingleRow`). Chart **style** can follow `ChartVariantProvider` when using `ChartsOverview`.
-- **Data tab canvas charts** (`data-view-dashboard-charts*.tsx`) share **`ChartFigure`**, **`ChartCard`**, and **`ChartDataTable`** with `charts-overview.tsx`. **Layout** for Placements / Team / Compliance is stored in one place: **`lib/data-view-dashboard-storage.ts`** (see `AGENTS.md` §4.3). **Keyboard-selected bars/slices** must use **`lib/chart-keyboard-selection.ts`** (`activeBar` / `activeShape`) so behavior matches the gallery — not opacity-only `Cell` dimming.
+- **Reuse the dashboard chart bundle** — `components/dashboard-report-charts.tsx` — `DashboardReportCharts`: flat `KeyMetrics` + middle chart section + period comparison `KeyMetrics` card. **`ChartsOverview`** is the default middle section for `/dashboard`. Hubs pass **`chartsSection={<MyDashboardChartsSection rows={tableState.rows} />}`** so charts reflect the hub's own row set. Reference: **`LibraryDashboardChartsSection`** in `components/library-dashboard-charts.tsx`. Chart **style** can follow `ChartVariantProvider` when using `ChartsOverview`.
+- **Data tab canvas charts** share **`ChartFigure`**, **`ChartCard`**, and **`ChartDataTable`** with `charts-overview.tsx`. **Layout** is stored in one place: **`lib/data-view-dashboard-storage.ts`** under a per-hub scope (see `AGENTS.md` §4.3). **Keyboard-selected bars/slices** must use **`lib/chart-keyboard-selection.ts`** (`activeBar` / `activeShape`) so behavior matches the gallery — not opacity-only `Cell` dimming.
 
 ## Persistence
 
@@ -130,13 +132,13 @@ Below the threshold, these may be omitted unless the page is a primary data hub
 
 ## Data pages: primary CTA + More + Export
 
-If the page **has exportable data** (rows, members, placements, etc.), follow the **Placements** header pattern:
+If the page **has exportable data** (rows, members, library items, etc.), follow the **Library** header pattern:
 
-1. **Primary action** — One default (filled) button for the main task (e.g. **New placement**, **Invite member**). Do **not** use `variant="outline"` for that primary action.
+1. **Primary action** — One default (filled) button for the main task (e.g. **New question**, **Invite collaborator**, **Add token**). Do **not** use `variant="outline"` for that primary action.
 2. **More (⋯)** — An outline **icon** button opening a menu that includes **Export** (and other overflow actions). Wire **Export** to `ExportDrawer` (or equivalent).
 3. **Subtitle** — Prefer a short line with **count + freshness** (e.g. `24 records · Last updated now`), matching `PlacementsPageHeader`.
 
-Reference: `components/placements-page-header.tsx`, `components/team-page-header.tsx`, `components/team-client.tsx`.
+Reference: `components/library-page-header.tsx`, `components/library-hub-client.tsx`.
 
 ---
 

package/template/docs/glossary.md

@@ -0,0 +1,58 @@
+# Exxat DS — Glossary
+
+> Shared vocabulary. When a rule or pattern uses a term in **bold**, it's defined here. Add a term when you find yourself explaining the same word twice in PR review.
+
+| Term | Definition | See also |
+|---|---|---|
+| **Active view** | The currently selected view tab on a hub (table, list, board, dashboard, …). Drives which `HubTableRenderers` entry mounts and what the **Properties drawer** shows in its view-type tile grid. | `exxat-table-properties-drawer.mdc` |
+| **Bare Kbd** | The `<Kbd variant="bare">` rendering — no background, no border, inherits `currentColor` at 70 %. Used inline **inside** a button so the chord doesn't look pasted on. The default `tile` variant is reserved for tooltips and menu shortcut slots. | `exxat-kbd-shortcuts.mdc` |
+| **Blueprint** | Framework-agnostic spec for one UI pattern. Says *what* the pattern is and *what* it must do without committing to React. See `docs/blueprints/`. | `docs/blueprints/README.md` |
+| **Board card** | The kanban-style card surface on a board view. Composed of `ListPageBoardCard` (shell), `ListPageBoardCardTitleRow`, optional `ListPageBoardCardAvatar`, optional badge row with `ListHubStatusBadge` (`surface="board"`), and a body using `BoardCardTwoLineBlock` / `BoardCardIconRow`. | `exxat-board-cards.mdc` |
+| **Brand glow** | The OKLCH-mixed brand tint applied as a soft halo behind a surface (KPI flat band, secondary panel). Not a hard background — the tint **adds**, the underlying surface still reads. | `docs/kpi-flat-band-pattern.md`, `docs/shell-surface-elevation-pattern.md` |
+| **Bulk-actions slot** | The floating action bar that appears when one or more rows are selected in a `HubTable`. Wired via `bulkActionsSlot={(selected) => …}`. | `packages/ui/src/components/data-views/hub-table.tsx` |
+| **Cell pattern** | One column's rendering recipe — built by composing existing primitives (`Badge`, `AvatarInitials`, `ListHubStatusBadge`, `ToggleSwitch`, FA glyphs, `Tip`, `Tooltip`, `DropdownMenu`). The canonical catalog of patterns lives in `apps/web/components/columns-showcase.tsx`; the live demo is at `/columns`. | `docs/reference-implementations.md` |
+| **Cell primitive** | One of the named, importable `ColumnDef['cell']` renderers exported from `@/components/data-views` (re-exported from `apps/web/components/data-views/table-cells.tsx`): `ProgressCell`, `CurrencyCell`, `NumericCell`, `RatingCell`, `SignalBarsCell`, `BooleanToggleCell`, `AttachmentCountCell`, `ExternalLinkCell`, `RelativeTimeCell`, `PeopleAvatarRailCell`, `PillCell`, `TagListCell`, `RowActionsCell`. Every cell renderer in the showcase comes from this module; new hubs **must** import these instead of inlining the same JSX. | `.cursor/skills/exxat-token-economy/SKILL.md` §3, `exxat-data-tables.mdc` |
+| **Centralized list dataset** | The rule that **one** `useTableState` row bag drives **every** view (table, list, board, dashboard, panel, tree, …) on a given hub. No parallel mock arrays per view. | `exxat-centralized-list-dataset.mdc` |
+| **Coach mark** | The onboarding overlay that highlights a UI element and explains it. State managed by `useCoachMark`. Dismissals stick per flow id. | `apps/web/lib/coach-mark-registry.ts` |
+| **Collaboration variant** | The `PageHeader` flavor that exposes the face rail + Invite-people overflow item for shared hubs. | `exxat-collaboration-access.mdc` |
+| **Column def (`ColumnDef`)** | The typed column shape consumed by `DataTable` / `HubTable`. Adding `filter:` to a column auto-generates a filter chip and toolbar dropdown entry. | `packages/ui/src/components/data-table/types.ts` |
+| **Conditional rule** | A `ColumnDef`-level rule that applies a background tint to a cell when its value matches an operator + value (e.g. "score < 60 → red"). Authored in the **Properties drawer**. | `packages/ui/src/components/table-properties/` |
+| **Content rail** | The centered, max-width column the `PrimaryPageTemplate` reserves for primary content. Width comes from the template, not the page; don't override per-page. | `apps/web/components/templates/primary-page-template.tsx` |
+| **DataTable** | The low-level table primitive in `packages/ui`. Mount this **only** outside a hub (drawer-body mini-grids, modal sub-tables). Inside `ListPageTemplate`, use `HubTable`. | `exxat-data-tables.mdc` |
+| **`delta`** | The KPI **count** of change (e.g. `"+5"`, `-3`, `"+12 %"`) on a `MetricItem`. Pass `""` or `0` to suppress the trend chip. Never prose. | `exxat-kpi-trends.mdc` |
+| **`description`** | The KPI **caption** beneath the value and trend row on a `MetricItem`. Use this for prose like `"left + right"` or `"vs last week"`. Never a delta count. | `exxat-kpi-trends.mdc` |
+| **Display options** | Per-table preferences (toolbar search visibility, density, gridlines, pagination toggle, …) that flow through `DataListDisplayOptions`. `HubTable` owns the state by default; the hub client can take it over with `displayOptions` + `onDisplayOptionsChange`. | `packages/ui/src/components/table-properties/` |
+| **Empty state** | The text + icon + (optional) action shown when a view body has zero rows after filters. Distinct from "no data ever" (use `EmptyTableState`) vs "no matches" (filter-aware copy). | `docs/voice-and-tone.md` |
+| **Face rail** | The small overlapping-faces row on a `PageHeader` (collaboration variant) showing collaborators. Click to open the invite drawer. | `exxat-collaboration-access.mdc` |
+| **Filter chip** | The dismissible chip rendered above a `HubTable` body for each active filter. Auto-generated from `ColumnDef.filter`. | `exxat-data-tables.mdc` |
+| **Flat band (KPI)** | `KeyMetrics variant="flat"` — transparent cell, brand glow only, hairline cell borders. The shape used on every primary hub metrics strip. | `exxat-kpi-flat-band.mdc` |
+| **Hairline** | A 1 px border at exactly `--border` color used to separate KPI cells, table cells, surface divisions. Never thicker for hierarchy — use spacing or color instead. | `docs/kpi-flat-band-pattern.md` |
+| **HubTable** | The canonical hub view body. Wraps `useTableState`, the toolbar (search + filter chips + filter dropdown + sort), `TablePropertiesDrawerButton`, view-type tiles, bulk-actions, and conditional rules. Always use this inside `ListPageTemplate.renderContent`. | `exxat-data-tables.mdc` |
+| **Hub primitive** | Synonym for `HubTable` — the single primitive that produces a "hub-shaped" view body. | same |
+| **Inspector** | A side-anchored drawer that shows a single record's details without leaving the hub. Resolved against the same `tableState.rows` as the grid. | `exxat-centralized-list-dataset.mdc` |
+| **`KeyMetrics`** | The KPI strip / band component. Accepts `MetricItem[]` (≤ 4) and a single `MetricInsight`. Use `variant="flat"` on hubs; `variant="card"` for embedded analytics cards. | `exxat-kpi-flat-band.mdc`, `exxat-kpi-max-four.mdc` |
+| **KPI strip** | The horizontal KPI row at the top of a hub. ≤ 4 tiles. | `exxat-kpi-max-four.mdc` |
+| **Lifecycle tab label** | The string shown under "Properties" in the drawer header (e.g. "Library", "Tokens & themes", "Columns"). Set on `HubTable.lifecycleTabLabel`. | `packages/ui/src/components/table-properties/drawer-button.tsx` |
+| **List hub status badge** | The shared status chip + icon used everywhere status appears (table rows, board cards, list rows). Colors and icons live in `lib/list-status-badges.ts`. `surface="table"` for grid; `surface="board"` for cards. | `exxat-board-cards.mdc` |
+| **List page template** | The hub frame component. Owns the page header slot, metrics strip slot, view-tabs row, and the `renderContent(tab, updateTab)` body callback. | `packages/ui/src/components/templates/list-page.tsx` |
+| **Mono ID** | A system-generated identifier shown in `font-mono tabular-nums` so digits align and the ID is visibly distinct from prose. Mono **only** the ID token in a mixed line. | `exxat-mono-ids.mdc` |
+| **OKLCH** | The perceptually uniform color space used by the brand-tint mix and the glow tokens. Surfaces stack: page → secondary panel → sidebar. | `docs/shell-surface-elevation-pattern.md` |
+| **Pattern** | Long-form narrative that explains a UI behavior in prose: when to use it, how it composes, anti-patterns, references. Lives in `docs/*-pattern.md`. Complements (but doesn't replace) a blueprint or rule. | `docs/HANDBOOK.md` |
+| **`PrimaryPageTemplate`** | The page chrome: breadcrumbs, site header, content rail with the project's standard max-width. Wrap every primary route in this. | `apps/web/components/templates/primary-page-template.tsx` |
+| **Progressive disclosure** | The principle that complexity is exposed only when the user opts into it. KPIs default visible, filters default folded into the toolbar, conditional rules live in the Properties drawer, etc. | `docs/HANDBOOK.md` §1 |
+| **Properties drawer** | The right-side `Sheet` opened from the table toolbar, hosting view-type tiles, column visibility, density, sort, group-by, filters, conditional rules, and pagination toggle. Mounted automatically by `HubTable`. | `exxat-table-properties-drawer.mdc` |
+| **Reference page** | A canonical full implementation of a hub or pattern in `apps/web/components/*.tsx` (e.g. `columns-showcase.tsx`, `tokens-themes-client.tsx`, `library-table.tsx`). Listed in `docs/reference-implementations.md`. Copy from these before inventing. | `docs/reference-implementations.md` |
+| **Rule (binding)** | A `.cursor/rules/*.mdc` doc with MUST / MUST NOT. Binds the AI agent and the human reviewer. Wins over patterns and narratives. | `docs/HANDBOOK.md` §4 |
+| **Secondary panel** | A scoped navigation rail (e.g. "Library → All / Mine / Tree", "Tokens & themes → Colors / Radius / Motion / …") that sits between the main sidebar and the page. Opening one collapses the main sidebar; closing one restores the previous sidebar state. | `exxat-primary-nav-secondary-panel.mdc` |
+| **Site header** | The top bar on a primary route (org/product switcher + breadcrumbs + actions). Owned by `PrimaryPageTemplate`. | `apps/web/components/templates/primary-page-template.tsx` |
+| **Skill** | A `.cursor/skills/<name>/SKILL.md` (mirrored in `.claude/skills/`) workflow + checklist for a recurring agent task. Use a skill when the same checklist would be repeated across many sessions. | `apps/web/AGENTS.md` |
+| **`supportedViewTypes`** | The allowlist of `DataListViewType` values a hub implements. Passed to `HubTable.supportedViewTypes` so the Properties drawer never offers a view the hub can't render. | `packages/ui/src/components/data-views/hub-table.tsx` |
+| **Trend polarity** | `MetricItem.trendPolarity` says whether "up" is good (`higher_is_better`, default), bad (`lower_is_better`), or value-neutral (`informational`). The arrow's tint follows the polarity, not the sign. | `exxat-kpi-trends.mdc` |
+| **`useTableState`** | The state hook that owns rows, filters, search, sort, pagination, group-by, and column visibility. Always one instance per hub. | `exxat-centralized-list-dataset.mdc` |
+| **View tab** | A tab on `ListPageTemplate` representing one view of the same dataset (table, list, board, dashboard, folder, panel, tree, …). Each tab carries a `viewType` and the `renderContent` callback receives it. | `exxat-list-page-connected-views.mdc` |
+| **View type (`DataListViewType`)** | The enum of view shapes the design system supports — `"table" \| "list" \| "board" \| "dashboard" \| "folder" \| "panel" \| "tree"`. Each tab declares one. | `apps/web/lib/data-list-view.ts` |
+| **Voice & tone** | The microcopy rules for the product: empty states, errors, banners, buttons, validation. See `docs/voice-and-tone.md`. | `docs/voice-and-tone.md` |
+
+---
+
+*Missing a term? Add it. Glossary entries are short — link to the rule or pattern for depth, don't restate it here.*

package/template/docs/kpi-flat-band-pattern.md

@@ -24,7 +24,7 @@ List hubs and the main dashboard mix view use **`KeyMetrics variant="flat"`** as
 
 ## MUST NOT
 
-- Add **`--key-metrics-flat-band-linear`** back into `flatBandStyle` or hub inline styles (e.g. question-bank hub hero).
+- Add **`--key-metrics-flat-band-linear`** back into `flatBandStyle` or hub inline styles (e.g. library hub hero).
 - Use **`variant="card"`** on **`ListPageTemplate`** metrics when the design calls for a **flat strip** on the page background.
 - Duplicate KPI numbers in ad-hoc **`Card`** grids on the same hub.
 - Set **`variant="mutedSuffix"`** on product wordmarks to grey out the **suffix** in dark mode — suffix stays **Exxat pink** (`wordmarkColor`); see **`lib/product-brand.ts`**.
@@ -42,9 +42,9 @@ Dark mode (`.dark`): same rules — transparent cells, radial glow only, no line
 
 ## Reference implementations
 
-- `components/question-bank-client.tsx` — `KeyMetrics variant="flat" metricsSingleRow`
+- `components/library-client.tsx` — `KeyMetrics variant="flat" metricsSingleRow`
 - `components/dashboard-tabs.tsx` — mix view flat band + insight
-- `components/placements-client.tsx`, `team-client.tsx`, `compliance-client.tsx` — list hub metrics slot
+- `components/library-hub-client.tsx`, `columns-client.tsx`, `tokens-themes-client.tsx` — list hub metrics slot
 
 ## Insight rail (flat + side-by-side)
 

package/template/docs/kpi-trend-pattern.md

@@ -13,10 +13,23 @@
 | Field | Role |
 | --- | --- |
 | `value` | Current bucket total or rate (formatted string or number). |
-| `delta` | Human-readable delta for the selected period, e.g. `+5`, `-3`, `+12%`, `—` when no comparison. |
-| `trend` | **Visual direction** of that delta: more → `up`, less → `down`, flat / N/A → `neutral`. |
+| `delta` | **Count change for the trend chip**, e.g. `+5`, `-3`, `+12%`. Pass `""` (or `0`) when there is no comparison this period — the chip is then **hidden**, not rendered as `—`. **Never** put captions or labels like `"left + right"` here. |
+| `description` | Optional **caption** rendered **below** the value + trend row (muted, small). Use for *what* moved or *how* the value breaks down — `"left + right"`, `"vs last week"`, `"across 4 sites"`, `"scheduled for removal"`. |
+| `trend` | **Visual direction** of the delta: more → `up`, less → `down`, flat / N/A → `neutral`. Combined with an empty `delta`, `neutral` collapses the chip. |
 | `trendPolarity` | Optional. **`higher_is_better`** (default) \| **`lower_is_better`** \| **`informational`**. |
 
+### Layout
+
+```
+┌─────────────────────────────────────────────┐
+│ Pinned columns                              │  ← label
+│ 2  ↑ +1                                     │  ← value + (delta in chip)
+│ left + right                                │  ← description (caption)
+└─────────────────────────────────────────────┘
+```
+
+The **only** thing next to the arrow is the **count**. Prose lives **below** the value as a description. When there is no direction *and* no count, the chip is **suppressed** entirely (no `—` placeholder).
+
 ## Polarity cheat sheet
 
 | `trendPolarity` | Use when | Up arrow tint | Down arrow tint |
@@ -36,7 +49,9 @@
 
 - Forcing **`trend: "up"`** green because “up feels good” when the metric is **defects** or **flags** — set **`lower_is_better`** instead.
 - Hiding a worsening metric by flipping the arrow without changing **`trend`** — arrows must match the data.
-- Using **`informational`** for KPIs that **do** have an agreed quality bar — pick a polarity or omit the trend chip (`delta: "—"`, `trend: "neutral"`).
+- Using **`informational`** for KPIs that **do** have an agreed quality bar — pick a polarity instead.
+- Rendering an **empty `—`** chip just for layout symmetry. The component already hides the chip when there is no direction *and* no count; leave `delta: ""` + `trend: "neutral"` and use `description` for the supporting caption.
+- Putting captions like **`"left + right"`**, **`"hidden"`**, **`"shown"`**, **`"vs last week"`** in **`delta`**. Those are not deltas. Use **`description`**.
 
 ## Related surfaces
 

package/template/docs/large-dataset-strategy.md

@@ -0,0 +1,155 @@
+---
+title: Large dataset strategy
+---
+
+# Large dataset strategy
+
+How the Exxat DS table stack scales as record counts grow — what works today, when to
+turn pagination on, and what to add when the dataset outgrows the browser. Cross-linked
+from [`apps/web/AGENTS.md`](../AGENTS.md) and [`data-views-pattern.md`](./data-views-pattern.md).
+
+## TL;DR
+
+| Row count | What to do |
+|---|---|
+| **≤ 200** | Default `HubTable` setup. No pagination. Filter / sort all in memory. |
+| **200 – 5K** | Turn pagination on (`pagination={true}` on `HubTable`). Default page size 10–25. List + board views auto-virtualize at 100 rows via `DataRowList`. |
+| **5K – 50K** | Stay client-side with pagination, but consider adding `@tanstack/react-virtual` to the `DataTable` `<tbody>` (follow-up; see below). Filtering all rows in memory still works — `useTableState` is sub-100ms at 50K on a typical laptop. |
+| **> 50K** | Switch to **server mode**: lift filters / sort / page out of `useTableState` via `paginationOverride` and fetch one page at a time. The hub composition (`ListPageTemplate` + `HubTable` + Properties drawer) does not change. |
+
+## Today (client mode, in-memory)
+
+The default `HubTable` rendering path is fully client-side:
+
+```mermaid
+flowchart LR
+  Mock["lib/mock/* (or API on first paint)"] --> Rows["rows: TRow[] (full dataset)"]
+  Rows --> UTS["useTableState(rows, columns, sort, paginationOverride?)"]
+  UTS --> FRows["state.rows (filtered + sorted)"]
+  UTS --> PRows["state.pagedRows (sliced when pagination is on)"]
+  FRows --> DT["DataTable body (renders every row in pagedRows)"]
+  FRows --> DRL["DataRowList (auto-virtualizes at 100 rows)"]
+  FRows --> Board["ListPageBoardTemplate (virtualizes per-column)"]
+  FRows --> Dash["Dashboard charts"]
+```
+
+Key properties:
+
+1. **One row bag, every view.** Table / list / board / dashboard / folder / panel all read
+   `tableState.rows` (already filtered + sorted). No parallel arrays — see
+   [`.cursor/rules/exxat-centralized-list-dataset.mdc`](../../.cursor/rules/exxat-centralized-list-dataset.mdc).
+2. **`useTableState` is the only filter pass.** Every keystroke in the toolbar search or any
+   filter-chip change re-runs the predicate set across the full input array. This is
+   in-memory `Array.filter` / `Array.sort` — fast enough to be invisible up to ~50K rows on
+   typical hardware.
+3. **Table grid does NOT virtualize today.** When pagination is off, `DataTable` renders
+   every row in `state.rows` as a `<tr>`. With pagination on, it only renders the current
+   page — typically 10–25 rows — so DOM cost is constant regardless of the dataset size.
+4. **List + board views DO virtualize.** `DataRowList` uses `@tanstack/react-virtual` with
+   a `virtualizeThreshold` (default 100) so 5K rows in the **list** tab paint instantly
+   even without pagination. `ListPageBoardTemplate` slices per column with the same
+   threshold.
+
+## When to turn on pagination
+
+`HubTable` accepts a `pagination={true}` prop that wires:
+
+- The Properties drawer's **Show pagination** toggle.
+- `CountSyncer` so filter changes reset to page 1.
+- `PaginationBar` glued to the bottom of the table card (sticky at viewport bottom on
+  overflow).
+
+```tsx
+<HubTable
+  rows={items}
+  columns={columns}
+  pagination
+  paginationInitialPageSize={25}
+  paginationPageSizeOptions={[10, 25, 50, 100]}
+  // …
+/>
+```
+
+Rule of thumb: **once the table no longer fits on one screen, enable pagination.** That's
+typically around 100 rows for product grids with avatars / two-line cells. Below that,
+scroll-everything feels lighter than chrome.
+
+## Beyond 50K — server mode
+
+`useTableState` accepts a `paginationOverride: { page, pageSize }` so the hub owner can
+lift page state out of the table. Pair that with a `fetcher(page, pageSize, filters,
+sort) => Promise<{ rows, total }>` and you have classic server-side pagination without
+touching any DS primitive.
+
+Skeleton (planned, not implemented today):
+
+```tsx
+function MyHubClient() {
+  const [page, setPage]         = useState(1)
+  const [pageSize, setPageSize] = useState(25)
+  const [filters, setFilters]   = useState<FilterStateShape>(EMPTY_FILTERS)
+  const [sort, setSort]         = useState<SortState>(DEFAULT_SORT)
+
+  // Server fetches one page at a time, returns 25 rows + total count
+  const { data, isLoading } = useQuery({
+    queryKey: ["my-hub", page, pageSize, filters, sort],
+    queryFn:  () => fetchMyHubPage({ page, pageSize, filters, sort }),
+  })
+
+  return (
+    <HubTable
+      rows={data?.rows ?? []}
+      paginationOverride={{ page, pageSize }}
+      // …filters / sort wired the same way
+    />
+  )
+}
+```
+
+What stays the same:
+
+- `HubTable` composition (toolbar + filter chips + Properties + view tabs).
+- `ColumnDef` shape, including `filter:` blocks.
+- The Properties drawer Display / Filter / Sort / Columns / Conditional rules panels.
+
+What changes:
+
+- The filter / sort / page state is **lifted** out of `useTableState`'s internal reducer
+  and into the hub client (so it can be threaded into the fetcher).
+- A loading row state in `DataTable` (already supported via `emptyState`; we'd add a
+  skeleton variant when the data array is empty but a fetch is in-flight).
+
+## Follow-up: row virtualization for `DataTable`
+
+For "infinite scroll" dense grids (Notion / Airtable feel) without pagination, add
+`@tanstack/react-virtual` to `DataTable`'s `<tbody>`:
+
+- The package is already a dependency (used by `DataRowList`).
+- The mechanics are very similar to `DataRowList` — measure visible viewport height,
+  render only the `<tr>` rows in the visible window, padding the head/tail with empty
+  rows of the right pixel height.
+- Caveats: row pinning (left / right sticky columns) needs care; row-detail "expanded"
+  rows complicate height estimation; `groupable` rows would need flat indexing.
+
+This is documented as a follow-up. Not on the critical path because pagination handles
+the same scaling concern with simpler ergonomics.
+
+## What we do NOT do
+
+- **No infinite-scroll-by-default on the table grid.** Pagination is explicit, keyboard
+  reachable, and links well. Infinite scroll on a primary product grid hurts deep-link
+  reachability and keyboard navigation.
+- **No per-cell async hydration.** Every cell render reads from the row prop synchronously.
+  Async cell content (e.g. user avatar from a separate endpoint) is a column-level
+  concern — the column's `cell:` renderer can `useQuery` for that data, but it should not
+  block the row from painting.
+- **No client-side fetch waterfalls.** When the dataset moves to server mode, fetch the
+  page once with the filter / sort / page key. Don't fan out per-row fetches.
+
+## See also
+
+- [`exxat-data-tables.mdc`](../../.cursor/rules/exxat-data-tables.mdc) — `HubTable` is the
+  only product-data-list stack.
+- [`exxat-centralized-list-dataset.mdc`](../../.cursor/rules/exxat-centralized-list-dataset.mdc)
+  — one `useTableState` row bag, every view.
+- [`data-views-pattern.md`](./data-views-pattern.md) — connected-view architecture.

package/template/docs/library-hub-header-pattern.md

@@ -0,0 +1,25 @@
+# Library hub header — folder scope + Customize folder
+
+**Audience:** Engineers extending the library library hub (`LibraryClient`, `LibraryPageHeader`, URL scope).
+
+## Problem
+
+The library uses **`ListPageTemplate`** with multiple **view tabs** (table, panel, tree, …). **`LibraryNewFolderSheet`** (customize mode) is also used inside **`LibraryTable`** for some views (e.g. panel columns). If **Customize folder** exists only there, users on **table** or other tabs **cannot** open the sheet from a consistent chrome entry point when the URL is scoped to a folder (`?scope=folder&folderId=…`).
+
+## Pattern
+
+1. **`LibraryPageHeader`** exposes optional **`onCustomizeFolder?: () => void`**. When **`navState.scope === "folder"`** and **`navState.folderId`** is set, the hub client passes a callback that opens customize mode for the matching **`LibraryFolder`**.
+2. **`LibraryClient`** (or equivalent hub client) mounts **`LibraryNewFolderSheet`** **once** beside **`SecondaryPanelHubTemplate` / `ListPageTemplate`**, with local state for **`open`** and **`customizingFolder`**. Saving updates **`folders`** the same way as table-embedded customize flows.
+3. The header **⋯ More** menu order stays aligned with **§4.7**: **Invite people** (when collaboration variant) → **Customize folder** (when folder-scoped) → **Export** → **Show / hide metric section** (when applicable).
+
+## References
+
+| Piece | Location |
+|-------|-----------|
+| Header prop + menu item | `components/library-page-header.tsx` |
+| Client wiring + sheet | `components/library-client.tsx` |
+| URL scope | `lib/library-nav.ts` (`parseLibraryNav`, `LibraryNavState`) |
+| Sheet UI | `components/library-new-folder-sheet.tsx` |
+
+**Cursor rule:** `.cursor/rules/exxat-library-hub-header.mdc`  
+**Handbook:** `AGENTS.md` §4.6 (folder-scoped hub chrome).

package/template/docs/migrations/_template.md

@@ -55,7 +55,7 @@ node packages/ui/scripts/migrate-NNNN-<slug>.mjs
 - [ ] No remaining matches for `<old pattern>` in code search (excluding this
       migration file)
 - [ ] Visual regression sweep on affected hubs (Placements / Team /
-      Compliance / Question bank)
+      Compliance / Library)
 
 ## References