@jielga/tmdatagrid 2.0.0-beta.0 → 2.0.0-beta.2

package/skills/getting-started/SKILL.md

@@ -11,7 +11,7 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.0'
+  library_version: '2.0.0-beta.2'
 sources:
   - 'Jielga/TMDataGrid:src/docs/getting-started.md'
   - 'Jielga/TMDataGrid:src/docs/anatomy.md'
@@ -169,10 +169,10 @@ Pass the row type so `onRowClick` stays typed:
 <TMDataGrid.Table<Employee> onRowClick={(row) => open(row.original.id)} />
 ```
 
-`renderRowContextMenu` fills the dropdown of a Mantine `Menu` the grid opens at the
-pointer on a right-click (or a long press). The grid owns the `Menu` - opening,
-positioning, and closing on Escape, outside click, body scroll or an item pick -
-so the render prop only says what goes in it:
+`renderRowContextMenu` fills the dropdown of a Mantine `Menu` that the grid
+opens at the pointer on a right-click (or a long press). The grid renders the
+`Menu`, positions it, and closes it on Escape, an outside click, a body scroll
+or an item pick, so the render prop supplies only the contents:
 
 ```tsx
 <TMDataGrid.Table<Employee>
@@ -192,11 +192,11 @@ so the render prop only says what goes in it:
 />
 ```
 
-`cell` is the one that was right-clicked, `table` is there for actions that read
-the selection, and `close` is for dropdown content that is not a `Menu.Item`
-(those close themselves). Return `null` to leave a row without a menu. It is
-called during render, and only for the open row, so it must stay pure - put the
-work in the item handlers. Right-clicking does not change the selection or the
+`cell` is the one that was right-clicked, `table` is for actions that read the
+selection, and `close` is for dropdown content that is not a `Menu.Item` (those
+close themselves). Return `null` to leave a row without a menu. It is called
+during render, and only for the open row, so it must stay pure: put the work in
+the item handlers. Right-clicking does not change the selection or the
 highlight; the row carries `data-context-menu` while its menu is open. Pass
 `rowContextMenuProps` for `width`, `shadow`, `position` and the rest.
 

package/skills/grouping/SKILL.md

@@ -14,7 +14,7 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.0'
+  library_version: '2.0.0-beta.2'
 sources:
   - 'Jielga/TMDataGrid:src/docs/grouping.md'
   - 'Jielga/TMDataGrid:src/docs/summary-row.md'
@@ -29,8 +29,8 @@ category, and the summary row totals everything along the bottom edge.
 
 ## Grouping
 
-On by default, and nothing changes until a column is grouped - the reader does
-that from **Group by …** in any column menu. To open already grouped, seed the
+On by default, and nothing changes until a column is grouped, which users do
+from **Group by …** in any column menu. To open already grouped, seed the
 state:
 
 ```tsx
