@exxatdesignux/ui 0.2.19 → 0.3.0

package/consumer-extras/handbook/voice-and-tone.md

@@ -0,0 +1,262 @@
+# Exxat DS — Voice and tone
+
+> The single biggest driver of "this feels like one product" — or "this feels random" — is **copy**. Empty states, errors, buttons, banners, validation, labels. This doc is the binding reference for all of it.
+>
+> **Audience:** designers writing copy, engineers shipping strings, AI agents drafting UI text. Reviewed in PR alongside `.cursor/rules/exxat-accessibility.mdc`.
+
+---
+
+## 1. Voice (the constant)
+
+Exxat copy is **clear, direct, and respectful**. We talk to grown professionals (faculty, admins) and to students. We never:
+
+- talk down (no "Oops!" / "Whoops" / "Uh-oh"),
+- over-celebrate ("Awesome!" / "Great job!" / 🎉),
+- guilt-trip ("You haven't… yet" / "Don't forget!"),
+- hide the cause behind metaphor ("Something went wrong" with no detail),
+- shout (sentence case everywhere; ALL CAPS only for system status acronyms).
+
+We **always**:
+
+- name the **thing**: the entity (placement, site, student), the action (Save, Invite, Export), the outcome (saved, sent, downloaded),
+- say what **changed** or what **the user can do next**,
+- use **present tense** (`Saving` / `Saved` / `Try again`), not past-aspirational (`We've saved your changes!`),
+- use **active voice** (`Exxat couldn't save the placement.` not `The placement could not be saved.`).
+
+---
+
+## 2. Tone (the variable)
+
+Tone shifts by surface. Same voice, different temperature.
+
+| Surface | Tone | Example |
+|---|---|---|
+| Primary action label | Imperative, 1–3 words | "Save", "Invite people", "Export" |
+| Empty state (filtered) | Helpful, names the filter | "No placements match the current filters. Clear them to see all 247." |
+| Empty state (no data ever) | Welcoming, names the next step | "No placements yet. Add your first one to get started." |
+| Inline validation | Neutral, says the rule | "Use the format MM/DD/YYYY." |
+| Banner (informational) | Calm, explains why | "Read-only — this term has ended." |
+| Banner (warning) | Direct, says the consequence | "Saving will overwrite 3 students' assignments." |
+| Banner (error) | Honest, names the failure + next step | "Exxat couldn't reach the placement service. Try again, or check your network." |
+| Dialog (destructive confirm) | Specific, names the object | "Delete placement P-2026-014? This cannot be undone." |
+| Microcopy (helper, hints) | Brief, format-only | "Out of 4.0", "MM/DD/YYYY" |
+
+---
+
+## 3. Buttons
+
+| Pattern | Use | Example |
+|---|---|---|
+| **Sentence case** | Always | `Save`, `Invite people`, `Export selection` |
+| **Title case** | Never | ~~`Save Changes`~~ → `Save changes` |
+| **Verb-first imperative** | Primary actions | `Save`, `Send invite`, `Create placement`, `Download CSV` |
+| **No "Please"** | The button is the request | ~~`Please save`~~ → `Save` |
+| **Don't repeat the field name** | Inline context is enough | ~~`Save changes to placement`~~ → `Save` |
+| **"Cancel" not "Discard"** | Cancel returns to a safe state; Discard is only for destructive draft loss | dialog primary = `Save changes`; cancel = `Cancel` |
+| **Loading verb** | When in-flight, swap to `…` form, preserve width | `Save` → `Saving…` |
+| **Disabled tooltip** | Always say why | "Add at least one collaborator first." |
+
+### Don't
+
+| ❌ Don't | ✅ Do |
+|---|---|
+| `Click here` | `Open placement` |
+| `OK` | `Save`, `Got it`, `Continue` (the actual outcome) |
+| `Submit` | `Send invite`, `Save changes`, `Create placement` |
+| `Yes` / `No` in destructive dialogs | `Delete placement`, `Cancel` |
+| `Loading…` for >2 s with no detail | `Loading placements…` (name the thing) |
+
+---
+
+## 4. Empty states
+
+There are **three** kinds. The copy is different for each.
+
+### 4a. Filter-empty ("zero matches")
+
+The dataset has rows; the active filters hide all of them. Tell the user the filters are responsible and offer to clear them.
+
+```
+No placements match the current filters.
+[Clear filters]
+```
+
+Rules:
+
+- Name the entity ("placements", not "items").
+- Mention "the current filters" — not just "no results".
+- Surface a **Clear filters** action if the toolbar has any filters applied.
+- If the search box is the only filter, the message becomes `No placements match "<query>".` (quote the query exactly).
+
+### 4b. True-empty ("no data ever")
+
+The dataset is empty for this user / scope. Tell them what to do next.
+
+```
+No placements yet.
+Add your first one to start tracking student rotations.
+[New placement]
+```
+
+Rules:
+
+- One-line headline + one-line context.
+- The CTA is the same imperative used elsewhere in the app — don't invent "Start now" for an empty state.
+- If creation requires a precursor ("Add at least one site first"), say so and link to the precursor.
+
+### 4c. Permission-empty ("not allowed to see")
+
+The user can't see anything because of access. Don't show counts; don't suggest creating.
+
+```
+You don't have access to this hub.
+Ask a coordinator to invite you with Viewer or higher access.
+```
+
+Rules:
+
+- Name the access level required.
+- Don't show row counts the user can't see.
+- Don't expose the existence of restricted records by mentioning "0 of N hidden".
+
+---
+
+## 5. Errors
+
+Errors must answer three questions: **What happened? Why? What can the user do?**
+
+| Element | Required? | Example |
+|---|---|---|
+| Subject | required | `Exxat couldn't save the placement.` |
+| Cause | when knowable | `The site was deleted while you were editing.` |
+| Next step | required | `Choose another site or refresh.` |
+
+### Don't
+
+- `Something went wrong.` — every word is empty. Replace with the subject + cause.
+- `Error 500: Internal Server Error.` — leak the trace ID to logs, not the user. User-facing: "Exxat had a problem. Try again in a moment."
+- Toasts for errors. Use `SystemBanner` (route-level) or inline `FormMessage` (field-level). See [`exxat-no-toast.mdc`](../../../.cursor/rules/exxat-no-toast.mdc).
+
+### Field-level (`FormMessage`)
+
+Match the rule, not the field name. Keep under 60 chars.
+
+| Rule | Message |
+|---|---|
+| Required | `This is required.` |
+| Format (date) | `Use MM/DD/YYYY.` |
+| Format (phone) | `Use +1 (555) 555-0100.` |
+| Range (number) | `Enter a number between 0 and 4.0.` |
+| Unique | `That ID is already in use.` |
+| Server | `Exxat couldn't save this field. Try again.` |
+
+---
+
+## 6. Banners
+
+We use **persistent banners** (not toasts) for all product feedback. See [`exxat-no-toast.mdc`](../../../.cursor/rules/exxat-no-toast.mdc) and `LocalBanner` / `SystemBanner` in `packages/ui`.
+
+| Variant | Use | Lead with |
+|---|---|---|
+| `info` | Read-only / scope notice / "you're viewing X" | The fact: "Read-only — this term has ended." |
+| `success` | Confirmed state change (long-lived; toasts forbidden) | The outcome: "Invite sent to 3 collaborators." |
+| `warning` | Action will cause consequence | The consequence: "Saving will overwrite 3 students' assignments." |
+| `error` | Recoverable failure | The subject + next step: "Exxat couldn't reach the placement service. Try again." |
+| `destructive` | Pending destructive change | The object + reversibility: "This term will be archived in 7 days. Restore now to keep it." |
+
+Rules:
+
+- One banner per region. If two compete, the higher-severity wins.
+- Pair a banner with an **action** when there's something the user can do (`[Restore]`, `[Try again]`, `[Open log]`).
+- No exclamation marks. The variant color carries the tone.
+
+---
+
+## 7. Status badges
+
+Status labels live in [`lib/list-status-badges.ts`](https://github.com/ExxatDesign/Exxat-DS-Workspace/blob/main/apps/web/lib/list-status-badges.ts) and are shared across every surface (table, board card, list row). Don't fork labels per page.
+
+| Type | Conventions | Example |
+|---|---|---|
+| Lifecycle | Title case, single word where possible | `Active`, `Draft`, `Archived`, `Pending` |
+| Outcome | Past-tense verb when an action completed | `Approved`, `Rejected`, `Sent`, `Skipped` |
+| Risk | Plain language, no jargon | `On track`, `At risk`, `Blocked` |
+| Mandatory pairing | Color **AND** icon (WCAG 1.4.1 — never color alone) | green check, amber triangle, red circle-x |
+
+Never: `OK`, `N/A`, `?` as a status label. Show the actual lifecycle state or `Unknown` with a tooltip describing how to resolve it.
+
+---
+
+## 8. KPI copy (the highest-stakes copy in the product)
+
+KPIs read top-down: **label → value → trend chip → description**. The reader is scanning, not reading. Each line earns its place.
+
+| Field | Rule | Example |
+|---|---|---|
+| `label` | Sentence case noun phrase. ≤ 24 chars. No "Total" prefix (the value is total by default). | `Active placements`, `New invites`, `Compliance issues` |
+| `value` | The number. Use `tabular-nums`. Round to a sensible precision. Suffix unit (`%`, `hrs`) without space when natural. | `247`, `12 %`, `38 hrs` |
+| `delta` | The **count** of change. Empty (`""` or `0`) hides the chip entirely. Never prose. | `+12`, `-3`, `+8 %` |
+| `description` | The caption beneath the value row. Prose explaining what the number is or how it splits. Never the delta. | `vs last week`, `across 4 sites`, `left + right` |
+
+See [`exxat-kpi-trends.mdc`](../../../.cursor/rules/exxat-kpi-trends.mdc) for the trend-polarity rules (when up means bad, set `trendPolarity: "lower_is_better"`).
+
+### Don't
+
+- `Total: 247` — drop "Total".
+- `247 placements` in `value` — put `247` in `value`, `placements` is in `label`.
+- `+5 (up 12 % from last week)` in `delta` — `delta = "+5"`, `description = "vs last week"`.
+
+---
+
+## 9. Form labels and helper text
+
+| Element | Rule | Example |
+|---|---|---|
+| Label | Sentence case, no colon, no "*" — pair `*` decoration with `aria-required` only. | `Date of birth` |
+| Required marker | Visible `*` (`aria-hidden`), programmatic `aria-required="true"`. | `Date of birth *` |
+| Helper text | Persistent, format-first. Use `FormDescription`. Never placeholder-only. | `MM/DD/YYYY` |
+| Placeholder | May mirror the format. Never the sole carrier. | `MM/DD/YYYY` |
+| Inline error | Replaces helper while active. Match the rule, not the field name. | `Use MM/DD/YYYY.` |
+| Unit in label vs description | Units go in description when context-dependent (`Out of 4.0` under "GPA"), in label when fixed (`Hours per week`). | — |
+
+See [`exxat-accessibility.mdc`](../../../.cursor/rules/exxat-accessibility.mdc) §"Form fields — format hints MUST be persistent".
+
+---
+
+## 10. Dates, times, numbers
+
+| Type | Format | Example |
+|---|---|---|
+| Date (UI) | Locale-aware, defaults to `MM/DD/YYYY` for en-US | `12/14/2025` |
+| Date range | Same format, en-dash with hair-thin spaces (or hyphen-minus in mono) | `12/14/2025 – 12/20/2025` |
+| Time | 12-hour with am/pm in lowercase | `2:30 pm` |
+| Relative time | Use sparingly; pair with absolute on hover/tooltip | `Updated 3 hours ago` (tip: `12/15/2025, 11:14 am`) |
+| Numbers | `tabular-nums`. Use thousands separator (`12,547`) for ≥ 4 digits | `12,547` |
+| Currency | Symbol-first, no space (`$1,200.00`) | `$1,200.00` |
+| Percent | No space (`12 %` is wrong, use `12%`) | `12%` |
+| Duration | Short form (`38 hrs`, `2 wks`) | `38 hrs` |
+
+---
+
+## 11. Reviewer checklist (paste into PRs that touch copy)
+
+- [ ] Sentence case (not title case) everywhere.
+- [ ] No `Click here`, `Submit`, `OK`, `Loading…` without a noun.
+- [ ] No toasts; banners or inline status instead.
+- [ ] Empty state names the entity and surfaces a next action or "Clear filters".
+- [ ] Errors answer: what / why / what now.
+- [ ] Status labels come from `lib/list-status-badges.ts`, not new strings.
+- [ ] KPI `delta` is a count; KPI `description` is prose. Polarity matches the metric.
+- [ ] Form helper text is `FormDescription`, not placeholder-only.
+- [ ] No exclamation marks outside `success` banners (and even those rarely).
+- [ ] No emoji unless explicitly approved for that surface.
+
+---
+
+## See also
+
+- [`HANDBOOK.md`](./HANDBOOK.md) — where this fits in the docs map
+- [`glossary.md`](./glossary.md) — vocabulary
+- [`.cursor/rules/exxat-no-toast.mdc`](../../../.cursor/rules/exxat-no-toast.mdc) — why banners, not toasts
+- [`.cursor/rules/exxat-kpi-trends.mdc`](../../../.cursor/rules/exxat-kpi-trends.mdc) — KPI delta vs description
+- [`.cursor/rules/exxat-accessibility.mdc`](../../../.cursor/rules/exxat-accessibility.mdc) — format-hint persistence rule

package/consumer-extras/patterns/command-menu-pattern.md

@@ -42,4 +42,4 @@ The command menu is the app’s **global search and AI entry**—one place to ju
 
 ---
 
-Keep this document aligned with **`exxat-ds/AGENTS.md` §7.1** when behavior or copy changes.
+Keep this document aligned with **`apps/web/AGENTS.md` §7.1** when behavior or copy changes.

package/consumer-extras/patterns/consumer-upgrade-checklist.md

@@ -25,26 +25,6 @@ The npm package includes a full Next.js reference under:
 
 Use it when you need to know **what files exist**, **how shims re-export** `@exxatdesignux/ui`, or **what AGENTS / layout** patterns look like for the current release. Porting is manual: diff template vs your repo and apply intentional changes (imports, new components, CSS entrypoints).
 
-### List-page view registry (required for data hubs)
-
-After upgrading, confirm each hub table uses **`ListPageConnectedViewBody`** (not long **`if (view === …)`** chains) and that these stay aligned:
-
-| File | Purpose |
-|------|---------|
-| `lib/data-list-view-registry.ts` | Render kinds + hub KPI strip rules |
-| `lib/<hub>-supported-views.ts` | What the hub can add/switch to |
-| `components/templates/list-page.tsx` | `supportedViewTypes` on Add view + shortcuts |
-| `components/data-views/list-page-connected-view-body.tsx` | View router |
-| `lib/hub-connected-view-renderers.ts` | **`defineHubViewRenderers(supported, { … })`** — dev warnings when a supported view has no body |
-| `components/data-views/list-page-folder-columns-panel.tsx` | Generic Miller columns for **panel** view (hub wrapper for QB colors/actions) |
-
-Pass the **same** `supportedViewTypes` array to **`ListPageTemplate`** and **`TablePropertiesDrawerButton`**. Wrap hub renderers with **`defineHubViewRenderers`**. Import **question-bank-only** tree/folder nav from hub files, not the generic **`data-views`** barrel. See **`docs/exxat-ds/data-views-pattern.md`** § “View registry and connected bodies” and **`consumer-app-pattern.md`** for the full consumer-app checklist.
-
-### Shell + sidebar (after DS token changes)
-
-- [ ] Dark mode **secondary panel** uses **`--secondary-panel-bg`** from DS globals (sidebar-accent mix) — spot-check Question bank **Library** rail.
-- [ ] Collapsed **product switcher** — **`SidebarMenuButton` `tooltip=`** + **`DropdownMenuTrigger`** only (no outer **`Tooltip`** wrapping the trigger).
-
 ## 4. Dependency and Node
 
 - Keep **`@exxatdesignux/ui`** on the same semver your team tested; prefer explicit **`^x.y.z`** or pinned **`x.y.z`**.

package/consumer-extras/patterns/data-views-pattern.md

@@ -10,17 +10,17 @@ 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/data-list-client.tsx` + `components/templates/list-page.tsx` |
-| **Table shell** (search, filter bar, sort, grouping, columns, pagination) | `DataTable`, `DataTableToolbar`, `useTableState` | `components/data-table/`, `components/data-list-table.tsx` |
-| **Properties drawer** (display, columns, filters, sort, view type tiles) | `TablePropertiesDrawer` from `@/components/table-properties` | `DrawerToolbar` / list–board shells in `data-list-table.tsx` |
-| **Board / list** | `PlacementsBoardView`, `PlacementsListView` + same `useTableState` | `DataListTable` |
+| **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` |
+| **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 `DataListClient`) | `components/team-client.tsx`, `lib/mock/team-kpi.ts` |
+| **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 |
-| **Export** | `ExportDrawer` | `ListPageTemplate` export props; `DataListClient` |
+| **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** |
 
 **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).
