` attribute (`className`, `style`, `id`,\netc.) via passthrough — `UnstyledTable` composes\n`ComponentPropsWithoutRef<'table'>` like every other primitive in this\nlibrary.\n\n`TableColumn`:\n\n| Field | Type | Default |\n|---|---|---|\n| `key` | `keyof T` | — |\n| `header` | `string` | — |\n| `render` | `(row: T) => ReactNode` | — |\n| `sortable` | `boolean` | `false` |\n\nUncontrolled by default — pass `sort` + `onSortChange` to control the sort\nstate yourself. `render` overrides how a cell displays a column's value;\nwithout it, a cell just shows `String(row[column.key])`.\n\n### Sorting\n\nOnly one column can be sorted at a time. Clicking a `sortable` column's\nheader cycles ascending → descending → unsorted; clicking a different\nsortable column resets to ascending on that column instead. Non-sortable\ncolumns render as plain `
` text — no button, no `aria-sort`.\n\n### Filtering\n\n`filterable` renders a single `` above\nthe table. Typing filters `data` client-side by a case-insensitive\nsubstring match against every column's raw value (`row[column.key]`, not\nits rendered output) — there's no async/remote search, matching the same\nclient-side-only scope as `@asnewyla/unstyled-select`'s search. Filtering\nis always applied before sorting.\n\n### Row identity and selection\n\n`getRowKey` gives each row a stable identity — used both for React's own\n`key` (so a row's DOM state, like an uncontrolled input inside a custom\n`render`, stays attached to that row across a sort/filter reorder) and for\ntracking `selected`. Without it, identity falls back to\n`JSON.stringify(row)`, which works as long as rows are unique by content.\n\n`selectable` adds a checkbox column: a per-row checkbox plus a \"select\nall\" checkbox in the header (`aria-label=\"Select all rows\"`, native\n`indeterminate` when some but not all *currently rendered* rows are\nselected). `UnstyledTable` never mutates `data` — deleting/exporting/\nacting on a selection is entirely the consumer's job, using `selected` +\nwhatever action they wire up next to the table (see the\n`BulkDeleteSelectedRows` Storybook story).\n\n### Pagination\n\n`paginated` slices the final (filtered, then sorted) row set into pages of\n`pageSize` rows and renders a footer below the table: four buttons —\n\"First page\", \"Previous page\", \"Next page\", \"Last page\" (plain text\ncontent, which doubles as the accessible name) — around a plain-text\n`\"Page X of Y\"` indicator. First/Previous are disabled on the first page,\nNext/Last on the last page, via native `disabled` rather than just visual\nstyling. Each button also carries `data-pagination-action=\"first\" |\n\"previous\" | \"next\" | \"last\"`, a stable hook for consumers to style them\n(e.g. as icon buttons) without depending on their text content. There's no\nbuilt-in page-size selector; `pageSize` is a fixed prop. The\ncurrent page clamps automatically if the underlying row count shrinks out\nfrom under it (e.g. filtering down to fewer rows/pages than the page you\nwere on) — this happens on every render as a plain derived value, not via\nan effect, so it can't ever momentarily show a page that no longer exists.\n\n### Accessibility\n\nRenders a real semantic `
`/``/`` — row/column-header/\ncell roles all come from the native elements, not ARIA overrides. Sortable\nheaders use a real `