nexus-shared 3.2.0 → 4.1.0

package/CHANGELOG.md

@@ -4,6 +4,2365 @@ Notable changes to `nexus-shared`. The **values** of exported constants count as
 Nexus backend's own numbers, and a value that differs from the backend by one does not fail loudly — it silently
 means the wrong thing on every record and every permission check.
 
+## 4.1.0
+
+**Additions only.** Everything written after `4.0.0` was published (2026-11-07 16:14 UTC; the first change after it is
+card SUB4-component-review-fix-finish on 2026-11-09). Checked against the published `4.0.0` (`npm pack nexus-shared@4.0.0`)
+with the four scripts in `Frontend/scripts/release-compare`, on 2026-11-11:
+
+- **Exports** (`compare-exports.cjs`): every export of `4.0.0` is still exported; **279 are new**, 212 from
+  `nexus-shared` and 67 from `nexus-shared/client`, none from `nexus-shared/server`. Per card, as each counted its own:
+  2 are [card SUB4-component-review-fix's](#the-round-4-reviews-fixes-a-hasty-enter-a-question-read-out-a-remembered-value-kept), 4 are [card C-crud-hidden-value-after-save's](#the-row-a-save-leaves-is-what-was-sent), 58 are [card C-mail-thread's](#a-mail-thread-its-source-and-backend-and-three-params-any-page-can-use), 49 are [card C-domain-card's](#a-records-card-in-a-message-read-live-from-its-module), 18 are [card C-message-bell's](#a-message-bell-the-unread-count-on-a-top-bar-one-read-however-many-bells), 3 are [card C-mail-thread-fit's](#a-mail-threads-window-opens-on-its-subject-and-its-reply-box-keeps-one-row-on-a-phone), 1 is [card C-crud-row-confirm's](#a-row-form-asks-before-it-saves-a-picker-reads-another-listing-a-history-names-who), 8 are [card C-documents-add-only's](#an-owners-files-that-a-records-state-lets-only-be-added-to), 9 are [card C-row-picker-narrow's](#a-rows-picker-narrowed-by-the-forms-value-and-the-rows-own), 36 are [card C-mail-client's](#a-mail-client-three-panes-docked-chat-windows-and-a-compose-window), 58 are [card C-dashboard-board's](#a-customisable-dashboard-widgets-in-size-presets-one-call-per-module-only-near-the-screen), 1 is [card C-rows-solve's](#a-rows-worked-out-input-typed-in-a-lines-total-sets-its-rate), 5 are [card C-mail-client-fix's](#the-mail-clients-fixes-and-a-crud-forms-computewith), 5 are [card component-details-0620-look's](#details-as-the-2026-06-20-window-drew-them-a-list-of-rows-as-a-table-history-names-from-the-app), 7 are [card C-gallery-pending-removal's](#a-gallery-whose-removals-wait-for-a-review); the rest are named in their sections
+  ([tree filters](#a-trees-filter-tabs), [the picture column first](#a-tables-picture-column-first-and-unpin-on-a-column-its-page-pins), ...).
+- **Constants** (`compare-values.mjs`): 94 compared (90 from `nexus-shared`, 4 from `nexus-shared/server`), 2 differ,
+  both additions: `NexusModule.Inventory` (131072) and its
+  `NEXUS_MODULES` entry ([card INV-0-comp](#inventory-added-at-bit-17-no-value-moves)). No value changed or moved;
+  `NexusModule.Report` keeps its value and is [deprecated](#nexusmodulereport-is-deprecated-the-backend-retired-it).
+- **Types** (`compare-types.cjs`, new with this release: each exported type's members and optionality, each function's
+  required parameters): 1,410 exports compared, **0 breaks**. 12 members are new and required, all on types this package
+  builds and an app only reads: `ChatRun.notification` (made by `groupChatMessages`), `TreeNode`'s six `shown...` counts
+  (made by `TreeStore`), and `FormStore.setFromPerson` (a method of the class, which no app can implement: it has
+  private members). One member's type widened: `TableState.pinned` may hold `null` for a column its page pins and the
+  user unpinned, which [could not be done before](#a-tables-picture-column-first-and-unpin-on-a-column-its-page-pins);
+  `columnPin(column, pinned)` reads the side. No app in this repository reads it.
+- **Stylesheet**: no class name or custom property of `4.0.0` removed; 241 added.
+- **`nexus-icons ^1.2.0`** (`compare-floor.cjs`): the 130 names this package imports are all in the published `1.2.0`.
+
+The packages built on this one take it as they are: `nexus-admin` `4.0.0` asks `^4.0.0` and is unchanged since it was
+published; `nexus-public` `3.0.2` asks `^3.0.0 || ^4.0.0`.
+
+### `NexusModule.Report` is deprecated: the backend retired it
+
+The backend retired its Report module (`EModules.Report`, 256) on 2026-11-11: print layouts, the print door and their
+history are the Configuration module's now. `NexusModule.Report` is `@deprecated` and **keeps its value**, so bit 8 is
+never given to another module and an old permission mask that holds it still reads; its `NEXUS_MODULES` entry stays as
+well (removing an entry changes a published constant, which only a major may do), so an old `/api/app/report/...` proxy
+URL is still recognised. An app sets no `API_REPORT` any more, and a list a person picks a module from leaves it out
+(`info.module !== NexusModule.Report`). This package builds no such list; `nexus-admin`'s `fallbackModules()`, used only
+when the backend's module list cannot be read, still names it until `nexus-admin` is next released.
+
+### A tree's filter tabs
+
+Card C-tree-filters (2026-11-10), for a permission set editor: small tabs above a checkable `TreeView` (All actions ·
+View only · Add and edit · Trash and delete) that narrow its rows. 2 exports added (`TreeFilter`, `TreeFilterMatch`).
+
+- **`TreeView` `filters`**: each a `TreeFilter` with an `id`, a `label` and a `match` asked of every leaf (none shows
+  all). The tree shows the leaves a filter takes and the parents that hold one. While one is on, checking a parent or
+  Select all checks only the leaves shown, a parent's box and count read only them, and a hidden leaf keeps its check.
+  The value is the same whatever tab is on: switching never changes it and never makes a form dirty.
+  `defaultFilter`, `rememberFilter` (`{ key, viewer }`, kept per signed-in person), `onFilterChange` and
+  `filtersLabel` (default "Show").
+- **`TreeStore`**: `setFilter` and the option `filter`; each node gains its `shown...` counts beside the whole ones,
+  which the value and `counts()` still read.
+- **`TabButtons` `wrap`**: the options wrap onto more rows when they do not fit (`nav` design), as the tree's tabs do on
+  a phone.
+- Proved by `test-tree-store.mts` and nexus.template's `/demo/tree-view` "Filter tabs: a permission set".
+
+### A table's picture column first, and Unpin on a column its page pins
+
+Card C-picture-first (2026-11-10): every data table draws its picture or logo column first, after the row number.
+
+- **`TableColumn.lead`**: drawn first of the page's columns until the user moves it; when the page pins other columns on
+  the left, a lead column is pinned there too, at their head. `pictureColumn` sets it. The user hides, moves, pins and
+  unpins it like any column, and Reset columns brings it back. `leadColumns(columns)` arranges them;
+  `namingColumn(columns)` is the column that names a row in a question ("Delete Kathmandu?"), never a picture.
+- **Unpin works on a column its page pins.** The user's sides are a `TablePins` (`null` for unpinned), read by
+  `columnPin(column, pinned)`; before, a page's own `pinned` came back.
+- Proved by `test-table.mts`.
+
+### A full-size popup fits a phone screen while the address bar shows
+
+A full-size popup is `100dvh` tall where the browser knows it (`100vh` stays for older ones), so on a phone or tablet
+its footer (Save, a tab's footer) is no longer under the screen's edge while the address bar shows; the theme panel's
+height follows the same rule. CSS only.
+
+### The round-4 review's fixes: a hasty Enter, a question read out, a remembered value kept
+
+Cards SUB4-component-review-fix and SUB4-component-review-fix-finish (2026-11-07/08): six findings of the review of
+the subscription round's work in this package. Additions only: 2 exports, both from `nexus-shared`
+(`isAwaitedCrudField` and the type `CrudRecordRead`, the read-state rule the profile and the Details tab share), and
+`Popup`'s `aria-describedby` prop. **One behaviour changes for every message box**: a held Enter, or one within 300 ms of the Enter
+before it, no longer answers it.
+
+- **A hasty Enter never answers a box.** The Enter that opened a question (in a form's box, with `confirm`) could press
+  the Confirm it gave the focus to - by the key's repeat or the second tap of a double press - and save before the
+  details were read. Any Enter inside a message box with `repeat`, or within 300 ms of the Enter before it, is held;
+  the next deliberate Enter answers as before. A check that opens a box with Enter and answers with Enter waits 300 ms.
+- **The question is read out.** A message box is described (`aria-describedby`) by its message and its `details`, so
+  a screen reader reads them with the title as the focus enters, before Confirm.
+- **A remembered choice on a long list is kept.** A picker that cannot name a record by its key is looked through page
+  by page; when the 20 pages ran out before the list ended, a kept value not met was counted gone and forgotten. It is
+  now unknown: kept, not opened. Only the list's end (as the box reads one) makes it gone, and the pages are asked in
+  the box's own `pageSize`, so a loader paging by its own size with no `hasMore` is no longer cut after one page.
+- **A value opened from memory redraws what follows it.** An input worked out from it (`compute`), sized by it
+  (`spanWhen`), shown or labelled by it, drew its old state until something else changed; memory's opening and a
+  picker's late answer now redraw the inputs that follow, as a change does.
+- **A profile field the row lacks** (`details.profile.fields`) holds its line while the record is read and says "Not
+  loaded" when the read fails, as the Details tab's fields do; before, it was left out of both the profile and the
+  Details tab, and appeared late, moving the profile.
+- **A picker asked for a remembered value says it is busy**: its box is `aria-busy` and described "Loading" while the
+  value may still come (a search's pages stay the list's busy state), and a person in the box keeps the focus when the
+  value opens - any input mounted again under the focus (a late value, a load, a reset) gets it back.
+- Proved by `test-input-memory.mts` (1,200 records, a loader paging by 20, followers drawn), `test-crud-profile-fields.mts`
+  (the read state) and nexus.template's `form-confirm.cjs` E, `crud-workspace.cjs` M and `input-memory-picker.cjs` K;
+  each new line seen red against the package as it was before.
+
+### The row a save leaves is what was sent
+
+Card C-crud-hidden-value-after-save (2026-11-09), found by the HR leave setup (card H2): a value hidden by `showWhen`
+stayed on screen after a save until the list was read again, though the server held none. A CRUD built the saved row
+from the form's own values, over the row, under the answer; a page's `transform` that sends null for a hidden value
+(a leave type's "Carry forward at most" while it does not carry forward) changed only the body, and a Nexus answer
+leaves its nulls out, so nothing took the form's old value off the row. Additions only: 4 exports, all from
+`nexus-shared` (`crudSavedRecord`, `crudHiddenOnSave` and the types `CrudSent`, `ApiFormSent`). **What can move for an
+app:** the row after an Add or an Edit, on a data table and in a tree, wherever it differed from what was sent.
+
+- **The row is what was sent** (`crudSavedRecord`): the row the form was opened on, then the body `transform` made -
+  when it is a record - over the form's values, then the answer. A field the body sends as null is empty on the row;
+  one it reshapes (a range sent as its two days) shows as sent, also when the answer is only a token. A shown field the
+  body leaves out keeps the form's value, as before; a body that is not a record (a list, a `FormData`) changes nothing.
+- **A value `showWhen` hid when the form was saved** is on the row only as the server holds it: as the answer gives it
+  when the answer is a record - a field it leaves out has none - else as the body gives it. So a hidden value the server
+  clears by its own rule leaves the row too, with no `transform` (the demo's amenities: a free one has no charge). The
+  hidden box still keeps what was typed in it, and showing it again brings it back. A picture and an input worked out
+  from others (`compute`) hold no value of the form's and are left as they were.
+- The values of a row are the ones the save sent, never ones typed while it ran.
+- **`ApiForm` `onSuccess`** gets a fourth argument, `sent` (`ApiFormSent`): the values as they were sent and the body
+  `transform` made of them.
+- Not changed: what a form sends. A value `showWhen` hides is still sent unless the page's `transform` clears it.
+- Proved by `test-table.mts` (the leave type's case under the old merge and the new one, a dropped field, a token
+  answer, a reshaped body) and nexus.template's new `crud-saved-row.cjs`, whose answers a route makes Nexus-shaped (nulls
+  left out): its three row lines failed in both motion modes against the package as it was before.
+
+### A mail thread, its source and backend, and three params any page can use
+
+Card C-mail-thread (2026-11-09), card 2 of the domain messages spec: mail inside an app - a thread with a subject, a
+sender and its people (To, Cc, Bcc), whose replies are the chat's own lines, which a module can write into when
+something happens. Built to the spec's wire before the Message module's `Mail` doors exist, and proved against a
+pretend `Mail` controller in nexus.template that answers that wire. Additions only: 58 exports (45 from `nexus-shared`,
+13 from `nexus-shared/client`), compared with the build before the card by `Frontend/scripts/release-compare`; no
+exported constant changed. **What can move for an app:** nothing it already draws - a chat line that names no kind is
+drawn as before, and `.nx-chat-list__badge` is `inline-grid` (the same in the conversation list, where it is a flex
+item; now its own width in a table cell too).
+
+- **`MailThread`** (`nexus-shared/client`): the head - subject, time, From, To, Cc and Bcc **only as the source gives
+  it**, each list folded to three names and a "+2" button that opens the rest in place (`MailPeople`), the reader's own
+  name saying "you", the record it is about (`MailDomainLine`, or `renderDomain`) - over the chat's `ChatThread` and
+  `ChatComposer` on `source.threadSource(id)` through `ChatStore`, unchanged. A person copied unseen reads
+  `MAIL_BCC_NOTE` over the reply box; when they reply, or when anyone else's line arrives, the head is read again
+  (a reply makes a blind copy a Cc). `onChanged` tells the page what arrived (`reason: "notification"` when the record
+  may have changed, which also bumps the record slot's `revision`), `onSummary` its counts (a list's row clears its
+  unread), `onHead` each head read. States: bones while the head loads, a failure with Try again in the head and in
+  the thread, "This message is not available to you." for a 403 or 404, a closed thread read but not answered. A band
+  across the panel, never a box (`Nexus.Mail.css`, new); the chat panel's frame and body.
+- **`ChatMessage.kind`** (`ChatMessageKind`: `chat`, `mail`, `notification`): `NexusChatBackend` reads it from a row's
+  `messageType` (the backend's `EChatMessageTypes` 0, 1, 2, or the word). A notification is its own run
+  (`ChatRun.notification`) and `ChatThread` draws it as an event line (`ChatEventNote`): the bell, who acted, when, and
+  the words, quiet, with no side and no bubble.
+- **`ChatComposer` `notice`**: a line over the writing area that the text area is described by.
+- **`MessageSource`** (`MailInterfaces.ts`, beside `ChatInterfaces.ts`; the builder's `MessageInterfaces.ts` keeps its
+  name): `inbox`, `thread`, `threadSource`, `compose`, `archive`, `unarchive`, `unread`, `people`, `defaults`, in this
+  package's words (`MailRole` `from | to | cc | bcc`, `MailList` `inbox | unread | sent | archived`).
+  **`MessageBackend`** / **`NexusMessageBackend`** / **`defineMessageBackend`** map them to an API (the Message
+  module's `Mail` controller by default; `module` and `controller` overridable, as `NexusChatBackend`), reading the
+  backend's numbers as words; **`apiMessageSource`** (`/client`) is the only file that calls.
+  **`localMessageSource`** keeps a mailbox in memory with a backend's rules (who sees a blind copy, a blind copy's reply
+  made a Cc, archive and unread per person, a retried send written once, every wrong input of a new message at once),
+  `as(userId)` to read it as somebody else and `post` for a module's notification.
+- **Words and helpers**: `mailPeopleLine` (three names then "+2", never "+1"), `mailBccNote`, `mailPreviewText`,
+  `newMailClientId`, `mailInboxLoader` (a server-paged table's loader), `MAIL_ROLE_LABELS`, `MAIL_LIST_LABELS` and the
+  limits `MAIL_PEOPLE_MAX` (50), `MAIL_SUBJECT_MAX` (100), `MAIL_BODY_MAX` (4000).
+- **An inbox's columns** (`mailInboxColumns` `from`, `subject` with the record as a tag before it, `lastMessage`,
+  `when` as "14 min ago", `unread` in the chat's badge; `mailInboxColumnList` all five, fitting a 1280px window beside a
+  menu) read a `MailInboxRow`'s fields, which are the answer's own names, so a CRUD of raw rows uses them too.
+- **Three params any page can use**:
+  - **`pagedPicker(load, options)`** and **`holdPickerItems`**: a dropdown over any server search, paged, that names
+    every value it holds - from the pages shown, items handed over, a lookup by key (`find`), or the server's first
+    pages (`findPages`, 4) - so a form opened on values, or a draft brought back, never shows "Not found" for what a
+    page showed. `mailPeoplePicker(source)` is one for the people a message goes to.
+  - **`Crud` `form.createDefaults(signal)`**: an Add form's values read as it opens, over `newValues` and under the
+    values `create(values)` fixes; the inputs show disabled until they land and a draft comes back over them; a failed
+    read opens the form on `newValues` with a toast, since defaults are a help, not the record.
+    `mailComposeDefaults(source, picker)` is one: To, Cc and Bcc from the reader's defaults, named at once, and a new
+    `clientId` (give `newValues: () => ({ clientId: newMailClientId() })` too, so a form opened without its defaults
+    still sends one).
+  - **`DataTable` `rowStrong(row)`** (and a `Crud`'s `table.rowStrong`): the row's cells heavier in the text colour
+    (`data-strong`), nothing else, so it keeps its height and no column moves when it reads plain.
+- Proved by `test-mail.mts` (146: roles, Bcc hidden also in read marks, a Bcc reply made Cc, archive, unread, a
+  notification, a closed thread, a new message refused with every wrong input at once and written once, paging, the
+  paged picker, the Nexus backend's requests and answers, a notification's run, a thread through `ChatStore`; red with
+  the Bcc rule taken out) and nexus.template's new `mail-thread.cjs` (82 in both motion modes, red with the strong
+  look or the blind copy's head refresh taken out).
+
+### A record's card in a message, read live from its module
+
+Card C-domain-card (2026-11-09), card 5 of the domain messages spec: the owner's "if type is chat and it has domain type
+and id then we fetch those domain info and render those info into its own components ... we fetch that person's
+remaining and taken leave". A message about a record shows the record as a card, read from the module that owns it each
+time it is drawn, never a copy kept in the message. Additions only: 49 exports (39 from `nexus-shared`, 10 from
+`nexus-shared/client`), compared with the build before the card by `Frontend/scripts/release-compare`; no exported
+constant changed. **What can move for an app:** a `MailThread` whose record's kind has a card draws the card where
+`MailDomainLine`'s line was (folded to its title line on a thread narrower than 480px); a kind with no card draws the
+same line as before, now `DomainLine` (`.nx-domain-line`; `.nx-mail__domain` is gone).
+
+- **`ChatDomainInfo.card`** (`DomainCardDefinition`): `load(id, signal, context)` reads the record through its
+  module's card door, which checks the reader; `view(data, context)` maps the answer to `DomainCardParams`; optional
+  `extra(data)` (one more piece of this package's parts), `held` (what the placeholder holds the first time) and
+  `lifetime`. **`domainCard({ load, view })`** types `view` by `load`'s answer; `defineChatDomains` refuses a card
+  without both. **`domainCardOf(kind)`** finds it. This package holds no kind and no number: the app's rows do.
+- **`DomainCard`** (`nexus-shared/client`) `domain`, `id`, `label`, `revision`, `viewer`, `card` (instead of the
+  registered one, or `null`), `kind`, `headingLevel`, `collapsible`, `defaultCollapsed`, `ref` (`reload()`): a
+  placeholder of the card's own parts in the shape of the kind's last card (so the record lands without moving what is
+  under it, at any width - the head is laid out by the card's width, never its words), the card, "You cannot open this
+  leave request." for 403 and 404 alike, "Could not load this leave request." with Try again (which reads once) for any
+  other failure or a `view` that throws, and the kind and the record's words alone for a kind with no card or a message
+  with no id. Read again when `revision` grows, `reload()` or **`refreshDomainCards(kind, id?)`**: the card stays,
+  marked "Updated 2:45 PM" when the record turned out different or "Not up to date" with Try again when the read
+  failed; a refusal drops it. A screen reader is told each. `MailThread` passes its notifications' `revision` and its
+  reader.
+- **`DomainCardFrame`**: a card from `DomainCardParams` alone (title, kind, code and subtitle on one quiet line with the
+  link at its end, state in its tone, fields, figures with a tone mark and a hint, lines with "and 3 more", currency),
+  with an optional fold button. Values by kind with the reader's settings (`domainCardValueText`): `date`, `datetime`,
+  `days`, `money`, `number`, `person`, `text`. **`DomainLine`**: a kind's tag and a record's words.
+  `Nexus.Domain.css` (new): a band, never a box; the mail head draws a line above it, edge to edge.
+- **Reads**: **`DomainCardReads`** / **`domainCardReads`** - one read of a record at a time however many cards draw it,
+  an answer kept 30 seconds per reader (`DOMAIN_CARD_LIFETIME`), a failure never kept, a read nobody waits for aborted,
+  a read again taking only a read started after the change (and forgetting what other readers kept of the record).
+  **`DomainCardRun`** (one card's read outside React: `start`, `stop`, `reload`, `retry`, a snapshot to subscribe to)
+  and **`useDomainCard`** for a page's own look. Words: `domainCardNoun`, `domainCardRefusedText`,
+  `domainCardFailedText`; shapes: `domainCardShape`, `heldDomainCardShape`, `rememberDomainCardShape`,
+  `DEFAULT_DOMAIN_CARD_SHAPE`.
+- **`formatDays(value, { decimals, locale, empty })`** and **`dayWord`** in NumberHelpers: "1 day", "0.5 days", "2.5
+  days", grouped as `formatNumber` does.
+- Proved by `test-domain-card.mts` (100: the registry, keys, shared and kept reads, a read again after a change, abort
+  and remount, every state of a run, `refreshDomainCards`, words, values by kind, shapes; red on each of nine key lines
+  taken out on a scratch copy), `type-checks/domain-cards.tsx` (`view` typed by `load`), and nexus.template's new
+  `domain-card.cjs` (88 in both motion modes: a thread's leave card from a pretend `RequestCard` controller, one read,
+  kept per reader, Accounts' notification read once and marked updated, a reader refused with the thread whole, a
+  requisition's lines, the fold and the keyboard; every state; the placeholder's height kept at seven widths; a phone;
+  seven themes light and dark at AA - red on a scratch copy with the band rule, the revision, the narrow fold, the
+  placeholder's shape or its width-led head taken out).
+
+### Inventory added at bit 17; no value moves
+
+Card INV-0-comp (2026-11-09), card 1 of the Inventory spec (`owner-requests-2026-11-09/inventory-spec.md`): the owner's
+Demand, Dakhila and Clearance get a backend module of their own, `EModules.Inventory = 1 << 17`, after Portfolio.
+
+- **`NexusModule.Inventory`** = `1 << 17` (131072), the last bit. Every other value is what it was (`Portfolio` stays
+  65536), so no permission bitmask an app holds changes meaning - unlike `Chat`'s insertion of 2026-09-25 below. A new
+  module takes the next bit at the end, never one in between; the enum's comment says so.
+- **`NEXUS_MODULES`** gains `{ module: NexusModule.Inventory, key: "inventory", label: "Inventory", env: "API_INVENTORY" }`
+  before the app's own row: its root is read from `API_INVENTORY` on the server and its browser calls go through the
+  proxy at `/api/app/inventory/...`.
+- No export is added or removed (`NexusModule` gains a key); compared with the build before the card, every value of
+  `NexusModule` and every row of `NEXUS_MODULES` is kept and only these two are new.
+- Proved by `test-api.mts` (210: the value, Portfolio's unchanged, the key, the label, the environment name, a lookup by
+  key and by number, the browser root, the proxy, and a new check that the list names every module of the enum with an
+  API exactly once; red on a scratch copy with Inventory on bit 16, its environment misnamed, its key misspelt or its row
+  left out) and nexus.template's `api-calls.cjs` (its modules table's Inventory row, both motion modes).
+- **For an app on the published package**: nothing to do until it calls the Inventory API; then set `API_INVENTORY`
+  (the module's `.../App/Api` root) where the app's other `API_*` roots are, and allow the module in its proxy route.
+
+### A message bell: the unread count on a top bar, one read however many bells
+
+Card C-message-bell (2026-11-09), card 8 of the domain messages spec: how much internal mail waits, on every page.
+Additions only: 18 exports (13 from `nexus-shared`, 5 from `nexus-shared/client`), compared with the build before the
+card by `Frontend/scripts/release-compare`, none removed; no exported constant changed. **What can move for an app:** the
+chat icon's unread badge is drawn by the rule `Button`'s new badge shares (`Nexus.Button.css`; the same look, moved),
+and `localMessageSource`'s `unread()` now counts to 100 as the Message module's does.
+
+- **`MessageBell`** (`nexus-shared/client`) `source`, `href`, `threadHref`, `label` ("Messages"), `interval` (a
+  minute), `size`, `icon`, `maxBadge` (99), `time`: one of a top bar's ghost buttons with the count over its corner in
+  the chat's badge - one size whatever the count, "99+" from 100 on - and named for a screen reader ("Messages: 3
+  unread messages", "not checked yet", "could not be checked"). A click opens a `Menu`: the newest unread threads
+  (subject; who wrote the newest line, the record, "14 min ago"), each a link to `href?thread=<id>`, Try again after a
+  failure, and "Open inbox" (with how many in all when more wait); the arrow keys walk it, Escape and a click outside
+  close it, and opening it reads the count again. When the count goes up, one bell of the page says it once in a polite
+  live region - not on every read, not as the page loads. Drawn in nexus-admin's bar through `renderUtility` with no
+  change to nexus-admin.
+- **`useMessageUnread(source, { interval, enabled })`** and **`MessageUnreadPoller`** / **`messageUnreadPoller(source)`**:
+  one poller per source object, shared by every bell on the page. It reads when the first bell appears, then every
+  `MESSAGE_UNREAD_INTERVAL` (60 s) while the page is in front, at once when the window takes the focus or the tab is
+  shown again (`MESSAGE_UNREAD_WAKE_GAP` keeps the two from reading twice), never while the tab is hidden, never two
+  at once; a failure keeps the count read before; the last bell gone stops everything and the next one starts from what
+  was read. **`refreshMessageUnread(source)`** after a page reads or archives threads. The environment
+  (`MessageUnreadEnvironment`, `browserUnreadEnvironment`) is injected, so the rules are tested with a fake clock.
+- **Words**: `mailUnreadWords`, `mailUnreadBadge`, `mailThreadHref`; **`MAIL_UNREAD_MAX`** (100, the backend's last
+  count). `LocalMailFailure` gains `"unread"`.
+- **`Button` `badge`**: a count over a button's corner, the chat's badge, the button's size unchanged. Generic: any bar
+  or list button with a number on it.
+- Proved by `test-message-bell.mts` (48: one read for two bells, a minute, hidden reads nothing, shown and focused,
+  never two on their way, the shortest interval, failures, what is said and by which bell, the last bell gone, a hidden
+  first draw, the words, the badge, a thread's address, the local count to 100) and nexus.template's new
+  `message-bell.cjs` (77 in both motion modes: a page's clock moved by a minute, a hidden tab, the bar unmoved against
+  the server's drawing, the menu by keyboard and pointer, the arrow, a line said once, a row that opens its thread and
+  lowers the count, every state, nexus-admin's bar, a phone, seven themes light and dark).
+
+### A mail thread's head scrolls with its lines, and its record's card folds by the thread's real width
+
+Card C-mail-thread-head (2026-11-09, a bug card): nexus.web's request and leave cards in `MailThread` (REQ-thread-pages)
+showed two faults. No export added or removed; no constant changed. **What can move for an app:** a mail thread's head is
+no longer a box of its own - it scrolls with the lines; a record's card shows its figures first and folds its details
+(fields, lines, what a kind adds) under them, keeping the figures; a figure's hint keeps two lines.
+
+- **The fold follows the thread's real width.** `MailThread` measured its width once, before a window had laid out
+  (a closed dialog reads 0), so an inbox window opened the card folded at 1280 px. Now a ResizeObserver follows the
+  width: the card is drawn once a real width is known - the first decision before the browser paints, so it never
+  shows one way and then the other - and folds under 480 px, unfolds over it, until the reader folds or unfolds it
+  themselves. **`DomainCard` `collapsed` / `onCollapsedChange`**: the fold a page holds (`defaultCollapsed` stays for
+  one it does not).
+- **The head scrolls with the lines.** The head was capped at 45% of the thread with a scroll of its own, so a leave's
+  or a requisition's card showed in part at 720 px tall. **`ChatThread` `lead`**: what a conversation opens with, above
+  its first message and in the same scroll - the lines alone stay the screen reader's log. With a lead the thread opens
+  at its top (its first unread line at the top when that would be out of view), older pages load from their button so
+  the lead stays put, and whether the reader is at the bottom is worked out again when the lead grows (a card landing).
+  `MailThread` passes its head as the lead: at 1280×720 a leave's card shows whole as the window opens, every part of
+  either card is read by scrolling the thread, and the reply box keeps its 206 px.
+- **The card's fold keeps the figures.** Folded, a card is its title, its code and its figures - a leave's balance -
+  with "Show the details" for the rest; a card with nothing to fold has no fold button. The figures come first, the
+  details under them, so opening them moves nothing above. A figure's hint keeps two lines (`min-height`), so a long
+  one ("1.5 paid, 0.5 unpaid (1 day's pay)") does not change the card's height against its placeholder.
+- Proved by nexus.template's `domain-card.cjs` (105 in both motion modes; a new section reads every part of the leave
+  and requisition cards in the thread's one scroll at 1280×720 and 390×844, light and dark, the reply box's room
+  beside it) and `mail-thread.cjs` (122; a new section opens Puja's leave thread in the inbox's window: whole at 1280
+  and folded on a phone, never the other way first; the head in the thread's scroll, the thread at its top with the
+  figures in view; the fold following a narrowed and widened window until the reader folds it), red on a scratch copy
+  of the parent commit's sources. The demo's leave card carries the real one's hints: the year under Available, and the
+  paid/unpaid split under This request.
+
+### A bell's refresh asked during a read is read after it, not lost
+
+Card C-unread-requeue (2026-11-09, a bug card): nexus.web's bell (MAIL-bell) found that `MessageUnreadPoller.refresh()`
+did nothing while a read was on its way; when that read had started before a read mark, an archive or an unarchive, the
+bell kept the old count for up to a minute. No export added or removed; no constant changed.
+
+- **`refresh()` (and `refreshMessageUnread(source)`, unchanged in its contract)**: with no read on its way it reads now,
+  as before; with one on its way it asks for exactly one more read after it - however many refreshes are asked
+  meanwhile, and whether that read answers or fails - so never two reads at once. While the page is hidden nothing is
+  read: the read asked for waits and runs at once when the page is shown, even within the two seconds a shown tab's
+  focus otherwise skips. The last bell gone drops it. The minute's timer counts from the read that followed.
+- nexus.template's bell source now counts when asked and answers 150 ms later, as a server does, so the case can be
+  seen: `message-bell.cjs` presses Check now, lets Kiran write while that read is on its way, presses it again, and
+  the bell shows his line at once (red on the parent commit's poller, with the read mark's case beside it).
+- Proved by `test-message-bell.mts` (66: three refreshes during a read make one read after it, the stale answer drawn
+  meanwhile, never two on their way, the minute from the read that followed, hidden then shown, a failed read followed,
+  the last bell gone, a bell drawn again inheriting nothing; red on the parent commit's poller and on each of five lines
+  of the fix broken) and `message-bell.cjs` (79 in both motion modes).
+- **For an app that worked around it** (nexus.web's `recountUnread()` in `admin/mailbox.ts`, which refreshed once more
+  when the read on its way answered): a plain `refreshMessageUnread(source)` now does that by itself.
+
+### A mail thread's window opens on its subject, and its reply box keeps one row on a phone
+
+Card C-mail-thread-fit (2026-11-09, a bug card): nexus.web's Inbox (MAIL-pages) found two faults in `MailThread` that a
+page cannot mend without CSS of its own. Additions only: 3 exports (`fitToolbar`, `ToolbarFit`, `ToolbarSizes`, from
+`nexus-shared`), compared with the build before the card; no exported constant changed. **What can move for an app:** a
+popup given no `initialFocus` now starts on an element of its body or footer marked `data-nx-focus` before the first
+control (only `MessageBox`'s buttons carried the mark, and it names it itself); every `ChatComposer` - a chat panel's
+too - keeps its formatting buttons on one row.
+
+- **Where the focus lands.** A window opened on a thread put the focus on the first control in its body, which for a
+  thread with no "+2" and no record is the lines' scroller (`tabIndex 0`), and opened with its ring showing. The
+  window now starts on the thread's subject (`tabIndex -1`, marked `data-nx-focus`, no ring: a place to start reading,
+  the WAI dialog pattern for a long read), a screen reader reads it first, and Tab goes on through the people, the
+  record's card and the scroller - which shows its ring when the keyboard reaches it. `Popup`: with no `initialFocus`,
+  `[data-nx-focus]` in the body or footer first, then the first control.
+- **The reply box on a phone.** Under 560 px the editor's buttons took a row of their own and wrapped, three rows over a
+  two-line text area, leaving about 190 px for the lines at 390 px. **`MarkdownEditor` `toolbarOverflow`**: `"wrap"`
+  (the default, as before) or `"menu"`, one row at any width - the buttons take the room the views and the full-screen
+  button leave, and those that do not fit go into a "More formatting" menu at their end, with their shortcuts (which
+  keep working); the arrow keys reach it with the other buttons. `ChatComposer` uses `"menu"`: at 390 px the bar is
+  Write, Preview, B, I, S, "…", full screen; the reply box is as tall as on a wide window (206 px) and the lines get
+  258 px. **`fitToolbar(items, width, sizes)`** is the arithmetic, pure.
+- Proved by `test-toolbar-fit.mts` (10; red with the More button's room, the trailing divider, the all-fit case or the
+  gaps taken out) and nexus.template's `mail-thread.cjs` (107 in both motion modes: opened from the keyboard and by a
+  click, the subject focused with no ring and the scroller unringed, Tab reaching the scroller with its ring, the bar's
+  one row at 1280 and 390 light and dark, More formatting's tools at work, End reaching it, the composer's height the
+  same on a phone; red on a scratch copy of the parent commit's sources).
+
+### A row form asks before it saves, a picker reads another listing, a history names who
+
+Card C-crud-row-confirm (2026-11-09): three gaps nexus.web's pay runs (P1a) worked around. One export added
+(`PickerListController`, a type); no constant changed. **What can move for an app:** a row form's save now marks what
+pickers and joins looked up from the controller as old, as every other CRUD change does, so they read it again where it
+is next shown; and `expireLookups` marks a CRUD's own `lists` old too.
+
+- **A row form's question: `CrudRowForm.confirm`.** The same question a form's `confirm` asks (C-form-confirm): after
+  every value passes its checks, what will be saved drawn in full as a record's details, Confirm holding the focus, read
+  out with its line and details, a hasty second Enter never answering it. Params, or a function of the record and of
+  what `load` read, so it names the record: "Lock Kartik 2083?" over the run's totals. `when` asks only for some saves
+  (the demo's Duties asks only when duties are taken away).
+- **A row action that is its question alone: a `CrudRowForm` with no `inputs`.** No popup form: choosing it asks
+  (`confirm`, else "{label} {the record's name}?"), then sends what `load` read - else the record as the list has it -
+  through `transform`, and writes what `writes` names. Its buttons are the action's own word (`submitLabel`, else
+  `label`) and "Cancel". The API's toasts say it was done or why not; a refusal writes nothing; Cancel, Esc and the
+  close button send nothing; choosing it again while it asks or sends does nothing. A pay run's Lock no longer needs
+  `api.confirm` by hand. `inputs` is optional for this; an empty list is still a form.
+- **A picker over another listing: `crudPicker` `list`, `usable` and `option`.** `list` reads a listing in place of
+  the controller's `activeListing` - a controller with none, such as a pay run's CRUD endpoints (`PickerListController`,
+  `findListing` optional: without it a value the list does not offer is not looked up). `usable` says which records
+  count as usable - offered, and untagged when a form holds one - in place of the backend's rule (under 30), so a draft
+  run (31) or an invited person (30) can be picked. `option` makes each record's option, its words from two fields or a
+  state's word, made once per record read; the search reads them too. `expireLookups` also marks a CRUD's own `lists`
+  old, so a picker reading one is read again after a change there. Without them, a picker is as before.
+- **A history names who made a change**: `AuditEntry.creatorName`, when the backend's answer carries it, is said as
+  "by Sita Rai" in place of the start of the token. The Nexus backend's `AuditResponseContract` carries only
+  `CreatorUserId` (a token), so HR's histories - every module's - show "User 3fA9b2…" until it fills a `CreatorName`.
+- Proved by `test-crud-row-forms.mts` (36: a question alone, the question made for the record, its words),
+  `test-crud-picker-plan.mts` (11: the listing read, the lookup, the usable rule) and `test-audit-entries.mts` (8), each
+  key line red when broken on a scratch copy (8 of 8); `type-checks/crud-row-confirm.tsx`; nexus.template's
+  `crud-row-form.cjs` (56 with one theme, in both motion modes: the Duties question, Back, a double Enter; Promote as a
+  question alone, its refusal when the role changed since; a post's history naming Sita Sharma and showing another's
+  token; the question at 1280×720 and 390×844, light and dark) and the new `crud-picker-list.cjs` (17: `/admin/posts?people=all`
+  offers the invited people, says so under their names, and picks Maya Tamang), red on a scratch copy of the parent
+  commit's package sources.
+
+### An owner's files that a record's state lets only be added to
+
+Card C-documents-add-only (2026-11-09): since INV-2b a posted goods receipt's documents may only be added to - Drive
+refuses a rename, a mark or a delete with the core's `API_X084` ("These files can only be added to now") - but
+`DocumentList` still offered Rename and Delete on it. Eight exports added (`FileChange`, `FILE_CHANGES`,
+`allowsFileChange`, `narrowFileChanges`, `fileChangesNote`, `ownerFileActions`, `OwnerFileActions`, `FILES_ADD_ONLY`);
+no constant changed. Without the new params nothing moves.
+
+- **`changes` and `changesReason`** on every owner's files (`OwnerFilesParams`: `DocumentList`, `PictureGallery`,
+  `openPictureGallery`, the picture input, `pictureColumn`): the changes a person may make here from the record's state,
+  within what the backend allows - `["add"]` for a posted receipt keeps Upload and offers no Rename, Delete, Make main or
+  Remove, nor a Replace or an Edit that would delete or mark - with the page's sentence under the files. The changes are
+  words (`FileChange`: `add`, `rename`, `primary`, `remove`), the core's `EFileChanges` one for one, as a category's kinds
+  are MIME types. `readOnly` and `lockReason` are as they were: the files shown, nothing offered.
+- **A stale page learns from the refusal.** `FileAdapter.changesLeft(answer)` says which changes a refusal leaves
+  (`NexusDriveAdapter`: `API_X084` -> `["add"]`); after one, the list offers only those for that owner, under the server's
+  words, so a page read while the receipt was a draft stops offering what the server now refuses. The toast says what
+  was refused and why ("The file was not renamed" - "These files can only be added to now: ...").
+- The buttons offered are one pure rule (`ownerFileActions`), and an action called while not allowed does nothing.
+- Proved by `test-files.mts` (113: the rule for documents, pictures and a one-file category, the note, the refusal read
+  through the Nexus adapter), each of 8 key lines red when broken on a scratch copy; `type-checks/files-add-only.tsx`;
+  nexus.template's `/demo/pictures` "Documents only added to" (a receipt on the demo's Drive, Draft, Posted or Reversed,
+  and "Post it in another window") and its new `documents-add-only.cjs` (16 in both motion modes, light and dark at
+  1280×720 and 390×844), red on a scratch copy of the parent commit's sources (7 lines in each mode); `pictures.cjs` 123.
+
+### A gallery whose removals wait for a review
+
+Card C-gallery-pending-removal (2026-11-11): Drive holds the removals of a reviewed gallery (`company-public-gallery`,
+whose changes Nexus support approves): a Delete of a picture the public sees only marks it `pendingRemoval`, still
+served and listed, until the reviewer decides, and the person may Keep it until then. Seven exports added
+(`removalHeld`, `removalHeldSentence`, `removalHeldQuestion`, `PENDING_REMOVAL_TAG`, `REMOVAL_REVIEWER`,
+`OwnerFilesChange`, `OwnerFilesChangeKind`); no constant changed. Without a holding category nothing moves.
+
+- **Records.** `StoredFile.pendingRemoval?` and `removalAt?` (Drive's `removalTime`, while one waits), and
+  `FileCategoryInfo.holdsRemovals?` (Drive's List); each read only when true, so every other record is as before.
+- **The adapter.** `FileAdapter.remove` in a holding category answers the file marked (`removalHeld(result)` reads it);
+  the new optional `FileAdapter.keep(owner, fileId)` cancels the removal (`NexusDriveAdapter`: `PUT File/Keep/{id}` with
+  `{ ticket, id }`, a run-out ticket asked again once). An adapter without `keep` offers no Keep.
+- **The views.** A waiting picture is faded with "Removal waiting for review" as a warning band across its foot, and its
+  buttons are View and Keep (no Delete, Make main or Edit); a waiting document's row says it with the time it was asked
+  and offers Keep in place of Rename and Delete; a waiting main picture's tag sits beside it. In a holding category the
+  Delete asks "If the public sees this picture, it stays until Nexus support approves its removal." and the answer
+  decides: held, the file stays marked and the toast says "Removal sent for review"; else it is gone, as before. A
+  one-file holding category offers no Replace or in-place Edit (its Delete frees no room until the review).
+  `ownerFileActions` gains `holdsRemovals`, `keeps` and the `keep` button.
+- **Params.** `holdsRemovals` (told before the list is read; the backend's says it too) and `removalReviewer` (default
+  "Nexus support"); **`onFilesChange(files, { kind, file })`** after every change the backend took - `upload`, `edit`,
+  `primary`, `rename`, `delete`, `hold`, `keep` - with the files read again, for a page whose record follows its files.
+  `onChange(primary)` is as it was.
+- Proved by `test-files.mts` (142: the records, the Delete and Keep calls, the buttons), nexus.template's `/demo/pictures`
+  "A reviewed gallery" (the demo's Drive holds `guest-public-gallery`, `Demo/Review` publishes, approves, declines) and the
+  new `gallery-held-removals.cjs` (56 in both motion modes: by keyboard, the list, seven themes light and dark at
+  1280×720 and 390×844).
+
+### A row's picker narrowed by the form's value and the row's own
+
+Card C-row-picker-narrow (2026-11-09): nexus.web's Nikasha (INV-3) had to type an asset line's tags, because a picker
+in a line table could not be narrowed by two values at once - the form's Store and the line's Item. Nine exports added
+(`narrowingsOf`, `inputNarrowingsOf`, `narrowInputParamsBy`, `NarrowingRead`, `isEmptyNarrowed`, `formNarrowingNames`,
+`narrowedFollowers`, `DropdownNarrow`, `RowsFormValue`); no constant changed. **What can move for an app:** a row
+input's `narrowedBy` now narrows in rows (it was ignored there), and a row redraws when a value its inputs `dependsOn`
+changes; `narrowedBy` and `narrowQuery` are wider types, so code that reads `params.narrowedBy.name` reads
+`narrowingsOf(params)` instead.
+
+- **Several narrowings at once: `narrowedBy` as a list.** The options must fit every one; the box asks for the first
+  one still empty ("Pick a store first", then "Pick an item first"); the list loads afresh when any changes (one load key
+  for all). A loader is asked with `request.narrows` (every one) beside `request.narrow` (the first), and one narrowing
+  is asked exactly as before. `narrowInputParamsBy(params, read)` narrows by any values; `narrowInputParams` stays.
+- **In rows, by the row's value and the form's: `from: "form"`.** A row input's narrowing names an input of its row
+  (`{ name: "itemId" }`) or of the form around the rows (`{ name: "storeId", from: "form" }`). The Form hands a rows
+  input the form values its rows follow (`formValues`, a prop a rows input used alone takes from the page) and redraws
+  its rows when one changes. A person's change clears a value picked among the old options: a row's Item clears that
+  row's Tags (and down the row's chain), the form's Store clears every row's (to the input's own empty value); a value
+  set from code - a saved document loading - keeps them. The rule is one pure function, `narrowedFollowers`, for a
+  form, a row and every row of a form.
+- **A cell that follows its row: `dependsOn` in rows.** A change of a row value a row input names in `dependsOn` draws
+  the row again, so `cellParams` answers for the row as it is now: a line's Tags at most its Quantity (`{ max }`), the
+  picker's own rule then stopping a save when the quantity drops under the picks.
+- **`crudPicker` narrowed by several values, or by its door's path.** Each value goes into the listing's path when the
+  path names it (`list: StockBalance/Units/{storeId}/{itemId}`), as a query when `narrowQuery` (now one name or a list)
+  names it, else narrows in the browser; each answer is kept per values, shared by every row that names them, and a
+  saved value is named from them. A path listing is never read unnarrowed.
+- Proved by `test-input-narrowing.mts` (104), `test-rows-store.mts` (132) and `test-crud-picker-plan.mts` (20), each of
+  11 key lines red when broken on a scratch copy; nexus.template's `/demo/tabular-form` "An issue" (a Store, lines of an
+  Item, a Quantity and Tags from the demo backend's `StoreUnit/Units/{storeId}/{itemId}`, and "Open a saved issue") and
+  its new `row-picker-narrow.cjs` (25 in both motion modes, the Item and the Tags from the keyboard, light and dark at
+  1280×720 and 390×844), red on a scratch copy of the parent commit's sources (21 lines in each mode); the tabular,
+  group, forms, input-memory, narrowing, dropdown, form-figures and CRUD checks in both modes.
+
+### A mail client: three panes, docked chat windows and a compose window
+
+Card C-mail-client (2026-11-10), card 1 of the mail client spec (the owner: "the mail project UI make UI as mail,
+compose, send, inbox ... chat exist inside mail ... we separate by this types"). 36 exports added: `MailClient`,
+`MailReader`, `MailComposeWindow`, `ChatPopup` with their props, the pure `MailClientHelpers.ts` (the types a rail lists,
+a row's time, a thread's discussion as a chat source, the split and the drafts kept per viewer), and the wire's
+`MailThreadKind`, `MailFolders`, `MailFolderCount`, `MailKindCount`. No constant changed. **What can move for an app:**
+`NexusMessageBackend.readInboxRow` no longer reads a row's `kind` as what the thread opened with (that is `messageType`
+or `headMessageType`): on the MAIL-hub wire `kind` is the conversation's, Mail 1, Chat 2, Domain 3, and a chat's `kind`
+2 used to read as a notification.
+
+- **`MailClient`**: a bar (title, search, the split button, the app's `settings` slot - the ⚙ to its admin pages), the
+  rail (Compose; Inbox, Unread, Sent, Archived with their unread counts; Types - Mail, Chat, one per record kind the app
+  named in `defineChatDomains`, each with its unread count, a type with nothing in it left out), the list, and the
+  reading pane. Side by side, or one over the other by the reader's choice, remembered for them in this browser
+  (`nx-mail-split:<viewer>`); one over the other under 1000px of its own width; one pane at a time under 700px, with a
+  back arrow and a Folders button. It fills what holds it and never scrolls: each pane does. Params only: `source`,
+  `userId`, `view`/`onViewChange` and `threadId`/`onThreadChange` for a page's URL, `settings`, `chatSourceFor`,
+  `renderDomain`, `onChanged` (a bell's `refreshMessageUnread`), `pageSize`, `pollInterval`.
+- **The list reads as mail**: avatar, sender (strong while unread, with the thread's line count), subject — last line (a
+  chat: its last line after its author), the type as a tag in its kind's tone, the time (today's as a time, yesterday's
+  as "Yesterday", older as a date, in the reader's zone and calendar), a select box and a star (only when the source
+  stars). Ticked rows take Archive or Move to inbox, Mark read and Mark unread in one `SplitButton`. The arrow keys,
+  Home and End move between rows, Enter opens (and puts the focus at the subject); more rows load as the end shows.
+- **`MailReader`**: the subject, its type, From → To · Cc (· Bcc as the source gives it), when; the record's
+  `DomainCard`; the mails, the newest open and the earlier folded to a line each, a module's notifications as notes
+  among them; **Discuss (n)** (the thread's chat lines) and **Reply**. A chat is drawn by its head - who, since when, its
+  last line - and Open chat. Opening a conversation reads it.
+- **`ChatPopup`**: a conversation's lines and composer in a window docked at the bottom right, minimisable to the dock,
+  several at once side by side (each next one to the left; on a screen too narrow, over each other, the last used on
+  top), Esc inside one closes it. A mail's Discuss opens its discussion (`mailDiscussionSource`: the chat lines alone,
+  whatever is written there a chat line, a chat line quoting a mail quoting nothing); a chat opens in one at once.
+- **`MailComposeWindow`**: docked, minimise, maximise, close; To, Cc and Bcc (the source's people, To from its
+  `defaults`), subject, a Markdown body that fills the window, Send (Ctrl+Enter) and Discard. What is typed is kept per
+  viewer (`nx-mail-draft:<viewer>:new` or `:reply:<thread>`, every access in try/catch) until it is sent or discarded;
+  closing with words asks "Keep draft" or "Discard". A reply is a new mail in the thread (`ChatDraft.kind: "mail"`).
+- **`Popup` `docked` and `height`** (general): a docked popup is non-modal (no backdrop, no page lock, Tab leaves it),
+  drawn on the body through a portal, placed along the bottom edge above the dock's bars. `height` sets any popup's
+  height (`--nx-popup-height`); without it a popup is `fit-content` tall as before.
+- **The wire MAIL-hub answers** (the backend card may still change it, and says so in its card): an inbox row's `kind`
+  (1-3), `starred`, `fromAvatar`; the Inbox body's `kind` and `domainType` alone (a type); `GET Mail/Folders` answering
+  `{ folders: [{ list, unread }], kinds: [{ kind, domainType, unread, total }] }`; `PUT Mail/MarkRead`, `MarkUnread`,
+  `Star`, `Unstar` with `{ ids }`; Reply's `messageType: 1` for a mail (Chat stays the default). `MessageSource`'s
+  `folders`, `markRead`, `markUnread` and `star` are optional, and `MessageBackend.supports(...)` turns them off for an
+  older API. `localMessageSource` answers all of it (`chat` threads, `starredBy`, the failures `folders` and `marks`).
+- Proved by `test-mail-client.mts` (103) and the CSS contract; nexus.template's `/demo/mail-client` (a mailbox with a
+  discussion, chats, two record kinds and a month of reports; Kiran writes, Keep a draft, Answer slowly, Server down,
+  Full window; empty, loading, failed and a 390px phone) measured by a 73-check browser pass (the client never scrolls,
+  one row height, the keyboard, Discuss and chat windows non-modal at the bottom right and side by side, Esc, minimise,
+  compose with its draft, a reply as mail, types, the record's card, stars, Archive, the remembered split, no layout
+  shift, no box in a box, a phone's one pane and no sideways scroll, the muted words at 4.5:1 or more on the open and
+  the hovered row in all seven themes light and dark, cozy density, animations on), and `popup-windows.cjs`,
+  `mail-thread.cjs` and the CRUD popup checks unchanged.
+
+### A worked-out input that can be typed in: the total sets the price
+
+Card C-editable-calculated-amount (2026-11-10), the owner: *"if i put final 2500 inside the calculate amount then it
+calculate or set the price which is very easy. this logic we have inside 06-20 ... as possible generic dynamic."*
+Additions only: 6 exports, all from `nexus-shared` (`priceFromNet`, `PriceFromNetOptions`, `PriceFromNetFound`,
+`PriceFromNetRefused`, `InputSolved`, `NetAmountOptions`). **One behaviour changes:** `crudInputs.netAmount()` can be
+typed in by default (below); `{ editable: false }` keeps it as it was.
+
+- **`InputCompute.solve(typed, values, withValue)`**: a worked-out input worked backwards. With it a Number input's box
+  is a real text box (a NumberBox: its own Tab stop, the person's number format, its prefix and suffix) instead of the
+  `<output>`. Typing does nothing until the person leaves the box (Tab, a click away) or presses Enter; then `solve`
+  answers the values of the inputs it is worked out from (`InputSolved`: `{ values, note? }`), a sentence to refuse, or
+  `null` to change nothing. The answer is written as the person's own change (**`FormStore.setFromPerson(values)`**:
+  the inputs mount again with it, their rules are asked, the form's `onFieldChange` runs, inputs narrowed by them lose
+  their picks, it is a change for Save, drafts and the leave guard; nothing while the values load) and the input still
+  holds no value of its own. The box then shows the figure worked forward again, and a line under it says what was set
+  ("Price set to 2,458.21."), and when the typed figure cannot be reached exactly, the nearest it now shows ("2,500.04
+  cannot be reached exactly; nearest is 2,500.05. Price set to 2,458.26."). A refusal is said in `--nx-danger` with the
+  alert icon and the box goes back. An input that is read-only or disabled is never written: that is refused by name.
+  Escape puts back the figure (and closes nothing); Enter with nothing new submits the form as from any box; an emptied
+  box or the same figure changes nothing. Read-only, disabled and loading forms keep the box read-only, disabled, blank.
+- **The line under the box** shares one place with the hint (`nx-field__notes`, a one-cell grid, at least a line tall),
+  so nothing below moves when it comes and goes; it is `aria-live="polite"` and part of the box's description. It shows
+  until the figure moves on (another input changed), then the hint is back.
+- **`priceFromNet(target, { quantity, discountPercentage, vatPercentage, decimals = 2, places = 2 })`**: the price that
+  comes to a net amount by the server's rule (`priceAmounts`). Plain division (06-20's `FindOriginalPrice`) often lands
+  a paisa off, because each step is rounded; this gallops from that estimate and halves among the prices at the
+  price's own places, each worked forward on exact decimals. The net amount never falls as the price rises, so **when
+  any price reaches the figure exactly, the smallest such price is answered** (`exact: true`); otherwise the price whose
+  net amount is nearest (a tie goes above, so the total is never short), with the net amount it reaches. A quantity of 0
+  or none counts as 1; a negative figure or quantity, a 100 % discount and VAT of -100 % are refused in words
+  (`{ ok: false, message }`). 2,500 at 10 % and 13 % is 2,458.21 exactly.
+- **`crudInputs.netAmount(keys?, changes?, { editable = true, priceDecimals = 2 })`** wires `solve` to `priceFromNet`
+  on the `PriceKeys` (the quantity key too) and writes the price at `priceDecimals`. Its hint is "Price less the
+  discount, plus VAT. Type a total to set the price." (the old hint with `editable: false`). A `changes.compute` of the
+  page's own (a counter's server preview) has no `solve` and stays read-only, as before.
+- **Not in rows** in this card: rows came with [card C-rows-solve](#a-rows-worked-out-input-typed-in-a-lines-total-sets-its-rate).
+- Proved by `test-number-helpers.mts`: the owner's case and 20 more, and **560,000 targets** (every 0.01 to 100.00,
+  against 8 rate pairs from -5 % to 60 % off and 0 % to 13 % VAT, quantities 1, 2, 3, 7 and 1.5, and a price in 0, 2
+  and 3 places) against a sweep of every price: the net amount never fell, every one of the 287,075 reachable targets
+  was answered with its smallest exact price, every one of the 272,925 others with the nearest net amount any price
+  reaches, and every answer's net amount is what its price comes to (about 3.5 s). `test-form-store.mts` (the preset's
+  `solve`, `setFromPerson`: a change, its rule, `onFieldChange`, a new stamp, nothing while loading), the CSS contract,
+  and nexus.template's `/demo/form` "Worked out from other inputs" with `form-figures.cjs` (156 in each motion mode): 2,500
+  typed sets 2,458.21; 2,500.04 the nearest; Enter, Escape, an emptied box; a refusal; nothing below moving in compact
+  and cozy at 1280 and 390 wide; a percentage of marks with no money in it; the box as tall as Price with its edge and
+  background in three designs; the line under it at 4.85:1 or more and a refusal at 5.5:1 or more in 7 themes light and
+  dark. `form-confirm.cjs` unchanged (80).
+
+### A customisable dashboard: widgets in size presets, one call per module, only near the screen
+
+Card C-dashboard-board (2026-11-10), card 1 of the dashboard widgets spec (the owner: "customizable dashboard ...
+similar lighweight best optimize ... some can specific module base components only allow to add on same module, some
+can allow to add any place ... what's new, version info and more. comming soon"). Additions only: 58 exports, 35 from
+`nexus-shared` (`DashboardInterfaces.ts`, `DashboardHelpers.ts`) and 23 from `nexus-shared/client` (`DashboardBoard`,
+`WidgetFrame`, `WidgetLink`, `WidgetNavigateContext`, and the looks). No constant changed. Two shared components gained a
+prop: `Popup` `drawer` and `ChatFailure` `flat`; without them both draw as before.
+
+- **`DashboardBoard`**: a bar (the place's `title`, the page's `actions`, Refresh, Customise) over a 12-column grid whose
+  rows are three controls tall (102px compact, 114 cozy), `grid-auto-flow: dense`. A widget takes a size preset - S 3×1,
+  M 6×2, L 6×4, W 12×2, T 12×4 (`WIDGET_SPANS`) - from the sizes it declares, the first its default. The board is a size
+  container: under 48rem of its own width a small widget takes half and a medium or large one the whole; under 30rem
+  every widget is the full width, in the layout's order. A layout is an ordered list of `{ code, size }`; no coordinates.
+  Params only: `place`, `placeModule` (default `place`), `widgets` (the app's registry), `canSee(widget)` (the module
+  held, the key held), `layout` / `version` (the person's, or `null`), `defaultLayout` (the company's, else the code's),
+  `onSave(layout, version)`, `onReset(version)`, `canCustomise`, `canSaveCompanyDefault` + `onSaveCompanyDefault(layout)`,
+  `loadModule(module, codes)`, `initialData` (read with the page: drawn at once), `moduleLabel`, `onNavigate(href)` (the
+  app's router for every link inside), `loadMargin`.
+- **Edit mode** (Customise): a dashed edge on every widget, its heading the drag handle, a size menu holding only its sizes,
+  and Remove. **Drag** by pointer events, no library: the widget follows the pointer and the others make room as it
+  passes over them; Esc puts the order back; listened for on the window, since the grid moves the widget in the document
+  and a moved element loses a pointer capture. **Keyboard**: a focused widget moves with the arrow keys (up and down to
+  the nearest widget in the row above or below, `neighbourInColumn`), Home and End; Enter or Space opens its size menu;
+  Delete or Backspace removes it, the focus going to the widget in its place. Every move is read out. **Add widget**
+  opens a drawer (`Popup drawer`) listing the widgets this place may hold, by module (the place's own first), each with
+  its shape on a small grid, its sizes, and Add or "On the board"; closing it shows the widget added last with the focus
+  on it. **Save** (with "Save as the company's default" in its menu when allowed), **Cancel**, **Reset to default** (Save
+  then calls `onReset`). A save answered `stale` (the server's 409 with the saved layout) draws that layout and says
+  "Changed in another window: the layout saved there is shown."
+- **Hidden widgets**: a widget the person cannot see now (`canSee`), one not allowed in the place (`placement: "own"` on
+  another module's board), or one the app no longer declares, is drawn nowhere and offered nowhere, but **keeps its place
+  in the saved layout** (`mergeHidden`: each after the drawn widget it followed), so it comes back where it was.
+- **Data**: `WidgetDefinition.batch: { module, codes?, pick? }` puts a widget in its module's one call per draw
+  (`createWidgetBatcher`: everything asked in one task goes together, a call per module with every code its widgets
+  need); `load(context)` is a widget's own call; a widget with neither needs no data. **Only widgets near the screen
+  load** (one IntersectionObserver for the board, `rootMargin` and `scrollMargin` of `loadMargin`, so a scroller between,
+  as an admin shell's page area, is widened too). Each answer is kept for the page's life, or `refresh` seconds while on
+  screen (one 5-second timer for the board, nothing while the page is hidden); Refresh reads everything near the screen
+  again and the rest when it comes near. A module that fails fails its own widgets alone.
+- **`WidgetFrame`**: the title, an optional link ("View all"), its own refresh, and its body in one of four states - bones
+  by its size while it loads (one line for S, three for M and W, seven for L and T), the `empty` sentence, the failure
+  with Try again (`ChatFailure flat`: the tint without an edge, no box in the frame), or its content. Its size is the
+  grid's, so nothing moves when the data lands. Usable alone.
+- **The looks**: `StatWidget` (figures side by side as they fit, each a link if it has `href`, a tone dot), `ListWidget`
+  (picture or icon, words and a muted second line, a time and a tag; **only the rows that fit whole**, the rest counted
+  on its more line: `total`, `more: { href, label? }`, `fit`), `CalendarWidget` (the package's `Calendar` with typed
+  marks under each day - `holiday`, `leave`, `event` or the app's own `kinds` - a holiday's number in the danger tone,
+  a legend counting the month's marks, the picked day's marks beside the month or under it; AD or BS; `marksByDay`
+  spreads a mark over its days), `NewsWidget` (release notes: title, version and Released / Coming soon tags, the
+  application and day, the first lines of the Markdown notes, Read more), `VersionWidget` (the version large, the
+  application and build day, What's new).
+- **`Popup drawer`** (general): the window's whole height at its end edge, its width from `size` (all of it on a phone),
+  modal, neither moving nor maximising, fading in as every popup does.
+- Proved by `test-dashboard.mts` (63: the sizes, own and anywhere, canSee, a layout kept whole with hidden widgets, moving
+  by keyboard and pointer, the Add list, the batcher - one call per module, the cache, refresh seconds, a shared call,
+  failures per module, a pick that throws), the CSS contract, and nexus.template's `/demo/dashboard` measured by
+  `dashboard-board.cjs` (98 in each motion mode): the first draw asks each module once and nothing below the fold until
+  it is scrolled near (then one call of its module alone), no layout shift, the spans, rows three controls tall in compact
+  and cozy, no list with a half row, the keyboard (move, size menu with only its sizes, Delete, focus kept), the drawer at
+  the right edge the window's height (the whole width at 360px), Add, Save, Cancel, Reset, drag and Esc, a stale save, the
+  company's default, Kiran's hidden Request widgets back in place for Puja after Kiran's save, a failed module with Try
+  again, 360px with no sideways scroll and every widget the full width in order, no box inside a widget, and every word
+  at 4.5:1 or more (the lowest 4.85) in all seven themes light and dark, the drawer's too. `popup-windows.cjs` unchanged.
+
+### A row's worked-out input, typed in: a line's total sets its rate
+
+Card C-rows-solve (2026-11-10), the follow-up C-editable-calculated-amount named: the owner's "if i put final 2500 inside
+the calculate amount then it ... set the price", for a table of lines (Inventory's Dakhila). Additions only: 1 export
+(`withComputeSources`, `nexus-shared`), and new members of exports already listed (`RowsStore.setFromPerson`,
+`RowsInputProps.computeWith`, `crudInputs.lineAmount`, `PriceKeys.other`, `NetAmountOptions.taxed`). **One behaviour
+changes:** a row input with `compute` was ignored in rows (drawn as a plain input holding a value); it is now worked out
+on each row and holds none.
+
+- **`compute` works in a tabular or group form's rows**, as in a form: `from` names the row's inputs, `values` is the
+  row, `withValue` is the rows' new **`computeWith`** (a `Form` hands the rows its own unless their params name one;
+  a new one draws every row's worked-out cells again). Read-only by default (an `<output>` on the read-only tint, no Tab
+  stop, named "Amount, line 2" in a table); with `solve` a Number is a box that can be typed in. A table has no line under
+  a cell, so the note ("Line 3: Rate set to 2,458.21.", or the nearest, or a refusal in red) goes in the line under the
+  rows until the figure moves on, and a hidden live region in the cell says it. Enter with a new figure sets it and
+  stays; with nothing new it moves down the column (on the last line it adds one), as from any cell. Escape puts the
+  figure back.
+- **The rows hold no value under a worked-out name** (as `FormStore`'s `isComputedInput`): a loaded row's field of that
+  name is dropped, a value from code, an `onRowChange` or `deriveRows` patch, `newRow` or a new row's values naming it is
+  not taken, it has no rule and is never remembered, so the rows' value, `isChanged`, Save and the leave guard never see it.
+- **`compute.from` joins the row input's `dependsOn`** (`withComputeSources`), so the row draws again when a source changes.
+- **`RowsStore.setFromPerson(key, values)`**: a person's change of a row made through another cell, written as code
+  writes (the cells mount again with it) and followed as typing is (`onRowChange` runs for each value, narrowed followers
+  clear, value listeners hear it, so a parent form has unsaved changes and its leave guard asks).
+- **`ComputedInput`** (inside the package, `Components/Inputs/ComputedInput.tsx`) is the one worked-out box, lifted out
+  of `Form.tsx` with `read`/`write` callbacks; `Form` and the rows' cells both draw it, and the Form behaves as before
+  (`form-figures.cjs` unchanged, 156 in each motion mode). `formInputLabel` moved with it and is still exported from the
+  same place.
+- **Found and fixed on the way, in Form too:** a click straight into the Price after typing a total dropped the focus to
+  the page, because the Price box mounts again with its new value; it now lands in the box that took its place.
+- **`crudInputs.lineAmount(keys?, changes?, options?)`**: `netAmount` for a table of lines - the rate (`unitPrice`)
+  times the `quantity`, less the discount, plus VAT - as a 9rem column, typed in per row with `priceFromNet`.
+  **`PriceKeys.other`** adds an amount whole after VAT (a line's other costs, rounded to 2 places: the Inventory
+  service's `StockMaths.Line`), taken off a typed total before the rate is worked out ("The amount cannot be less than
+  the other costs."). **`NetAmountOptions.taxed(withValue, values)`** says when the discount and VAT count (a purchase's
+  lines, not a donation's), read from `computeWith`.
+- **An `<output>`'s text fills its box** (`.nx-field__output-text { flex: 1 }`), so the box's `text-align` places it: at
+  the end of a table's number column, as a typed figure is.
+- Proved by `test-rows-store.mts` (section Z: no value held, `dependsOn` joined, `setFromPerson` with `onRowChange`, the
+  value listeners and a remount, other costs, `taxed`), the CSS contract, and nexus.template's `/demo/tabular-form` "A
+  goods receipt" with `rows-solve.cjs` (50 in each motion mode): figures on open and per keystroke, exact (Enter) and
+  nearest (Tab), Escape, a refusal, Tab order, a click into the Rate, Donation through the form's `computeWith`, Save
+  sending neither worked-out figure; 7 themes light and dark at 1280 and 390 wide, the Amount and the note at 4.5:1 or
+  more. `tabular-form.cjs` (85), `group-form.cjs` (61), `form-confirm.cjs` (80) and `input-memory.cjs` (22) unchanged.
+
+### The mail client's fixes, and a Crud form's computeWith
+
+Card C-mail-client-fix (2026-11-10), the four gaps nexus.web's Message › Inbox (card MAIL-client-pages) found in the mail
+client, and the gap C-rows-solve left for a Crud page (Inventory's Dakhila). Additions only: 5 exports (`nexus-shared`:
+`followMailReadMarks`, `followMailboxReadMarks`, `MailReadMarks`, `crudComputeWith`, `sameShallow`) and new members of
+exports already listed (`MailClientProps.title` may be `false`, `.description`, `.headingLevel`;
+`CrudFormOptions.computeWith`). **Two behaviours change:** a `threadId` that names a chat opens its chat window, and the
+client's folder counts and its `onChanged` wait for the read marks on their way.
+
+- **A long list no longer makes the page scroll.** `.nx-mailbox__rows` scrolled but was not positioned, so each unread
+  row's visually hidden ", unread" (`nx-visually-hidden` is `position: absolute`) was placed against the page at its
+  row's place down the list: 126 unread rows made the demo page 8,253px tall instead of 3,286px, and nexus.web's Inbox
+  taller than the window. Every scroller of the client and the chat is now `position: relative` (the list, the rail, the
+  reader's body and record card; the chat's thread, list, New chat, mentions and people), and the CSS contract holds
+  every rule of `Nexus.Mail.css` and `Nexus.Chat.css` that scrolls to setting a position (9 today).
+- **A link to a chat opens its window.** A `threadId` the page sets (the bell's `?thread=`, an e-mail copy's) that names
+  a chat opens its chat window as a click on its row does - once its kind is known, from its row in the list or from its
+  head when the list shown does not hold it - once per opening, so a window closed stays closed until the row is clicked.
+- **The counts wait for the read mark.** A conversation shows read as soon as it opens, before its read mark reaches the
+  server; the client read its counts at once, so the Unread folder stayed one too high (nexus.web's `mailbox.ts` waited
+  for its marks itself). The reader's and the chat windows' read marks now go through `followMailboxReadMarks`: the
+  folder counts are read once no mark is on its way, and read again (with `onChanged`, the page's bell) when each is
+  answered. A page needs no wrapper of its own for its counts.
+- **One heading on a page.** `title={false}` draws no title in the bar (the search starts it), for a page whose own
+  heading names the client (nexus-admin's `AdminPage` with the menu row's words); `description` draws a sentence beside
+  the title, clipped to the rail's width with the whole of it on hover; `headingLevel` (default 2) makes it the page's h1.
+- **`CrudFormOptions.computeWith(values, { action, row })`**: what a Crud's Add and Edit forms hand their worked-out
+  inputs (`compute`, and the rows' `crudInputs.lineAmount` with `taxed`), worked out from the form's own values after
+  every change and before the browser paints. The answer is compared field by field with the last (`sameShallow`), so a
+  fresh object of the same figures redraws nothing; a new one redraws the worked-out cells alone, with nothing remounted
+  and the focus kept. A rule that throws keeps its last answer and says why in the console (`crudComputeWith`).
+- Proved by `test-mail-client.mts` (112: a mark held while on its way, let go and counted again once answered or refused,
+  every other door kept), `test-table.mts` (490: `crudComputeWith`, `sameShallow`), the CSS contract (3,035), and
+  nexus.template's browser checks on a production build of their own: `mail-client.cjs` 92 (new M: 126 unread rows keep
+  the page's height, every hidden word inside the client, the client as the window leaves the document no taller than it;
+  N: a link opens the chat's window, from its head when not listed, a closed one stays closed, a row click brings it back;
+  O: with read marks 1.5s slower than a count, the Unread folder still drops by one; P: one heading, the bar one height),
+  `rows-solve.cjs` 56 in each motion mode (new L: the receipt on a Crud page, `/demo/tabular-form` "The same receipt on a
+  Crud page", Source switched from the keyboard redraws the lines with the same inputs and the focus kept, a donation's
+  line typed in, the save's total), and `form-figures.cjs` 156 in each motion mode, unchanged.
+
+### Details as the 2026-06-20 window drew them, a list of rows as a table, history names from the app
+
+Card component-details-0620-look (2026-11-10), the owner's asks 1, 2 and 6 for the subscriber window, built for every
+page with a details view.
+
+- **The built-in details look** (`CrudDetails`: a Crud's details popup and workspace tab, a tree's panel, a form's
+  question): each field a label and its value in a box - a `--nx-border` hairline on `--nx-surface-2` - two pairs to a
+  line where the details are 46rem or wider and one where they are not, the label over its value under 20rem. The details
+  are their own size container (`nx-crud-details`), so a popup, a tab, a column beside a panel and a question's box each
+  get the look their width allows; every label has one width, so the values of both columns and of a field across the
+  line start on shared edges, and a label sits on its value's first line. Sections from the columns' `group` get a
+  numbered heading, "01. Contact", "02. Account", in the order they come. A `wrap` or Markdown column takes the whole
+  line. A form's question (`confirm`) now shows two fields to a line on a wide box, not three.
+- **`TableColumn.table?: readonly TableColumn[]`**: the value is a list of rows (a subscriber's contacts, devices). The
+  details draw it as a small read-only table across the line - a header row, each row's number first, an option's tone
+  as its tag, a boolean as Yes or No in words - and say "None" for an empty list. A data table, an export and a search
+  show how many rows it holds (`formatCellText`).
+- **`setAuditActorNames(resolver | null)`** and its type **`AuditActorNamesResolver`** = `(tokens: string[], signal:
+  AbortSignal) => Promise<Record<string, string>>` (`nexus-shared`): how `AuditHistory` names the person behind an entry
+  its answer names nobody for. It asks once for each page it shows, only for tokens it has had no answer for, and says
+  "by {the answer}" ("by Sita Rai (sita.rai)"); answers are kept for the page's life, a failed call keeps
+  "User 3fA9b2…" and is asked again by the next history, a token left out of the answer keeps it. The answer's own
+  `creatorName` still comes first.
+- **A workspace's popup footer is the Details tab's alone.** View history, Edit, Close and the load's line show only
+  while the built-in Details tab is chosen; every other tab runs to the popup's foot and has its own `CrudTabFooter`. The
+  title bar's X and Esc still ask about unsaved changes, as do the footer's Edit and Close on Details. A details popup
+  without a workspace is unchanged.
+- **A section that changes on its own** (`details.sections: [{ group, edit, label?, hidden? }]`, type
+  **`CrudDetailsSection`**): in a workspace's Details tab, a small ghost Edit at the end of the section's heading opens
+  the Crud's own Edit form (`edit: "edit"`) or one of its `rowForms` (`edit: "<id>"`) over the workspace, offered by the
+  row menu's rules (a list that offers Edit, the endpoint allowed, no lock); once saved the workspace reads the record
+  again (`refresh()`), the Details are drawn again in place, and the focus is back on the button. `CrudDetails` takes
+  `headingEnd(group)` for anything at the end of a heading, and follows a new `row` in place.
+- **`openCrudForm`** and its **`CrudFormRequest`** are exported from `nexus-shared/client`: a controller's Add or Edit
+  form in a popup, opened from anywhere.
+- **The workspace's profile picture is a circle** (`ProfilePicture`'s new `round`; the pictures window keeps the
+  picture's own shape and aspect).
+- Proved by `test-audit-entries.mts` (25), `test-table.mts` (491), the CSS contract, and nexus.template's
+  `crud-workspace.cjs`, `form-confirm.cjs` and `crud-row-form.cjs` on a production build.
+
+## 4.0.0
+
+**Breaking: an input's `type` is a number, a member of `EInputTypes`, and a string is refused.** Everything else in
+this version was prepared as `3.3.0`, which was never published; it follows under
+[the changes prepared as 3.3.0](#also-in-400-the-changes-prepared-as-330).
+
+Every export of the published `3.2.0` is still exported (287 are new: 226 from `nexus-shared`, 61 from
+`nexus-shared/client`, none from `nexus-shared/server`; 55 of them are [pictures and documents](#pictures-and-documents-declared-by-params), 19 are [cards C1's and C1-fix's](#the-editor-loads-in-every-bundler-a-reason-initials-one-action-locked-options-narrowed), 24 are [card RF-comp's](#a-printable-document-money-in-a-currency-inputs-shown-by-another-focus-kept-through-a-picture-change), 20 are [card TABS-comp's](#a-records-workspace-a-profile-and-tabs-in-the-details-popup), 3 are [card R2-comp's](#a-servers-page-in-a-sandboxed-frame-code-text-in-a-text-area), 1 is [card C-table-whole's](#a-short-list-read-whole-paging-in-the-footer-only), 1 is [card C-choice-tabs'](#a-choice-drawn-as-tabs), 1 is [card C-input-memory's](#an-input-that-remembers-its-last-value-or-opens-on-the-companys-default), 1 is [card C-label-follows'](#a-label-that-follows-another-input), 6 are [card C-server-preview's](#a-preview-the-server-works-out-as-the-person-types), 1 is [card C-print-logo's](#a-printable-documents-logo), 12 are [card C-crud-scope's](#a-list-that-can-be-widened-to-other-endpoints), 5 are [card C-row-form's](#a-row-action-that-opens-a-form-of-its-own-for-the-record), 3 are [cards C-leave-guard's and C-leave-fix's](#a-form-with-changes-asks-before-a-navigation-inside-the-app), 4 are [cards IMG-comp's and IMG-comp-fix's](#every-picture-through-the-editor-and-within-drives-limits), 2 are [card C-pin-narrow's](#pinned-columns-give-way-on-a-narrow-table), 56 are [card C-record-cards'](#a-records-page-of-cards-every-change-in-a-popup), 2 are [card C-tab-footer's](#a-record-tabs-footer-that-stays-in-view), 13 are [card C-form-figures'](#form-figures-an-input-worked-out-from-others-the-servers-money-rule-and-a-money-column), 7 are [card C-form-confirm's](#a-form-asks-before-it-saves-the-full-details-in-sections), 2 are [card C-profile-fields'](#a-few-fields-in-a-records-profile-left-out-of-its-details-tab), 2 are [card C-span-when's](#an-inputs-width-that-follows-a-value), 6 are [card C-record-cards-fit's](#record-cards-that-fit-what-was-built-on-them); the rest are named in the sections below or
+[in the list at the end of these notes](#new-exports-no-section-names)), and no exported constant changed a value (86
+compared), both checked against the published `3.2.0` with `Frontend/scripts/release-compare` (again on 2026-11-06,
+which corrected the hand count of 195; card C-record-cards' 56 are counted from its three files). What breaks is a type: `InputParams` and
+every params type in it take `type` as an `EInputTypes` member, so every list of inputs an app writes changes.
+`nexus-icons` stays `^1.2.0`; its published copy exports every name this package imports (125). The packages built on
+this one move with it: `nexus-admin` `4.0.0` asks `^4.0.0` (a major, because its range crosses this one), and
+`nexus-public` `3.0.1` asks `^3.0.0 || ^4.0.0` (it imports only `cx`).
+
+### Breaking: an input's type is the numbered `EInputTypes`
+
+The owner, 2026-10-30, pointing at `type: "switch"` and `type: "dropdown"` in an app's inputs: the old project held an
+input's type as a numbered enum, and so does this package now. A number is what a database, a generated page and a C#
+enum can hold, and a member name that does not exist fails to compile where a mistyped string compiled.
+
+```tsx
+// 3.x
+import type { InputParams } from "nexus-shared";
+const INPUTS: InputParams[] = [
+  { type: "text", name: "fullName", label: "Full name", required: true },
+  { type: "dropdown", name: "tags", label: "Tags", multiple: true, options: TAGS },
+  { type: "switch", name: "isActive", label: "Active" },
+];
+
+// 4.0.0
+import { EInputTypes, type InputParams } from "nexus-shared";
+const INPUTS: InputParams[] = [
+  { type: EInputTypes.Text, name: "fullName", label: "Full name", required: true },
+  { type: EInputTypes.Dropdown, name: "tags", label: "Tags", multiple: true, options: TAGS },
+  { type: EInputTypes.Switch, name: "isActive", label: "Active" },
+];
+```
+
+`EInputTypes` is written as `ENumberScales` is: an `as const` object and a type of the same name, so it is a value and
+a type, works in a server component, and `InputParams` still narrows on it (a dropdown's `multiple: true` still makes
+its value a list). Its numbers are this package's own, in blocks by kind with room to grow; **0 is never a kind**, so a
+value left out is never a valid one, and a released number is never reused or given another meaning.
+
+| Block | Kind | Member | Number | Was |
+|---|---|---|---|---|
+| 1–19 | Text boxes | `Text` | 1 | `"text"` |
+| | | `Email` | 2 | `"email"` |
+| | | `Password` | 3 | `"password"` |
+| | | `Search` | 4 | `"search"` |
+| | | `Tel` | 5 | `"tel"` |
+| | | `Url` | 6 | `"url"` |
+| | | `TextArea` | 7 | `"textarea"` |
+| | | `Code` | 8 | `"code"` |
+| 20–39 | Choices | `CheckBox` | 20 | `"checkbox"` |
+| | | `Switch` | 21 | `"switch"` |
+| | | `Radio` | 22 | `"radio"` |
+| | | `CheckBoxGroup` | 23 | `"checkbox-group"` |
+| | | `RadioGroup` | 24 | `"radio-group"` |
+| | | `Dropdown` | 25 | `"dropdown"`, one item or many by `multiple` |
+| 40–59 | Dates and times | `Date` | 40 | `"date"` |
+| | | `DateRange` | 41 | `"date-range"` |
+| | | `Time` | 42 | `"time"` |
+| | | `DateTime` | 43 | `"date-time"` |
+| 60–79 | Numbers and sliders | `Number` | 60 | `"number"` |
+| | | `Slider` | 61 | `"slider"` |
+| | | `RangeSlider` | 62 | `"range-slider"` |
+| 80–99 | Editors | `Markdown` | 80 | `"markdown"` |
+| | | `RichText` | 81 | `"rich-text"` |
+| 100–119 | Structures | `Tree` | 100 | `"tree"` |
+| | | `Tabular` | 101 | `"tabular"` |
+| | | `Group` | 102 | `"group"` |
+| | | `Picture` | 103 | new: [a record's picture](#pictures-and-documents-declared-by-params) |
+
+Every number fits a byte. To move an app: import `EInputTypes` from `nexus-shared` and write the member in place of
+each string in the table; the type checker lists every place it is still a string. A page that compared an input's type
+(`params.type === "radio"`) compares the member. Unchanged: a `TextBox`'s own `type` prop is still its HTML type
+(`<TextBox type="email" />`), which is not an input's params; a dropdown column's `type` (`"code"`, `"muted"`), a table
+column's `format` and the chat's conversation `type` are not inputs either and keep their strings.
+
+New beside it, and counted in the 30 above: `TextInputType` (the six text box members, whose `TextBox` gets its HTML
+type from one map in the renderer) and `inputTypeName(type)`, the member's name for a message or a log
+(`inputTypeName(EInputTypes.RichText)` is `"RichText"`; a number that is no member comes back as its digits). A table's
+filter that cannot filter now warns with the name: *a RichText input cannot filter rows*.
+
+### Pictures and documents, declared by params
+
+Card D2 of the subscription demo round (2026-11-02). A record's pictures and documents - a company's logo, a branch's
+pictures, a person's own picture, a subscriber's documents - are the files of an **owner** (a row of a module) in a
+**category** (what they are for, with its limits), and a page adds them by declaration:
+
+```tsx
+import { EInputTypes, NexusModule } from "nexus-shared";
+import { DocumentList, openPictureGallery, pictureColumn } from "nexus-shared/client";
+
+const BRANCH_PICTURES = { module: NexusModule.Enterprise, category: "branch-picture", aspect: 4 / 3 };
+
+// A form: the owner's main picture, changed at once (Upload, Edit, Remove, All pictures).
+inputs: (action, row) => [{ type: EInputTypes.Picture, name: "picture", label: "Picture", ...BRANCH_PICTURES, ownerId: row?.id }];
+// A table: each row's picture, the page's rows read in one call; a click opens the row's gallery.
+columns: [pictureColumn({ ...BRANCH_PICTURES, rowTitle: row => row.branchName }), ...];
+// A window, and a list for a category that takes PDF.
+openPictureGallery({ ...BRANCH_PICTURES, ownerId: branch.id, title: branch.branchName });
+<DocumentList module={NexusModule.Subscription} category="subscriber-document" ownerId={subscriber.id} />;
+```
+
+- **`EInputTypes.Picture` (103)**, the next number of the structures block: `PictureInput`, the owner's main picture
+  with Upload (choose, edit with the shape locked, store, make it the main one), Edit (a new picture from the main one),
+  Remove (no main picture; the pictures stay) and All pictures. In a category that keeps one file, Upload is Replace
+  (the new picture takes the kept one's place once the editor has saved) and Remove is Delete, so the input is never
+  left with a file it cannot delete. It holds no value of the form: the form store keeps no field for it
+  (**`holdsValue`**), so a save sends nothing under its name, and it takes no `required`, since the form could not
+  refuse a save without a picture. A record not saved yet (`ownerId` null) says "Save the {subject} first".
+- **`PictureGallery` / `openPictureGallery`**: upload several at once up to the category's count (each clamped to
+  2048 px and given its thumbnail by the editor's `renderImage`, without opening it; a picture's size is checked once
+  it is made, so a phone photo over the category's size is stored), make one the main picture, view
+  them in the editor module's viewer, edit one (saved as a new picture), delete. **`DocumentList`**: the same for a
+  category that takes PDF, as a list (kind, size, date, open, rename, delete); the gallery picks it by itself, and
+  `openPictureGallery` without `view` names its window after it ("Documents") once the category is read.
+- **`pictureColumn`**: each row's picture; every row a table draws asks `primaryPictures` (`PrimaryPictures`), which
+  gathers the asks of one moment into **one call per module and category**, at most the adapter's `maxOwners` (200),
+  and keeps the answers until a change on the page writes one in, so a row redraws without a reload. A refused or
+  failed read is kept as no picture for `retryAfter` (30 s), so rows that draw again do not each ask again; `clear()`
+  also drops the reads under way, so an ask after a sign-out never gets the answer meant for the person before.
+- **`loadImageEditor()`** (about 1 KB): the image editor (`nexus-image-editor`) is **never in an app's bundle**. The
+  adapter names its versioned address (with Nexus, Drive's `Assets/File/nexus-image-editor.txt`), and the loader
+  imports it with the bundler told to leave the import alone (`webpackIgnore` / `turbopackIgnore`; proved in a
+  Next.js 16 Turbopack build: the chunk holds a plain `import(url)`), once per page; a failed load is not kept.
+  `preloadImageEditor()` starts it on the hover of an Edit or Upload button. Its types are in `ImageEditorModule`.
+- **`FileAdapter`** is the abstract class an app implements for its own file backend (`list`, `primaries`, `upload`,
+  `setPrimary`, `rename`, `remove`, `fileUrl`, `editorModuleUrl`), registered once with `defineFileAdapter`;
+  **`NexusDriveAdapter`** is the default: a write ticket from the owner's module (`Files/Ticket/{category}/{ownerId}`,
+  kept until a minute before it runs out, asked again once when Drive answers `DRV_X011`), a read ticket
+  (`Files/Owners/{category}`) for a page's rows and for a person who may see but not change an owner's files, then
+  Drive's `File/List`, `Primaries`, `Upload`, `SetPrimary`, `Rename`, `Delete` and `View/{id}/{Original|Thumbnail}`.
+  Nothing generic names a backend's numbers: a category's kinds are MIME types.
+- New shared helpers: `fileRefusal` (a kind or size the category refuses, said before the upload), `fileKindsSentence`,
+  `fileSizeText`, `roomLeft`, `takesDocuments`, `pictureName`; one stylesheet, `Nexus.Files.css` (`nx-picture`,
+  `nx-picture-input`, `nx-files`), whose hovered pictures get a ring and never a new size.
+
+Proved by `npm run test:files` (the adapter against a pretend backend: the tickets, the fresh one after `DRV_X011`, the
+read-only fallback, the page's order, the multipart fields, the pointer file) and nexus.template's `/demo/pictures`
+with its browser check `pictures.cjs`, on a pretend Drive that answers as the C# one.
+
+### The editor loads in every bundler; a reason, initials, one action locked, options narrowed
+
+Card C1 of the subscription demo's second round (2026-11-02): fixes to the pictures above, and two features the
+subscription pages needed and kept as code of their own.
+
+- **The image editor loads in an app's production build.** The package build rewrites "./x.ts" imports to "./x.js"
+  (`rewriteRelativeImportExtensions`), and for an `import()` of a variable it wrapped the address in a run-time helper,
+  `import(__rewriteRelativeImportExtension(url))`. The bundler-ignore comments were then inside a call, and Next 16's
+  Turbopack compiled the import to "Cannot find module as expression is too dynamic": in every app built on `dist`,
+  Upload and Edit on a picture never opened the editor (an app reading the source, like nexus.template, never saw it).
+  The import now lives alone in **`importModule(url)`** (`Services/ModuleImport.ts`, which imports nothing), built a
+  second time without the rewrite (`tsconfig.build.module-import.json`, the second step of `npm run build` and of
+  `copy-packages`' watch), so `dist` keeps `import(/* webpackIgnore: true */ /* turbopackIgnore: true */ /* @vite-ignore */ url)`.
+  The setting stays for every other file. `scripts/test-dist-loader.mts` (in `npm test`) runs the build's steps into a
+  scratch folder and fails if any built file holds the helper.
+- **An editor that cannot load says so.** `loadImageEditor()` rejects in plain words ("The image editor could not be
+  downloaded. Check the connection and try again; ...") and logs the cause (a network error, a 404, a bundler that
+  rewrote the import) with `console.error`; the picture input, the gallery and the viewer show it as a toast.
+- **A picture input says why it is read only.** `OwnerFilesParams.lockReason` (on `PictureInput`, `PictureGallery`,
+  `openPictureGallery`, and `pictureColumn` as a sentence or `row => sentence`) makes the files read only with that
+  sentence under them: a record that is closed, a year that is locked. Without it, a person the backend lets only look
+  is told the backend's own words: `NexusDriveAdapter` keeps the refused write ticket's message as
+  `OwnerFiles.readOnlyReason`, and **`READ_ONLY_REASON`** stands in when there is none.
+- **Initials for an owner with no picture.** `OwnerPicture` `name` and `pictureColumn` `nameKey` (the row's field with
+  a name): without a picture, the name's initials, on the tone the shared `Avatar` gives that name
+  (`.nx-picture--initials`; the avatar tones now also apply to `.nx-picture[data-tone]`).
+- **One action locked on a row: `Crud` `rowActionLock`**: `row => ({ trash: "The head office stays open..." })` switches
+  off single actions of a record, each with its sentence in the row's menu, in a selection that holds it, and for
+  `edit` in its details too; the rest still run. `rowLock` still locks every change at once. New types
+  `CrudLockableAction`, `CrudActionLocks`.
+- **Options narrowed by another input: `narrowedBy`** on any input (Form only), `{ name, key?, placeholder? }`: a
+  Package list only of the Group picked. The form hands the input its params narrowed by the other value as it draws
+  (`narrowInputParams`, `narrowingValue`, `narrowingPlaceholder`, pure): static `options` filtered, `loadOptions` asked
+  with the new **`DropdownPageRequest.narrow`**, a load key per value, nothing offered and "Pick a group first" while the
+  other is empty; the form store follows it as `dependsOn` would and clears the narrowed value when a person changes the
+  other (never when code sets it). `crudPicker` answers `narrow` from its kept list, or, with the new **`narrowQuery`**,
+  asks the server (`activeListing?{narrowQuery}={value}`, one kept list per value, dropped with the others on a save).
+  `FormStore.inputParams(name)` is new.
+- **A list narrowed by a box of its own, remembered per viewer: `Crud` `narrowPicker`** (`CrudNarrowPicker`): the
+  picker's params, the box's label, `remember: { key, viewer }` and `onPick`. The CRUD draws the box in its toolbar, keeps
+  the pick as `narrow` would, and opens the same pick on the next visit in this browser for the same viewer while the
+  box still offers it; only the record's key is stored. `useCrudNarrowPicker` is exported (`nexus-shared/client`).
+
+Proved by `npm test` (`test-dist-loader`, `test-input-narrowing`, `test-files`' reason), nexus.template's `/demo/pictures`
+(`pictures.cjs`: initials, the lock reason, an editor whose module is refused) and `/demo/crud`'s "One group at a time"
+(`crud-narrowing.cjs`), and nexus.web's production build against a Drive API.
+
+Card C1-fix (the review of C1, 2026-11-02):
+
+- **`narrowedBy` clears down a chain.** A person changing the Country clears the Region, and now the District picked
+  among that Region's too, whatever order the form lists them in (before, the District kept a value of the old Region,
+  and could be saved).
+- **A narrowed input's getters answer on every draw.** `Form` copied a `narrowedBy` input's params once and kept the
+  copy, so a `readOnly`, `hint`, `label` or `options` getter that `dependsOn` follows stayed as it first read. The
+  copy is now made afresh each time the input draws.
+- **A `narrowPicker`'s words name its box**: "Pick a group in the Group box to see its amenities.", "... to add a new
+  amenity for it." on Add, and "Added for Bathroom: pick another group in the Group box to add elsewhere." on the Add
+  form's fixed field (before, all three said "the other list"). New on `CrudNarrow` (and so on `narrowPicker`):
+  **`addMessage`** and **`fixedMessage: name => sentence`**, beside `emptyMessage`; the words are
+  **`narrowPickWords(label, subject, plural)`**.
+- **The remembered pick keeps the key alone, and only for a viewer.** No name is written to local storage (a pick kept
+  with one by C1's build still opens, and is written again without it), and without `remember.viewer` nothing is
+  remembered: **`narrowPickerStorageKey`** (now from `nexus-shared`) answers `null`. A kept pick is found again by its
+  key alone, **`findNarrowPick`**: `resolveOptions` when the picker has it, else the box's pages at 50 a page (never one
+  page of everything, which a server-paged source refuses). `readNarrowPick`, `writeNarrowPick`,
+  `narrowPickerPlaceholder` are the rest of `Helpers/CrudNarrowPick.ts`, pure.
+- **An owner not in use is not "not found".** When a module refuses the write ticket with a 404 (the owner pending,
+  ended, in the trash or deleted) and a read ticket still finds it, the files say **`OWNER_NOT_IN_USE_REASON`** ("This
+  record is not in use now, so its files can be seen but not changed.") rather than "The record was not found.".
+- **`test-dist-loader` checks this folder's whole `dist`** with the scratch build's rules (ModuleImport.js there, its
+  import plain, no helper in any file), so a dist built with only the first step fails.
+
+Proved by `npm test` (23 suites; `test-input-narrowing` 49, `test-files` 73, `test-dist-loader` 17) and nexus.template's
+`crud-narrowing.cjs` (55, both motions: the three sentences, a narrowed Icon whose hint follows "Free for guests"),
+`staff-posts.cjs` (86, the other-list words unchanged), `crud.cjs`, `forms.cjs` (154) and `pictures.cjs` (83).
+
+### A record's workspace: a profile and tabs in the details popup
+
+Card TABS-comp (2026-11-03), from the owner's request for the tab buttons of the 2026-06-20 project's record popups:
+View, and a click on a row under `table.openOnClick`, open the record as a wide popup with who it is and its tabs on the
+left and the chosen tab on the right. Additions only.
+
+- **`CrudDetailsOptions.tabs`**: `{ id, label, icon?, endpoint?, hidden?(row), badge?, render(context) }[]`. A tab that
+  names an `endpoint` shows only to a person who may call it (the rule of `CrudDetailsAction`, again whenever the rights
+  change). `render` is handed a **`CrudDetailsTabContext`**: `row` (as the list has it now), `form` (the record in the
+  `FormStore` the `aside` is handed: the row, then the `details` endpoint's record, then each refresh's), `popup`, `tab`,
+  `select(tabId)` and **`refresh()`**, which reads the record again from the `details` endpoint and writes it into the
+  table, the pinned band, every list kept and every tree (`trees`), as an edit's answer is - no list is read again - and
+  answers the record (or `null`). The built-in tab `details` (the fields, with `aside` beside them) comes first; list
+  `{ id: "details" }` to move or rename it, give it `hidden: () => true` to leave it out, or a `render` to replace it.
+  Only the chosen tab is drawn. With tabs the popup's default size is `full`.
+- **`CrudDetailsOptions.profile`**: `row => ({ picture?, title, subtitle?, tags? })` or anything to draw. `picture` is
+  the owner's main picture by the params the picture column takes (`{ ...GUEST_PICTURE, ownerId }`, a
+  **`CrudDetailsPicture`**: a click opens the pictures, initials stand in without one) or a node; `tags` are
+  `{ label, tone? }` in the look of a table's tags. It follows the record as it is loaded and refreshed.
+- **`CrudDetailsOptions.remember`**: `{ key, viewer }` keeps the last tab chosen in this browser
+  (`nx-crud-tab:{key}:{viewer}`) and opens it next time while it is still offered; nothing is kept without a viewer.
+- The layout: a 20rem column (the picture 10rem, the name, the line, the tags, then the tabs as `design="list"` rows)
+  and the tab beside it, which scrolls inside itself; the popup's body never scrolls and a switch never changes its
+  size. The workspace is a size container: below 720px of popup width (a phone) the profile is one row (a 3rem
+  picture) and the tabs one strip that scrolls sideways, above the tab. The focus opens on the chosen tab, a switch
+  that takes away the panel holding the focus puts it on the chosen tab, and it never drops to the page.
+- **`Tabs`** and **`TabPanel`** (`nexus-shared/client`): tabs that switch panels, as a WAI-ARIA `tablist` - the one
+  piece `TabButtons`' own doc pointed to and the package did not have. The look is `TabButtons`', from the same
+  stylesheet (`design` `list`, `nav`, or `auto`: the list, and a strip in a container under 720px); the chosen tab is
+  `aria-selected` and the only one in the Tab order, the arrows (either way), Home and End move and open, the panel is
+  joined by `tabIds(id, value)` and takes the focus itself when it holds nothing that does. `TabOption`, `TabsDesign`,
+  `TabsProps`, `TabPanelProps`.
+- The tabs' rules without a browser, in `nexus-shared`: `offeredCrudTabs`, `openingCrudTab`, `crudTabStorageKey`,
+  `readCrudTab`, `writeCrudTab`, `isCrudProfile`, `isCrudPicture`, `CRUD_DETAILS_TAB`, `OfferedCrudTab`.
+- `OwnerPicture` `size` also takes a CSS length (`"var(--nx-crud-profile-picture)"`), so a picture can follow a
+  container query.
+- Styles: `Nexus.Crud.css` (`nx-crud-workspace`, `__frame`, `__frame--alone`, `__side`, `__profile`, `__nav`,
+  `__panel`; `nx-crud-profile`, `__picture`, `__text`, `__title`, `__subtitle`, `__tags`) and `Nexus.Tab.Buttons.css`
+  (the chosen option is `:checked` or `[aria-selected="true"]`, a button's own look taken away, `nx-tabs--auto`,
+  `nx-tab-panel`).
+- Proved by `scripts/test-crud-details-tabs.mts` (33) and nexus.template's `/demo/crud` "A guest's workspace" with
+  `scripts/browser-checks/crud-workspace.cjs` (60 in both motion modes: the click on a row, the keyboard, one Update
+  and one Detail for a check-in with the row's visits written in, the remembered tab, a role without the endpoint, every
+  theme light and dark at 1280x720 and 390x844).
+- Card TABS-fix1-comp (2026-11-03), from the review of the first page built on it:
+  - **A form in a tab is never thrown away without asking.** A `SubmitForm` (and so an `ApiForm`) joins the place it
+    is drawn in by itself (`FormLeaveGuard`, by the rule of its "leave the page?" question: not while locked, not when
+    a draft keeps it); while one has changes, choosing another tab, Close, Edit, the popup's X, Esc and its bar on the
+    dock ask "Discard your changes?". Keep editing stays where it was. No new export.
+  - **`refresh()` lands after the popup closed.** Only the first read of the record stops when the popup closes; a
+    save in a tab followed at once by Close still writes the row's new status and dates into the lists.
+  - **A record off the page shown is patched in place.** `refresh()` hands the record as the popup held it, so one
+    opened from the pinned band, or from a page turned since, is written into every page kept that has it: no page is
+    dropped and the page shown is not read again.
+  - **A popup closed over another never leaves the focus on the page.** When its opener cannot take the focus back (an
+    item of a menu that closed, a button disabled while its action runs), the popup now on top takes it where it puts
+    it on opening: in a workspace, the chosen tab.
+  - The examples here, in the README and in `CrudDetailsOptions.tabs`' doc are a guest's, as the template's demo is.
+
+### A printable document, money in a currency, inputs shown by another, focus kept through a picture change
+
+Card RF-comp (2026-11-03), from the whole-round review of the subscription demo's second round: three pieces the
+subscription pages had written as code of their own (findings rules-3, rules-4, rules-5), and the picture input and
+gallery keeping a keyboard's focus (packages-3).
+
+- **`PrintDocument`** (`nexus-shared`, no state, so server components too): a receipt, a bill or a statement by params:
+  `paper` (`"a5"`, the default, or `"thermal"`, an 80 mm roll), `title`, `subtitles`, `kind`, `stamp` ("Voided: ..."),
+  `blocks` in order - `{ facts: [{ label, value, hidden? }] }` and `{ columns: [{ label, align? }], lines: [{ cells,
+  note?, hidden? }], totals: [{ label, value }] }`, falsy entries left out - and `footer` (line breaks kept). On screen it
+  reads in the theme's colours at its paper's width (128 mm, or 72 mm); printed with `window.print()` it is the only thing
+  on the paper, black on white, at the paper's left edge, and the component writes the page's `@page` rule (A5 portrait
+  with 10 mm margins, or 80 x 297 mm with 4 mm) while it is on the page. The print rule applies only while a document is
+  on the page (`body:has(.nx-print)`), so any other page prints as it is. **`PRINT_PAPERS`** are the papers as
+  `TabButtons` options. Styles: `Styles/Nexus.Print.css` (`nx-print`, `--thermal`, `__head`, `__title`, `__kind`,
+  `__stamp`, `__facts`, `__lines`, `__end`, `__note`, `__foot`). Types `PrintPaper`, `PrintFact`, `PrintColumn`,
+  `PrintLine`, `PrintFactsBlock`, `PrintLinesBlock`, `PrintBlock`, `PrintDocumentProps`.
+- **Money in the company's currency, set once.** `DataTableProps.currency` (and `Crud` `table.currency`) writes every
+  `money` column as "Rs. 1,250.00" in the cells, the details, the CSV and the print; **`TableColumn.currency`** gives a
+  column its own, a text or `row => row.currencyText`. `formatCellText(column, value, options, row?)` takes the row for
+  it and `CellTextOptions.currency` the table's; **`columnCurrency`** answers which. **`formatMoney(value, { currency,
+  decimals = 2, locale, empty })`** writes the same anywhere else (a dashboard's figures, a receipt): "Rs. 1,250.00".
+  `prefix` still works as before.
+- **An input shown by another input's value: `showWhen`** on any input (Form only): `{ name, in?, notIn?, filled? }`
+  or a list of them, every one holding (`InputCondition`). Values compare as text (1 matches "1"), a list value matches
+  `in` by any item. The form gives such an input a live `hidden` that reads its store and follows the inputs named as
+  `dependsOn` would; a hidden input keeps its value and is not checked; its own `hidden` still hides it. Pure helpers
+  `withInputConditions`, `inputShown`, `inputReadOnly`, `conditionsHold`, `conditionHolds`, `conditionsOf`, `isEmptyValue`.
+- **An input read-only by another input's value: `readOnlyWhen`** (Form only), the same `InputCondition`s: a live
+  `readOnly` that follows the inputs named, the input's own `readOnlyMessage` as the reason, its value kept in the data
+  and not checked while read-only; its own `readOnly` still locks it. A CRUD's Edit form holds the record's key and its
+  Add form does not, so `readOnlyWhen: { name: "id", filled: true }` is a field picked on Add and fixed on Edit (a
+  price's group).
+- **Options narrowed by a fixed value: `narrowedBy: { key, value, orUnset?, placeholder? }`** beside the
+  `{ name }` form (`InputNarrowing` is now `InputNarrowingByInput | InputNarrowingByValue`): the subscriber's own group,
+  known when the form opens; nothing followed, nothing cleared, a `null` value offers nothing. **`orUnset`** (both forms)
+  also offers the options whose field is empty, a fee of every group: `DropdownPageRequest.narrow` carries it (and a
+  `null` value with it), and `crudPicker` honours it from its kept list. `isFixedNarrowing` tells the forms apart.
+- **The picture input and the gallery keep a keyboard's focus.** Their buttons no longer switch themselves off while a
+  change runs (`disabled` sent the focus to the page in every browser): they stay focusable, `aria-disabled`, their
+  press ignored (**`busyProps(busy, run)`**). When a change ends with the focused button gone - Remove and Edit with
+  the main picture, a star once its picture is the main one, a deleted file's buttons - the focus goes to the first
+  control left in its tile, else in the input (**`useFocusThroughChange(root, busy)`**, `nexus-shared/client`).
+
+Proved by `npm test` (24 suites; `test-input-conditions` new, 37; `test-input-narrowing` 61, `test-table` 439,
+`test-number-helpers` 125; the CSS contract), and nexus.template's `/demo/print-document` and `/demo/form`'s "Inputs
+shown by another input" (`print-document.cjs`, 52: the money cells, the receipt, its widths and `@page`, printed alone
+and black on white, a page without one printed whole, `showWhen` and the fixed narrowing, every theme light and dark at
+1280x720 and 390x844 at AA) and `pictures.cjs` (87: Remove, the star and Delete from the keyboard keep the focus).
+
+### A server's page in a sandboxed frame; code text in a text area
+
+Card R2-comp (2026-11-05), for the Report module's Print layouts page: its preview and print door answer a whole HTML
+page (`{ html }`, with its own `@page` sheet, screen style and a CSP that runs no script), and its editor holds a
+layout's HTML. Additions only.
+
+- **`DocumentFrame`** (`nexus-shared/client`): the page in an `<iframe srcdoc>`, sandboxed `""` (an opaque origin) or,
+  with `printable`, `"allow-same-origin allow-modals"`, so the handle's **`print()`** (`DocumentFrameHandle`) opens the
+  print dialog for the page alone; never `allow-scripts`. Props (`DocumentFrameProps`): `html`, `title` (required; the
+  frame's name to a screen reader), `loading` (the page area `aria-busy` at once; a read that lasts 0.4s dims the page
+  and says `loadingMessage`, default "Loading…"), `error` (a `role="alert"` line over the last page, which stays),
+  `emptyMessage` (default "Nothing to show yet."), `actions` (buttons at the end of the frame's bar - the form's bar and
+  status line, shown only with actions or a status - which wrap under the line on a phone), `printable`, `className`,
+  `style`, `ref`. It fills the height its container gives (a flex column, a grid row) and is never under 22rem; the page
+  scrolls inside it, an A4 sheet sideways too. While loading or failed, an `html` of null keeps the last page; a
+  printable page read again keeps its scroll while the title stays. A frame that becomes printable is a new frame (a
+  sandbox counts from the next page). Styles in `Nexus.Print.css` (`nx-document-frame`, `__bar`, `__view`,
+  `__view--busy`, `__page`, `__empty`).
+- **`TextArea` `code`** (and `code: true` in a TextArea's `InputParams`): the monospace token, lines kept as typed
+  (`wrap="off"`, a long line scrolled sideways in the box), `tab-size: 2`, and `spellCheck`, `autoCapitalize`,
+  `autoCorrect`, `autoComplete` off and `translate="no"`; Tab still leaves the box. `nx-field__control--code` in
+  `Nexus.Input.css`; read-only and disabled code keep the look.
+- `.nx-form-status` takes its room beside a bar's buttons from `--nx-form-status-basis` (default 14rem, as before), so
+  the frame's bar, whose words are few, keeps two buttons beside its line in a half-width frame (10rem).
+- A CRUD's details footer and the frame share one rule for a slow read (said after 0.4s, held 0.3s): `useSlowBusy`,
+  internal, moved out of `Crud.tsx`.
+
+Proved by `npm test` (25 suites; the CSS contract) and nexus.template's `/demo/document-frame`
+(`document-frame.cjs`, 68 and 69 with reduced motion: the sandboxes, srcdoc, the empty, slow and failed states, the
+bar's buttons by keyboard, Print firing the frame's `beforeprint` and `false` without a page or when not printable, the
+scroll kept, a script that never runs printable or sealed, the code text area, every theme light and dark at 1280x720
+and 375x812 with no overflow and the status lines at AA), with `crud.cjs` and `crud-workspace.cjs` for the footer.
+
+### A field at the top of a CRUD popup's column keeps its label and focus ring whole
+
+Card R2-fix-label (2026-11-05), the owner's "overflow hidden bug": in a subscriber's window, the outlined "New note" box
+first in the notes beside the details showed only the lower half of its raised label, and its focus outline was cut at
+the top and at the panel's right edge. No export changed.
+
+- **`.nx-crud-aside__main` and `.nx-crud-aside__side`** (side by side, from 1000px) each scroll on their own, and a
+  scroll box clips at its padding edge, so a field first in either lost what it draws past its box. Both now keep room
+  inside their edges, paid back by a negative margin so nothing moves: above, an outlined field's raised label (0.6em
+  of the xs text) and its 2px outline; on every side, the 3px focus ring. The form's column had only 2px (rings), now
+  the same room; the panel's column had none.
+- **`scroll-padding`** on those columns, `.nx-crud-workspace__panel` and **`.nx-popup__body`**: focus scrolls a field's
+  control to the box's edge, and the raised label above it, or the box's border and ring below it, were cut there by 4
+  to 7.2px. The room past the control is now kept the same way in every popup.
+- Proved by nexus.template's `/demo/crud` "A guest's workspace", which now has the guest's notes beside the details (a
+  form first) and the guest's card beside the Add and Edit forms, and `scripts/browser-checks/crud-field-room.cjs`.
+  It measures the label and the outline's and shadows' reach against every box that clips them, focused with text,
+  in the standard, outlined and inbox designs and the sm, md and lg sizes, light and dark, at 1280x720, 1040x720 and
+  390x844, and at each scroll edge. 306 pass. On the old CSS 108 failed: every case in a column side by side. With
+  `scroll-padding` off, 20 failed: the edge cases.
+
+### A short list read whole; paging in the footer only
+
+Card C-table-whole (2026-11-05), the owner on a subscriber's notes: *"footer have gap top side have gap ... used only
+footer for this types of datatable"*, *"or do not put limit here"* (a subscriber keeps at most 50 notes). Additions only:
+a table without the new prop draws as before.
+
+- **`DataTable` `pager`** (`TablePagerMode`: `"bar"` | `"footer"` | `"none"`, default `"bar"`), where the paging lives:
+  - `"bar"`: rows per page inside the search box (or the bar without a search), the pager in the footer - as before.
+  - `"footer"`: rows per page beside the pager, in the footer; a table with nothing else on top draws no bar.
+  - `"none"`: every row on one page, for a short list read whole: no pager, no rows per page, no remembered or
+    preferred page size, and no footer unless a search or the filters leave rows out ("Showing 1–2 of 2 · filtered from
+    6"). The count line stays as a visually hidden live line, so a screen reader still hears it. With
+    `searchable={false}`, `columnsMenu={false}`, `exportable={false}` and `printable={false}` the table is its rows
+    alone in its frame (the bar already hid itself when it held nothing; the empty footer band was what was left). A
+    server's pages cannot all be shown, so `paging="server"` takes `"none"` as `"footer"`.
+- **`Crud`** passes it through `table: { pager }` (`CrudTableOptions`).
+- Proved by nexus.template's `/demo/data-table` "A short list read whole" (`data-table-pager.cjs`, 52 in each motion
+  mode: the whole table with 3, 14 and no notes, the footer's own rows per page and pager, a whole table's search, the
+  default unchanged, every theme light and dark at 1280x720 and 390x844 with no overflow), with `data-table.cjs` and
+  `crud.cjs`.
+
+### A record's workspace draws its panel under the details
+
+Card C-workspace-below (2026-11-05), the owner on a subscriber's window: *"make width full 100% for right side
+content. the details page make full width 100% then bellow show others informations"*. No export changed; one option
+was added to an exported type.
+
+- **`CrudDetailsOptions.asidePlace`**: `"beside"` | `"below"`. `"below"` draws `details.aside` under the fields at
+  every width: the fields across the whole width of the tab, the panel across the whole width under them, as tall as
+  it needs, scrolled with them by the workspace's panel (or the popup's body) - never a column of its own, so no box of
+  its own clips a raised label or a focus ring. `"beside"` is the layout as it was: side by side from 1000px, stacked
+  under that.
+- **The default changed for a record's workspace** (`tabs` or `profile`): `"below"`, so its Details tab reads as the
+  record first, then what belongs to it. Only the Subscribers page passes a workspace aside today; a plain details
+  popup keeps `"beside"`.
+- `nx-crud-aside--below` in `Nexus.Crud.css`; the side-by-side rules now name `:not(.nx-crud-aside--below)`.
+- Proved by nexus.template's `/demo/crud` "A guest's workspace" (a switch: notes under the details / beside them) and
+  `crud-aside-below.cjs` (82 per motion mode: widths, order, no scroll of its own, the note field's label and ring, at
+  1280x720, 1040x720 and 390x844, light and dark); `crud-field-room.cjs` now picks "beside" for the columns it
+  measures; `crud-workspace.cjs` and `crud.cjs` unchanged.
+
+### A choice drawn as tabs
+
+Card C-choice-tabs (2026-11-05), the owner on the counter's "What is it?" (Payment, Activate, Disconnect, each with a
+sentence under it): *"if we make it tab types of design maybe it batter. (nav style) the helper label should be tool tips
+or somethings"*. Additions only.
+
+- **`RadioGroup` `design: "tabs"`** (`RadioGroupDesign` = `ChoiceDesign | "tabs"`, in `nexus-shared/client`; a
+  RadioGroup's `InputParams` take it too): the options as nav-style tabs on one `TabButtons` track, still native
+  radios in a fieldset with `role="radiogroup"` - the arrow keys move the choice, `required` and `validate` stop a
+  form's save with the group's message (the track edged in the danger colour), `readOnly` keeps the value with its
+  lock and note, `disabled` dims every tab, `size` sm/md/lg is the track's. The tabs wrap onto more rows where they do
+  not fit (a phone). `orientation` and `columns` do not apply.
+- **Each option's `description`** is its tooltip (`title`, when it is text) and its input's accessible description
+  (`aria-describedby` to its note, which a screen reader reads even while hidden). The chosen option's note shows
+  under the track, since a phone has no tooltip; it follows every change and a form's reset (`showChosenNote`, the
+  group's `sync` rule), with no React state.
+- **`Nexus.Tab.Buttons.css`**: the rules that raise each chosen option on its own (`multiple`) are shared by
+  `nx-tabs--wrap` (`:is(.nx-tabs--multiple, .nx-tabs--wrap)`, the same specificity), since a radio group's choice lives
+  in its inputs, not in a value a sliding indicator could follow; only `multiple` keeps the pointer on a chosen option.
+  `Nexus.Choice.css`: `nx-choices--tabs` (the danger edge) and `nx-choices__note`.
+- The read-only note finds a tab as it finds a choice (`optionAnchor`: `.nx-choice, .nx-tabs__option`).
+- Proved by nexus.template's `/demo/form` "A choice drawn as tabs" (`choice-tabs.cjs`, both motion modes: the track,
+  the tooltips and descriptions, required, a click and the arrow keys, read-only, disabled, the values sent, a reset,
+  every theme light and dark at 1280x720 and 390x844 with the labels and the note at AA), with `forms.cjs` and
+  `read-only.cjs`.
+
+### An input that remembers its last value, or opens on the company's default
+
+Card C-input-memory (2026-11-05), the owner on the counter's Paid by and Bill: *"we should be remember the input value.
+we also need company level preference to select default, if default not config then we need remember"*. Additions only.
+
+- **`InputLayoutParams.remember`** (`InputRemember`: `key`, `viewer`, `preferred`; Form only, any input type). When
+  the values the form opens with leave the input without one (they do not name it, or hold it empty - a new record), it
+  opens on `preferred` (the company's default, from a setting the page reads), else on the person's last saved choice,
+  else on its own `defaultValue`; `preferred` and the kept choice each only while the input still offers them (a
+  choice group's or a dropdown's own `options`: not disabled, not inactive, still listed; a list keeps what is
+  offered; a server's list is asked since [card C-input-memory-offered](#a-remembered-choice-from-a-servers-list-kept-per-group-on-add-only-and-in-rows)).
+  A value no longer offered is dropped without a word, never drawn as a broken one. It is the value the form opened with, not a change: no "Unsaved changes", no "Discard?".
+- **Kept when a form saves** (`SubmitForm`, so `ApiForm` and a CRUD's forms too), in local storage under
+  `nx-input:{key}:{viewer}` as `{ value }`; an empty value forgets. A form reset after the save (`resetOnSuccess`)
+  opens on the new choice. No `viewer`: nothing read or kept (`preferred` still applies). A hidden input keeps nothing.
+- **No hydration difference:** the storage is read once the form is in the browser (a layout effect, before the first
+  paint), so a form drawn by a server opens the same there and while it hydrates; `preferred` needs no storage and
+  applies from the first draw. A later load (a CRUD's record) opens remembered inputs again from what it was given.
+- `FormStore` gains `attachMemory(storage)` and `rememberSaved(values)` (both `@internal`); the rules are pure in
+  `Helpers/InputMemory.ts` (`scripts/test-input-memory.mts`, 46 checks).
+- **Fixed (card C-input-memory-fix):** an input with `showWhen` whose other input gets its value in the same load (its
+  `defaultValue`, the record's) opened empty - without its own `defaultValue` and without its remembered value -
+  because the form judged it hidden on the store's values from before the load. A load, a reset and a draft's restore
+  now judge `showWhen` on the values they open with (the store's `get` answers from them while they are worked out); a
+  hidden input still keeps only what the data gave it.
+- Proved by nexus.template's `/demo/form` "Remembered choices" (`input-memory.cjs`, both motion modes: empty with
+  nothing kept, a save keeps and the reset opens on it with nothing unsaved, a new form, the company's default winning,
+  a disabled and a gone value dropped with no broken tag, a server-drawn page with no hydration error, Forget, light
+  and dark at 1280x720 and 390x844), with `forms.cjs`.
+
+### A label that follows another input
+
+Card C-label-follows (2026-11-05), the owner on a company's registration number: *"label should dynamic if possible like
+if user choosed pan then pan number if vat then vat number if it possible our component allow minimal code logic"*.
+Additions only.
+
+- **`InputLayoutParams.labelWhen`** (`InputLabelWhen`: `name`, `labels`, `otherwise`, `placeholders`; Form only):
+  the input's label is `labels[value]` for the other input's value as it is now (compared as text, so `1` matches
+  `"1"`), else `otherwise`, else its own `label`; its placeholder is `placeholders[value]` where listed, else its own.
+  Its messages name it by the label shown ("VAT number is required.") unless it has a `fieldName`.
+- Built on the `showWhen` machinery: `withInputConditions` gives such an input a live `label` (and `placeholder`)
+  getter and joins the other input's name into `dependsOn`, so the field draws again when it changes - no remount,
+  what was typed and the focus stay. `textFor` and `labelFor` are the pure rules (`test-input-conditions.mts`, 52 to 59).
+- Proved by nexus.template's `/demo/form` "A label that follows another input" (`label-when.cjs`, both motion modes).
+
+### A preview the server works out as the person types
+
+Card C-server-preview (2026-11-05): nexus.web's counter form and the Print layouts editor each wrote by hand "ask the
+server a moment after the last change, drop the older question, keep the last answer while a new one runs". Additions
+only; nexus.web is not changed here.
+
+- **`useServerPreview(ask, { delay, failure })`** (`nexus-shared/client`): `request(question)` asks `ask(question,
+  signal)` `delay` ms (default 300) after the last request; an older question is aborted (its signal) and a late
+  answer of it is never shown; `result` and the `question` it answers stay while a newer one waits or runs and after
+  one fails; `waiting` during the pause, `loading` while it is with the server; `error` is the thrown error's message (an abort is no failure; `failure`
+  is the words when it has none); `cancel()` drops what waits or runs, `clear()` the answer too; leaving the page
+  stops what runs; `request`, `cancel` and `clear` are the same functions on every draw.
+- **`ServerPreviewStore`**: the same outside React (`getState`, `subscribe`), and the types `ServerPreview`,
+  `ServerPreviewState`, `ServerPreviewAsk`, `ServerPreviewOptions`.
+- Proved by `scripts/test-server-preview.mts` (17: a burst asks once, waiting then loading, an older answer dropped, the last answer kept
+  through a newer question and a failure, cancel, clear, the latest ask) and nexus.template's `/demo/document-frame`
+  layout editor, which now reads its preview through the hook (`document-frame.cjs`, both motion modes, unchanged).
+
+### A printable document's logo
+
+Card C-print-logo (2026-11-05), for the receipt: the company's bill logo at its head. Additions only.
+
+- **`PrintDocument` `logo`** (`PrintLogo` `{ src, alt }`, or any node) and **`logoOnThermal`** (default true). On A5 the
+  logo sits beside the title lines in a 24 mm column (at most 16 mm tall) with a column as wide after the lines, so they
+  stay centred on the paper and the head grows no taller than they are: a one-page receipt stays one page. On an 80 mm
+  roll, and on an A5 document shown narrower than 100 mm (a phone; `.nx-print` is now the `nx-print` container), it
+  sits small and centred above them (at most 36 x 10 mm on the roll); `logoOnThermal={false}` leaves it off a roll.
+  Printed in black and white (`filter: grayscale(1)`). An `{ src }` image is decoded at once (not lazy); it must
+  have loaded before `window.print()`.
+- `Nexus.Print.css`: `nx-print__head--logo`, `nx-print__logo`, `nx-print__heading`. Without a logo the head's markup
+  is as it was.
+- Proved by nexus.template's `/demo/print-document` (a colour logo, switches for it and for the roll) and
+  `print-document.cjs`: beside the title on A5 within 24 x 16 mm, the title centred, the head no taller than its lines;
+  centred above on the roll within 36 x 10 mm; off with `logoOnThermal`; grey in print; the longest receipt, voided,
+  printed alone to PDF: one A5 page (420 pt) and one roll page (227 pt).
+
+### A page's own switch in the table's bar keeps its label on one line
+
+Card C-bar-noshrink (2026-11-06), from nexus.web's Branch users: a `Switch` beside Add ("All branches") broke its label
+between its words at every width, and a non-breaking space made it run into the lists instead. The cause was the Add
+itself: it is a `block` button, `width: 100%` of the Add section, so on a shared line it claimed the section and the
+page's own items shrank (a switch's field may shrink to nothing; a button stopped at its label).
+
+- `Nexus.Table.css`: every item of `.nx-table__bar-add` keeps its width (`flex: none`, `min-width: fit-content`), and
+  the Add beside other parts is as wide as its label (`width: auto`), so a bar that does not fit takes its next step
+  (search, Reload into ⋮, the Add section's own line). On that line the items still share it (`flex: 1 1 0`) and one
+  that would not fit its share wraps whole onto a line of its own. No markup or prop changed.
+- Proved by nexus.template's `/demo/data-table` section "The page's own controls in the bar" (a Switch and a Button in
+  `actions`, lists in `toolbar`) and `/demo/crud`'s amenities ("Reset demo") in `data-table-bar.cjs`: at table widths
+  1000, 899, 680, 660, 380, 370, 330, 320 and 300, with the switch and the button, each alone, and the CRUD's button,
+  in seven themes light and dark, compact and cozy: no label broken or cut, no two controls overlapping, nothing
+  outside the bar, one line from 670px (compact), the search alone under 670, Reload in ⋮ under 375, the Add section
+  last under 325.
+
+### A list that can be widened to other endpoints
+
+Card C-crud-scope (2026-11-06), from nexus.web's Branch users: the branch signed in at (`BranchUser`) and, for a person
+who may, every branch (`AllBranchUser`), picked by a switch in the toolbar and remembered per person - written by hand
+with a remounted `Crud`, a page-level hook for the storage and two copies of its columns and inputs. Additions only.
+
+- **`Crud` `scopes`** (`CrudScopes`: `options`, `label`, `description`, `remember: { key, viewer }`,
+  `onChange`): other lists in place of the CRUD's own, each a **`CrudScope`** (`id`, `label`, `description`, `api`,
+  `when`, and where they differ `columns`, `inputs`, `form`, `table`, `aria-label`; `form` and `table` over the
+  CRUD's, field by field). One scope is a `Switch` after Add (`description` its tooltip); two or more are tabs, the
+  CRUD's own list first. A scope is offered to a person who may call one of its lists and passes `when`, again on every
+  change of their rights; a kept scope not offered opens the CRUD's own list and stays kept.
+- **Switching keeps the CRUD**: the new list is read on its endpoints (`loadKey` names the scope), the switch keeps
+  the focus, popups stay open. Each scope keeps its own cache of lists while the page is open, so switching back costs
+  no request; a change made on one scope drops the other scopes' lists (the server alone knows which hold the record).
+  An answer asked on one scope and landing after a switch (a row action, a mark, a mass action, a form's save, a
+  details refresh) writes nothing into the list on screen: every kept list is dropped and the one on screen read again,
+  quietly, and `onChange` still hears of it.
+- **Each scope keeps its own table settings**: its `table.stateKey`, else the CRUD's and `:{id}`. **`DataTable`
+  reads a changed `stateKey`** as the first draw does (page size, sort, hidden columns with each column's own
+  default, order, widths, pins, open sections) and never writes the settings on screen under the new key;
+  `TableStore.restore(saved, { notify: true })` restores over a table already shown.
+- **`remember`** keeps the choice in this browser (`nx-crud-scope:{key}:{viewer}`, the CRUD's own list as nothing,
+  storage in try/catch), read after the first draw and before any list is asked for: a reload asks for one list.
+- **`CrudHandle.scope`** and **`setScope(id | null)`**.
+- **A `CheckBox`'s or `Switch`'s `title`** is now its whole row's tooltip (its label too), still on the input.
+- New exports: `CrudScope`, `CrudScopes`, `offeredCrudScopes`, `shownCrudScope`, `crudScopeProps`,
+  `crudScopeStateKey`, `crudScopeStorageKey`, `readCrudScope`, `writeCrudScope` (`nexus-shared`);
+  `useCrudScopes`, `CrudScopeControl`, `CrudScopeState` (`nexus-shared/client`).
+- Proved by `scripts/test-crud-scopes.mts` (32) and nexus.template's `/demo/crud` section "One desk, or every desk"
+  (posts through `DeskStaffPost` and, for the Admin role, every desk's through `StaffPost`; the demo backend's
+  narrower controllers are views of the same records) in `crud-scopes.cjs`.
+- **Review fixes** (card C-scope-fix, review round 4):
+  - **Opening on a remembered scope no longer wipes the CRUD's own list's table settings.** `DataTable` saves what its
+    store holds, never the draw's settings: the first draw, which still held the opening defaults, wrote them under the
+    own list's key when the kept scope was read, and its sort and hidden columns were gone on the way back.
+  - **A form stays in the scope it was opened on**: an Edit pressed in a details popup after a switch is the details'
+    scope's form - its `inputs`, `form` and endpoints - and its save is that scope's answer (it went to the scope shown,
+    with the other scope's fields).
+  - **Each scope keeps its own Add**, and so its draft (the popup's name is `{name}@{scope}`): a minimized Add of one
+    list never comes back on another. An Edit keeps one popup per record wherever it is opened.
+  - **An answer that lands after a switch** still marks the lookups of the scope it was asked on and of the one shown as
+    old (`expireLookups`: a picker's or a join's next read asks again) and drops every tree's kept pages, as an answer on
+    screen writes them.
+  - Proved by `crud-scopes.cjs` section K, each line failing on the code before: the own list's sort and hidden
+    Department kept through a client navigation that opens on the kept scope; a Spa post's Edit from details restored
+    after a switch is every desk's form and saves to `StaffPost/Update`; the own Add's draft stays the own list's; the
+    demo's "Find a post" box (every desk's `StaffPost/ActiveListing`, its pages dropped on every change of the CRUD)
+    asks its list again after an answer for every desk lands on the front desk's list.
+
+### Pinned columns give way on a narrow table
+
+Card C-pin-narrow (2026-11-06, with C-scope-fix), from nexus.web's Branches at 390 px: Name and Picture pinned left took
+284 of the table's 354 px, leaving 70 for every other column. Additions only, and no page passes anything.
+
+- **The columns that stay - the numbers and checkbox column and the actions, which always stay, and the pinned ones -
+  take at most 60% of the table's width on screen** (`PINNED_SHARE`). Pins are kept from the outer edge in; a pinned
+  column that would pass that share, and every one inside it on the same side, scrolls with the others until the table
+  is wide enough again. Measured after every draw and whenever the table's width changes; staying or scrolling changes
+  no width, so it settles at once.
+- A column that gives way keeps its side: it is drawn there, moves among its side's columns, and its menu still offers
+  Unpin. **`TableViewColumn.side`** (new) is the side chosen; **`pin`** is the side it stays on now (null while it
+  scrolls, so its cells carry no `data-pin`). Headings carry `data-pin-side`, which the drag's drop targets follow.
+- New exports (`nexus-shared`): `PINNED_SHARE`, `releasedPins(view, frame, left, right, share?)`.
+- Proved by `scripts/test-table.mts` (the rule, and `viewColumns` with released columns) and nexus.template's
+  `data-table.cjs` at 390 px with Booking and Guest pinned: the columns that stay keep to 60% of the table, the outer
+  ones stay with their cells and the others scroll, both keep their side, and at 1280 both stay.
+
+### A row action that opens a form of its own for the record
+
+Card C-row-form (2026-11-06), from nexus.web's Permissions row action (`usePermissionSetActions`, written by hand: a
+popup with an `ApiForm` reading the set, saving it elsewhere, then `apply` of the row's count). Additions only.
+
+- **`Crud` `rowForms`**, each a **`CrudRowForm`**: `id`, `label`, `description`, `icon`, `inline`, `modes`
+  (default the lists that offer Edit), `when(row, mode)`, `lock(row)` (listed switched off with its sentence), `target(row)`
+  (the `{id}` the endpoints are called with), `inputs` (params, or a function of the record and of what `load` read;
+  it may answer a promise), `load` (an endpoint or a function), `submit`, `transform(values, row, loaded)`, `writes`
+  (the answer's fields by name, or a function), `title`, `size`, `submitLabel`, `onSaved(result, row, values)`.
+  Offered after the built-in actions and before `rowActions`, to a person who may call `submit` and an endpoint
+  `load`; one popup per record and form (`reopen: "restore"`), a discard question before changes are lost.
+- **A read that fails never leaves a savable form**: the API client answers `ok: false` rather than throwing, so a
+  failed answer (and one with no record, and a function's `null`) is turned into `ApiForm`'s failed state - "Could not
+  load the values" with Retry - and the footer's Save is gone until a read succeeds. (A permission set read that failed
+  opened empty, and its Save wiped the set.)
+- **The write-back is only what the answer names**: `writes` fields merged over the record as the CRUD holds it when the
+  answer lands (the table, else a kept list, else a pinned section), never the record as the action was clicked, so an
+  Edit saved while the popup was minimized stays. Written through the cache sync (`applyRows` with the held record),
+  so every list kept and the pinned sections follow with no list read; an answer after a scope switch writes nothing.
+- **`CrudHandle.openRowForm(id, row)`**. New exports: `CrudRowForm`, `crudRowFormOffered`, `crudRowFormWrites`
+  (`nexus-shared`); `openCrudRowForm`, `CrudRowFormRequest` (`nexus-shared/client`).
+- Proved by `scripts/test-crud-row-forms.mts` (24) and nexus.template's `/demo/crud` posts, whose Duties (PostDuty's
+  Detail and Update in the demo backend, a count joined into each post) are a row form, in `crud-row-form.cjs`.
+
+### A held menu item says why when it is pressed
+
+Card C-held-action-note (2026-11-06), from a review of nexus.accounts' dashboard: a row action switched off with its
+reason (`rowLock`, `rowActionLock`, a row form's `lock`) showed that reason only as its menu line, and a press did
+nothing, where the table's held Add says why under it. Behaviour of `Menu`, `ContextMenu` and `SplitButton`'s list; no
+export is new.
+
+- **`MenuPanel`**: an item `disabled` with a `description` is held (`data-held`). A press - a click, Enter, Space -
+  shows the description in the note a read-only field and a held Add show (`useReadOnlyNotice`, `.nx-field-notice`,
+  `role="status"`), under the item; the menu stays open, nothing is chosen, and the note goes when the menu closes. The
+  arrow keys and the pointer reach a held item (`ENABLED_ITEM` takes `[data-held]`), so the keyboard can press it;
+  a disabled item without a description is skipped as before.
+- Proved by nexus.template's `held-row-actions.cjs` on `/demo/crud`: Wi-Fi's held Move to trash (`rowActionLock`) and
+  a not-yet-joined person's held Duties (a row form's `lock`) say their menu line's words when clicked and on Enter
+  after the arrow keys reach them, with the menu open and no request sent; Esc closes both; `/demo/menus`' Print
+  (switched off with no reason) is still skipped; the note inside the window and its words at 4.5:1 or more in seven
+  themes, light and dark, at 1280 and 390.
+
+### A form with changes asks before a navigation inside the app
+
+Card C-leave-guard (2026-11-06), from a review of nexus.accounts' dashboard: its profile form lost its edits through the
+side menu, since only the page's close (`beforeunload`) asked. Additions only.
+
+- **The page's own forms**: a `SubmitForm` (and so an `ApiForm`) that asks before the page closes (`confirmLeave`, on
+  without a draft) also joins the tab's page guard (`PageLeaveGuard` in `FormLeaveGuard.ts`, beside the workspace's
+  guard), unless it is drawn in a `PopupHost` popup, which stays open through a navigation (`PopupHost` gives its
+  popups no page guard).
+- **Links**: while one of them has changes, a press on a same-origin link - next/link or a plain `<a>`, the side menu,
+  the brand, the trail, a menu's link row - is held in the capture phase on `window` (before any other handler) and
+  asks "Discard your changes?" (`confirmDiscard`'s words, as a workspace tab and a form popup ask); Keep editing stays,
+  Discard follows the link as it was pressed (the app's router for its links). A link to another tab, a download,
+  another site (the browser's close question asks there) or this page is left alone. Set up once, by the first such
+  form.
+- **`confirmPageLeave()`** (`nexus-shared/client`): the same question for a navigation the app makes itself
+  (`if (await confirmPageLeave()) router.push(href)`). A confirmed navigation is let go for a moment
+  (`PageLeaveGuard.allow`), so the form's `beforeunload` does not ask a second time after a plain link's Discard.
+- Proved by nexus.template's `leave-guard.cjs` on `/admin/settings`: the side menu, the brand, the trail, Back to the
+  site, the account menu's link and the module menu each ask and Keep editing keeps what was typed; Discard goes (by the
+  router, and by the address for a plain link with no browser question); a form without changes, and one just saved,
+  goes with no question; a minimized Add with changes (a `PopupHost` popup) holds nothing and is still on the dock; a
+  reload with changes still gets the browser's question.
+- **Review fixes** (card C-leave-fix, review round 4):
+  - **A popup's form keeps the browser's close question**: a confirmed Discard of the page's form let the next moment's
+    full-page load go with no question for every form, so a minimized Add with changes was lost without a word. Only the
+    page's own forms are let go now.
+  - **The page already in view asks nothing**: a module or account menu row for it lost nothing and still asked.
+    **`keepsPage(href, target?, download?)`** (new, `nexus-shared/client`) is the one test, for links and for the
+    rows nexus-admin moves by `router.push`.
+  - **A link inside text being edited** (the rich-text editor's) is not a navigation: a click there places the caret,
+    and nothing is asked.
+  - **`confirmPageLeave({ unload: true })`**, for a move that loads a whole page (a sign-out, `location.assign`): asks
+    about every form with changes, the popups' too, since the load takes them all; once confirmed, neither it nor the
+    browser's close question asks again until the page goes (`pagehide`), however long the call before the move takes.
+    **`endPageLeave()`** (new) gives the questions back when the move did not happen.
+  - Proved by `leave-guard.cjs` section F: the module row for the page in view and a link in the House rules editor ask
+    nothing and keep the typing; a page Discard followed by a full load still gets the browser's question for a
+    minimized Add with changes; Sign out (slowed by 2.5 s) asks about a minimized Add first, Keep editing sends nothing,
+    Discard signs out with no second question.
+
+### Every picture through the editor, and within Drive's limits
+
+Card IMG-comp (2026-11-06), the owner: *"any image editor should be open the editor then it upload ... first compress
+then save ... ~300KB max but put it into config ... max resolutions, max quality (%) in config for drive."* A picture
+of about 3 MB was stored: the gallery's Upload never opened the editor, a PNG stayed a PNG at up to 2048 px, a
+remembered quality could be 100, and nothing kept a byte budget. Drive's side is card IMG-api
+(`drive-picture-limits-contract.md`): its host settings `Nexus:Drive:Pictures` (MaxSide 1920, Quality 80, MaxKilobytes
+300), answered by `File/List` and enforced on every upload.
+
+- **`FileCategoryInfo`** gains `pictureMaxSide` (px), `pictureQuality` (%) and `pictureMaxBytes`, optional, read by
+  `NexusDriveAdapter` from `File/List` with the defaults when an older Drive answers none (so every picture is still
+  made small). **`PICTURE_LIMITS`** (`{ maxSide: 1920, quality: 80, maxBytes: 307200 }`) and **`pictureLimits(category)`**
+  (the category's, else the defaults; the bytes never above its `maxBytes`) are new. `MAX_PICTURE_SIDE` is now the
+  default 1920 (it was 2048) and nothing in the package reads it.
+- **Every picture through the editor** (`useOwnerFiles`): the gallery's Upload - every picture column, the top bar's own
+  picture, a record's workspace, the accounts dashboard - opens the editor for each picture in turn ("Picture 2 of 5 ·
+  {title}"); Cancel skips that one and, with more to come, asks "Go on with the next file?" (Next file, Stop here). It
+  keeps the chosen file's name with the kind written. Documents (a PDF) are sent as they are. `renderImage` is no longer
+  called by the package.
+- **Within the limits**: the editor gets the long edge at most `pictureMaxSide` (less when the params say), `maxQuality`
+  `pictureQuality` / 100 and `maxBytes` `pictureMaxBytes` (`ImageEditorOptions` and `renderImage`'s options take both;
+  `ImageEditorResult.fitted` says what the budget took, see nexus-image-editor's CHANGELOG). The toast after a save
+  says when a picture was made smaller.
+- **`fileRefusal`** checks a picture against `pictureLimits(category).maxBytes` and a document against `maxBytes`; the
+  gallery's line says "up to 300 KB each", or "pictures up to 300 KB, documents up to 10 MB" where both are taken.
+- Proved by `scripts/test-files.mts` (84) and nexus.template, whose pretend Drive answers and enforces the three
+  (`Demo/PictureLimits` raises them for the checks): `picture-limits.cjs` (a 4.2 MB photo stored at about 175 KB with the
+  Save panel's real size and its note, the slider's top 80 and a remembered 95 starting at 80, a see-through PNG stored
+  as a WebP that keeps its see-through parts, an opaque PNG as a JPEG, three pictures each through the editor with a
+  Cancel and Next file, Stop here, DRV_X059 for a client that skips the editor, raised settings letting a 1.8 MB
+  picture through) and `pictures.cjs` (the gallery's three uploads each through the editor, the page's square shape).
+- **Review fixes** (card IMG-comp-fix, review round 4):
+  - **Only into a kind the category takes**: the editor gets the category's picture kinds (`ImageEditorOptions.types`,
+    from `pictureOptions`). Its Save panel offers only those, a picture opens on one of them, and a PNG over the size is
+    made a JPEG or a WebP only where that kind is taken - where neither is, it stays a PNG and is made smaller. A
+    see-through PNG for a category of JPEG and PNG was written as a WebP and then refused.
+  - **A picture the browser could not type** (no type, or `application/octet-stream`: a phone's share, a name with no
+    extension) is typed from its first bytes and goes through the editor, where it was sent as it was:
+    **`sniffPictureType(blob)`** (JPEG, PNG or WebP, else null) and **`typedFile(file)`** (new, `nexus-shared`). Any other
+    untyped file is still the backend's to judge.
+  - **An editor that cannot be downloaded says so where it was asked for**: the picture input's line under its buttons
+    and the gallery's alert say the loader's words ("The image editor is not installed on this server yet." for Drive's
+    DRV_X053) until a try opens it, besides the toast; the button stays ready, and pressing it again tries again.
+    `useOwnerFiles` answers `editorProblem`.
+  - Proved by `test-files.mts` (88) and `picture-limits.cjs` section G: the ID photo's category (JPEG and PNG) offers
+    those two in Save and stores a 3 MB see-through PNG as a PNG under 300 KB that is still see-through; a photo handed
+    over with no type opens the editor and is stored as "IMG_2041.jpg" under 300 KB; with Drive's editor missing the
+    input and the gallery say why, and once it is there the same button opens it and the line goes.
+
+### A record's page of cards, every change in a popup
+
+Card C-record-cards (2026-11-06), from the owner's request for nexus.accounts' profile: *"make card types block
+buetifull design ... when click editor then show popup and apply editor or add or something do not show direct save or
+update"*, and *"Emails / Phones / Addresses - those all put inside profile tab as card. put right side icons to verify if
+not. switch primary like this. single page, CURD from popup show add button, edit, remove like this. primary do not
+allow"*. Additions only.
+
+- **`RecordCards`** (`nexus-shared/client`): one record that is not a list - a person's profile, my company, a
+  subscriber's details - as a hero and cards, declared by params (`RecordCardsProps`): `sources` (each read once by GET
+  through the app's `api`, or a function; `{ read, held }` draws what is known before, such as the session's name),
+  `hero` (`picture` by Drive params - a click opens the pictures window - `title`, `lines`, `marks`, `actions`), `cards`,
+  `readOnly`, `signedOut` (the page's words, `onSignIn`, `onEnded`), `isSessionEnded`, `name`, `headingLevel`. **The page
+  itself never saves.**
+- Three cards, each with an `id` (its element id, so `#emails` leads to it), a `source`, `title`, `icon`, `description`,
+  heading `actions`, `hidden`, `wide`, `readOnly`:
+  - **fields** (`RecordFieldsCardParams`): label over value, each value drawn by the `InputParams` its Edit uses - a
+    choice by its label, a date in the person's format, a number with its format, Yes or No, a multiple choice or
+    `look: "chips"` as chips, long text on its own lines, Markdown and rich text as such, a password never, "Not said"
+    (`empty`) when empty; `show` draws one by the page. **`edit`**: a popup of the card's inputs on the record, its values
+    merged over the record as held now when sent, so an endpoint that takes the whole record works.
+  - **items** (`RecordItemsCardParams`): rows between hairlines (a picture or icon, the title, marks, lines) with **icon
+    actions on the right** (`RecordItemActionParams`), each named as a tooltip and to a screen reader with its item
+    ("Verify: ram@example.com"), hidden, or held with its reason - aria-disabled, the reason in its tooltip and said in
+    the note a held Add shows when pressed; **`add`** in the heading, held at the `limit` ("5 of 5" beside the title,
+    `limitReason`).
+  - **content** (`RecordContentCardParams`): `render(context)`, the page's own; `context.open(flow)` opens a popup.
+- **Every change is a popup** (`RecordFlowParams`): one step, or `steps` with `start` and `next` (a code sent, then
+  typed), each with its `lead`, `inputs`, `submit` (a URL, a request, an endpoint or a function), `transform`,
+  `submitLabel`/`submitTone`, `writes`, `also` (a button that calls and stays, held with a countdown while the server says
+  to wait: "Send again in 20s"), `done` (run another action: the code step after an Add, Make primary after a Verify),
+  `onError`, `render`, `confirmCancel`; one popup per card, action and item, brought back as it was; closing with changes
+  asks first. A form opens only on the plain values its inputs name, so a code box never opens on an item's `code`
+  record. **`confirm`** (`RecordConfirmParams`) asks, then calls.
+- **The card shows the answer at once**: `writes` (`RecordWrites`) - the answer merged over the data as held now (the
+  default), the values, one item replaced or added, the item removed, a read again, named fields, or a function - into
+  the source, so every card on it (the hero too) follows and nothing is read again.
+- **States**: loading draws every card as it will be, held (labels and bones as tall as their values, a held mark row,
+  Edit held with "Still being read."); a source that fails says why in each of its cards with Try again (the first says
+  it aloud); read-only draws no button; an answer that ended the session (default a 401 naming no input - a wrong
+  password names its box) closes the page's popups and leaves the page's words with Sign in again, which takes the
+  focus. The focus comes home when a popup's or a question's opener went with the change (the row's first button, else
+  the card's). A link to a card (`#emails`) is followed again once every source has answered, since the cards above it
+  grow as their records come.
+- **Layout**: the hero across, then as many cards to a row as have 26rem (one on a phone), each as tall as what it
+  holds; fields as many to a row as have 11rem. It sits in the admin page's scroller, so the window never scrolls.
+  `Nexus.Record.css`; the table's tag gets `nx-table__tag--plain` (no dot) for a chip.
+- New exports: `RecordCards` (`nexus-shared/client`); in `nexus-shared` the interfaces `RecordCardsProps`, `RecordRead`,
+  `RecordSourceParams`, `RecordWrites`, `RecordMark`, `RecordSubmit`, `RecordContext`, `RecordStepContext`,
+  `RecordStepAnswer`, `RecordCallParams`, `RecordStepParams`, `RecordFlowParams`, `RecordConfirmParams`,
+  `RecordCardActionParams`, `RecordItemActionParams`, `RecordCardBase`, `RecordFieldParams`, `RecordFieldsCardParams`,
+  `RecordItemView`, `RecordItemsCardParams`, `RecordContentCardParams`, `RecordCardParams`, `RecordHeroParams`,
+  `RecordSignedOutParams`; the typed helpers `fieldsCard`, `itemsCard`, `contentCard`; and the pure half
+  (Helpers/RecordCards.ts) `recordCardKind`, `recordField`, `recordFieldInputs`, `recordOpenedValues`, `recordFieldWide`,
+  `recordFieldHeld`, `recordValueView`, `RecordValueView`, `recordItems`, `recordItemKey`, `recordWithItems`,
+  `recordLimit`, `recordCount`, `recordLimitReason`, `recordWrite`, `RecordWriteRequest`, `RecordWriteOutcome`,
+  `recordActionState`, `recordActionEndpoint`, `RecordActionState`, `recordSteps`, `recordStartStep`, `recordStatusLine`,
+  `recordSessionEnded`, `secondsUntil`, `RecordSources`, `RecordSourceState`, `RecordReader`.
+- Proved by `scripts/test-record-cards.mts` (130) and nexus.template's `/admin/profile` (a pretend person's profile on
+  `src/app/api/demo-profile`, with a menu of demo states) in `record-cards.cjs`.
+
+### The pictures window in two panes, as 2026-06-20's
+
+Card C-gallery (2026-11-06), from the owner's look at the pictures window on nexus.accounts' profile: *"the over all
+design i do not like. when hover then show inside the image the absolute position. look like the second image. this
+image capture from: 06-20 version. when click profile icon then show popup like this."* No new exports, nothing removed;
+the look and where the buttons are changed, every behaviour stayed.
+
+- **`PictureGallery` / `openPictureGallery`**, for pictures: two panes with a hairline between them. On the left the
+  main picture large (about 15rem on its long side, a rounded square for every shape; the picture icon when there is no
+  main one), **Upload** (a solid primary button; Replace in a category that keeps one file) and **Remove** (no main
+  picture, the pictures kept; Delete in a one-file category) under it, then the count and kinds ("2 of 20 · PNG, JPEG or
+  WebP, up to 300 KB each"), a read-only reason and the editor-cannot-load note. On the right the pictures as a grid of
+  rounded squares (about 11rem, at least two a row), a round category's too - only an avatar stays round. The main one
+  has the accent ring and a **Main** mark in its top left corner.
+- **Each picture's buttons are inside it**, centred on a popover's panel: View, Make main and Delete (neither on the
+  main one: it is never deleted from its own picture, as in 2026-06-20's gallery - Remove it first, or make another the
+  main one) and Edit. They show on hover and on a keyboard's focus in the picture (`:has(:focus-visible)`, so a click
+  does not leave them shown), and always where nothing can hover (`@media (hover: none)`: a touch screen); hidden, they
+  stay in the Tab order and to a screen reader, each named as a tooltip and to a screen reader ("Make Sita.png the main
+  picture"). They fade in briefly, and not at all with animations off.
+- **Under 560px of its own width** (a phone, a narrow tab) the main picture is 7rem beside its buttons, over the grid.
+- **The window** (`openPictureGallery`) is `xl` and edge to edge for pictures, with a height of its own
+  (`min(36rem, 100dvh - 10rem)`, the whole window when maximized): only the grid scrolls. Documents stay a list in an
+  `lg` window; one opened without `view` changes to it once the category says it takes PDF.
+- **States**: loading draws the panes at their size, the main picture's place held and three held pictures where the
+  grid will be ("Loading the pictures…"); a gallery with none says "No pictures yet." with Upload on the left; read-only
+  owners (`readOnly`, `lockReason`, a refused write ticket) get no Upload, Remove, Make main, Edit or Delete. Upload
+  and Edit when the category is full are `aria-disabled` with the reason as their tooltip, and say it when pressed.
+- **`PictureInput`**: a click on its picture, or Enter, opens the same window, as All pictures does (read only where the
+  input is); its buttons stay. The picture is named by what it opens ("Picture: open the pictures"), never by the
+  file's name. Its buttons are a `role="group"`, and `useFocusThroughChange` keeps the focus in a tile, row or group, so
+  after a Delete the focus lands on Upload, not on the picture.
+- The data hook is `data-state="loading|ready|failed"` on `.nx-files`; the tile's `.nx-files__tile[data-primary]`,
+  `.nx-files__thumb` and the buttons' names are as before. `.nx-files__tile-bar` and `.nx-files__thumb--round` are gone.
+- Proved by nexus.template's `pictures.cjs` (its section K: the panes, the mark, hover, keyboard and touch, Remove,
+  loading, empty, read only, a 390 px phone, the picture input's picture) and `picture-limits.cjs`, both motion modes.
+
+### A popup has no minimize button unless it asks
+
+Card C-popup-minimize (2026-11-06), from the owner: *"every place do not put minimize popup buttons - for example the
+profile picture viewer, or something just full admin page + CURD this place put minimized option for only the edit and
+add"*. No new exports, nothing removed; **one default changed**, which an app sees without changing a line.
+
+- **`Popup` / `openPopup`'s `minimizable` defaults to false** (it was `closable`, so every closable popup had the
+  button). Maximize and close are as they were. A page may still ask: `minimizable` on a `Popup` or in `openPopup`'s
+  options, or a rule by key (`definePopupRules({ "booking-edit-*": { minimizable: true } })`).
+- **Only a CRUD page's forms ask**: a `Crud`'s Add and Edit (`openCrudForm`: from the list's Add, a row's Edit, a
+  tree's Add inside a row, and the details popup's Edit) and its row forms (`openCrudRowForm`, such as a record's
+  Permissions). They ask with `popupRuleFor(key)?.minimizable ?? true`, so a page's rule for their key can still take it
+  away. The dock, `reopen`, and the leave guard work for them as before: a minimized form with changes is still asked
+  about by a full-page move (`confirmPageLeave({ unload: true })`) and by the browser's `beforeunload`.
+- **Everything else has none**: the details popup and a record's workspace (its Edit opens the form that has one), the
+  mass Description, the audit history, the spreadsheet import and bulk insert, the pictures window and gallery
+  (`openPictureGallery`), a record's cards' popups (`RecordCards`, `openRecordFlow`), a `Chat`'s popup, message boxes
+  and confirms (which already said `minimizable: false`), and any popup a page opens without asking. The image
+  editor's window and the picture viewer are the editor module's own and never had one.
+- `handle.minimize()` from code still minimizes any popup opened with `openPopup`; the dock shows it as before.
+- Proved by nexus.template's `popup-windows.cjs` (a popup that asks has Minimize, Maximize, Close; one that does not -
+  from a page, from code, opening maximized - has Maximize and Close; the dock, the stack, the rules by key, a scrolled
+  body kept), `crud.cjs`, `crud-row-form.cjs`, `staff-posts.cjs`, `leave-guard.cjs` (the forms that minimize),
+  `crud-workspace.cjs` (the workspace has none; a record off the page shown is now opened from the pinned guests),
+  `crud-scopes.cjs` (the details have none; the Edit form they open is minimized across a switch), `excel.cjs`,
+  `pictures.cjs` and `record-cards.cjs` (none), both motion modes, and `test-popup-rules.mts` (the forms' rule).
+
+### A CRUD's narrowing box asks to be set
+
+Card C-narrow-required (2026-11-06), from the owner on nexus.web's subscribers: *"when open it focus on the group and
+high light the required tab which help user to it need to set"*. Every `Crud` `narrowPicker` changes; a page changes
+nothing. New: `Field` / `Dropdown` `invalid`, `DataTable` `add.onDisabledPress`, and in `CrudNarrowPick.ts`
+`findLoneNarrowPick`, `startNarrowPick` (`NarrowPickStart`) and `narrowBoxTakesCursor` (`NarrowCursorMoment`).
+`useCrudNarrowPicker` takes the list's words too (optional) and returns more parts (`CrudNarrowPickerParts`); `Crud`
+is its only caller in the packages.
+
+- **It settles before it asks.** As the page opens, the box shows a spinner and the list waits (no "Pick a group" that
+  flashes before a remembered pick opens) while the kept pick is looked up; a kept pick no longer offered is forgotten.
+- **A box that offers one record picks it by itself**, and keeps it as a person's pick is (`remember`), `onPick` told.
+  Offered as the box offers it: a record it never offers (a person still invited, an inactive one) does not count, and
+  its pages are read at the box's own size, only until a second record shows.
+- **With nothing picked it asks:** the box is required (`aria-required`) and drawn with a field's invalid edge and ring
+  (`invalid`: the look an error gives, with no message line in the toolbar), and a screen reader hears the list's
+  words with it (`aria-describedby`; the page's `emptyMessage` when given). It takes the cursor as the page opens,
+  without scrolling, unless the person has already pressed a key or a pointer there, focus is elsewhere, a popup or a
+  panel is open, the box is not wholly on screen (a CRUD further down a demo page), or the screen is touch-only (a
+  cursor would raise the on-screen keyboard over the list). A pick removes the mark; clearing it brings it back.
+- **The list points at it:** its empty message has a button with the box's placeholder ("↑ Pick a group") that sends
+  the cursor to the box and opens its list. A read-only list (no Add for this person) asks the same way.
+- **Add pressed with nothing picked** sends the cursor to the box and nudges it (the field's nudge, as a read-only lock's;
+  none with reduced motion), and the box's description becomes Add's reason (`addMessage`), so a screen reader hears
+  why it landed there; the note under Add no longer shows for it. Add still looks unavailable and keeps its tooltip.
+- **A failed read** of the box's records leaves it asking, the cursor in it; its own list says "Could not load the
+  options." with Retry when opened.
+- Proved by nexus.template's new **Admin › Posts** page (`/admin/posts`: one person's posts, the Person box in the CRUD's
+  toolbar; `?people=one` offers one person) and `crud-narrow-required.cjs` (settling, the mark, the cursor, Add from the
+  mouse and the keyboard, the list's button, a pick, remembered, forgotten, at work, a popup open, a failed read and
+  Retry, one person offered among invited ones, below the fold and the Viewer role on /demo/crud, 390 px with a mouse
+  and on a touch screen, the edge at 3:1 and the button at AA in all seven themes light and dark), both motion modes,
+  and `test-input-narrowing.mts` (the opening and the cursor rule).
+
+### A remembered choice from a server's list, kept per group, on Add only, and in rows
+
+Cards C-input-memory-offered (2026-11-06, committed unfinished) and C-input-memory-offered-finish (2026-11-07), from what
+nexus.web's Subscribers Add (card SUB-defaults) found in [`remember`](#an-input-that-remembers-its-last-value-or-opens-on-the-companys-default):
+a kept type, area or package since trashed opened tagged "Inactive", one moved to another group opened untagged and the
+save was refused, a contact's or a box's kind could not be remembered, and the page wrote "on Add only" and "per group"
+by hand. Additions only; no new export.
+
+- **A picker confirms a kept choice before it opens.** A dropdown whose options come from `loadOptions` (as `crudPicker`
+  gives) is asked by the value's key: at once from what the page holds (`peekOption`), else by `resolveOptions`, and for a
+  key that answers nothing (a picker that names only its kept list) or a record without its narrowing's field, through
+  its own pages narrowed as the form narrows them. Offered = found, not disabled, not inactive (`isOptionInactive`, else
+  `inactive`/`isActive: false`), and inside its `narrowedBy` narrowing; for a list of values, the part offered. A kept
+  choice not offered never opens and is forgotten; `preferred` gives way to the kept choice the same way. Before it was
+  "a server's list takes any value".
+- **While it is asked** the box shows its spinner (`Dropdown` `loading`, through the new `InputOverrides.loading`) and
+  opens nothing; the answer opens the value as the one the form opened with. It opens nothing over the person: a pick
+  (even one cleared again) or a value set from code ends the ask at once. A save, a reset and a later load stop it. An
+  answer given for a group (the `narrowedBy`, `per` or `when` inputs) the form no longer holds opens nothing. A picker
+  that cannot be read opens nothing and forgets nothing; it is asked again by the next form. A reset that finds the
+  kept choice gone, or still to be asked, takes back the value memory opened before instead of leaving it in.
+- **`remember.per`:** one value kept per value of another input, under `nx-input:{key}-{that value}:{viewer}`: a package
+  per group, since a package is one of its group's. While the other input holds no single value nothing is read or kept.
+- **`remember.when`:** remember only while these `InputCondition`s hold on the values the form opens with and saves.
+  A CRUD's Edit form holds the record's key and its Add form does not, so `{ name: "id", filled: false }` remembers on
+  Add only: Edit opens on the record's values, asks no picker, and its save keeps nothing.
+- **Rows remember** (a tabular or group form's row inputs): a new row's input opens on its kept value unless `newRow` or
+  the values it is added with name it (so a remembered row input takes its first choice as its own `defaultValue`, not
+  in `newRow`); a save of the form around them (`SubmitForm`) keeps the value of the row added last that is still there
+  (one added then removed does not count; none added, nothing kept). `per` and `when` read the row's own values. A
+  picker in a row is asked the same way (no spinner there), judged on the row as it was added.
+- Inside: `Helpers/InputMemory.ts` (`keptStandingNow`, `findKeptStanding`, `rememberedOpeningNow`,
+  `findRememberedOpening`, `rememberDependencies`, `lastAddedRowKey`; pure), `FormStore` (`isRemembering`, internal),
+  `RowsStore` (`attachMemory`, `rememberAdded`), `RowsInput` and `SubmitForm` (the save tells the rows inside the
+  `<form>`). `test-input-memory.mts` 115 checks, `test-rows-store.mts` 123.
+- Proved by nexus.template's `/demo/form` "Remembered picks from a server's list, and in rows" (an order's amenity, a
+  `crudPicker` narrowed by the order's group and kept per group on a new order only; a contact's kind in rows) and
+  `input-memory-picker.cjs`: nothing kept, a save and the reset, another group, a page drawn by the server with the
+  lookup held (the spinner, then the value, no hydration error), a trashed amenity and another group's (asked by key on
+  a cold page, and at once from the list the page holds; no tag), a pick before the answer, the lookup down and the
+  whole picker down, Edit, a row added then removed, a pick by the keyboard while asked and the kept value heard with
+  the box, light and dark at 1280x720 and 390x844, both motion modes.
+
+### A record tab's footer that stays in view
+
+Card C-tab-footer (2026-11-07), the owner's first ask of the day for the subscriber window's counter tabs: their line
+("To pay …") and Save sat under the form, so at 1280x720 Save was at y=807 of a 644px panel and had to be scrolled to.
+Additions only: 2 exports.
+
+- **`CrudTabFooter`** (`nexus-shared/client`), with **`CrudTabFooterProps`** (`children`, `className`): put last in a
+  tab's content, it holds the tab's words (a `<p>`) at the start and its buttons (`FormButtons`, or `Button`s) at the
+  end. In a record's workspace it sticks to the bottom of the tab's scrolling panel while the tab scrolls and sits in its
+  place at the end of the content, so Save is always in view; it reaches across the panel's whole inner width on the
+  panel's own surface under a `--nx-border` hairline, with the popup footer's room (`--nx-space-3` above and below, the
+  panel's side padding at the sides) and gap, no shadow and no frame of its own. On a phone the words and the buttons
+  wrap as whole groups. Outside a workspace it is a plain bar where it stands.
+  ```tsx
+  <ApiForm form={form} buttons={false} api={COUNTER_CREATE} inputs={inputs} />
+  <CrudTabFooter>
+    <p role="status" aria-live="polite">{summary}</p>
+    <FormButtons form={form} submitLabel="Save" />
+  </CrudTabFooter>
+  ```
+- **The keyboard and the footer.** A field (or a text box's caret) the focus moves to is scrolled clear of the footer:
+  the panel keeps the footer's height as room (`scroll-padding`), from `--nx-crud-tab-footer-size`, which the footer
+  measures and keeps on its panel while it is drawn. While the focus is in the footer that room goes, so Save taking
+  the focus never scrolls the tab. A Save that finds a problem scrolls the field to above the footer.
+- Styles: `Nexus.Crud.css` (`nx-crud-tab-footer`; the panel's side padding is now `--nx-crud-panel-pad-x`, the same
+  `--nx-space-5`, and `--nx-space-4` under 720px, and it keeps no padding under a footer).
+- Proved by nexus.template's `/demo/crud` "A guest's workspace", a new tab, **Book a stay** (a form longer than the
+  panel at 1280x720, its line and Save in the footer, saved into the guest's notes), and `crud-workspace.cjs` section K
+  and section F: the footer at the panel's foot scrolled to the top and to the end (Save hit at its centre both times),
+  across the panel's inner width, covering what scrolls under it, a field reached by Tab and Shift+Tab clear of it, Save
+  focused by code and by Shift+Tab without the tab moving, the first problem scrolled to, one Update and one Detail for
+  a save, the panel's own padding back on another tab, and a plain bar outside a workspace; then in 7 themes, light and
+  dark, at 1280x720 and 390x844, a `--nx-border` hairline, the panel's background, no shadow, the line at AA, nothing
+  past the bar or the window, whole groups wrapped.
+
+### Form figures: an input worked out from others, the server's money rule, and a money column
+
+Card C-form-figures (2026-11-07), the owner's first ask of the day: *"after the calculate what is actual value here not
+showing the old version 06-20 showing as calculate value"*, on the price list, the miscellaneous fees and the counters.
+Additions only: 13 exports, all from `nexus-shared`. One look moved by a pixel: a column dropdown's cells now meet their
+headings' edges (below).
+
+- **`InputLayoutParams.compute`** (`InputCompute`: `from`, `value(values, withValue)`; Form only): an input worked out
+  from others, shown and never typed. It is written when the form opens (new values, a loaded record) and again when an
+  input in `from` changes - typed, set from code, loaded, reset - or when the form's `computeWith` changes. It is **no
+  form value**: the store keeps none under its name (a loaded record's own field of that name is dropped), so it is
+  never in `getValue()`, `getChanges()` or what Save sends, never checked (`problems()`), never a change (`isChanged()`,
+  the leave guard, drafts), never remembered, and a value set from code or an `onFieldChange` patch naming it is not
+  taken. A server's message or the form's rule naming it is the form's message. In rows it is ignored, as `showWhen` is.
+  ```ts
+  { type: EInputTypes.Number, name: "netAmount", label: "Calculated amount", decimals: 2, compute: { from: ["price", "vatPercentage"], value: values => priceAmounts(values).netAmount } }
+  ```
+- **The box**: the field's frame (label, hint, prefix, suffix, size, design) around an `<output>` named by its label,
+  `aria-live="polite"`, on the read-only tint, its value in `--nx-text`: no lock, no read-only note, no − / +, no Tab
+  stop. A Number is written with its `decimals` always (1,073.50), grouped, in the person's number format; null,
+  undefined, "" and NaN leave it blank, never "NaN" or "0.00". While the values load (`loading`, an ApiForm's
+  `loadValue`) it is blank and disabled with the inputs beside it; in a disabled or read-only form it takes that look.
+  It is as tall as a NumberBox beside it, with the same edge, in every input design. A rule that throws shows nothing and
+  says so in the console. Styles: `nx-field__control--output` and `nx-field__output-text` in `Nexus.Input.css`.
+- **`FormProps.computeWith`** (so `SubmitForm`'s and `ApiForm`'s too): what the page knows beside the values, such as a
+  server's preview answer, handed to each `compute` as `withValue`. Only the worked-out inputs draw again when it
+  changes, compared by identity, so pass state or a `useMemo` value. `compute: { from: [], value: (_values, line) =>
+  line?.netAmount }` shows a figure the server worked out, and nothing until it answers.
+- `withInputConditions` joins `compute.from` into the input's `dependsOn`. **`isComputedInput`**, **`computedValue`**
+  and **`computedText`** are the pure rules (`test-input-conditions.mts`).
+- **`priceAmounts(input, places = 2)`** (`PriceAmountsInput`: `price`, `quantity`, `discountPercentage`,
+  `vatPercentage`; `PriceAmounts`: `amount`, `discountAmount`, `vatAmount`, `netAmount`): the Nexus server's money rule
+  (`SubscriberRenewals.Price`, 06-20's `FN_CalculateAmount`), each step rounded half away from zero, on exact decimals
+  (a scaled BigInt, each figure read from its shortest text), never on floats. A missing, null or NaN figure is 0, and a
+  missing quantity 1. 1,000 at 5 % off and 13 % VAT is 1,073.50; 99.99 at 12.5 % and 13 % is 98.86.
+- **`priceLadder(row, { keys, locale, totalLabel })`** (`PriceLadderKeys`, `PriceLadderLine`, `PriceLadderOptions`): a
+  receipt's money lines from a row's own figures, on the server's `CounterAmounts` names by default: Rate (left out
+  when the row has none), Amount, "Discount (5%)" and "VAT (13%)" (each left out at 0), then "Calculated amount". A
+  percentage has up to 4 places and no trailing zeros, in `locale` ("Discount (2,5%)" with a decimal comma).
+- **The presets** (`CrudColumns.ts`, one wording for every page; **`PriceKeys`**: `price`, `quantity`, `discount`,
+  `vat`, by default `price`, `discountPercentage`, `vatPercentage` and no quantity):
+  - `crudInputs.netAmount(keys?, changes?)`: a Number `netAmount` labelled "Calculated amount", 2 places, span 3, hint
+    "Price less the discount, plus VAT on the rest.", worked out from the keys, and blank while the price is empty.
+    `changes` replaces any key, `compute` included (a counter's box shows the server's preview instead).
+  - `crudColumns.amounts(keys?, { group })`: Price (money), Discount and VAT (percents) and Calculated amount
+    (`netAmount`, money, worked out from the row's own figures, so a row a save just answered shows it), under one band,
+    "Amount details". A page spreads them: `...crudColumns.amounts()`.
+  - `crudColumns.priceLadder(row, { keys, locale, totalLabel, group = "Money" })`: the ladder's lines as money columns
+    for a record's details.
+- **A money column in a dropdown**: `DropdownColumnType` gains `"money"`: the item's figure with 2 places in the
+  person's number format (1,00,000.00 under lakh and crore), at the end of its column (its heading too), in even digits,
+  and empty for a missing one. Its track is `auto` unless it has a `width`. **`dropdownColumnAlign`** says where a
+  column's cells sit. A column dropdown's rows now take the list's gutters (`column-gap: normal` on the row's subgrid),
+  so every cell meets its heading's edges. Before, a row's own 8px gap set each cell a pixel past both sides of its
+  heading.
+- Proved by `test-number-helpers.mts` (SubscriberRenewalCheck's money cases and more, and the ladder),
+  `test-form-store.mts` (a computed input never in getValue, getChanges or problems, never a change; the presets),
+  `test-input-conditions.mts` and `test:types`. Also by nexus.template's `/demo/form` "Worked out from other inputs"
+  and `/demo/dropdown`'s Fee, with `form-figures.cjs` in both motion modes: 1,073.50 on open, every keystroke followed
+  (900 / 0 / 13 gives 1,017.00), Reset, a held Load blank and disabled then 904.00, a cleared price blank, a 12-digit
+  price's figure whole inside its box, the disabled look, and no netAmount sent; an `<output>` with no lock, stepper or Tab stop, as tall as Price with its edge in the
+  three designs; the "From the page" pair blank, then 800.00 | 904.00; the money column at 1,00,000.00 and
+  100,000.00, ending on its heading's edge; and in 7 themes, light and dark, at 1280x720 and 390x844, the figure at
+  7.54:1 or more with nothing past its box or the window.
+
+### A form asks before it saves, the full details in sections
+
+Card C-form-confirm (2026-11-07), the owner's second ask of the day: *"the misc counter and payment counter when click
+save show popup all full details then user do contirm then save"*, as 2026-06-20's "Confirm Counter Payment" did. 7
+exports, all from `nexus-shared`, and three additions to existing options. Two looks change without a line of the
+app's: a record's details whose columns name a `group` now show a heading over each run (below), and a press outside a
+popup that stays open through it no longer takes the focus.
+
+- **`SubmitFormProps.confirm`** (**`FormConfirmParams`**: `when`, `title`, `message`, `details`, `confirmLabel`,
+  `cancelLabel`, `size`), so `ApiForm`'s too, and **`CrudFormOptions.confirm`** for a CRUD's Add and Edit: a question
+  after every value has passed its checks and before the save starts. It is always a `question`, so its confirm button
+  has the focus and Enter saves. While it is open nothing else submits the form (Save, Enter, Ctrl+S, `form.submit()`),
+  Ctrl+S does not open the browser's Save page, and the form says no "Saving…". **Back to the form** (the default
+  `cancelLabel`), Esc and × send nothing and leave every value as it was, the focus back on what opened it; a click
+  outside leaves it open. **Confirm and save** (the default `confirmLabel`) goes on to the save as before. A rule here
+  that throws shows its message under the form and asks nothing. `when` limits it to some saves (the kinds that take
+  money). The question goes if the form leaves while it asks.
+  ```tsx
+  <ApiForm api={COUNTER_CREATE} transform={saveBody} confirm={{
+    when: values => ASKS_BEFORE_SAVING.includes(values.counterType),
+    title: "Save this payment?",
+    message: summary,
+    details: () => ({ row: line, columns: counterDetailColumns(line, "confirm"), currency }),
+    confirmLabel: "Confirm payment",
+    size: "xl",
+  }} />
+  ```
+- **What it shows is what is sent.** Each text and the details are handed the values and **`body`**, what will be sent:
+  an `ApiForm`'s `transform` runs once, before the question (a throw there shows under the form and asks nothing), and
+  that very body is sent after Confirm, never worked out again; a plain `SubmitForm`'s body is its values. Without
+  `confirm`, `ApiForm` sends as before.
+- **`details`** answers **`FormConfirmDetails`** (`row`, `columns`, `currency`; the row and columns may be the page's own
+  types) and is drawn by `CrudDetails`, in the normal text colour, under the muted line. The box is `lg` with details
+  (two fields to a line) and `sm` without, unless `size` says otherwise (`xl`: three to a line). Its body scrolls while
+  the buttons stay in view.
+- **`CrudDetails` draws `column.group`**: each run of neighbouring columns that name one group is a section under an
+  `h3` heading (`nx-crud-details__section`, `nx-crud-details__heading`, the small muted heading style of a dropdown's
+  groups), the heading nearer its fields than the section above it. Columns with no group draw as before, without a
+  heading; with no group anywhere the markup is exactly as before. So every details view gets it: the View popup, a
+  workspace's Details tab, a counter's preview, the question. **`crudDetailsRuns(columns)`** (**`CrudDetailsRun`**) is
+  the rule; a group named again further on starts a new run, as a table's band does.
+- **`formConfirmAsks(confirm, values)`** and **`formConfirmQuestion(confirm, values, body)`**
+  (**`FormConfirmQuestion`**) are the question's pure rules: whether to ask, each text settled, the defaults.
+- **The message box** (`messageBox.confirm`, `show`, `alert`, `prompt`) takes **`details`**: drawn after the message in
+  its own `.nx-message__details`, in the normal text colour (the message stays muted), scrolling with the body. Also
+  **`closeOnBackdrop`** (default: as `closable`; `false` keeps a box open through a click outside while Esc and × still
+  dismiss it) and **`signal`** (an abort dismisses the box). A box without them draws exactly as before.
+- **`Popup`**: a press on the backdrop of a popup that stays open through it (`closeOnBackdrop: false`: the question, a
+  CRUD's Add and Edit, a row's form, a spreadsheet import) leaves the focus where it was. It used to move to the
+  dialog, so after a stray click Enter no longer confirmed and a field lost its caret.
+- Styles: `Nexus.Crud.css` (`nx-crud-details__section`, `nx-crud-details__heading`), `Nexus.Popup.css`
+  (`nx-message__details`).
+- Proved by `test-form-confirm.mts` (the runs, `when`, the texts and the defaults) and `test:types` (`form-confirm.tsx`:
+  a page's own row type in the details, the mistakes refused). Also by nexus.template's `/demo/form` "Confirm before
+  saving" (an order: "Place this order?", the body in Order and Money sections, "Place order", `xl`, a transform that
+  can throw, a customer the demo server refuses), with `form-confirm.cjs` in both motion modes: Place order, Enter in a box
+  and Ctrl+S in a box each open one question with no call and no "Saving…"; a click where the form's button is, the
+  form's own submit, Ctrl+S (its default held) and a backdrop click while it asks change nothing and leave the focus on
+  Place order; Enter sends one call whose body is the figures shown; Esc, × and Back send nothing, keep every value and
+  give the focus back to the button or the box that opened it; a throw and a refusal show under the form and the next
+  save asks again; and in 7 themes, light and dark, at 1280x720 and 390x844, the details at 8.3:1 or more in the text
+  colour, the headings at 4.85:1 or more, three fields to a line at `xl` and one on a phone, nothing past the window,
+  and in windows too short for them the body scrolling with Place order still in view. `/demo/crud`'s guest workspace
+  shows its Details in Contact and Account sections (`crud-workspace.cjs`, in every theme and both sizes).
+
+### A few fields in a record's profile, left out of its Details tab
+
+Card C-profile-fields (2026-11-07), the owner's third ask of the day: *"in subscriber profile when open then show the
+expirations status like the how much will run when disconnect the status which displaying in the datatable"* - a
+subscriber's Expiry and Inactive under the status tags of its window. Additions only: 2 exports, both from
+`nexus-shared`, and one addition to an existing type. A profile without `fields` draws exactly as before.
+
+- **`CrudDetailsProfile.fields`** (the type takes the row now, `CrudDetailsProfile<TRow>`, defaulting as before): a
+  few of the record's fields under the profile's tags, each a label and a value, the value drawn as the table and the
+  details draw it (`TableCellValue`): its format in the person's settings (a date in their date format, read again when
+  they change it), an option's tone, the column's `tag` after it. A field is a column given whole or a key of the
+  details' `columns` (the table's, unless the details name their own); a key no column has is left out, and so is a
+  field with no value for the record (null, undefined, blank text, an empty list, NaN; `false` and `0` are values).
+  ```ts
+  profile: row => ({ title: row.fullName, tags: [...], fields: [EXPIRY_COLUMN, INACTIVE_COLUMN] })
+  ```
+- **The built-in Details tab leaves out every key `fields` names**, an empty one too, so a record's window never shows
+  a field twice and a page filters nothing by hand. Sections (`group`) stay as they were for the columns left.
+- **The look**: a `<dl class="nx-crud-profile__fields">`, a `div.nx-crud-profile__field` a pair (`dt.nx-crud-profile__label`,
+  `dd.nx-crud-profile__value`). Beside a wide popup's tabs it is a small grid in the middle of the 20rem column, a pair a
+  line on the grid's two tracks, labels in `--nx-text-muted` and values in `--nx-text` at `--nx-text-sm`; a long value
+  wraps inside the column and a tag that no longer fits goes under its value, at its start. Under 720px of popup width
+  (the one-row profile) the pairs follow the tags as one wrapped line - beside them when they all fit, else on the next
+  line - each pair wrapping as words do with its label kept with the start of its value.
+- **`crudProfileFields(fields, columns, row)`** (the fields a profile shows for a record) and
+  **`crudDetailsWithoutProfile(columns, fields)`** (the details' columns less the keys named; the same list when none
+  are) are the rules. `isCrudProfile` takes the row type too.
+- Styles: `Nexus.Crud.css`, beside the profile's.
+- Proved by `test-crud-profile-fields.mts` (37 checks: a column or a key, an unknown key, a key named twice, every kind of
+  empty value, a column's own `value` and a path, the keys taken out of the Details and the groups kept) and
+  `test:types` (`crud-profile.tsx`: a page's own row type, a column written in place with its tag typed from the row,
+  a column of another row's type refused). Also by nexus.template's `/demo/crud` "A guest's workspace" (the guest's next
+  stay, Arrives with how soon as a tag and Leaves, in the profile and not in the Details; Book a stay moves them), with
+  `crud-workspace.cjs` section L: the `<dl>` after the tags, the dates in the default format and again as DD/MM/YYYY
+  after a live change of the preference, no Arrives or Leaves in the Details, a long date (`dddd, MMMM DD, YYYY`) inside
+  the 20rem column with its tag under it, one wrapped line at 700px and 390px with each label beside its value, a stay
+  booked followed with one Update and one Detail, and a guest with no stay with no fields; then in 7 themes, light and
+  dark, at 1280x720 and 390x844, the labels muted, the values and the tag at AA, the tag's dot in `--nx-info`, the
+  date in two formats, nothing past the profile, its column or the window, and no Arrives or Leaves in the Details.
+
+### An input's width that follows a value
+
+Card C-span-when (2026-11-07), the owner's fourth ask of the day: *"if possible and easy: in the cash counter make:
+Bill date as col-12 when it put value and during the visible input time make it col-6."* - read as: Bill date takes
+the whole row while it is empty and half once a date is put, with the switch that counts from it beside it, so Bill
+number and what follows never move. Additions only: 2 exports, both from `nexus-shared`. An input without `spanWhen`
+draws exactly as before.
+
+- **`InputLayoutParams.spanWhen`** (`InputSpanWhen`: `when`, `span`; Form only): the input spans `span` columns while
+  every condition of `when` holds - `showWhen`'s conditions, one or a list, each on an input's value as it is now; the
+  input's own name follows its own typing - else its own `span` (a value or a getter).
+  ```ts
+  { type: EInputTypes.Date, name: "billDate", label: "Bill date", span: 6, spanWhen: { when: { name: "billDate", filled: false }, span: 12 } }
+  ```
+- Built on the `showWhen` machinery: `withInputConditions` gives such an input a live `span` getter and joins the names
+  its conditions read into `dependsOn`, so its cell takes the new width on the key that makes or unmakes the value,
+  without mounting the input again: the text, the caret, the focus and an open calendar stay. Form's grid and
+  `Nexus.Form.css` are unchanged (a cell reads `span` each time it draws), so a narrow form (under 34rem) still gives
+  every input the whole row. **`spanFor(spanWhen, read, own)`** is the pure rule.
+- The `dependsOn` docs now name `span` among the getters a followed change reads afresh: a `get span()` with
+  `dependsOn` already worked (nexus.builder.web's class shape uses one); `spanWhen` says it without a getter.
+- Like `showWhen`, it is Form's only: a tabular or group form's rows ignore it.
+- Proved by `test-input-conditions.mts` (21 new checks: the rule both ways, a list, an empty list, the live span both
+  ways, a condition on the input's own name, its own `span` getter kept and giving way, with `showWhen` on the same
+  input, `dependsOn` joined once each, the page's params unchanged; in a form store, the cell drawn again on its own
+  typing with the same stamp, and a load) and `test:types` (`input-types.ts`: one condition or a list; refused without
+  `span`, without `when`, a condition with no name, a span as text). Also by nexus.template's `/demo/form` "Inputs
+  shown by another input", whose form now ends with a Bill section - Bill date, the switch "Count the dates from the bill
+  date" (shown while the date is filled) and Bill number - with `label-when.cjs` section S in both motion modes: on every
+  key the width follows the value and the focus and caret stay at the end of the same box, the calendar the click opened
+  stays open at the box's start, the switch's top is the date's with its knob level with the date's box, Bill number
+  never moves (typing, a key that unmakes the date, ×, a calendar pick), Tab goes from the date to the switch and then
+  Bill number; every density and input design; then 7 themes, light and dark, at 1280x720 and, where every cell is the
+  whole row, 390x844. Seen red with the rule broken (42 lines) and with a remount on a width change (33 lines).
+
+### Record cards that fit what was built on them
+
+Card C-record-cards-fit (2026-11-07): the nine gaps the two Accounts agents met while building nexus.accounts'
+dashboard on `RecordCards`, and the seven findings of the round-2 review in this package. Additions only: 6 exports, all
+from `nexus-shared` (`keepsTyping`, `recordActionName`, `recordBusyKeys`, `recordHeldLines`, `RECORD_STILL_READ`, the
+type `RecordGoToOptions`), and new optional params. **Three looks change with no app change**: a card's heading buttons
+go under its title where the card is narrow, a window popup's description wraps under its title on a phone, and a
+picture's hidden buttons take no press. **One behaviour changes**: a password or a one-time code typed is no longer
+asked about before it is dropped (below).
+
+- **A step's form** (`RecordStepContext.form`): every step is handed its `FormStore`, and `inputs` as a function gets
+  it, so an input's label, `hidden` or options can follow another input as typed (getters with `dependsOn`) - the
+  region levels of an address, named after the place picked above. nexus.accounts' address card can now be a flow.
+  ```tsx
+  add: { title: "Add an address", inputs: ({ form }) => addressInputs(form), submit: ACCOUNT_API.addAddress }
+  ```
+- **A step's own rule**, `RecordStepParams.validate(values, context)`, the form's `validate` (messages by input, or one
+  for the step), asked before anything is sent: a new password and its confirmation that differ.
+- **A step shown fresh**: `goTo(step, { fresh: true })`, and `RecordStepParams.fresh` for a step shown fresh each time
+  it is reached again (by `next` or `goTo`): its form is dropped and it opens on its values, so an old code or
+  password is gone.
+- **Nothing worth keeping** (`FormStore.isWorthKeeping()`, `keepsTyping(params)`): a value typed in a `Password` or
+  `Code` input is a change (Save and the status line say so) but never asked about - not by Cancel or a popup's close
+  (`confirmDiscard`), not by a link inside the app, not by `beforeunload` or `confirmPageLeave`. Any other change is
+  asked about as before. A record step with `confirmCancel: false` also leaves the page's guards.
+- **A heading's buttons while the data is read**: a card's (and the hero's) action `hidden` and `held`, typed on the
+  data, are asked only once it is read; until then the button is held, saying "Still being read." (the hero's were
+  hidden), or not drawn yet with the new `loading: "hidden"`. `recordActionState(action, null, ...)` is that rule.
+- **Heading buttons named with their card** to a screen reader ("Edit: Personal details"), as an item's icons are with
+  their item (`recordActionName`); the visible label is unchanged and starts the name.
+- **Nothing moves when the records come**: a held list row is a read row's height (its name's line and lines under it
+  as line boxes; a row's title is at least a mark's height, with marks or without), a content card's two held lines
+  are two lines of text, a count in a title no longer makes its line a pixel taller, and the new
+  `RecordFieldParams.heldLines` and `RecordItemsCardParams.heldRowLines` hold as many lines as a value or a row
+  usually takes (`heldRows` already held as many rows). Text that wraps by the width can still grow its card.
+- **A narrow card's buttons under its title**: the heading's text keeps 12rem (8rem for a title alone) beside its
+  buttons, else the buttons go on a line under it, at its start - no title squeezed to a word a line on a phone.
+- **A window popup's description on a phone** (600px and under) takes the lines under the title it needs, in full; the
+  icon and the window buttons keep the bar's first line. Wider, it is the one low bar as before.
+- Review fixes: a page's popups close with it and are keyed by the page that opened them, so a page drawn afresh never
+  brings back a popup bound to the old data (whose Save sent the stale record); an Edit with a Tabular or Group input
+  opens on its rows (`recordOpenedValues`), so its Save no longer wipes them; a card keeps a list of its calls on their
+  way (`recordBusyKeys`), so one that ends first never frees a row whose own call still runs; the once-only scroll to
+  a linked card (`#emails`) is skipped once the person has scrolled, touched, pressed a key or 5 seconds have gone, or
+  when the card is already in view; a picture's hidden buttons take no press (`pointer-events: none` until shown) and
+  are always shown where any pointer is coarse (a laptop's touch screen); a list that could not be read in the pictures
+  window has the window's padding; the document list's Upload in a full one-file category is held with its reason
+  ("This keeps one file: delete it first.").
+- Proved by `test-record-cards.mts` (151 checks: rows opened, the rules not asked while read, `loading`, busy keys,
+  held lines), `test-form-store.mts` (worth keeping), `test:types` (`record-cards.tsx`), and nexus.template's
+  `/admin/profile`, whose demo now has an address's lines named after what it is, Change password with its
+  confirmation, Send a reset link, Back on the code step, and held rows as many as the lists: `record-cards.cjs` section
+  K and new lines in A (every card's place and height through the load at 1280, every heading button's name), and
+  `pictures.cjs` K7. Seen red with the busy list, the popups' closing, and the row's height undone.
+
+### Also in 4.0.0: the changes prepared as 3.3.0
+
+Prepared on 2026-10-22 with asks 1-6 of the template's auth follow-ups and everything unreleased since `3.2.0`, with the
+solid fills' hover added on 2026-10-26, and never published. On their own they are new features with no code break;
+the sections below say what each added. What can move for an app:
+
+- **A list's Add button reads "Add New"** on every `Crud`, whatever its subject; the form it opens keeps its subject.
+- **Menus** fade a switched-off item's icon and label, not its reason, and wrap a long second line.
+- **A table's spreadsheet menu** offers only what the app's permissions allow; the template and the export stop at a
+  failed settings call, with that call's one toast.
+- **A Nexus save is not read back**, except a new record with a `crudColumns.dbJoin` column given no `from`.
+- **An Edit saved while the CRUD shows another list** goes where its band says, no longer into that list.
+- **A `crudPicker` with a `valueKey` other than `id` and no `find`** no longer posts its values to `findListing`.
+- **A solid fill under the pointer is darker than at rest in every theme**, light and dark (it turned lighter in a dark
+  theme): a primary or danger `Button`, and so `SplitButton`, `FormButtons` and every solid button built on them, the
+  chat's unread button and Send, and the popup's close button while it is pressed. **An app's own theme that puts a
+  dark label on a light solid fill** loses contrast under the pointer now: give its fills a light label at 4.6:1 or
+  more, as the README's example does.
+- **Nord's dark solid fills are a little lighter and carry white**: `--nx-primary-solid` `#557b86` (was `#4b717c`),
+  `--nx-danger-solid` `#99686d` (was `#8e5e63`), and `--nx-primary-text` and `--nx-danger-text` `#ffffff` (were snow,
+  `#eceff4`), on every button, check, selected day and tab indicator in Nord's dark mode.
+
+### A solid fill under the pointer keeps its label readable
+
+2026-10-26, the owner's decision of 2026-10-22: "fix it everywhere". `--nx-primary-hover` and `--nx-danger-hover` mixed
+the fill 16% toward `--nx-text`. That darkened it in light mode, but lightened it in dark mode, where the fill is already
+as light as its white label allows, so the label under the pointer fell from 4.6:1 to 3.48-3.69:1 in all seven dark
+themes. Both are now the fill with **12% black** mixed in (OKLab), in every theme and in both modes:
+
+- the label under the pointer, and pressed, measures **6.06:1 or more** in a dark theme and **7.09:1 or more** in a light
+  one (it was 5.94:1 or more there); at rest and with the keyboard's focus nothing changed (4.60:1 or more);
+- the step from rest is the same size in every theme, an OKLab difference of **5.8 to 7.4** (x100). Light mode's was
+  1.9 to 6.0, so a light theme's hover is a little darker than it was (Rosé Pine's, Nord's and Solarized's the most),
+  and now seen in every theme.
+
+Measured in a browser under a real mouse, the colours composited through a canvas, on every solid fill the packages
+hover: `Button` primary and danger, both halves of a `SplitButton`, `FormButtons`' danger submit, the chat's unread
+button and Send, and the popup's close button. The close button still turns `--nx-danger-solid` under the pointer;
+pressed, it takes `--nx-danger-hover`, so it now turns darker instead of lighter. Its minimise, maximise and restore
+buttons did not change. `npm run check:themes` reads the two lines from `Nexus.Tokens.css` and checks both: the label at
+4.5:1 or more, and a step of 5 or more. No export or constant changed. An app that used either token for something
+other than a solid fill's hover gets the darker colour in dark mode too.
+
+**The fill under the pointer keeps 2:1 on the panel**, as it does at rest. In a dark theme the darker step moves the
+fill toward the panel. In Nord's dark mode it reached 1.79:1 on `#2e3440`, under the 2:1 every solid fill keeps at rest:
+Nord's panel is lighter than other themes' and its label was snow (`#eceff4`), which left the fill no room to darken.
+Nord's dark fills now carry white, as five of the other six themes' do, and were set the way every dark fill was: the
+same hue and chroma, at the lightness where white reaches 4.6:1. They stand 2.71:1 off the panel at rest (were 2.35)
+and 2.04:1 under the pointer, and the label reads 4.60:1 at rest and 6.11:1 under the pointer. The other dark themes'
+fills keep 2.30:1 or more under the pointer. `check:themes` now holds every hovered fill to 2:1 on `--nx-surface`. A
+solid fill's label is light in every theme and both modes, because hover and pressed darken the fill: a dark label on
+a light fill reads at rest and loses contrast under the pointer.
+
+### A QR code, `QrCodeImage`
+
+2026-10-22, ask 4 of the template's two-step pages (`nexus.accounts`, whose authenticator setup drew its own). Added
+only.
+
+- **`QrCodeImage`** (`nexus-shared`; a server component can render it: nothing in it needs the browser): `value`,
+  `label` for screen readers, `level` (L, M, Q, H; M by default), `className` and `style` for where the page puts it.
+  One SVG path of black modules on a white square that holds the quiet zone, black on white in every theme and in
+  forced colours. New stylesheet `Nexus.QrCode.css`, class `nx-qr`: 9rem wide, a control's rounded corners - the look
+  of nexus.accounts' `.tp-auth__qr`, whose grid area stays the page's.
+- **`encodeQr(text, level)`** and **`qrPath(code, border)`** (`QrCode`, `QrLevel`): QR Code Model 2 written by hand,
+  byte mode (UTF-8), versions 1 to 40, levels L, M, Q and H, Reed-Solomon, the eight masks scored by the four penalty
+  rules. A text past version 40 throws, with how much the level holds. Plain erasable TypeScript, so Node runs it as it
+  is: `Project-Skills/Checks/qr-code-check.mjs` reads every code back with jsQR 1.4.0 (410 of 410 against this file),
+  and `npm run test:qr` checks its shape without a decoder.
+
+### A list beside the record picked in another, and a picker's own find
+
+2026-10-22, asks 5 and 6 of nexus.web's company users page. The owner picked "the places of the person picked beside
+the people", and decided that a person is given a place only once they have joined. Added only: no export removed and no
+exported constant changed. A table or CRUD that passes none of the new props is unchanged, but for the two fixes at the
+end, which any app can see.
+
+- **A picked row, `DataTable` `onPick`** (and `Crud` `onPick`): rows the user picks one of, for a page that shows the
+  picked one's records beside the table.
+  - A click on a row picks it; a double-click still opens it, and `openOnClick` gives way. The keyboard reaches the rows
+    through a radio button each, out of sight in the first column and named with the row: Tab to the picked one, and the
+    arrow keys move the pick.
+  - The picked row is tinted as a selected one is, a ring round it shows the radio's focus, and the rows are numbered
+    unless `numbered` is false.
+  - The pick lives in the store (**`TableState.picked`**, **`TableStore.pick`**, **`TableStoreOptions.onPickChange`**)
+    and follows the record: a search, a sort or another page keep it, an upsert hands the page its new copy, and it is
+    let go when the record is removed, is gone after a load, or another list starts over.
+  - New attributes `data-pick` and `data-picked` on a row, and the class `nx-table__pick`.
+- **A list narrowed to it, `Crud` `narrow`** (**`CrudNarrow`**: `picked`, `key`, `valueKey`, `labelKey`, `addLock`,
+  `emptyMessage`), fed from the other list's `onPick`.
+  - Only the picked record's records show, under a caption naming it ("Places of: Ram Thapa"). The table's name for
+    screen readers says it too.
+  - A list paged in the browser keeps the whole list and shows the picked record's rows from it, so another pick costs
+    no request. A server's pages carry the value as a filter named `key`, and are kept per picked record.
+  - Add fixes the value in the new record, read-only with the lock and a note, in a form of its own per picked record
+    ("For Ram Thapa" in its title bar). Its box is named from the picked record, with no lookup.
+  - Add waits, saying why on a press, while nothing is picked or the picked record may take none: `addLock`, by default
+    the backend's rule (`CrudBackend.isPickable`), so a Nexus record pending (30-39), trashed or deleted takes none.
+  - A save lands in the list of the record it names and in no other, whichever record is picked when it is saved.
+    Joined names come from the picked record with no call (a `crudColumns.dbJoin` given `from`).
+  - New helpers **`crudNarrowing`** and **`crudInNarrowing`** (**`CrudNarrowing`**).
+- **`DataTable` `caption`**: a line inside the table's frame, over its bar, saying what its rows are. Beside another
+  table, the two frames still start level. New class `nx-table__caption`.
+- **`DataTable` `add`** takes `disabled` and `description`, as `TreeView`'s own button does. The button stays in the Tab
+  order, `aria-disabled`, and a press shows the description in a note under it; the description is its tooltip too. While
+  it waits, the spreadsheet's items stay in the options menu, without Bulk insert.
+- **`crudPicker` `find`**: where a value the kept list does not offer is looked up when `valueKey` is not `id` - an
+  endpoint POSTed such values, as `findListing` is the keys, whose answers are read by `valueKey` (a person's `userId`,
+  which their company row carries beside its own key); or a source of the page's own. Its answers are kept apart from
+  `findListing`'s, and `expireLookups` marks them old with the controller's own. **`joinSource(source, backend, key)`**
+  takes the field the answers are filed under.
+- **`lockInputs(inputs, locked, values, known)`** and **`CrudFormRequest.known`**: records the caller holds for the values
+  it fixes. A fixed dropdown whose value one of them holds gets it as a selected option.
+- A save names its joined columns from a dropdown's `selectedOptions` too, after what the user picked.
+
+What can move for an app on 3.2.0:
+
+- **An Edit saved while the CRUD shows another list** - its form minimized, the trash shown meanwhile - no longer goes into
+  that list's table, which then filed it in the cache under that list's name. It goes where its band says, and out of
+  the table when an edit took it out of the list on screen.
+- **A `crudPicker` whose `valueKey` is not `id`, with no `find`**, no longer posts its values to `findListing`, which
+  takes the records' keys and could answer none of them. The form names such a value from the record it holds
+  (`selectedOptions`), or shows it as not found, without the call.
+
+### A step that removes something
+
+2026-10-22, asks 1-3 of the template's two-step pages (`nexus.accounts`, `/account/security`): a step that removes an
+authenticator app, turns two-step off or makes new codes confirms with a password, and carried two stand-ins of its own.
+Added only: no export removed, no exported constant changed, and a form that passes none of the new props is unchanged.
+
+- **`FormButtons` `submitTone="danger"`** (and so `SubmitForm`, `ApiForm`): the submit button filled with
+  `--nx-danger-solid` and `--nx-danger-text`, the `Button` `danger` variant every solid danger fill uses, for a save
+  that removes something. Default `primary`, as before. New type **`FormSubmitTone`**.
+- **`downloadText(name, text, type)`** (`nexus-shared/client`): the file a table's CSV export hands over, for any text
+  made in the browser - a Blob behind a link that is clicked and taken out, its address let go ten seconds later, the
+  text after a byte order mark so Excel and Windows editors read UTF-8.
+- **`SubmitForm` `aria-describedby`** (and so `ApiForm`): passed to the `<form>` beside `aria-label` and
+  `aria-labelledby`, so a step that puts the focus straight into its password box can point at the line saying what
+  goes.
+
+### A record nobody may change here, and a switched-off item's reason readable
+
+2026-10-12, for the Builder's locked system models (the auth tables a person may only read). Added only: no export
+removed, no exported constant changed, and a `Crud` without the new prop behaves as before.
+
+- **`Crud` `rowLock`** (`(row) => string | null | undefined`): why a record may not be changed here. Its Edit, Flag,
+  Move to trash, Recover, Delete permanently and Move back to trash are listed **switched off** with that sentence under
+  each (none on the row as an icon), its details offer no Edit, the handle's `edit(row)` opens its details instead, and
+  a selection holding it has the mass actions that change records switched off. View, History, Pin and Favourite stay.
+  It fills the gap pages worked around with row actions of their own ("`Crud` cannot switch a built-in action off for
+  one row"); a page's own `rowActions` are still the page's to switch off.
+- **Menus** (`Nexus.Menu.css`): a switched-off item fades its icon, check, label and shortcut to half, no longer the
+  whole item, so its second line (why it is off) is read at full strength: at half it measured 2.0 to 3.1:1 in every
+  theme. `.nx-menu` sets `white-space: normal`, so a row's menu inside a table's actions cell (which does not wrap)
+  wraps its items' second lines instead of cutting them. An app that undid either rule for its own menus can drop that.
+
+### A table's spreadsheet menu asks the permissions
+
+A review of 2026-10-10 found an Admin offered a model's whole spreadsheet menu on nexus.web, every item of it refused
+by the backend (the sheets are SuperAdmin's). No export or constant changed. What can move for an app on 3.2.0:
+
+- **`DataTable` `excel`** (and so `Crud` `table={{ excel }}`): each item is offered only when the app's permissions
+  (`canCall`) allow every endpoint it calls - Download template the settings and the template, Import from a
+  spreadsheet and Bulk insert the settings, Verify and Import, Export to Excel the settings and the export - and the
+  menu follows a change of rights. An app with no permissions registered allows everything, so it sees no change; one
+  with `NexusPermissions` now needs its users' access actions to hold the `{Model}/Excel/...` actions for the menu to show.
+- **`downloadExcelTemplate` and `exportExcel`** stop at a failed settings call and answer it (`ok: false`, its status
+  and message): the person sees that call's one toast. Before, the template went on to a second refused call and a
+  second toast, and the export went on without knowing its row limit.
+
+### The list's Add button says "Add New"
+
+The owner, 2026-10-10: *"the CRUD has Add Region, Add Country and ... I want just fixed name Add New ... no dynamic"*.
+A `Crud`'s Add button above its list reads **Add New** on every page, whatever its `subject`; it was `Add <subject>`.
+The form it opens keeps its subject in the title and on its submit button ("Add region"), and Edit still says Save.
+No export or constant changed. An app's test that finds the list's button by its old name ("Add region") finds
+nothing now; one that finds the form's submit button is unaffected.
+
+### A tree that fills
+
+The owner, 2026-10-10, on nexus.web's administrative region tree: *"make full height here similar datatable both side
+panel, make sure responsive"*. Added only; a tree without the new prop is unchanged.
+
+- **`TreeView` `fill`**: the tree takes the height it is given, as `DataTable` `fill` does - the toolbar on top, the
+  rows scrolling inside under it - and `height` and `maxHeight` are ignored while it is on. New class
+  `nx-tree-field--fill` on the field. Give it a cell with a height: a side of nexus-admin's `AdminSplit` on an
+  `AdminPage` with `fill` (both new in nexus-admin), or a parent of your own.
+
+### CRUD inside a tree, and changes written into a tree's kept pages
+
+The owner, 2026-10-10, on the same page: *"allow CRUD ... inside the treeview"*. Added only: no export removed, no
+exported constant changed, and a page that passes none of the new params behaves as before - with one call fewer where
+a picker's saved value is in the list it keeps (see `crudPicker` below).
+
+- **`CrudTree`** (`nexus-shared/client`): a controller's records as a lazy tree with Add New (under a row, or from the
+  toolbar), Edit, Move to trash, Recover, Delete permanently, Move back to trash and History - through the **same**
+  Add/Edit popup and calls `Crud` uses. Row icons for Add New, Edit and Move to trash (Insert, F2 and Delete on a
+  focused row, all in its context menu); the picked record's fields and buttons go to a panel the page draws
+  (`details`). Every change is written into the tree and the pages it keeps: a record added is placed where its
+  siblings' order puts it, an edit is written in place or moved to its new parent, one in the trash leaves, and the
+  parents' counts and chevrons follow. A Create still reads its record back once (as `Crud` does), and an edit that
+  moved a record reads it once for the names joined from its new parent. New class `nx-crud-tree__actions`.
+- **`CrudTreePlacement`** (`cacheKey`, `rules`, `itemOf`, `parentOf`, `recordOf`, `childValues`): where a controller's
+  records sit in a tree, given to `CrudTree` and to **`Crud` `trees`** - a data table on another page then writes its
+  changes into that tree's kept pages too (an import drops them instead). `crudTreeChanges` turns a `CrudChange` into
+  tree changes; **`CrudChange.before`** carries the records as they were.
+- **Changes into a tree's kept pages**: `writeTreeChanges(cacheKey, changes, rules)` patches `treePages`
+  (`patchTreePages`) and every tree on screen with that `cacheKey` (`subscribeTreeChanges`); `TreeItemChange`
+  (`put` / `remove`) and `TreeChangeRules` (`valueKey`, `hasChildrenKey`, `compare`). `TreeStore.placeItem` and
+  `removeItem` keep a lazy parent's `loaded`/`total` and its own count right, so the next page skips the right number.
+- **`TreeView`**: `rowActions` (`TreeRowAction`: `TableRowAction` and a `shortcut` of Insert, F2 or Delete), `add` (a
+  toolbar button of the page's own), and on the handle `apply(changes, rules)`, `getItem(value)`, and a `reveal` that
+  waits for an item still loading. Focus follows a row that leaves or moves, released before the row leaves the page.
+- `RequestCache.entries(prefix)` and `set(key, value, at)` (a value written over a kept one keeps its age);
+  `TableJoins.remember(source, records)` and `peekList(name)`.
+- **`crudPicker`'s `resolveOptions` names a saved value from the list it keeps** before asking `findListing`, so a form
+  opened with a value the list offers (an Edit, an Add under a tree's country) makes no lookup. A value the list does not
+  offer - a parent since trashed - is still looked up and shown tagged.
+- `Crud`'s form popup, its call for an action on one record and its action words now come from one internal module
+  shared with `CrudTree` (`Components/Forms/CrudActions.tsx`): no change to what `Crud` shows or sends.
+
+### A tree that fixes where a record sits
+
+The owner, 2026-10-10, on the same tree: *"I have select the row to add, auto add inside this. Not allow to switch
+parent ... both should be disabled, not allow to change those values."* Added only: no export removed, no exported
+constant changed, and a tree whose placement names no `placeKeys` behaves as before - except that a `CrudTree` now
+selects the row it shows (below).
+
+- **`CrudTreePlacement.placeKeys`**: the fields that say where a record sits (its parent, its country). Given, `CrudTree`
+  fixes them in every form it opens - an Add inside a row takes them from `childValues` (a field it leaves out is fixed
+  empty), an Edit keeps the record's own - and every Add goes inside a row: the row's +, Insert, the context menu, the
+  panel's Add New, `handle.create(parent)`, and the toolbar's Add New, which now adds inside the selected row - the one
+  the panel shows - and, while there is none (or the selected record is in the trash), says why on a press (a click, a
+  tap, Enter); it used to open with nothing filled. A record then moves only where those fields are offered, such as a
+  data table's form. Fixed is read-only, the design's "cannot change" look: the lock, and a note on any try ("Added
+  inside Bagmati: pick another row in the tree to add elsewhere.", "Its place cannot be changed in the tree."); the
+  values stay and are sent as before, and a form's own `onFieldChange` never rewrites them (**`lockedFieldChange`**).
+- **The selected row**: a click or Enter on a `CrudTree` row selects it - tinted, and staying so while focus, the arrow
+  keys and the chevrons move on - and a record's row shows that record in the panel, while a row that is no record (a
+  country above its regions) empties the panel and opens. So the toolbar's Add New and the panel's never disagree.
+- **`lockInputs(inputs, locked, values)`**: inputs fixed for one opening of a form (input name -> why), copied with their
+  own property descriptors so a getter param keeps working; a required input with no value stays free. The Add and
+  Edit popup `Crud` and `CrudTree` share (internal) takes them as `locked`. An Add with fixed inputs is a popup of its
+  own per set of fixed values (**`crudFormPlace`**, added to the popup's and the draft's keys) and says where in its
+  title bar ("Inside Bagmati"): an Add started inside one row never comes back inside another, and asking for an Add
+  replaces every untouched Add of the controller, so only forms with work in them wait on the dock. A record keeps **one**
+  Edit popup wherever it is asked for: with the same inputs fixed it comes back; with others (a tree's fixed form, a
+  data table's free one) an untouched one is replaced, and one with changes comes back as it is, with a note saying
+  why - an older form's save would undo what a newer one saved. Drafts stay one per set of fixed values, so a draft
+  written before a record moved is not brought back over its new place.
+- **`TreeView`**: `selectedValue` - the row the page picked, marked `aria-selected` and tinted (new class
+  `nx-tree__row--selected`); moving focus, a chevron, opening or closing a row leave it where it is. `add.disabled` with
+  `add.description`: the toolbar button stays in the Tab order (`aria-disabled`) and a press shows the description in a
+  note under it; the description is also its tooltip and what a screen reader hears after its name.
+- **`Button`** with `aria-disabled="true"` looks disabled, stays focusable, and draws a stronger ring through the dimming.
+- **The dock** shows a popup's `description` under its title (`DockedWindow.description`, new classes `nx-dock__text`
+  and `nx-dock__description`), in the bar's tooltip and in its buttons' names: two Edit forms, or two Adds, read apart.
+- A **read-only** field's placeholder is drawn in muted text, at least 4.5:1 on the read-only box (it was under 3:1 in
+  light themes), since it is all the field shows ("None: directly under the country").
+- The details panel's Add New says "Add New: inside {name}" in its tooltip (it said "under").
+
+### A save is never read back
+
+The owner, 2026-10-10: *"When I created a new item it calls a new API and gets details; this is not needed. We return the
+details during the creating time, so use this; the creationTime, recordStatus we will provide fake or just right now."*
+With the Nexus backend an Add is now one Create and an Edit one Update, on a data table and in a tree: the row shown is
+built from the answer, the form and what the page holds. This replaces the read backs described under "CRUD inside a
+tree" above (a Create read once, a move read once). Added only: no export removed, no exported constant changed. What
+can move for an app on 3.2.0:
+
+- **A `crudColumns.dbJoin` column without `from`** - the form 3.2.0 documented - still has its new record read back once
+  after an Add (`details`), as 3.2.0 read every Create with a payload answer back; it is now the only reason a Nexus save
+  reads anything. Give the column `from` (the field of the joined record's key) and the read goes.
+- `TableColumn.dbJoin` is set by every `crudColumns.dbJoin` column, its `from` optional.
+
+The changes:
+
+- **`CrudBackend.savedRow(action, record, before)`**: the fields only the server keeps, written as the backend writes
+  them. The default leaves the record as it is, and a CRUD still reads a record back once when its list cannot be told
+  from it (another app's backend). **`NexusCrudBackend`**: a new record lacking them is Active (`NEXUS_ACTIVE_STATUS`),
+  has no marks, was added now (`creationTime`, a UTC ISO string) and never changed; an edited one takes the status, the
+  marks and the time added from the record the page holds now (`before`) - over its form's copies, which a flag or a
+  mark made while the form was open has left behind - and was changed now.
+- **Joined names with no call**: `crudColumns.dbJoin` takes `from`, the field holding the joined record's key (kept as
+  **`TableColumn.dbJoin`**), and after a save **`crudJoinedNames`** writes each such column again. A key kept keeps its
+  name and status, an emptied one empties both, and a new or changed one takes the name (the dropdown's `labelKey`) and
+  the `recordStatus` of the record behind it. That record is the one the user picked (the form now keeps a dropdown's
+  item: **`FormStore.pickedItem(name)`**, `input(name, value, stamp, item)`), else one the page holds (**`Dropdown`
+  `peekOption(key)`**: `crudPicker` gives one from its kept list and the FindListing cache, and **`peekFound(findListing,
+  key)`** serves a picker of a page's own), else, in a tree, the parent the record sits under, else one the page held
+  and has marked old (`peekOption(key, true)`). A key nothing names is left unnamed - an edit drops the old key's name -
+  and **`crudJoinsMissing`** then has the record read back once. A data table's Edit that moves a record now shows the
+  new parent's name; it showed the old one until the page was read again.
+- **Counts**: with `trees`, **`crudSavedCount`** gives a new record its placement's count (0) and an edited one the count
+  the page holds now (a child added since its form opened counts), and **`crudParentCounts`** moves the counts on the
+  parents' own rows that a data table holds - one more under the new parent, one fewer under the old - on a create, a
+  move, the trash and back, as the tree's parents already did; each parent row once, however many placements the page
+  gives. Both write what `CrudTreePlacement.recordOf` gives over the row, so `recordOf` carries the item's count back.
+- **In a tree**, a record added under a parent never opened is counted there and shown in the panel; the parent stays
+  closed, since opening it would read its page.
+- `Dropdown` `peekOption` on its own: a value the page already holds is named from the first draw, with no
+  `resolveOptions` call - while it is fresh: a record marked old since (a save on its controller, a Reload) is asked for
+  again, so the box shows it as it is now. **`TableJoins.peekFresh(name, key)`**, and `peekFound`'s `aged`.
+
+### New exports no section names
+
+The types and small helpers that come with the parts the sections describe, so that every new name is listed once:
+
+- `nexus-shared`: the file types `FileOwner`, `FileCopy`, `StoredFile`, `FileUpload`, `FileCallOptions`,
+  `PictureType`, `PICTURE_TYPES`, `isPictureType`, `ImageViewerItem`, `PictureParams`; the file helpers `fileKindName`,
+  `fileOwnerKey`, `acceptOf`, `readStoredFile`, `readOwnerFiles`, `FileApiClient`, `NexusDriveAdapterOptions`,
+  `PrimariesReader`, `PrimaryPicturesOptions`; `QrCodeImageProps`, `MoneyFormatOptions`, `CrudJoinedRecord`,
+  `NarrowPickWords`, `CrudNarrowPickerSource`, `CrudDetailsProfile`, `CrudDetailsTab`, `TableDbJoin`.
+- `nexus-shared/client`: `getFileAdapter`, `toastFileFailure`, `usePrimaryPicture`, the props types
+  `PictureInputProps`, `OwnerPictureProps`, `PictureGalleryProps`, `OpenPictureGalleryOptions`, `PictureColumnParams`,
+  and the tree CRUD's `CrudTreeProps`, `CrudTreeDetails`, `CrudTreeHandle`.
+
 ## 3.2.0
 
 **New features, no code break.** Every export of `3.1.0` is still exported (99 are new: 72 from `nexus-shared`, 16