@toclocoinc/lattice-grid 1.11.0 → 1.12.0

package/README.md

@@ -4,24 +4,24 @@
 dependencies, no build step required. Optional adapters for React, Vue, Svelte
 and Web Components ship alongside it.
 
-Version 1.11.0 · [latticegrid.dev](https://www.latticegrid.dev) · TOCLOCO Inc
+Version 1.12.0 · [latticegrid.dev](https://www.latticegrid.dev) · TOCLOCO Inc
 
 ---
 
 ## What's here
 
 This repository is the distribution: the built library, its type declarations
-and the documentation. Everything is self-contained — nothing is fetched at
+and the documentation. Everything is self-contained: nothing is fetched at
 runtime, not a CDN, not a font, not an icon sprite.
 
 | File | What it is |
 |---|---|
-| `lattice-grid.min.js` | The library. UMD — works with a `<script>` tag. |
+| `lattice-grid.min.js` | The library. UMD: works with a `<script>` tag. |
 | `lattice-grid.esm.min.js` | The same, as an ES module. |
 | `lattice-grid.min.css` | The theme. Required. |
 | `lattice-grid.d.ts` | TypeScript declarations. |
 | `docs/API.html` | The complete API reference. |
-| `docs/api-detail.html` | The developer guide — what each part does, and why. |
+| `docs/api-detail.html` | The developer guide: what each part does, and why. |
 
 Every module is optional and none of them is loaded unless you import it.
 
@@ -32,7 +32,7 @@ Every module is optional and none of them is loaded unless you import it.
 | `modules/vue.esm.min.js` | Vue adapter. |
 | `modules/svelte.esm.min.js` | Svelte adapter. |
 | `modules/webcomponent.esm.min.js` | `<lattice-grid>` as a custom element. |
-| `modules/htmx.esm.min.js` | htmx integration — survives htmx's DOM swaps, hydrates from a server-rendered `<table>`, and drives sort, filter and infinite scroll over plain htmx requests. UMD and CJS builds sit beside it. |
+| `modules/htmx.esm.min.js` | htmx integration: survives htmx's DOM swaps, hydrates from a server-rendered `<table>`, and drives sort, filter and infinite scroll over plain htmx requests. UMD and CJS builds sit beside it. |
 | `modules/dhtmlx-compat.esm.min.js` | A compatibility wrapper for dhtmlx Grid, for moving an existing integration across without rewriting it. |
 | `modules/devtools.esm.min.js` | The devtools panel, including the accessibility checks. |
 
@@ -55,20 +55,20 @@ enough to know whether the grid covers what you need.
 - **Live data.** `rows.apply({add, update, remove})` patches in place: the grid
   re-queries the stages a change actually touched and repaints the cells that
   moved. A feed can be paused and resumed with the queue held.
-- **Any source.** Rows in memory, or a source you write — server-side paging,
+- **Any source.** Rows in memory, or a source you write: server-side paging,
   infinite scroll, streaming, or an async provider. Sorting and filtering can be
   handed to the server or left to the grid.
 
 ### Working with the data
 
-- **Editing.** Cell, row and form editing, with twenty-three editors — text,
+- **Editing.** Cell, row and form editing, with twenty-three editors: text,
   number, date, time, select, multi-select, colour, rating, slider, segmented,
   code, password, icon picker and more. Validation, async commits, optimistic
   updates with rollback, and a full undo history.
 - **Selection and ranges.** Cell, row, column and rectangular range selection,
   with clipboard behaviour that round-trips through Excel.
 - **Fill, copy and paste** across a range, including formulas.
-- **Formulas.** A closed, safe expression language — no `eval`, no host access —
+- **Formulas.** A closed, safe expression language, no `eval`, no host access , 
   with maths, text, logic, date and statistical functions, evaluated against
   other columns.
 - **Export.** CSV with fields sanitised against formula injection, real `.xlsx`
@@ -79,18 +79,18 @@ enough to know whether the grid covers what you need.
 ### Seeing the data
 
 - **Charts.** `modules/charts` draws thirty-five chart types from the grid's own
-  data — line, bar, area, scatter, pie, donut, sunburst, treemap, radar, gauge,
+  data: line, bar, area, scatter, pie, donut, sunburst, treemap, radar, gauge,
   funnel, heatmap, histogram, box plot, candlestick, combo, geomap, sankey,
   chord, network, stream, violin, gantt and more. They follow the grid's
   filters, and clicking a mark can filter it in turn.
-- **Statistics.** `grid.statistics` profiles a column in one pass — count,
+- **Statistics.** `grid.statistics` profiles a column in one pass: count,
   missing, distinct, five-number summary, standard deviation, outliers and a
-  histogram — and answers correlations and weighted averages. Thirty-eight
+  histogram, and answers correlations and weighted averages. Thirty-eight
   reduction kernels are available to the totals row, and you can register your
   own.
 - **Shadow columns.** Values the grid maintains about itself: how many times a
   row has changed, what a value was when the page loaded, how fast it is moving,
-  its rank, percentile or share of the total. Real columns — sortable,
+  its rank, percentile or share of the total. Real columns: sortable,
   filterable, exportable, saved into a view.
 - **Conditional formatting** as runtime state a user can change, with rules that
   either name a threshold or describe the data: the top decile, the outliers,
@@ -102,14 +102,14 @@ enough to know whether the grid covers what you need.
 
 - **Tool panels** for columns, filters, views, quick filter, formatting and
   statistics, docked or as an icon rail.
-- **Saved views** — the whole grid state as a named, shareable object, stored
+- **Saved views**, the whole grid state as a named, shareable object, stored
   on your server or in the browser.
 - **Column menu, context menu and status bar**, each extensible with your own
   items.
 - **Pinned columns and rows**, column groups, resize, reorder, autosize, and a
   density control.
 - **Master–detail rows**, tree data, and full-width rows.
-- **Presence** — live cursors, selections and edit locks for collaborative use,
+- **Presence**: live cursors, selections and edit locks for collaborative use,
   carrying intent and never values.
 - **Comments** threaded on cells, and an annotation layer for presenting.
 - **Full-screen mode**, print, and image capture.
@@ -126,7 +126,7 @@ enough to know whether the grid covers what you need.
   a reset that keeps a host page's stylesheet out.
 - **Typed.** Complete TypeScript declarations, checked against the runtime on
   every build.
-- **Zero runtime dependencies.** Nothing is fetched at runtime — not a CDN, not
+- **Zero runtime dependencies.** Nothing is fetched at runtime, not a CDN, not
   a font, not an icon sprite.
 
 ---
@@ -189,7 +189,7 @@ const LatticeGrid = createLatticeGrid({ React, createGrid });
 ```
 
 The web component is the exception: it carries the grid inside it, so use it *or*
-`createGrid` in a page, not both — two copies keep separate registries, and a
+`createGrid` in a page, not both, two copies keep separate registries, and a
 renderer registered through one will not appear in the other.
 
 The full setup for each framework is in the developer guide.
@@ -200,9 +200,9 @@ Two integrations that are not framework adapters.
 
 **htmx.** `modules/htmx` lets a grid survive htmx's own DOM swaps, hydrate from
 a server-rendered `<table>`, and drive sort, filter and infinite scroll over
-plain htmx requests. It is a complete package rather than an add-on —
+plain htmx requests. It is a complete package rather than an add-on , 
 `createGrid`, `autoInit`, `hydrateTable`, `readTable`, `serialiseState` and
-`restoreState` are re-exported alongside its own functions — so a page using it
+`restoreState` are re-exported alongside its own functions, so a page using it
 imports this and never the base package as well.
 
 **dhtmlx.** `modules/dhtmlx-compat` exposes a dhtmlx Grid-shaped API over
@@ -212,7 +212,7 @@ than rewriting it in one go.
 ### TypeScript
 
 Declarations ship in the box and are wired up in `package.json`, so editors find
-them without configuration — autocomplete, inline documentation and type
+them without configuration: autocomplete, inline documentation and type
 checking against the real API.
 
 ```ts
@@ -228,7 +228,7 @@ your editor tells you and what the grid does cannot drift apart.
 
 A grid usually lives in whatever box the page layout gave it, and that box is
 usually too small for the job. The left rail's last button fills the browser
-window with the grid; clicking it again — or pressing <kbd>Esc</kbd> — puts it
+window with the grid; clicking it again, or pressing <kbd>Esc</kbd>: puts it
 back exactly where it was.
 
 ```js
@@ -248,8 +248,8 @@ it was found.
 
 ## Data types
 
-Seven built-in types — `text`, `number`, `boolean`, `date`, `dateString`,
-`object` and `lookup` — cover ordinary business data and are inferred from your
+Seven built-in types: `text`, `number`, `boolean`, `date`, `dateString`,
+`object` and `lookup`: cover ordinary business data and are inferred from your
 rows automatically.
 
 Beyond those, Lattice Grid ships **88 technical field types** for the data that
@@ -259,16 +259,16 @@ editor, filter, alignment, clipboard behaviour and Excel mapping.
 
 | Group | Types |
 |---|---|
-| **Network** | `ipv4`, `ipv6`, `cidr` — sort in address order, not lexically, so `10.0.0.9` comes before `10.0.0.10`. |
-| **Time** | `time`, `datetime`, `duration` — three things a single `date` type keeps being asked to be. |
-| **Radix** | `hex`, `hex8`, `hex16`, `hex32`, `binary`, `binary8`, `octal` — the stored value stays a plain number; the base is presentation and input only. |
-| **Data** | `bytes`, `megabytes`, `gigabytes`, `bitrate`, `gigabits` — shows `10 GB`, accepts `10,000M` typed in, stores `10`. Decimal and binary ladders are both first class, because `MB` and `MiB` are different quantities. |
+| **Network** | `ipv4`, `ipv6`, `cidr`: sort in address order, not lexically, so `10.0.0.9` comes before `10.0.0.10`. |
+| **Time** | `time`, `datetime`, `duration`: three things a single `date` type keeps being asked to be. |
+| **Radix** | `hex`, `hex8`, `hex16`, `hex32`, `binary`, `binary8`, `octal`, the stored value stays a plain number; the base is presentation and input only. |
+| **Data** | `bytes`, `megabytes`, `gigabytes`, `bitrate`, `gigabits`: shows `10 GB`, accepts `10,000M` typed in, stores `10`. Decimal and binary ladders are both first class, because `MB` and `MiB` are different quantities. |
 | **Mechanical** | length, mass, duration, speed, acceleration, area, volume, force, pressure, torque, density, energy, power, angle, `rpm` and angular velocity. |
 | **Fluid and thermal** | volumetric flow, mass flow, dynamic and kinematic viscosity, thermal conductivity, specific heat, and temperature in `celsius`, `fahrenheit` and `kelvin`. |
-| **Electrical and SI** | voltage, current, resistance, capacitance, inductance, charge, conductance, frequency, flux density, luminous flux, luminous intensity, illuminance and substance — all auto-prefixed across the SI range. |
+| **Electrical and SI** | voltage, current, resistance, capacitance, inductance, charge, conductance, frequency, flux density, luminous flux, luminous intensity, illuminance and substance: all auto-prefixed across the SI range. |
 | **Chemistry and radiation** | `molarity`, `ppm`, `ppb`, absorbed dose, equivalent dose, radioactivity and dose rate. |
-| **Finance and ratios** | `basisPoints`, `ratio`, `percentRate`, and decibels — which are reduced logarithmically, not averaged. |
-| **Structured** | `json`, `secret` — `secret` is write-only: editable, never displayed, never exported. |
+| **Finance and ratios** | `basisPoints`, `ratio`, `percentRate`, and decibels, which are reduced logarithmically, not averaged. |
+| **Structured** | `json`, `secret`: `secret` is write-only: editable, never displayed, never exported. |
 
 ### Units of your own
 
@@ -297,7 +297,7 @@ createGrid(el, {
 
 `display: 'auto'` walks the ladder and picks the most readable rung, so 1,500
 tex renders as `1.5 ktex`. A unit given `{ auto: false }` stays off that ladder
-while remaining accepted on input and available as an explicit `display` — which
+while remaining accepted on input and available as an explicit `display`: which
 is how imperial units sit beside metric ones without an auto readout jumping
 between the two.
 
@@ -313,15 +313,15 @@ createUnitType({ system: 'money', unit: '$', placement: 'prefix', decimals: 2 })
 ```
 
 Whatever the display, **the stored value is always a plain number in the
-column's base unit** — so sorting, filtering, grouping, totals and the pivot all
+column's base unit**, so sorting, filtering, grouping, totals and the pivot all
 work on the number and never on the text.
 
 ---
 
 ## Documentation
 
-- **[API reference](docs/API.html)** — every namespace, method, config key and event.
-- **[Developer guide](docs/api-detail.html)** — what each part does and why, with worked examples.
+- **[API reference](docs/API.html)**: every namespace, method, config key and event.
+- **[Developer guide](docs/api-detail.html)**: what each part does and why, with worked examples.
 
 ---
 
@@ -335,7 +335,7 @@ edition, no pro tier, no feature held back behind a key.
 - **Licensed to deploy.** On any other host, an unlicensed grid renders
   everything and carries a small trial watermark.
 
-Nothing is ever disabled, degraded or withheld — the failure to avoid is a
+Nothing is ever disabled, degraded or withheld, the failure to avoid is a
 production screen breaking because a licence lapsed over a weekend. A key
 removes the watermark; that is the whole of what it does.
 

package/docs/AI-SKILL.md

@@ -1,7 +1,7 @@
 # The AI skill layer
 
 A prompt input above the grid that turns "EMEA deals over 50k, biggest first"
-into a filter and a sort — via whichever language model you choose.
+into a filter and a sort: via whichever language model you choose.
 
 This document has two halves. The first is for the developer wiring it up. The
 second is written to be handed to a model, and describes the grid as a skill it
@@ -14,18 +14,18 @@ can drive.
 **The grid never calls a language model. It makes no network request of any
 kind.** It calls one async callback you supply, and whatever that callback
 returns is validated and previewed. You own the model, the API key, the
-request, and — the part that matters — the privacy decision.
+request, and (the part that matters) the privacy decision.
 
 By default the callback receives:
 
-- `schema` — the generated description of your columns: ids, titles, types,
+- `schema`, the generated description of your columns: ids, titles, types,
   which are filterable/sortable/groupable, and the declared option lists of
   lookup columns.
-- `context` — **empty**, unless you put something in it.
+- `context`: **empty**, unless you put something in it.
 
 **No row values leave the grid.** Not a sample, not a summary, not the first
-page. If you want the model to see data — and for some questions it genuinely
-helps — you put it in `context` yourself, deliberately, having decided that
+page. If you want the model to see data, and for some questions it genuinely
+helps: you put it in `context` yourself, deliberately, having decided that
 sending it to a third party is acceptable for that data, that tenant and that
 jurisdiction. There is no flag that turns it on by accident.
 
@@ -43,7 +43,7 @@ Two things worth knowing before you do:
 
 ---
 
-# Part one — wiring it up
+# Part one: wiring it up
 
 ## Setup
 
@@ -68,7 +68,7 @@ gets a preview:
 > **Filter Region is EMEA, sort Margin descending**
 > [ Apply ] [ Discard ]
 
-Nothing changes until Apply. That is not a configurable nicety — it is the
+Nothing changes until Apply. That is not a configurable nicety, it is the
 reason the feature is shippable to a customer with an audit function.
 
 ## The callback contract
@@ -186,13 +186,13 @@ if (plan.ok && await userConfirms(plan.describe())) {
 
 `plan` is `{ ok, actions, rejected, explain, describe() }`:
 
-- `ok` — true when at least one action survived validation.
-- `actions` — the validated, normalised actions.
-- `rejected` — `{ at, what, reason }` for every part refused, whether or not
+- `ok`: true when at least one action survived validation.
+- `actions`, the validated, normalised actions.
+- `rejected`: `{ at, what, reason }` for every part refused, whether or not
   anything survived. Show these: a user approving three of five conditions
   needs to see the other two.
-- `explain` — the model's own one-liner. Informational only.
-- `describe()` — the plan in English, **built from the validated actions**, not
+- `explain`, the model's own one-liner. Informational only.
+- `describe()`, the plan in English, **built from the validated actions**, not
   from `explain`. A model is not a reliable narrator of its own output.
 
 ## Keeping the schema small
@@ -200,7 +200,7 @@ if (plan.ok && await userConfirms(plan.describe())) {
 A 200-column grid with a 5,000-option lookup on every column would produce a
 schema nobody can afford to send, and a schema truncated by the transport is a
 schema the model silently misreads. Everything is budgeted, and every cut is
-reported in `schema.truncated` and stated in the prompt text — a model told
+reported in `schema.truncated` and stated in the prompt text, a model told
 "20 of 812 options shown" asks for the rest or falls back to `contains`,
 whereas one shown a silently short list concludes those 20 are all there is.
 
@@ -222,7 +222,7 @@ ai: {
 ## Events
 
 Applying goes through `filters.set`, `sort.set`, `columns.group`,
-`columns.show` and `columns.hide` — the public API, nothing private. So a
+`columns.show` and `columns.hide`, the public API, nothing private. So a
 model-driven change emits the same `filter:changed`, `sort:changed` and
 `model:changed` events, lands in the same `state.get()` snapshot, and sits on
 the same undo path as the user having done it by hand. If you want to record
@@ -262,12 +262,12 @@ And the boundary this feature does *not* claim:
 > boundary against a hostile model. **Never give a model more authority than
 > the user already has.** Run the callback with the user's own credentials,
 > filter server-side by the user's own permissions, and treat what comes back
-> as a suggestion from an untrusted source — because that is exactly what it
+> as a suggestion from an untrusted source, because that is exactly what it
 > is.
 
 ---
 
-# Part two — the skill, for the model
+# Part two, the skill, for the model
 
 *Everything below is written to be given to a model, whether pasted into a
 system prompt or emitted by `promptText(schema)`.*
@@ -276,7 +276,7 @@ system prompt or emitted by `promptText(schema)`.*
 
 You can reshape a Lattice data grid: filter rows, sort them, group them, and
 show or hide columns. You cannot read, edit, delete or export data, and you
-cannot run code. Your output is a proposal — a human sees a plain-English
+cannot run code. Your output is a proposal, a human sees a plain-English
 summary of it and decides whether to apply it.
 
 You will be given a schema listing every column: its id, its title, its family,
@@ -307,7 +307,7 @@ Reply with one JSON object and no other text:
 | `setQuick` | `text` | Sets the quick filter, which matches across every column |
 | `clear` | `what` | One of `filters`, `sort`, `group`, `quick`, `all` |
 
-Nothing outside this table exists. To remove something, use `clear` — an empty
+Nothing outside this table exists. To remove something, use `clear`, an empty
 `setSort` or `groupBy` is rejected, not treated as a clear.
 
 ### Filters
@@ -356,7 +356,7 @@ Which operators apply depends on the column's **family**, given in the schema:
 | `object` | `eq` `ne` `blank` `notBlank` |
 
 `contains` on a number column is rejected. So is `eq` on a `lookupMulti`
-column, whose cells hold arrays — use `containsAny`.
+column, whose cells hold arrays: use `containsAny`.
 
 Dates are ISO 8601 strings: `"2026-01-01"` or `"2026-01-01T00:00:00Z"`.
 
@@ -396,7 +396,7 @@ notes     | Notes    | text        |
 ```json
 {
   "actions": [ { "type": "groupBy", "columns": ["region"] } ],
-  "explain": "Grouped by region. I cannot add total rows — that is a grid setting."
+  "explain": "Grouped by region. I cannot add total rows: that is a grid setting."
 }
 ```
 
@@ -436,7 +436,7 @@ column is the commonest way to answer this question wrongly.
 { "actions": [ { "type": "clear", "what": "all" } ], "explain": "Cleared the view." }
 ```
 
-**"sort by notes"** — `notes` has no capabilities listed, so it cannot be
+**"sort by notes"**: `notes` has no capabilities listed, so it cannot be
 sorted:
 
 ```json