# XWUISuperDataWorkspace

A generic record workspace: `collection`, `record`, `view` and `field` items behind
one provider. It is the closest thing in the tier to a table-with-everything-attached, and the
starting point when a product needs CRUD over data whose shape is configured rather than compiled
in.

## When to use

- An admin-style data surface where collections and fields are defined at runtime.
- Saved views, where each view is a `section` and the provider narrows the query.
- Bulk edits over a selection with confirmation and a capability check.

Reach for `XWUICRUD` or `XWUISpreadsheet` when the schema is fixed and the interaction is
form-shaped or grid-shaped; this hub is for provider-defined data.

## Configuration surface

The constructor is `new XWUISuperDataWorkspace(container, data, config)`. `data` is the state
you already hold; `config` is how the hub talks to your backend.

`config.provider` is the only integration point that matters:

- `list(query, signal)` -> `{ items, total?, nextCursor? }`. `query` carries
  `text`, `sectionId`, `cursor`, `limit` and `sort`; honour `signal`, because
  every new search, section switch or refresh aborts the in-flight request.
- `execute(request)` -> `{ message?, items?, refresh? }`, required by any entry
  in `config.actions`. An action with no `execute` fails with
  `XWUI_SUPER_ACTION_PROVIDER_REQUIRED` rather than silently doing nothing.
- `subscribe(listener)` is optional; when present the hub reloads on every
  push and unsubscribes on destroy.

The rest of `config`: `title` / `subtitle` / `className` for chrome;
`columns` (each `key` indexes the row built from the item's own fields plus its
`values` bag, so a custom column needs a matching `values` entry); `actions`
scoped `global` | `selection` | `item`, optionally `requiresConfirmation` and
`capability`; `confirmAction(action, items)` to gate confirmations (without it
a confirming action only emits `confirmationRequired`); `mountDetail` to own
the detail pane; `context` for the `XWUISuperContext` that authorizes
capabilities; plus `searchable`, `selectable`, `selectionMode`
(`single` | `multiple`), `autoLoad` (default true, loads on connect when a
provider exists), `refreshAfterAction` (default true), `pageSize` (default 50),
`density` (`compact` | `comfortable` | `spacious`) and a `labels` bag for every
piece of built-in copy.

Authorization is fail-closed: an action carrying a `capability` with no
`config.context` authorizer is **denied**, not allowed. Leave `capability` off
actions that genuinely need no permission.

`data` seeds and mirrors the view: `items`, `sections` (the tab strip),
`metrics` (the tile row), `query`, `activeSectionId`, `activeItemId`,
`selectedIds`, `loading`, `loadingMore`, `actionPendingId`, `error`, `total`,
`nextCursor` and `lastActionMessage`. Omit `columns` and the table falls back to
Title / Status / Updated.

## Data workspace

Provider-driven records, collections, views, fields, bulk actions, and detail experiences.

```example
file: examples/BasicUsage.ts
html: examples/BasicUsage.html
title: Data workspace
description: Provider-driven records, collections, views, fields, bulk actions, and detail experiences.
```

```api
```