@@ -41,8 +41,8 @@ const grid = useTMDataGrid({
 });
 ```
 
-Grouping a column **removes it** - its values have moved into the tree lane -
-and a generated Group column (`GROUP_COLUMN_ID`) appears at the front, pinned
+Grouping a column **removes it**, since its values have moved into the tree
+lane, and a generated Group column (`GROUP_COLUMN_ID`) appears at the front, pinned
 beside the checkbox lane. Each group row shows its value, its record count and a
 chevron. Grouping a second column nests.
 
@@ -53,9 +53,8 @@ instead of removing them.
 
 ## Aggregation
 
-Off unless asked for. A grouped grid is a tree, not a summary: a group row
-leaves every cell blank except the tree lane. Give a column an `aggregationFn`
-and it fills in.
+Off by default. A group row leaves every cell blank except the tree lane. Give a
+column an `aggregationFn` and its group cells fill in.
 
 ```tsx
 columnHelper.accessor("salary", {
@@ -81,8 +80,8 @@ leaves the groups where they are.
 
 ## Group rows are not data rows
 
-A group row is built on its first child's record, so handing it to a callback
-would hand over a real-looking row that is the wrong one. Group rows therefore:
+A group row is built on its first child's record, so passing it to a callback
+would pass a row that looks real but is the wrong one. Group rows therefore:
 
 - do not fire `onRowClick` or the cell handlers
 - cannot be highlighted, pinned, or given a details panel
@@ -91,8 +90,8 @@ would hand over a real-looking row that is the wrong one. Group rows therefore:
 
 A group row's checkbox selects every record under it at any depth, including
 records inside collapsed sub-groups, showing a tick once all are selected and a
-dash while only some are. Only the records reach `rowSelection` - a group row is
-never in it - so `getSelectedRowModel()` and the toolbar count are unaffected by
+dash while only some are. Only the records reach `rowSelection`; a group row is
+never in it, so `getSelectedRowModel()` and the toolbar count do not depend on
 how the tree is arranged. Under `enableMultiRowSelection: false` group rows carry
 no checkbox.
 
@@ -102,14 +101,14 @@ no checkbox.
 
 **Grouping and the built-in pager do not work together, and grouping wins.** As
 soon as a column is grouped the grid renders the whole tree and relies on
-virtualization; `TMDataGrid.Footer` greys its pager out and replaces the range
+virtualization. `TMDataGrid.Footer` greys its pager out and replaces the range
 with `Grouped · all N rows`. Ungroup and paging resumes where it left off.
 
 This is deliberate. A page can only count one kind of thing, and once the rows
-are a tree neither answer is usable: counting every row splits a group across a
-page boundary, and counting top-level rows quietly redefines "rows per page" as
-groups per page. Rendering the whole tree is the grid's default mode anyway -
-pagination is the opt-in - so nothing is lost but the pager.
+are a tree neither option works: counting every row splits a group across a page
+boundary, and counting top-level rows redefines "rows per page" as groups per
+page. Rendering the whole tree is the grid's default mode in any case, so only
+the pager is lost.
 
 `isPagingActive(table, features)` is exported so a custom pager can grey itself
 out the same way. To have both, page on the server: group there and feed the
@@ -117,8 +116,8 @@ grid one page of a tree at a time with `manualPagination` and `manualGrouping`.
 
 ## The summary row
 
-There is no flag. Give a column a `footer` and the row appears; it exists
-exactly when at least one visible column defines one.
+There is no flag. Give a column a `footer` and the row appears. It exists
+whenever at least one visible column defines one.
 
 ```tsx
 import { aggregateColumn } from "@jielga/tmdatagrid";
@@ -131,8 +130,8 @@ columnHelper.accessor("salary", {
 ```
 
 `footer` is TanStack's own column option, rendered the way the header is.
-`aggregateColumn({ table, columnId, fn })` computes over every **filtered** row -
-all pages, following the filters live - through the registered aggregation
+`aggregateColumn({ table, columnId, fn })` computes over every **filtered** row,
+all pages, following the filters live, through the registered aggregation
 functions, with `fn` defaulting to `"sum"`.
 
 ```tsx
@@ -140,9 +139,8 @@ aggregateColumn({ table, columnId: "age", fn: "mean" });
 aggregateColumn({ table, columnId: "location", fn: "uniqueCount" });
 ```
 
-Following the filters is the point: a footer that keeps saying the same number
-while the reader narrows the grid looks like it is answering the question in
-front of them when it is not.
+It follows the filters deliberately. A total that does not change as the user
+narrows the grid is misleading.
 
 Pinned columns keep their lanes in the summary row, the generated lanes define
 no `footer` so their cells stay blank, and the row is sticky at
@@ -153,8 +151,8 @@ no `footer` so their cells stay blank, and the row is sticky at
 ### CRITICAL Expecting group rows to total automatically
 
 Grouping alone leaves every cell blank on a group row, because the grid clears
-TanStack's `aggregationFn: "auto"` default. Nothing errors - the tree simply
-looks empty, which reads as a broken feature.
+TanStack's `aggregationFn: "auto"` default. Nothing errors; the tree just looks
+empty.
 
 Wrong:
 
@@ -173,9 +171,9 @@ Source: `src/docs/grouping.md` (Aggregation).
 ### HIGH Looking for the grouped column in the grid
 
 `groupedColumnMode` defaults to `"remove"`, so grouping by Department takes the
-Department column out - its values are in the tree lane. Code that reads that
-column's cells, or a test that queries its header, stops finding it the moment a
-reader groups.
+Department column out, since its values are in the tree lane. Code that reads
+that column's cells, or a test that queries its header, stops finding it as soon
+as a user groups.
 
 Correct, when the column must stay:
 
@@ -187,19 +185,19 @@ Source: `src/docs/grouping.md` (What grouping does to the grid).
 
 ### HIGH Combining the pager with grouping
 
-`enablePagination: true` and a grouped column cannot both be honoured. The pager
-greys out rather than paging the tree, so a footer count wired to
-`getPageCount()` reports a number nobody can navigate to. Read
+`enablePagination: true` and a grouped column cannot both apply. The pager greys
+out instead of paging the tree, so a footer count wired to `getPageCount()`
+reports a number nobody can navigate to. Read
 `isPagingActive(table, features)` before trusting the pager state.
 
 Source: `src/docs/grouping.md` (Grouping suspends pagination).
 
 ### HIGH Handing a group row to a row callback
 
-Group rows sit out `onRowClick`, the cell handlers, pinning, details and
-editing, and their `row.original` is an arbitrary child's record. A bulk action
-built from `row.original` on the tree lane acts on one record instead of the
-group.
+Group rows do not fire `onRowClick` or the cell handlers, and cannot be pinned,
+expanded or edited. Their `row.original` is an arbitrary child's record, so a
+bulk action built from `row.original` on the tree lane acts on one record
+instead of the group.
 
 Correct:
 
@@ -214,16 +212,16 @@ Source: `src/docs/grouping.md` (Group rows are not data rows).
 ### MEDIUM Totalling the page instead of the data
 
 `aggregateColumn` deliberately runs over every filtered row, all pages. Summing
-`table.getRowModel().rows` instead totals only what is currently paged in, which
-matches the screen but answers a different question - and under virtualization
-it is not even the whole page.
+`table.getRowModel().rows` instead totals only what is currently paged in, and
+under virtualization not even that: only the mounted rows.
 
 Source: `src/docs/summary-row.md` (Totalling a column).
 
 ### MEDIUM Grouping a server-paged grid
 
-`manualPagination: true` turns grouping off: the client holds one page and would
-build groups out of an arbitrary slice. Group on the server and declare it.
+`manualPagination: true` turns grouping off, because the client holds one page
+and would build groups out of an arbitrary slice. Group on the server and
+declare it.
 
 Correct:
 
@@ -247,9 +245,9 @@ Source: `src/docs/grouping.md` (Server-side grids).
 | `groupedColumnMode` | Table option | `"reorder" \| "remove" \| false` | `"remove"` | Whether a grouped column leaves the grid or moves to the front. |
 | `manualGrouping` | Table option | `boolean` | `false` | The rows arrive grouped. Required to group a server-paged grid. |
 | `initialState.grouping` | Table option | `string[]` | `[]` | Column ids grouped at mount. A settings slice, so it persists. |
-| `aggregationFn` | Column option | `TMDataGridAggregationName \| fn` | – | How a column fills in its group rows. Unset means blank. |
+| `aggregationFn` | Column option | `TMDataGridAggregationName \| fn` | – | How a column fills in its group cells. Unset leaves them blank. |
 | `aggregatedCell` | Column option | `(ctx) => ReactNode` | The `cell` renderer | Renders a group row's value differently. |
-| `footer` | Column option | `(ctx) => ReactNode` | – | Renders this column's summary cell, and summons the row. |
+| `footer` | Column option | `(ctx) => ReactNode` | – | Renders this column's summary cell. Defining one adds the row. |
 | `aggregateColumn` | Export | `({ table, columnId, fn }) => unknown` | `fn: "sum"` | Aggregates over every filtered row, all pages. |
 | `TMDataGridAggregationName` | Export | type | – | The registered function names. |
 | `GROUP_COLUMN_ID` | Export | `"__group__"` | – | Id of the generated tree column. |

package/skills/options/SKILL.md

@@ -14,7 +14,7 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.0'
+  library_version: '2.0.0-beta.2'
 sources:
   - 'Jielga/TMDataGrid:src/docs/use-tm-data-grid.md'
   - 'Jielga/TMDataGrid:src/tmdatagrid/useTMDataGrid.tsx'
@@ -47,7 +47,7 @@ rather than forwarded to TanStack.
 | --- | --- | --- | --- |
 | `data` | `TData[]` | – | Row data. Keep the reference stable with `useMemo`. |
 | `columns` | `ColumnDef[]` | – | Created with `createTMDataGridColumnHelper`. |
-| `getRowId` | `(row, index) => string` | Row index | Used by row selection and virtualization. Required once `editMode` is set. |
+| `getRowId` | `(row, index) => string` | Row index | Used by row selection and virtualization. Required once `editing` is set. |
 | `enableRowSelection` | `boolean \| (row) => boolean` | `true` | `false` removes row selection and its checkbox column. |
 | `selectionMode` | `"checkbox" \| "row" \| "checkboxAndHighlight" \| "highlight"` | `"checkbox"` | What selecting looks like and what a row click does. Defined by the grid - see the `rows` skill. |
 | `showSelectedBackground` | `boolean` | Follows the mode | Background tint on selected rows: off for `"checkbox"`, on for `"row"`. Colour is `--dg-row-selected-bg`. Defined by the grid. |
@@ -65,7 +65,7 @@ rather than forwarded to TanStack.
 | `initialState` | `Partial<TableState>` | See below | Merged over the grid defaults. |
 | `meta` | `TMDataGridTableMeta` | `{}` | Grid configuration, see below. |
 | `persist` | `TMDataGridPersistence` | – | State persistence, see below. |
-| `editMode` | `"cell" \| "cellConfirm" \| "row" \| "batch"` | off | Turns editing on. Brings `rowValidators`, `isRowEditable`, `onEditCommit`, `onEditCommitBatch`, `newRowDefaults`, `onRowAdd` and `onRowDelete` with it - see the `editing` skill. |
+| `editing` | `TMDataGridEditingOptions` | off | Turns editing on. `mode` (`"cell" \| "cellConfirm" \| "row" \| "draft"`) picks the commit policy; the object also holds `onCommit`, `onCommitDrafts`, `rowValidators`, `isRowEditable`, `newRowDefaults`, `newRowsSticky`, `onRowAdd` and `onRowDelete` - see the `editing` skill. |
 | `labels` | `TMDataGridLabelsOverride` | English | Overrides for the grid's strings and `aria-label`s. |
 
 ### Default initial state
@@ -152,7 +152,7 @@ persistence is skipped rather than throwing.
 | --- | --- | --- |
 | `table` | `Table<TMDataGridFeatures, TData>` | The TanStack table instance. |
 | `ui` | `Store<TMDataGridUiState, TMDataGridUiActions>` | State of the filter and column panels. |
-| `edit` | `TMDataGridEditApi` | The edit engine, inert until `editMode` is set. See the `editing` skill. |
+| `edit` | `TMDataGridEditApi` | The edit engine, inert until `editing` is set. See the `editing` skill. |
 | `features` | `TMDataGridFeatureFlags` | Table-level feature switches, re-read on each render. |
 | `labels` | `TMDataGridLabels` | The resolved label set, overrides merged over English. |
 | `resetSettings` | `() => void` | Puts the settings state back to a clean first visit. |

package/skills/rows/SKILL.md

@@ -17,7 +17,7 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.0'
+  library_version: '2.0.0-beta.2'
 sources:
   - 'Jielga/TMDataGrid:src/docs/row-selection.md'
   - 'Jielga/TMDataGrid:src/docs/row-interaction.md'
@@ -36,8 +36,8 @@ cell cursors and ranges are `cell-selection`.
 ## Selection
 
 `selectionMode` sets what selecting looks like **and** what a bare row click
-does. One option rather than two, because a click can either toggle a
-multi-selection or move a highlight, never both.
+does. It is one option rather than two because a click can toggle a
+multi-selection or move a highlight, but not both.
 
 | Mode | Checkbox column | Row click |
 | --- | --- | --- |
@@ -50,18 +50,19 @@ multi-selection or move a highlight, never both.
 const grid = useTMDataGrid({ data, columns, selectionMode: "row" });
 ```
 
-The first two write to TanStack's `rowSelection`, so everything downstream - the
-toolbar count, `getSelectedRowModel()`, persistence - is unaffected by the
-choice. Under `"row"` the click follows desktop-list conventions: a plain click
+The first two write to TanStack's `rowSelection`, so the toolbar count,
+`getSelectedRowModel()` and persistence all behave the same either way. Under
+`"row"` the click follows desktop-list conventions: a plain click
 makes the selection this row, Ctrl/Cmd toggles it and leaves the rest, Shift
 selects the range from the anchor, Ctrl+Shift adds that range. Rows are
 focusable in this mode, and Space or Enter toggles the focused row.
 
-`enableRowSelection: false` removes the selection half whatever the mode.
+`enableRowSelection: false` removes the checkbox column and row-click selection
+in any mode.
 
 ### The highlight is not a selection
 
-The highlight is state of its own, not a slice of `rowSelection` - which is what
+The highlight is state of its own, not a slice of `rowSelection`. That is what
 lets `"checkboxAndHighlight"` run both at once: tick rows for a bulk action,
 click one to open its record beside the grid.
 
@@ -78,9 +79,9 @@ const grid = useTMDataGrid({
 
 ### Reading a selection
 
-Read it through the table store, never by calling the method bare. `table` keeps
-one identity across renders, so the React Compiler caches a bare
-`getSelectedRowModel()` and the reader stops updating.
+Read it through the table store rather than by calling the method directly.
+`table` keeps one identity across renders, so the React Compiler caches a bare
+`getSelectedRowModel()` and the component stops updating.
 
 ```tsx
 import { useSelector } from "@tanstack/react-store";
@@ -93,9 +94,9 @@ const selected = useSelector(grid.table.store, () =>
 ### The background
 
 `showSelectedBackground` follows the mode: on for `"row"`, where the background
-is the only feedback a click gives, off for `"checkbox"`, where the box already
-says so. Set it to override either way. The colour is `--dg-row-selected-bg`,
-changed on the grid element rather than through the flag:
+is the only feedback a click gives, and off for `"checkbox"`, where the box
+already shows it. Set it explicitly to override either way. The colour is
+`--dg-row-selected-bg`, set on the grid element rather than through the flag:
 
 ```tsx
 <TMDataGrid
@@ -124,13 +125,13 @@ not replace selection or the highlight; yours runs in addition.
 <TMDataGrid.Table<Employee> onRowClick={(row) => open(row.original.id)} />
 ```
 
-Pass the row type, as above, and `row.original` is typed. Group rows sit out all
-four: TanStack builds a group row on top of its first child's record, so a
-handler would receive a real-looking row that is the wrong one.
+Pass the row type, as above, and `row.original` is typed. None of the four fires
+on a group row: TanStack builds a group row on its first child's record, so a
+handler would receive a row that looks real but is the wrong one.
 
-`renderRowContextMenu` is a slot saying what goes inside the menu. The grid
-owns the Mantine `Menu`, opening it at the pointer and closing it on Escape, an
-outside click, a body scroll and after an item is picked.
+`renderRowContextMenu` supplies the contents of the menu. The grid renders the
+Mantine `Menu`, opens it at the pointer and closes it on Escape, an outside
+click, a body scroll and after an item is picked.
 
 ```tsx
 <TMDataGrid.Table<Employee>
@@ -157,10 +158,10 @@ a pure function of its arguments and do the work in the item handlers. Return
 the row with `data-context-menu` while its menu is open, so an action meant for
 a multi-selection reads `table` and falls back to the clicked row.
 
-Under `cellSelection: "range"` the grid has its own items for this menu - copy,
-export, include headers. `internalItems` is those items, and **reading it hands
-the composition over**: place it and the menu is exactly what you returned;
-never mention it and the grid keeps its half above a divider and yours below.
+Under `cellSelection: "range"` the grid has its own items for this menu: copy,
+export and include headers. `internalItems` is those items, and **using it takes
+over the composition**: place it and the menu is exactly what you returned; omit
+it and the grid keeps its own items above a divider and yours below.
 
 ```tsx
 renderRowContextMenu={({ row, internalItems }) => (
@@ -202,14 +203,14 @@ Returning an empty list leaves the column with no menu button at all.
 
 A row is a strip of cells, some sticky in pinned lanes, and hover, selection,
 the highlight, the cell range and striping all paint on top of it. `--row-bg`
-feeds the variable those layers compose against; `background` wins over all of
-them and kills them. `striped` follows position in the view, so it survives
-sorting and filtering rather than sticking to records, and pinned rows sit it
-out.
+sets the variable those layers compose against; `background` overrides all of
+them and they stop showing. `striped` follows position in the view, so it
+survives sorting and filtering rather than sticking to records, and pinned rows
+are not striped.
 
 Rows carry `data-selected`, `data-selected-bg`, `data-highlighted`,
 `data-grouped`, `data-depth`, `data-context-menu` and `data-row-id`, so a
-stylesheet can reach any of it without a callback.
+stylesheet can target any of it without a callback.
 
 ## The details panel
 
@@ -223,9 +224,9 @@ const grid = useTMDataGrid({
 });
 ```
 
-Each panel is measured, so heights need not be uniform;
-`renderDetailsEstHeight` (default `160`) is only what the virtualizer assumes
-for one it has not seen. A generated chevron column, `DETAILS_COLUMN_ID`, is
+Each panel is measured, so heights need not be uniform.
+`renderDetailsEstHeight` (default `160`) is what the virtualizer assumes for one
+it has not measured yet. A generated chevron column, `DETAILS_COLUMN_ID`, is
 prepended and pinned left after the checkbox and tree lanes; it cannot be
 hidden, moved, resized or unpinned, and its header opens and closes every panel.
 
@@ -233,8 +234,8 @@ Which rows are open is TanStack's own `expanded` state, so anything can open
 one - `row.toggleExpanded()` from a menu item, `initialState.expanded`,
 `table.toggleAllRowsExpanded()` - and it persists as a `data` slice. The panel
 is a cell spanning the row, not a row: `aria-rowcount` still counts records, and
-a click inside it stops there rather than selecting the row underneath. Group
-rows have no panel; expanding one opens its children.
+a click inside it does not select the row underneath. Group rows have no panel;
+expanding one opens its children.
 
 ## Pinning and numbering
 
@@ -249,26 +250,26 @@ const grid = useTMDataGrid({
 });
 ```
 
-There is no built-in pin gesture and no pin icon - build one from TanStack's own
+There is no built-in pin gesture and no pin icon. Build one from TanStack's own
 `row.pin("top" | "bottom" | false)`, `row.getIsPinned()` and `row.getCanPin()`,
 either as a display column whose cell is a pin button or in the row context
 menu. Read the pinned state through a subscription
 (`useSelector(row.table.store, () => row.getIsPinned())`) rather than calling it
 in a component body: the `row` identity survives a pin, so the React Compiler
-would cache the call and the icon would never change. Whichever gesture you
-build, put unpin in it too. Pinned rows leave the scrolling order and render in
+would cache the call and the icon would never change. Whichever control you
+build, include unpin in it. Pinned rows leave the scrolling order and render in
 sticky blocks: top under the header, bottom above the summary row.
 
-Pinned rows are still body rows - selection, editing, details, the context menu
-and per-row styling all behave normally. What they sit out are the statements
-about scrolling order: striping, the cell range, and the number gutter. A pinned
-row stays at its edge even when a filter or the pager would have dropped it, and
-**group rows never pin**.
+Pinned rows are still body rows: selection, editing, details, the context menu
+and per-row styling all behave normally. They are excluded only from the
+features that depend on scroll order: striping, the cell range and the number
+gutter. A pinned row stays at its edge even when a filter or the pager would
+have dropped it, and **group rows never pin**.
 
-`enableRowNumbers` adds a gutter outermost left that numbers the current view -
-sorted, filtered, continuing across pages. It answers "where am I in what I am
-looking at", not "which record is this"; a stable identifier is a column of your
-own over the record's id.
+`enableRowNumbers` adds a gutter outermost left that numbers the current view:
+sorted, filtered, continuing across pages. The number is a position in the
+current view, not an identifier for the record. For a stable identifier, add a
+column of your own over the record's id.
 
 ## Common mistakes
 
@@ -276,7 +277,7 @@ own over the record's id.
 
 A coloured row stops responding to hover, selection, the highlight and the cell
 range, because `background` paints over every layer composed on top of the row.
-Nothing errors; the row simply goes inert.
+Nothing errors; the row stops reacting.
 
 Wrong:
 
@@ -296,8 +297,7 @@ Source: `src/docs/row-styling.md` (Set `--row-bg`, not `background`).
 
 `table` keeps one identity for the life of the grid, so the React Compiler
 memoizes a bare `getSelectedRowModel()` against it. The count renders once and
-then never changes, which reads as a broken toolbar rather than a missing
-subscription.
+then never changes.
 
 Wrong:
 
@@ -317,9 +317,9 @@ Source: `src/docs/row-selection.md` (Acting on a selection).
 
 ### HIGH Looking for the highlight in `rowSelection`
 
-The highlight is separate state, which is what lets
-`"checkboxAndHighlight"` run both at once. It never appears in `rowSelection`,
-`getSelectedRowModel()` or the persisted selection slice.
+The highlight is separate state, which is what lets `"checkboxAndHighlight"`
+run both at once. It never appears in `rowSelection`, `getSelectedRowModel()` or
+the persisted selection slice.
 
 Wrong:
 
@@ -366,10 +366,10 @@ Source: `src/docs/row-details.md` (Opening a row from elsewhere).
 
 ### MEDIUM Assuming group rows behave like data rows
 
-Group rows are built on their first child's record. They sit out `onRowClick`,
-`onCellClick`, `onCellDoubleClick` and `onCellContextMenu`, they never pin, they
-take no row number, and they have no details panel. A handler written as though
-every row reaches it will silently skip them.
+Group rows are built on their first child's record. They do not fire
+`onRowClick`, `onCellClick`, `onCellDoubleClick` or `onCellContextMenu`, they
+never pin, they take no row number, and they have no details panel. A handler
+written as though every row reaches it silently skips them.
 
 Source: `src/docs/row-interaction.md`, `src/docs/row-pinning.md`.
 
@@ -388,16 +388,16 @@ Source: `src/docs/row-details.md`.
 
 ### MEDIUM Expecting pinned rows to persist
 
-`rowPinning` is deliberately left out of `settingsKey`: row ids are data, and a
+`rowPinning` is deliberately left out of `settingsKey`: row ids are data, and the
 layout store outlives any one data set. A pinned id whose row leaves `data` is
-simply not shown, and returns to its edge if the data comes back.
+not shown, and returns to its edge if the data comes back.
 
 Source: `src/docs/row-pinning.md`.
 
 ## References
 
 - [Rows API](references/rows-api.md) - every option, table prop, callback,
-  export, CSS variable and data attribute these five topics own.
+  export, CSS variable and data attribute belonging to these five topics.
 
 See also: the `grouping` skill for group rows and the tree lane, the
 `cell-selection` skill for the cell cursor and ranges, and the `appearance`

package/skills/rows/references/rows-api.md

@@ -33,17 +33,17 @@ All are props of `TMDataGrid.Table`, not hook options.
 | `onCellContextMenu` | `(args) => void` | Cell right-click. |
 | `renderRowContextMenu` | `({ table, row, cell, close, internalItems }) => ReactNode` | Contents of the row's context menu. `null` for no menu. Reading `internalItems` hands the composition over. |
 | `renderColumnMenuItems` | `({ column, table, internalItems }) => ReactNode[]` | Contents of a column's menu. An empty list removes the button. |
-| `rowContextMenuProps` | `MenuProps` | Passed to the Mantine `Menu` untouched apart from its open state. |
+| `rowContextMenuProps` | `MenuProps` | Passed to the Mantine `Menu` unchanged, apart from its open state. |
 
 `TMDataGridCellEventArgs` is `{ cell, row, column, event }`. The context-menu
 slot's `cell` is `null` only when a custom cell renderer stopped the
-event. One `Menu` serves the whole body: a closed Mantine `Popover` still runs
-its hooks on every render, and the virtualized body re-renders every scroll
-frame.
+event. One `Menu` serves the whole body rather than one per row: a closed
+Mantine `Popover` still runs its hooks on every render, and the virtualized body
+re-renders on every scroll frame.
 
 On touch devices a long press (500 ms) opens the same menu. Mantine sets
-`user-select: none` on the element it hangs a context menu off, so body cell
-text stops being mouse-selectable in a grid that has one.
+`user-select: none` on the element it attaches a context menu to, so body cell
+text is not selectable with the mouse in a grid that has one.
 
 ## Styling
 
@@ -69,7 +69,7 @@ Row data attributes:
 | `data-grouped` | Group rows |
 | `data-depth` | Every row - the nesting level |
 | `data-context-menu` | The row whose context menu is open |
-| `data-deleted` | Rows marked for deletion under batch editing |
+| `data-deleted` | Rows marked for deletion under draft editing |
 | `data-row-id` | Every row - its id |
 
 ## Details

package/skills/server-side/SKILL.md

@@ -10,7 +10,7 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.0'
+  library_version: '2.0.0-beta.2'
 sources:
   - 'Jielga/TMDataGrid:src/docs/server-side.md'
   - 'Jielga/TMDataGrid:src/tmdatagrid/useTMDataGrid.tsx'

package/skills/testing/SKILL.md

@@ -11,7 +11,7 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.0'
+  library_version: '2.0.0-beta.2'
 sources:
   - 'Jielga/TMDataGrid:src/docs/testing.md'
   - 'Jielga/TMDataGrid:src/tmdatagrid/components/TMDataGrid.tsx'
@@ -71,7 +71,8 @@ Body cells carry no `data-dg-part` - the coordinate pair already names them.
 
 **Keyed by `data-row-id`**: `row`, `entry-row`, `details`, `select-row`,
 `details-toggle`, `group-toggle`, `edit-row`, `delete-row`, `save-row`,
-`cancel-row`, `restore-row`, `confirm-new-row`, `discard-new-row`.
+`cancel-row`, `row-state`, `revert-row`, `restore-row`, `confirm-new-row`,
+`discard-new-row`.
 
 **Keyed by `data-column-id`**: `header`, `header-sort`, `header-menu`,
 `header-filter`, `filter-row`, `filter-pill`, `columns-toggle`.
@@ -148,11 +149,11 @@ rather than adding a timeout.
 
 ## Common mistakes
 
-### Selecting chrome by its aria-label
+### Selecting a control by its aria-label
 
-Every icon-only control has one, but they come from `labels` and are yours to
-translate. A suite written on `getByRole("button", { name: "Filters" })` breaks
-the day the grid renders in Swedish, and again on any copy change. Use the part.
+Every icon-only control has one, but they come from `labels` and are translated.
+A suite written on `getByRole("button", { name: "Filters" })` breaks as soon as
+the grid renders in Swedish, and again on any copy change. Use the part.
 
 ### Counting row elements
 
@@ -163,10 +164,10 @@ layout, so the count depends on the stubbed element size. Assert
 
 ### getByRole("cell") on a grid with cell selection
 
-`enableCellSelection` turns every `cell` into a `gridcell`, and the grid's
-`table` into a `grid` - a widget with a keyboard cursor is not a table of
-content. Tests written on the role break when the feature is switched on. Query
-cells by `[data-row-id][data-column-id]`, which do not move.
+`cellSelection` turns every `cell` into a `gridcell`, and the grid's `table`
+into a `grid`, because a widget with a keyboard cursor is not a static table.
+Tests written on the role break when the feature is switched on. Query cells by
+`[data-row-id][data-column-id]` instead.
 
 ### Expecting a row far down the list to exist