# XWUISuperInbox

A single work queue for everything that wants a person's attention: notifications,
mentions, assignments, approvals, and failures, whatever system produced them. Items carry a
`kind` of `notification`, `mention`, `assignment`, `approval` or `failure`, so one inbox can
front several upstream sources without the user learning where each alert came from.

## When to use

- One place for a user to triage cross-system alerts, instead of one badge per module.
- Approvals and failures that need an action (approve, retry, archive) taken from the list itself.
- A section per source or per state, with counts, driven by `data.sections`.

Reach for `XWUISuperSearch` when the user is *looking for* something rather than working a queue,
and for `XWUISuperObservability` when the audience is operators reading machine telemetry.

## Configuration surface

The constructor is `new XWUISuperInbox(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.

## Inbox

Unified notifications, mentions, assignments, approvals, and failures in one queue.

```example
file: examples/BasicUsage.ts
html: examples/BasicUsage.html
title: Inbox
description: Unified notifications, mentions, assignments, approvals, and failures in one queue.
```

```api
```