@@ -29,7 +29,7 @@ This document describes how list pages combine **views**, **toolbar** behavior,
 
 If the page uses a **`DataTable`** (or equivalent data grid) as the main surface, it **must** sit under **`ListPageTemplate`** so users get the **views toolbar** (tabs, add view, per-tab settings). The default `ViewTab` entries should include at least one tab whose `viewType` is **`table`** when the primary experience is tabular data. **Do not** render a `DataTable` alone under only `PageHeader` + body.
 
-- **Reference:** `DataListClient` (Placements) and `TeamClient` (Team).
+- **Reference:** `PlacementsClient` (Placements) and `TeamClient` (Team).
 - **Rationale:** Consistent navigation, saved views, per-tab view type (table / list / board), and export at the template level.
 
 ## View layout frame (centered, reusable)
@@ -38,45 +38,10 @@ Non-table view branches (e.g. **folder** icon grid, **panel** finder, OS-style f
 
 **Handbook:** **`AGENTS.md` §4.5**. **Cursor:** **`.cursor/rules/exxat-list-page-view-shells.mdc`**. **Skill:** **`.cursor/skills/exxat-list-page-view-shells/SKILL.md`**. **Do not** wrap **`DataTable`** in the frame if that stacks padding with the table toolbar (**`AGENTS.md` §5**).
 
-## View registry and connected bodies (extensibility)
-
-To add a **new view type** without breaking existing hubs:
-
-1. **Register once** — Add a tile in `lib/data-list-view.ts` (`DATA_LIST_VIEW_TILES`). Capabilities (hub KPI strip, render kind) derive automatically in `lib/data-list-view-registry.ts`.
-2. **Build the body once** — Add or extend a generic surface under `components/data-views/` (e.g. `ListPageCalendarView`). Entity-specific wiring stays in props (`getEventDate`, board `renderCard`), not a second calendar implementation per hub.
-3. **Declare what each hub supports** — `lib/<hub>-supported-views.ts` exports a `const` array; pass the same array to **`ListPageTemplate`** (`supportedViewTypes`), the hub table (`supportedViewTypes` → `TablePropertiesDrawerButton`), and rely on defaults if omitted. **Add view**, **⌘1–9** shortcuts, and **Properties → View type** tiles all use `dataListViewTilesForHub` / `dataListViewSelectionTilesForHub` so users cannot pick a view the hub never implemented.
-4. **Route in the hub table with `ListPageConnectedViewBody`** — Switch on **`getDataListViewRenderKind(view)`**, not raw `view === "…"` chains. Pass one renderer per kind the hub supports via **`defineHubViewRenderers(MY_HUB_SUPPORTED_VIEWS, { … })`** (`lib/hub-connected-view-renderers.ts`) so dev builds warn when a supported view has no body. **Do not** use a default branch that renders dashboard/KPIs; missing renderers show `ListPageViewNotConfigured`.
-5. **Let the template own hub chrome** — `ListPageTemplate` hides the metrics strip on calendar/dashboard via `showsListPageHubMetricsStrip(activeTab.viewType)`. Hub clients pass `showMetrics` only; they do not reimplement per-tab KPI visibility.
-6. **Panel / Miller columns** — Reuse **`ListPageFolderColumnsPanel`** (`components/data-views/list-page-folder-columns-panel.tsx`) for folder + record columns; hub-specific chrome (folder colors, actions) lives in a thin wrapper (e.g. `QuestionBankFolderColumnsPanel`). **Do not** export question-bank-only tree/folder nav from the generic `data-views` barrel.
-
-```tsx
-// lib/my-hub-supported-views.ts
-export const MY_HUB_SUPPORTED_VIEWS = ["table", "list", "calendar"] as const satisfies readonly DataListViewType[]
-
-// my-hub-client.tsx
-<ListPageTemplate supportedViewTypes={MY_HUB_SUPPORTED_VIEWS} showMetrics={showMetrics} … />
-
-// my-hub-table.tsx
-import { defineHubViewRenderers } from "@/lib/hub-connected-view-renderers"
-
-return (
-  <ListPageConnectedViewBody
-    view={view}
-    hubLabel="My hub"
-    renderers={defineHubViewRenderers(MY_HUB_SUPPORTED_VIEWS, {
-      "data-table": <DataTable … />,
-      "calendar-with-toolbar": toolbarShell(<ListPageCalendarView rows={tableState.rows} getEventDate={…} />),
-    })}
-  />
-)
-```
-
-**Checklist for a new view type:** registry tile → `data-views/` component → update each `*-supported-views.ts` that should expose it → add renderer in each `*-table.tsx` (via `defineHubViewRenderers`) → Properties drawer copy in `table-properties/drawer.tsx` if needed → `table-state-lifecycle` picks up types via `DATA_LIST_VIEW_TILES` (no separate allowlist).
-
 ## Architecture
 
 - **Page shell** — `ListPageTemplate` owns the views toolbar (tabs), optional metrics, and export drawer. Content for the active tab is rendered via `renderContent`.
-- **Per–lifecycle (or category) data** — `DataListTable` swaps **columns** and **row sets** based on `lifecycleTabId` (e.g. All / Upcoming / Ongoing / Completed). Each lifecycle tab gets its **own** `DataListTable` instance (`key={tab.filterId}`) so `useTableState` resets correctly when columns change.
+- **Per–lifecycle (or category) data** — `PlacementsTable` swaps **columns** and **row sets** based on `lifecycleTabId` (e.g. All / Upcoming / Ongoing / Completed). Each lifecycle tab gets its **own** `PlacementsTable` instance (`key={tab.filterId}`) so `useTableState` resets correctly when columns change.
 - **Shared table state** — `useTableState` holds sort, search, filters, grouping, column order/visibility/pins/widths, row height, gridlines, and pagination flags. **Table**, **list**, **board**, and **dashboard** all read the same state so switching view type keeps behavior aligned.
 
 ## Mock data and connected views
@@ -94,10 +59,10 @@ return (
 
 | Concern | Table | List | Board | Dashboard (view tab) |
 | --- | --- | --- | --- | --- |
-| Primary surface | `DataTable` | `PlacementsListView` / entity list | `PlacementsBoardView` / entity board | **`KeyMetrics`** (+ optional charts via shared dashboard components) |
+| Primary surface | `DataTable` | `DataRowList` + entity row body (e.g. `PlacementListRowContent`) wired via `HubTable.renderListRow` | `PlacementsBoardView` / entity board | **`KeyMetrics`** (+ optional charts via shared dashboard components) |
 | Data source | `useTableState` | **`tableState.rows`** | **`tableState.rows`** | **`tableState.rows`** via KPI helpers |
 | Column headers / labels | `showColumnLabels` | Same source columns, list layout | Phase columns + optional board column menu | N/A (metrics from same columns/filters) |
-| Row click / navigation | From `DataListTable` | From list shell | Card `onOpen` | N/A |
+| Row click / navigation | From `PlacementsTable` | From list shell | Card `onOpen` | N/A |
 | Pagination | Optional `PaginationBar` + `CountSyncer` | Same pattern | N/A (board uses phase columns) | N/A |
 
 ## Toolbar and properties
@@ -134,10 +99,10 @@ return (
 
 ## Persistence
 
-- **Page-level** (`lib/data-list-persistence.ts`, key `exxat-ds:data-list:page:v1`): `displayOptions`, `showMetrics`, `tabs`, `activeTabId`. Loaded in `DataListClient` with `useLayoutEffect`, saved debounced on change. `ListPageTemplate` runs in **controlled** mode when `tabs` / `onTabsChange` / `activeTabId` / `onActiveTabChange` are passed.
-- **Per–lifecycle tab** (key `exxat-ds:data-list:lifecycle:v1:<filterId>`): sort, search, filters, group by, column order/hidden/widths/pins/wrap, column menu search map, row height, gridlines, filter bar visibility, search popover, conditional rules, pagination toggle and page/size. Hydrated in `DataListTable` with `useLayoutEffect`; saved debounced when those fields change.
+- **Page-level** (`lib/data-list-persistence.ts`, key `exxat-ds:data-list:page:v1`): `displayOptions`, `showMetrics`, `tabs`, `activeTabId`. Loaded in `PlacementsClient` with `useLayoutEffect`, saved debounced on change. `ListPageTemplate` runs in **controlled** mode when `tabs` / `onTabsChange` / `activeTabId` / `onActiveTabChange` are passed.
+- **Per–lifecycle tab** (key `exxat-ds:data-list:lifecycle:v1:<filterId>`): sort, search, filters, group by, column order/hidden/widths/pins/wrap, column menu search map, row height, gridlines, filter bar visibility, search popover, conditional rules, pagination toggle and page/size. Hydrated in `PlacementsTable` with `useLayoutEffect`; saved debounced when those fields change.
 
-To add a new page: copy the `DataListClient` pattern (controlled `ListPageTemplate` + storage key namespace) or call `schedulePageSave` / `scheduleLifecycleSave` with your own keys.
+To add a new page: copy the `PlacementsClient` pattern (controlled `ListPageTemplate` + storage key namespace) or call `schedulePageSave` / `scheduleLifecycleSave` with your own keys.
 
 ## Rules of thumb
 
@@ -181,13 +146,11 @@ Reference: `components/placements-page-header.tsx`, `components/team-page-header
 
 **When to use a new page (route):** The flow is **primary**, **long-form**, **multi-step**, or should have its **own URL** / bookmark / history **without** the parent page behind it — e.g. full create/edit, wizards, or detail that *is* the task.
 
-**Focused workflow shell:** For dedicated create/edit, wizards, and sectioned settings, use **`FocusedWorkflowPageTemplate`** + layouts in **`focused-workflow-layouts.tsx`** — see **`docs/focused-workflow-page-pattern.md`** and **`AGENTS.md` §14**. **Not** for list hubs (**`ListPageTemplate`**) or Miller-column explorers.
-
-**Rule of thumb:** **Context + quick** → **drawer**; **blocking short choice** → **dialog**; **primary / long / wizard / settings** → **focused workflow route** (or other dedicated page).
+**Rule of thumb:** **Context + quick** → **drawer**; **blocking short choice** → **dialog**; **otherwise** → **new page**.
 
 **Modal vs side panel (same route):** When the overlay stays on the same URL, prefer **`docs/drawer-vs-dialog-pattern.md`** and **`.cursor/rules/exxat-drawer-vs-dialog.mdc`** — drawers keep the hub visible; dialogs trap focus for confirms.
 
-Canonical rules: **`AGENTS.md` §6.4**, **§14**, root **`.cursor/rules/exxat-page-vs-drawer.mdc`**, **`.cursor/rules/exxat-drawer-vs-dialog.mdc`**, **`.cursor/rules/exxat-focused-workflow-page.mdc`**.
+Canonical rules: **`AGENTS.md` §6.4**, root **`.cursor/rules/exxat-page-vs-drawer.mdc`**, **`.cursor/rules/exxat-drawer-vs-dialog.mdc`**.
 
 ---
 
@@ -195,7 +158,7 @@ Canonical rules: **`AGENTS.md` §6.4**, **§14**, root **`.cursor/rules/exxat-pa
 
 When a route is a **primary** destination in nav (main hub for an entity) **and** the dataset is **large** or **highly interactive**:
 
-- Use the **primary page template**: `ListPageTemplate` (tabs, metrics strip, export drawer at template level) + data client pattern as in **`DataListClient`** / **`DataListTable`** — not a minimal `PageHeader`-only layout.
+- Use the **primary page template**: `ListPageTemplate` (tabs, metrics strip, export drawer at template level) + data client pattern as in **`PlacementsClient`** / **`PlacementsTable`** — not a minimal `PageHeader`-only layout.
 - Smaller satellite pages may use **`PageHeader` + section content**; once the dataset grows past the dense-list threshold, add the toolbar rules above and consider promoting to the full template if the page becomes a main hub.
 
 ---
@@ -207,7 +170,7 @@ When a route is a **primary** destination in nav (main hub for an entity) **and*
 - [ ] **>10 items** → search, filter, sort, properties (per surface type above).
 - [ ] **Has data to export** → **More** menu with **Export** + shared `ExportDrawer` pattern.
 - [ ] **Primary + large / main hub** → `ListPageTemplate`-style shell where applicable.
-- [ ] **Page vs drawer vs dialog (§6.4)** — Quick with parent **context** → drawer/sheet; **blocking** confirm → **dialog**; primary or long flows → **focused workflow route** (`docs/focused-workflow-page-pattern.md`, **§14**) or other dedicated page (`docs/drawer-vs-dialog-pattern.md`).
+- [ ] **Page vs drawer vs dialog (§6.4)** — Quick with parent **context** → drawer/sheet; **blocking** confirm → **dialog**; primary or long flows → **new route** (`docs/drawer-vs-dialog-pattern.md`).
 - [ ] **Primary button** → `Button` default variant (`size="lg"` for parity with Placements), not outline.
 - [ ] **Dashboard view tab** → `KeyMetrics` + shared KPI helpers from **`tableState.rows`**; no duplicate one-off metric cards.
 - [ ] **Data view charts** → `ChartFigure` + `chart-keyboard-selection`; layout persistence via **`data-view-dashboard-storage`** (see `AGENTS.md` §4.3).

package/consumer-extras/patterns/shell-surface-elevation-pattern.md

@@ -1,7 +1,7 @@
 # Shell surface elevation (sidebar · secondary panel · page)
 
 > **Tokens:** `app/globals.css` — `--sidebar`, `--secondary-panel-bg`, `--background`, `--brand-tint*`.  
-> **Shell:** `components/templates/nested-secondary-panel-shell.tsx` — `bg-secondary-panel-bg` + `[data-slot="secondary-panel"]` rule in `globals.css`.  
+> **Shell:** `components/templates/nested-secondary-panel-shell.tsx` — `bg-[var(--secondary-panel-bg)]`.  
 > **Cursor:** `.cursor/rules/exxat-primary-nav-secondary-panel.mdc` · `.cursor/skills/exxat-primary-nav-secondary-panel/SKILL.md`
 
 ## Stack (back → front)
@@ -24,16 +24,14 @@
 ## OKLCH formulas (dark)
 
 ```css
---secondary-panel-bg: color-mix(in oklch, var(--background) 32%, var(--sidebar-accent) 68%);
+--secondary-panel-bg: color-mix(in oklch, var(--card) 32%, var(--brand-tint) 68%);
 ```
 
-**Do not** mix with light-mode **`--brand-tint`** in dark — product theme classes keep a light **`--brand-tint`** for logos/KPI glow; the secondary rail must use **`--sidebar-accent`** so the Library panel stays on-hue and dark.
-
 Per-product **dark** theme blocks (`.theme-one.dark`, `.theme-prism.dark`, …) set **`--brand-tint-light`** where needed so mixes stay on-hue.
 
 ## Implementation
 
-- **`NestedSecondaryPanelShell`** — `bg-secondary-panel-bg` (token + `[data-slot="secondary-panel"][data-state="open"]` in `globals.css`), `border-sidebar-border` (not generic `ring-border` alone).
+- **`NestedSecondaryPanelShell`** — `bg-[var(--secondary-panel-bg)]`, `ring-sidebar-border` (not generic `ring-border` alone).
 - **Do not** set secondary panel to `bg-sidebar` (same as level 0 — loses elevation).
 - **Do not** use `color-mix(… var(--sidebar) …)` without brand tokens if it drifts from active product theme.
 

package/dist/components/data-table/filter-date-calendar.d.ts

@@ -0,0 +1,10 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+
+/** Single-date calendar for table filters (YYYY-MM-DD). */
+declare function FilterDateCalendar({ valueYmd, onChangeYmd, label, }: {
+    valueYmd: string | undefined;
+    onChangeYmd: (ymd: string | undefined) => void;
+    label: string;
+}): react_jsx_runtime.JSX.Element;
+
+export { FilterDateCalendar };