@mieweb/ui 0.11.0-dev.55 → 0.11.0-dev.56

package/agent/README.md

@@ -22,8 +22,8 @@ governing spec: later tickets cite it instead of re-deciding.
 | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [mieweb-ui.instructions.md](mieweb-ui.instructions.md) | The rules template. Copied verbatim to the consumer's `.github/instructions/` (VS Code Copilot auto-applies it via the `applyTo` frontmatter) and embedded, minus frontmatter, in a marked block in the consumer's `AGENTS.md` (the cross-tool convention).                                                       |
 | [init-agent.mjs](init-agent.mjs)                       | The `mieweb-ui` bin. Idempotent — rerun after upgrading `@mieweb/ui` to refresh all targets. `--experimental-agents` additionally installs the agent team below.                                                                                                                                                  |
-| [agents/](agents/)                                     | Agent templates: `mieweb-ui-design` (orchestrator) + `mieweb-ui-styling` + `mieweb-ui-install` + `mieweb-ui-a11y` + `mieweb-ui-i18n` + `mieweb-ui-migration` + `mieweb-ui-richtext`. Installed to the consumer's `.github/agents/` behind `--experimental-agents`.                                                 |
-| [skills/](skills/)                                     | Skill templates: `mieweb-ui-catalog`, `mieweb-ui-tokens`, `mieweb-ui-icons` (generated — `pnpm agent:skills`, never hand-edit) + `mieweb-ui-brands`, `mieweb-ui-tailwind4`, `mieweb-ui-a11y-checklist`, `mieweb-ui-i18n-checklist`, `mieweb-ui-kerebron` (hand-written). Installed to `.github/skills/` behind `--experimental-agents`. |
+| [agents/](agents/)                                     | Agent templates: `mieweb-ui-design` (orchestrator) + `mieweb-ui-styling` + `mieweb-ui-install` + `mieweb-ui-a11y` + `mieweb-ui-i18n` + `mieweb-ui-migration` + `mieweb-ui-richtext` + `mieweb-ui-grids`. Installed to the consumer's `.github/agents/` behind `--experimental-agents`.                               |
+| [skills/](skills/)                                     | Skill templates: `mieweb-ui-catalog`, `mieweb-ui-tokens`, `mieweb-ui-icons` (generated — `pnpm agent:skills`, never hand-edit) + `mieweb-ui-brands`, `mieweb-ui-tailwind4`, `mieweb-ui-a11y-checklist`, `mieweb-ui-i18n-checklist`, `mieweb-ui-kerebron`, `mieweb-ui-datavis-api` (hand-written). Installed to `.github/skills/` behind `--experimental-agents`. |
 | `evals/` _(Phase 2+)_                                  | Golden-question eval sets per specialist; the regression harness for agent knowledge.                                                                                                                                                                                                                             |
 
 Rule content is sourced from [lessons/component-policy.md](../lessons/component-policy.md);

package/agent/agents/mieweb-ui-design.agent.md

@@ -27,6 +27,10 @@ handoffs:
     agent: MIE UI Rich Text Agent
     prompt: Handle the rich-text question above (Kerebron editors, install legs, WASM/patches, collaboration, markdown round-trip, EmailEditor) and report the minimal fix.
     send: false
+  - label: Grids & eSheet
+    agent: MIE UI Grids Agent
+    prompt: Handle the grid/eSheet question above (DataVis NITRO sources, columns, features, operations, eSheet Builder/Renderer) and report the minimal fix.
+    send: false
 ---
 
 # MIE UI Design Agent (orchestrator)
@@ -65,8 +69,9 @@ comparison tables) and `mieweb-ui-icons` (icon aliases and conventions):
 | translations, locale bundles, Intl formats, RTL      | MIE UI i18n Agent      |
 | migrating code to @mieweb/ui, raw-HTML compliance    | MIE UI Migration Agent |
 | rich text editors (RichEditor, TextAreaRich, EmailEditor), Kerebron peers/WASM/patches, collab, Markdown rendering | MIE UI Rich Text Agent |
+| DataVis NITRO config (sources, columns, features, operations), eSheet Builder/Renderer, grid debugging | MIE UI Grids Agent |
 
-More specialists (Grids, DataVis, Views,
+More specialists (DataVis, Views,
 SuperChat) land in later phases; until one ships, answer its domain
 from the skills and the component docs, or defer (below).
 

package/agent/agents/mieweb-ui-grids.agent.md

@@ -0,0 +1,87 @@
+---
+name: MIE UI Grids Agent
+description: Grids specialist for the @mieweb/ui design system — DataVis NITRO (DataVisNitroSource/Grid/Graph, column API, feature flags, grouping/aggregates, operations palette, perspectives) and the eSheet form pair (Builder/Renderer, clinical fields, EncounterVisit). Invoke for configuring or debugging a NITRO grid or graph, source/column/feature questions, row selection and mass operations, grid performance with large datasets, AGGrid deprecation questions, and eSheet Builder/Renderer integration.
+tools: ['search', 'codebase', 'fetch', 'runInTerminal']
+handoffs:
+  - label: Apply Fixes
+    agent: agent
+    prompt: Apply the grid/eSheet integration fixes identified above to the codebase.
+    send: false
+---
+
+# MIE UI Grids Agent
+
+You are the grids specialist for the **@mieweb/ui** design system. Consumers
+come to you after they have a grid (or know they need one) — to configure
+columns, sources and features, to wire selection and mass operations, to
+debug an empty or misbehaving grid, and to integrate the eSheet
+Builder/Renderer pair. You diagnose from evidence and report a minimal fix —
+you do not edit files (offer the **Apply Fixes** handoff instead).
+
+## Your sources of truth (never inline-duplicate them)
+
+- **`mieweb-ui-datavis-api` skill** — the domain bible: the grid policy,
+  Source/Grid/Graph architecture and context coupling, source types
+  (`http`/`local`/`file`) and declarative `groupBy`/`aggregates`, the curated
+  grid props (chrome, columns, features, operations, perspectives), the
+  no-virtualization reality, orders-grid composition patterns, the eSheet
+  pair and clinical fields, and the symptom→fix troubleshooting table. Start
+  every answer here.
+- **`mieweb-ui-catalog` skill** — entry points, the Grids family "Which one?"
+  table, and per-entry peer requirements.
+- **`mieweb-ui-kerebron` skill** — when EncounterVisit's RichEdit mode or
+  eSheet narrative fields drag in the Kerebron editor stack.
+
+## Workflow
+
+1. **Enforce the policy before configuring.** Any plain `<table>` growing
+   sort/filter/page/export features, any new `AGGrid` usage, or `Pagination`
+   bolted onto a NITRO grid is the real finding — redirect to NITRO first,
+   then configure.
+2. **Check the coupling before the props.** An empty or dead grid is usually
+   structural: Grid/Graph not nested inside a `DataVisNitroSource`, a
+   `local` source whose global isn't set at mount, or `datavis-ace` failing
+   to resolve.
+3. **Prefer declarative configuration.** `groupBy`/`aggregates` on the
+   Source, `features`/`columns`/`operations` on the Grid. Imperative
+   `setGroup`/`setAggregate` through `DataVisNitroContext` is library-internal
+   composition, not consumer API.
+4. **Be honest about limits.** There is no row virtualization and no
+   server-side row model — all operations run client-side over the fetched
+   dataset. For very large data, the fix is upstream (serve less, group,
+   aggregate), not a grid prop. Treat genuine capability gaps as NITRO
+   feature requests, never as a reason to reach for AGGrid.
+5. **Match the skill's troubleshooting table**, then report root cause,
+   evidence, and the smallest fix. Offer **Apply Fixes** for the edit.
+
+## Redirects
+
+- "Which component should I use?" → **MIE UI Design Agent** (selection is the
+  orchestrator's domain; you own configuration, APIs and debugging of a
+  chosen grid).
+- Install plumbing — Tailwind setup, `styles.css`, peer errors outside
+  `datavis-ace`/`@esheet/*` → **MIE UI Install Agent**.
+- Token/Tailwind/brand theming of surrounding UI → **MIE UI Styling Agent**.
+- Grid accessibility audits → **MIE UI A11y Agent** — but always carry the
+  caveat yourself: the engine's DOM is not screen-reader friendly; keep
+  critical actions reachable outside the grid.
+- Charts beyond the NITRO Graph (YChart, Deck, Globe, maps) → the DataVis
+  specialist once it ships; until then the orchestrator answers from the
+  catalog skill.
+
+## Rules
+
+1. Never invent grid props, feature flags, or engine capabilities — the grid
+   surface is deliberately curated; verify against the skill or the installed
+   types before recommending a prop.
+2. `AGGrid` is deprecated: never recommend it for new work; when NITRO lacks
+   a capability, say so and point to filing a NITRO feature request.
+3. Never tell a consumer to call `setGroup`/`setAggregate` on
+   `DataVisNitroContext` — declarative props only.
+4. eSheet Builder/Renderer never persist — storage always lives with the
+   host. Submission is either the Renderer's opt-in `onSubmit` button or a
+   host-driven `getValidResponse()` read (which returns
+   `{ response, errors }`, not a bare `FormResponse`) — never both.
+5. Prefer the smallest change that fixes the root cause; no grid rewrites.
+6. The installed `mieweb-ui.instructions.md` rules apply to any code you
+   recommend.

package/agent/evals/README.md

@@ -21,6 +21,7 @@ These files are maintainer-side quality tooling. They are **not** shipped by
 | [i18n.md](./i18n.md)           | Internationalization / RTL           | MIE UI i18n Agent      |
 | [migration.md](./migration.md) | Migration / compliance (incl. icons) | MIE UI Migration Agent |
 | [richtext.md](./richtext.md)   | Rich text / Kerebron editors         | MIE UI Rich Text Agent |
+| [grids.md](./grids.md)         | DataVis NITRO + eSheet grids         | MIE UI Grids Agent     |
 
 ## Entry format
 

package/agent/evals/grids.md

@@ -0,0 +1,241 @@
+# Evals — DataVis NITRO + eSheet grids
+
+Primary agent: **MIE UI Grids Agent**. See [README.md](./README.md) for
+format and scoring. Selection-level grid questions (Table vs NITRO) live in
+[selection.md](./selection.md); these cover configuration, APIs and
+debugging of a chosen grid.
+
+### GRD-1 — Minimal NITRO setup
+
+- **Ask:** "What's the minimal code to show a sortable, filterable grid over a JSON endpoint?"
+- **Expect:** `DataVisNitroGrid` nested inside
+  `<DataVisNitroSource type="http" url="…">` from `@mieweb/ui/datavis`;
+  parsing/type-inference automatic; sort/filter/group/export come from the
+  engine. No extra installs (`@mieweb/datavis` is bundled, `datavis-ace`
+  arrives as a dependency) and no extra CSS (base stylesheet already imports
+  the datavis styles).
+- **Agent:** MIE UI Grids Agent
+- **Source:** agent/skills/mieweb-ui-datavis-api/SKILL.md — Architecture/Source; DataVisNITRO MAINTAINERS.md
+
+### GRD-2 — Empty grid, no error
+
+- **Ask:** "My DataVisNitroGrid renders nothing and the console is clean."
+- **Expect:** Structural first: the Grid must render **inside** a
+  `DataVisNitroSource` (they're coupled through `DataVisNitroContext`); for
+  `type="local"`, `window[varName]` must be set (shaped `{ typeInfo, data }`)
+  before mount.
+- **Agent:** MIE UI Grids Agent
+- **Source:** datavis-api skill — troubleshooting; DataVisNitro.tsx
+
+### GRD-3 — Source is not a constructor
+
+- **Ask:** "I get `datavis_ace.Source is not a constructor` at runtime."
+- **Expect:** `datavis-ace` is a hard runtime requirement of
+  `DataVisNitroSource`, shipped as a regular dependency of `@mieweb/ui`
+  (external in the bundle) — it's missing or mis-resolved. Reinstall / check
+  `pnpm why datavis-ace`; never import it directly or add it manually as a
+  workaround.
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataVisNITRO MAINTAINERS.md — Dependencies
+
+### GRD-4 — Local data without a server
+
+- **Ask:** "How do I feed an in-memory array of rows to a NITRO grid?"
+- **Expect:** `type="local"` + `varName`: set
+  `window[varName] = { typeInfo, data }` before mounting and delete it on
+  unmount; the engine reads the global. Changing `varName` rebuilds the
+  source.
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataVisNitro.tsx — LocalDataVisNitroSourceProps; demo stories LocalDataset
+
+### GRD-5 — Column API
+
+- **Ask:** "How do I pin a column, set a header label, and render HTML in cells?"
+- **Expect:** `columns` on the grid: string = bare field name; object form
+  `{ field, header, pinned, allowHtml, … }` (plus
+  width/minWidth/maxWidth, visible, align, className,
+  typeInfo/sortable/filterable).
+- **Agent:** MIE UI Grids Agent
+- **Source:** nitro-columns.ts — DataVisNitroColumn; table/types.ts — TableColumn
+
+### GRD-6 — Grouping declaratively
+
+- **Ask:** "I'm calling `view.setGroup(…)` through DataVisNitroContext to group my grid — is that right?"
+- **Expect:** No — configure declaratively via the Source's
+  `groupBy={[ 'status' ]}` (or `{ field, functionName }`) and `aggregates`
+  (`{ functionName, fields }`). Imperative context calls are
+  library-internal composition (e.g. `OrdersGroupPresets`), not consumer
+  API, and fight the declarative props.
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataVisNITRO MAINTAINERS.md — gotchas; datavis-api skill — Source
+
+### GRD-7 — Checkbox selection + bulk actions
+
+- **Ask:** "Users need to select multiple rows and run a bulk delete."
+- **Expect:** `features={{ rowSelection: 'checkbox' }}` (tri-state select-all
+  over the currently filtered rows) + an `operations` array —
+  `{ label, icon?, category?, callback(ctx) }` with `ctx.rows` as the
+  selection; surfaces in the operations palette. `onSelectionChange` for
+  host-side tracking.
+- **Agent:** MIE UI Grids Agent
+- **Source:** table/types.ts — TableFeatures; DataVisNITRO.stories.tsx — Operations
+
+### GRD-8 — Feature flags inventory
+
+- **Ask:** "What built-in behaviours can I toggle on the grid without custom code?"
+- **Expect:** `features`: columnResize, columnReorder, stickyHeaders,
+  rowSelection (true | 'checkbox'), headerContextMenu, zebraStripe,
+  keyboardNav (j/k), drillDown, showMore, rowMode ('wrapped' | 'clipped').
+  Not an invented list — anything else needs verification against the types.
+- **Agent:** MIE UI Grids Agent
+- **Source:** table/types.ts — TableFeatures
+
+### GRD-9 — Virtualization
+
+- **Ask:** "How do I turn on row virtualization for my 50k-row grid?"
+- **Expect:** You can't — the engine has **no row virtualization**; `height`
+  + show-more/limit is the scrolling story. For very large data, fix it
+  upstream: serve a narrower dataset at the http `url`, group/aggregate, or
+  page before the grid. Honest-limit answers pass; invented virtualization
+  props FAIL.
+- **Agent:** MIE UI Grids Agent
+- **Source:** datavis-api skill — Grid chrome/troubleshooting (verified: no virtualization in packages/datavis)
+
+### GRD-10 — Server-side rows?
+
+- **Ask:** "Does NITRO support a server-side row model like AG Grid Enterprise?"
+- **Expect:** No — `type="http"` fetches the dataset and **all operations run
+  client-side** over it. The server-side pattern is serving the right
+  dataset at `url`. No new AGGrid usage either (deprecated); a genuine gap
+  is a NITRO feature request.
+- **Agent:** MIE UI Grids Agent
+- **Source:** datavis-api skill — Source; MAINTAINERS.md — Prefer NITRO over AGGrid
+
+### GRD-11 — Detail rows
+
+- **Ask:** "Can a row expand to show a full-width detail panel?"
+- **Expect:** `renderDetailRow` (adds a disclosure toggle per plain-mode row)
+  + `detailRowsExpanded` to expand/collapse all; leave undefined for per-row
+  control.
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataGrid.tsx — renderDetailRow/detailRowsExpanded
+
+### GRD-12 — Minimal chrome
+
+- **Ask:** "I want the grid without the title bar — just the table with a floating menu."
+- **Expect:** `mode="minimal"` (floating hamburger over the table);
+  `minimalMode` is deprecated in its favor. `'full'` restores the classic
+  title bar with row count and inline buttons; `titleActions` adds custom
+  title-bar controls (hidden in minimal mode).
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataGrid.tsx — mode/minimalMode/titleActions
+
+### GRD-13 — Perspectives on shared devices
+
+- **Ask:** "We deploy on shared kiosk machines — users' pinned grid views are leaking between logins."
+- **Expect:** Pinned-perspective names persist to localStorage by default;
+  set `persistPinnedPerspectives={false}` so pins stay in memory for the
+  session.
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataGrid.tsx — persistPinnedPerspectives
+
+### GRD-14 — Grid + chart over one fetch
+
+- **Ask:** "A dashboard needs the same records as a grid and a chart the user can reconfigure — do I fetch twice?"
+- **Expect:** No — Grid and Graph are two renderers over the same
+  `DataVisNitroSource`/view; render `DataVisNitroGraph`
+  (`config`/`onConfigChange` for user-changed axes/chart type) beside the
+  grid inside one Source. Tiny inline trend → `Sparkline` instead.
+- **Agent:** MIE UI Grids Agent
+- **Source:** Grids.mdx — How they fit together; DataVisNitroGraph.tsx
+
+### GRD-15 — i18n of the grid
+
+- **Ask:** "How do I localize the grid's labels and number/date formats?"
+- **Expect:** `locale` (BCP-47) drives number/date formatting;
+  `DataVisNitroLanguageSelector` switches the engine's own UI language
+  (toolbar/table strings). `trans` only customizes built-in
+  grouping-function labels — answers presenting it as a general grid
+  translator FAIL. Deeper string audits → i18n agent.
+- **Agent:** MIE UI Grids Agent
+- **Source:** DataVisNitro.tsx — trans/locale; stories LocalizedGrid
+
+### GRD-16 — Grid accessibility
+
+- **Ask:** "Is the NITRO grid screen-reader accessible?"
+- **Expect:** Honest caveat: the engine's DOM is **not** screen-reader
+  friendly and automated a11y checks are disabled on the NITRO pages. Keep
+  critical actions reachable outside the grid; provide textual summaries for
+  charts. Full audit → A11y agent.
+- **Agent:** MIE UI Grids Agent
+- **Source:** Grids.mdx — Shared limitations
+
+### GRD-17 — Hover row actions
+
+- **Ask:** "I need per-row edit/delete buttons that appear on hover, consistent with our Table rows."
+- **Expect:** `RowActionToolbar` (main barrel) with `group="grid"` composes
+  with NITRO cells — same component as `Table` rows use.
+- **Agent:** MIE UI Grids Agent
+- **Source:** Grids.mdx — How they fit together
+
+### GRD-18 — Pagination on a NITRO grid
+
+- **Ask:** "Which component adds page controls under my NITRO grid?"
+- **Expect:** None — `Pagination` is for server-paged `Table`/card lists;
+  rows already in a NITRO grid never need it (filter/group/show-more replace
+  paging).
+- **Agent:** MIE UI Grids Agent
+- **Source:** Grids.mdx — Which one? (Pagination row)
+
+### GRD-19 — eSheet pair contract
+
+- **Ask:** "How do Builder and Renderer hand data to each other, and where's the submit button?"
+- **Expect:** Builder `onChange` emits a `FormDefinition`; Renderer takes it
+  as `formDataInput`. Reading answers: the ref's `getValidResponse()`
+  returns `{ response: FormResponse | null, errors }` (store `response`, not
+  the wrapper), or opt into the built-in submit button via
+  `onSubmit`/`submitLabel`. Persistence is host-owned either way. Entry
+  `@mieweb/ui/esheet` needs **all four** matching `@esheet/*` peers
+  (`core`/`fields`/`builder`/`renderer`, `>=0.0.6-17`) even for
+  renderer-only use.
+- **Agent:** MIE UI Grids Agent
+- **Source:** CompositeForms.mdx — the eSheet pair; src/esheet.ts
+
+### GRD-20 — Clinical fields unknown
+
+- **Ask:** "My eSheet definition uses `medicationList` but the Renderer shows an unknown field type."
+- **Expect:** Call `registerMieEsheetFields()` once before rendering
+  definitions that use the Healthcare list fields (`medicationList`,
+  `allergyList`, …) — it plugs them into both Builder and Renderer.
+- **Agent:** MIE UI Grids Agent
+- **Source:** src/esheet.ts; CompositeForms.mdx — two install surfaces
+
+### GRD-21 — EncounterVisit RichEdit stack
+
+- **Ask:** "EncounterVisit's RichEdit mode won't load in my app — what does it need beyond @esheet?"
+- **Expect:** RichEdit rides the Kerebron editor: the `@kerebron/*` peers at
+  exactly 0.8.12 + ProseMirror overrides, `@mieweb/ui/kerebron.css`, and the
+  WASM assets at `/kerebron-wasm` — the full kerebron-skill install legs
+  (route depth to the Rich Text agent / kerebron skill).
+- **Agent:** MIE UI Grids Agent
+- **Source:** src/esheet.ts header; MIGRATION.md — eSheet and EncounterVisit
+
+### GRD-22 — AGGrid escape hatch
+
+- **Ask:** "NITRO doesn't do X that AG Grid does — can I use `@mieweb/ui/ag-grid` for this one grid?"
+- **Expect:** No — `AGGrid` is deprecated, never for new work. Treat the gap
+  as a NITRO feature request (file an issue) so usages can move back; the
+  maintainers' stated policy is to close gaps in NITRO, not fall back.
+- **Agent:** MIE UI Grids Agent
+- **Source:** MAINTAINERS.md — Prefer NITRO over AGGrid; Grids.mdx policy
+
+### GRD-23 — Orders grids as the pattern
+
+- **Ask:** "We're building an order-history grid with group-by chips and bulk status updates — is there prior art?"
+- **Expect:** `ChartOrdersGrid`/`EncounterOrdersGrid` (datavis entry) over
+  the HealthSurveillance order history, with `OrdersGroupPresets` chips and
+  native NITRO `rowSelection: 'checkbox'` + `operations` for mass updates;
+  pure row builders (`buildChartOrderRows`/`buildEncounterOrderRows`) in the
+  main entry. Copy the composition, don't re-implement it.
+- **Agent:** MIE UI Grids Agent
+- **Source:** src/datavis.ts; ordersGridShared.tsx

package/agent/skills/mieweb-ui-datavis-api/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: mieweb-ui-datavis-api
+description: Deep API reference for @mieweb/ui grids — DataVis NITRO (DataVisNitroSource/Grid/Graph, column API, feature flags, grouping/aggregates, operations palette, perspectives) and the eSheet form pair (Builder/Renderer, registerMieEsheetFields, EncounterVisit). USE WHEN configuring or debugging a NITRO grid or graph, choosing columns/features/sources, wiring row selection and mass operations, grouping or aggregating, or integrating eSheet Builder/Renderer and its clinical fields.
+---
+
+# DataVis NITRO + eSheet in @mieweb/ui
+
+Sourced from `src/catalog/Grids.mdx`, `CompositeForms.mdx`, the DataVisNITRO
+MAINTAINERS notes, `packages/datavis` source and `MIGRATION.md`. Grid
+*selection* policy lives in the catalog skill; this is the configuration/API
+layer.
+
+## Policy (non-negotiable)
+
+> **Tables and data grids start with DataVis NITRO.** Use `Table` only for a
+> few static rows the user will not sort, filter, page or export. Never
+> hand-roll grid features on a plain table; `AGGrid` is deprecated.
+
+`Pagination` is for server-paged `Table`/card lists only — rows already in a
+NITRO grid never need it.
+
+## Architecture
+
+- Entry: **`@mieweb/ui/datavis`** — exports `DataVisNitroSource`,
+  `DataVisNitroGrid`, `DataVisNitroGraph`, `DataVisNitroContext`,
+  `DataVisNitroLanguageSelector`, plus `ChartOrdersGrid`/`EncounterOrdersGrid`
+  and `OrdersGroupPresets`.
+- **Two moving parts, zero consumer installs:** `@mieweb/datavis` (the
+  engine's React surface) is **bundled into** the entry; `datavis-ace` (the
+  data engine: fetch/parse/type-inference/aggregation) is a regular
+  **dependency** of `@mieweb/ui` — consumers never install or import either.
+- **Source and Grid are coupled through React context:** a `DataVisNitroGrid`
+  must render inside a `DataVisNitroSource` (which creates the source/view
+  pair and publishes it through `DataVisNitroContext`). **Grid** and
+  **Graph** are two renderers over the same source — a dashboard flips
+  between rows and a chart without refetching.
+- Styles: the base `@mieweb/ui/styles.css` already imports
+  `@mieweb/datavis/styles.css` — no extra CSS wiring.
+
+## DataVisNitroSource
+
+```tsx
+<DataVisNitroSource type="http" url="/api/orders.json" groupBy={['status']}>
+  <DataVisNitroGrid title="Orders" />
+</DataVisNitroSource>
+```
+
+- `type: 'http'` — `url` is fetched by the engine; parsing and type inference
+  are automatic. **All grid operations (sort/filter/group/aggregate) run
+  client-side** over the fetched dataset — there is no server-side row model;
+  the "server-side pattern" is serving the right dataset at `url`.
+- `type: 'local'` — `varName` names a global: set
+  `window[varName] = { typeInfo, data }` **before** mounting (the engine
+  reads it from `globalThis`); clean it up on unmount.
+- `type: 'file'` — user-supplied file (the engine's file picker/parse path).
+- `groupBy?: Array<string | { field, functionName? }>` and
+  `aggregates?: Array<{ functionName, fields }>` configure grouped/aggregated
+  views **declaratively**. Do not reach into `DataVisNitroContext` to call
+  `setGroup`/`setAggregate` — that context is for the library's own
+  composition (e.g. `OrdersGroupPresets`), not the consumer API.
+- Changing `type`/`url`/`varName` rebuilds the source; changing
+  `groupBy`/`aggregates` reconfigures the live view.
+
+## DataVisNitroGrid
+
+A curated surface over the engine's `DataGrid` (the maintainers deliberately
+`Omit` `view`/`children`/`allColumns` and re-add a vetted set — do not assume
+an upstream `DataGrid` prop exists here without checking the types):
+
+- **Chrome:** `title`, `helpText`, `titleActions` (title-bar React nodes),
+  `mode: 'default' | 'full' | 'minimal'` (`minimalMode` is deprecated — use
+  `mode="minimal"`), `showToolbar`, `showControls`, `height` (CSS value —
+  this plus the engine's show-more/limit is the scrolling story; **there is
+  no row virtualization**, so cap very large result sets at the source).
+- **Columns:** `columns?: Array<string | TableColumn>` — a bare string is a
+  field name; the object form is
+  `{ field, header, width/minWidth/maxWidth, visible, pinned, align,
+  className, allowHtml, typeInfo: { type, format }, sortable, filterable }`.
+  Column menus, pinning, resize/reorder persistence and saved
+  **perspectives** come from the engine (`prefs`,
+  `persistPinnedPerspectives={false}` for shared/public devices).
+- **Features** (`features?: TableFeatures`): `columnResize`, `columnReorder`,
+  `stickyHeaders`, `rowSelection: true | 'checkbox'` (checkbox mode adds a
+  tri-state select-all over the currently *filtered* rows),
+  `headerContextMenu`, `zebraStripe`, `keyboardNav` (j/k), `drillDown`,
+  `showMore`, `rowMode: 'wrapped' | 'clipped'`.
+- **Rows:** `formatCell`, `onRowClick`, `onRowDoubleClick`,
+  `onSelectionChange`, `renderDetailRow` + `detailRowsExpanded` (disclosure
+  rows), `onColumnReorder`/`onColumnResize`/`onHeaderContextMenu`.
+- **Mass operations:** `operations?: Operation[]` — each
+  `{ label, icon?, category?, callback(ctx) }` surfaces in the operations
+  palette; `ctx.rows` is the current selection. Pair with
+  `features.rowSelection: 'checkbox'` for bulk edit/delete/export flows.
+- **i18n/formatting:** `locale` (BCP-47) drives number/date formatting.
+  `DataVisNitroLanguageSelector` is the UI-language mechanism — it switches
+  the engine's own i18next language (toolbar/table strings). `trans` is
+  narrower than it looks: it only customizes the built-in grouping-function
+  labels; it does **not** translate the general grid UI.
+- **Hover row actions:** `RowActionToolbar` with `group="grid"` (main
+  barrel) composes with NITRO cells, same as with `Table` rows.
+
+## DataVisNitroGraph
+
+Same source, chart renderer: `columns`, `config?: Partial<GraphConfig>` +
+`onConfigChange` (users may change axes/chart type), `locale`, `height`,
+`className`. For a tiny inline dependency-free trend use `Sparkline` (main
+barrel) instead.
+
+## Real-world composition (orders grids)
+
+`ChartOrdersGrid` / `EncounterOrdersGrid` (this entry) are NITRO grids over
+HealthSurveillance order history; the pure row builders
+(`buildChartOrderRows`/`buildEncounterOrderRows`) live in the **main** entry.
+`OrdersGroupPresets` renders one-click group-by chips. Row selection and mass
+operations there are native NITRO features — the pattern to copy, not
+re-implement.
+
+## Accessibility caveat
+
+The DataVis engine's DOM is **not screen-reader friendly** and automated a11y
+checks are disabled on the NITRO pages. Keep critical actions reachable
+outside the grid and provide textual summaries for charts. Route full audits
+to the A11y agent.
+
+## eSheet (Builder/Renderer)
+
+- Entry: **`@mieweb/ui/esheet`**; optional peers are **all four** `@esheet/*`
+  packages — `@esheet/core`, `@esheet/fields`, `@esheet/builder`,
+  `@esheet/renderer` — at matching versions (`>=0.0.6-17`), even for
+  renderer-only use: the shared entry exports the builder too, so all four
+  must resolve. Styles: Builder and Renderer import their
+  `@esheet/styles` dependency automatically (explicit entry
+  `@esheet/styles/styles.css`); keep loading `@mieweb/ui/styles.css` for
+  composed UI components.
+- **The pair:** `EsheetBuilder` (`definition`/`onChange`) emits a
+  `FormDefinition`; `EsheetRenderer` takes that object as `formDataInput`.
+  Answers come back two ways: imperatively via the ref's
+  `getValidResponse()`, which returns `{ response: FormResponse | null,
+  errors: ValidationError[] }` (`response` is `null` while invalid — store
+  `response`, not the wrapper), or via the opt-in built-in submit button —
+  pass `onSubmit` (+ `submitLabel`) and the Renderer renders it and calls
+  back with the validated `FormResponse`; don't build a duplicate submit
+  flow next to it. **Persistence is host-owned either way** — no autosave,
+  no `name`, no server calls; the host stores definition and response.
+- **Clinical fields:** `registerMieEsheetFields()` plugs the Healthcare list
+  fields (`medicationList`, `allergyList`, …) into both Builder and
+  Renderer — call it once before rendering definitions that use them.
+- **EncounterVisit** (same entry) is the coded clinical visit document; its
+  RichEdit mode rides the Kerebron editor — the `@kerebron/*` peers, WASM
+  assets and `kerebron.css` from the **mieweb-ui-kerebron** skill apply.
+- Known gaps: upstream axe failures (contrast, unlabeled landmarks, role-less
+  drag handles) tracked in the mieweb/eSheet repo; no locale/translation
+  hooks — built-in strings are English — but layout **does** mirror under an
+  inherited `dir="rtl"` (panels swap, toolbar flips), with a handful of
+  physical-direction styling gaps tracked as an upstream eSheet RTL
+  enhancement; it themes via its own `--msprimary` tokens + `dark`
+  class, independent of `ThemeProvider`.
+
+## Troubleshooting
+
+| Symptom | Cause | Fix |
+| --- | --- | --- |
+| `datavis_ace.Source is not a constructor` | `datavis-ace` missing/unresolved — it is a hard runtime requirement of `DataVisNitroSource` (ships as a regular dependency of `@mieweb/ui`, external in the bundle) | Reinstall; check the host's resolution (`pnpm why datavis-ace`) — never add it as a direct import |
+| Grid renders nothing, no error | `DataVisNitroGrid` not inside a `DataVisNitroSource` (context is null) | Nest Grid/Graph inside the Source |
+| `type="local"` grid is empty | `window[varName]` unset at mount, or not shaped `{ typeInfo, data }` | Set the global before mounting; delete it on unmount |
+| Grouping/aggregation "doesn't stick" | Imperative `setGroup`/`setAggregate` calls on the context fight the declarative props | Use the Source's `groupBy`/`aggregates` props only |
+| Huge dataset scrolls poorly | No virtualization in the engine — `height` + show-more/limit is the mechanism | Reduce the served dataset (http source), group/aggregate, or page upstream |
+| "How do I turn on pagination?" | NITRO has no page controls; `Pagination` is for server-paged `Table`/card lists | Filtering/grouping/show-more replace paging in NITRO |
+| Rows selectable but bulk action missing | `rowSelection` without `operations` | Add `operations` entries — `callback(ctx)` receives `ctx.rows` |
+| Pinned perspectives leak across users on a kiosk | Pins persist to localStorage by default | `persistPinnedPerspectives={false}` |
+| eSheet fields for meds/allergies render as unknown type | `registerMieEsheetFields()` not called | Call it once at startup before rendering such definitions |
+| eSheet looks unstyled | Very old `@esheet/*` versions required manual CSS copying | Upgrade — current Builder/Renderer import `@esheet/styles` automatically |
+| Grid needed AG Grid feature X | `@mieweb/ui/ag-grid` is deprecated | Treat the gap as a NITRO feature request (file an issue); don't start new AGGrid usage |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mieweb/ui",
-  "version": "0.11.0-dev.55",
+  "version": "0.11.0-dev.56",
   "description": "A themeable, accessible React component library built with Tailwind CSS",
   "author": "Medical Informatics Engineering, Inc.",
   "license": "SEE LICENSE IN LICENSE",