@loadbare/app 0.25.0 → 0.27.0

package/docs/reference/names.md

@@ -14,10 +14,9 @@ that declares a query, a handler or a `crud` entry whose name begins with
 
 | Flag       | Default | Names                                     | Defined in                                          |
 | ---------- | ------- | ----------------------------------------- | --------------------------------------------------- |
-| `--src`    | `src`   | The application's own tree, scanned whole | [Running the builder](./builder.md#running-the-builder) |
-| `--out`    | `dist`  | Where the builder writes                  | [Running the builder](./builder.md#running-the-builder) |
-| `--watch`  | off     | Rebuild on change under `--src`           | [Running the builder](./builder.md#running-the-builder) |
-| `--minify` | off     | Minify `client.js` and `app.css`          | [Running the builder](./builder.md#running-the-builder) |
+| `--src`    | `src`   | The application's own tree, scanned whole | [Running the builder](./builder.md) |
+| `--out`    | `dist`  | Where the builder writes                  | [Running the builder](./builder.md) |
+| `--minify` | off     | Minify `client.js` and `app.css`          | [Running the builder](./builder.md) |
 
 ## Reserved file names
 
@@ -66,7 +65,7 @@ A widget package declares these.  An application never does.
 
 ## Attributes
 
-The developer writes eighteen attributes in pages and the chrome, and the
+The developer writes ten attributes in pages and the chrome, and the
 builder refuses any other `lb-` attribute there.  `lb-exp-slot` and
 `lb-exp-template` are written for expansion, which removes them before the
 check.  The hub and the builder write the rest, as stamps, and script never
@@ -77,12 +76,10 @@ assigns one.
 | `lb-query`           | Developer       | [Landing](./data-binding.md#landing)                             |
 | `lb-column`          | Developer       | [Landing](./data-binding.md#landing)                             |
 | `lb-show`            | Developer       | [Conditional rendering](./data-binding.md#conditional-rendering) |
-| `lb-order`           | Developer       | [Order](./data-binding.md#order)                                 |
 | `lb-filter`          | Developer       | [Filters](./data-binding.md#filters)                             |
 | `lb-manual`          | Developer       | [Placing by hand](./data-binding.md#placing-by-hand)             |
 | `lb-group`           | Developer       | [Groups](./data-binding.md#groups)                               |
-| `lb-count`, `lb-sum`, `lb-avg`, `lb-min`, `lb-max` | Developer | [Aggregates](./data-binding.md#aggregates)       |
-| `lb-select`          | Developer       | [Selecting rows](./data-binding.md#selecting-rows)               |
+| `lb-aggregate`       | Developer       | [Aggregates](./data-binding.md#aggregates)                       |
 | `lb-request`         | Developer       | [Requests](./data-binding.md#requests)                           |
 | `lb-url-link`        | Developer       | [Links](./chrome.md#links)                                       |
 | `lb-url-parm`        | Developer       | [A link from a row](./chrome.md#a-link-from-a-row)               |
@@ -100,7 +97,6 @@ assigns one.
 | `lb-row-created`, `lb-row-changed`, `lb-row-moved`, `lb-row-requested` | Hub | [What happened to a row](./data-binding.md#what-happened-to-a-row) |
 | `lb-row-leaving`, `lb-group-leaving` | Hub | [What happened to a row](./data-binding.md#what-happened-to-a-row) |
 | `lb-row-editing`     | Hub             | [Editing a row in one form](./data-binding.md#editing-a-row-in-one-form) |
-| `lb-row-selected`    | Hub             | [Selecting rows](./data-binding.md#selecting-rows)               |
 | `lb-request-pending` | Hub             | [Request state](./data-binding.md#request-state)                 |
 | `lb-request-error`   | Hub             | [Request state](./data-binding.md#request-state)                 |
 | `lb-request-refused` | Hub             | [Refusals](./data-binding.md#refusals)                           |
@@ -116,9 +112,10 @@ them, and a page declares none.
 
 | Query        | Kind  | Key       | Columns                                                         | Defined in                            |
 | ------------ | ----- | --------- | --------------------------------------------------------------- | ------------------------------------- |
-| `lb-url`     | `row` | `lb-path` | `lb-path`, `lb-page-label`, `lb-page-unknown`, every query parm | [The URL](./chrome.md#the-url)        |
-| `lb-choices` | `row` | `lb-path` | `lb-path`, every choice                                         | [Choices](./data-binding.md#choices)  |
-| `lb-hub`     | `row` | `lb-path` | `lb-path`, `lb-load-state`, `lb-server-state`, `lb-error`, `lb-pending`, `lb-as-of` | [The hub's state](./chrome.md#the-hubs-state) |
+| `lb-url`     | `row` | `lb-path` | `lb-path`, `lb-page-label`, every query parm                    | [The URL](./chrome.md#the-url)        |
+| `lb-sort`     | `rows` | `query` | `query`, `order`                                                | [Sort and filters](./data-binding.md#sort-and-filters) |
+| `lb-filters`  | `rows` | `query` | `query`, every filter column                                    | [Sort and filters](./data-binding.md#sort-and-filters) |
+| `lb-hub-status` | `row` | `lb-path` | `lb-path`, `lb-load-state`, `lb-server-state`, `lb-error`, `lb-pending`, `lb-as-of` | [The hub's state](./chrome.md#the-hubs-state) |
 
 No query parm is reserved: a column of `lb-url` whose name begins with
 `lb-` is never a query parm.
@@ -176,7 +173,7 @@ accessor or field named `lb` and a capital.
 
 | Entry point                | Exports                                                          | Defined in                                     |
 | -------------------------- | ---------------------------------------------------------------- | ---------------------------------------------- |
-| `@loadbare/app/server`     | `row`, `rows`, `patch`, `url`, `choices`, `refusal`, `createHub`, and the types `Queries`, `Requests`, `HubContext`, `Hub` | [Page Files](./page-files.md), [The data channel](./server.md#the-data-channel) |
+| `@loadbare/app/server`     | `row`, `rows`, `patch`, `url`, `sort`, `filters`, `refusal`, `createHub`, and the types `Queries`, `Requests`, `HubContext`, `Hub` | [Page Files](./page-files.md), [The data channel](./server.md#the-data-channel) |
 | `@loadbare/app/express`    | `hubRoutes`                                                      | [The Express Server](./server.md)              |
 | `@loadbare/app/dev`        | `devServer`, `appServer`, `gate`, `devProxy`, `DOWN_MESSAGE`     | [The Dev Server](./dev-server.md)              |
 | `@loadbare/app/build`      | `buildApp`, `watchApp`                                           | [Assembling your own](./dev-server.md#assembling-your-own) |
@@ -207,12 +204,16 @@ imports them rather than writing a string.
 | `ATTR_GROUP_COLUMN`       | `lb-group-column`                       |
 | `ATTR_GROUP_VALUE`        | `lb-group-value`                        |
 | `LIVE_GROUP`              | `[lb-group-live]`, the selector for a group's element |
-| `ATTR_COUNT`, `ATTR_SUM`, `ATTR_AVG`, `ATTR_MIN`, `ATTR_MAX` | `lb-count`, `lb-sum`, `lb-avg`, `lb-min`, `lb-max` |
-| `AGGREGATES`              | All five aggregate attributes           |
+| `ATTR_AGGREGATE`          | `lb-aggregate`                          |
+| `AGGREGATE_COUNT`, `AGGREGATE_SUM`, `AGGREGATE_AVG`, `AGGREGATE_MIN`, `AGGREGATE_MAX` | `count`, `sum`, `avg`, `min`, `max` |
+| `AGGREGATES`              | All five aggregate functions            |
 | `ORDER_DESCENDING`        | `-`, written before a column in an order |
 | `COLUMN_TYPES`            | `number`, `boolean`, `text`             |
-| `CHOICES_QUERY`           | `lb-choices`                            |
-| `ATTR_ORDER`              | `lb-order`                              |
+| `SORT_QUERY`              | `lb-sort`                               |
+| `SORT_COLUMN_QUERY`       | `query`                                 |
+| `SORT_COLUMN_ORDER`       | `order`                                 |
+| `FILTERS_QUERY`           | `lb-filters`                            |
+| `FILTERS_COLUMN_QUERY`    | `query`                                 |
 | `ATTR_FILTER`             | `lb-filter`                             |
 | `ATTR_MANUAL`             | `lb-manual`                             |
 | `MANUAL_ORDER`, `MANUAL_FILTER` | `order`, `filter`: the sides `lb-manual` names |
@@ -236,13 +237,12 @@ imports them rather than writing a string.
 | `LB_COMMANDS`             | All four commands                       |
 | `LB_COMMAND_PREFIX`       | `--lb-`                                 |
 | `ATTR_ROW_EDITING`        | `lb-row-editing`                        |
-| `ATTR_SELECT`             | `lb-select`                             |
-| `ATTR_ROW_SELECTED`       | `lb-row-selected`                       |
 | `LB_RESERVED_PREFIX`      | `lb-`                                   |
 | `REQUEST_ROW_INSERT`      | `lb-row-insert`                         |
 | `REQUEST_ROW_UPDATE`      | `lb-row-update`                         |
 | `REQUEST_ROW_DELETE`      | `lb-row-delete`                         |
 | `LB_ROW_REQUESTS`         | All three request names                 |
+| `REQUEST_READ`            | `lb-read`, the hub's own read of a bound form's lists; markup never writes it |
 | `LB_METHODS`              | The four reserved methods               |
 | `BROWSER_LIFECYCLE`       | The browser callbacks the build refuses |
 | `KIND_ROW`                | `row`                                   |
@@ -250,8 +250,7 @@ imports them rather than writing a string.
 | `URL_QUERY`               | `lb-url`                                |
 | `URL_COLUMN_PATH`         | `lb-path`                               |
 | `URL_COLUMN_PAGE_LABEL`   | `lb-page-label`                         |
-| `URL_COLUMN_PAGE_UNKNOWN` | `lb-page-unknown`                       |
-| `HUB_QUERY`               | `lb-hub`                                |
+| `HUB_QUERY`               | `lb-hub-status`                         |
 | `HUB_COLUMN_LOAD_STATE`   | `lb-load-state`                         |
 | `HUB_COLUMN_SERVER_STATE` | `lb-server-state`                       |
 | `HUB_COLUMN_ERROR`        | `lb-error`                              |
@@ -268,7 +267,7 @@ imports them rather than writing a string.
 | `ATTR_EXP_TEMPLATE`       | `lb-exp-template`                       |
 | `ATTR_PAGE`               | `lb-page`                               |
 | `ATTR_PAGE_TITLE`         | `lb-page-title`                         |
-| `DEVELOPER_ATTRIBUTES`    | The eighteen attributes a developer writes |
+| `DEVELOPER_ATTRIBUTES`    | The ten attributes a developer writes |
 | `HUB_TAG_NAME`            | `lb-hub`                                |
 | `LB_ENDPOINT`             | `/lb`                                   |
 | `LB_REQUEST_TIMEOUT_MS`   | `10000`                                 |

package/docs/reference/page-files.md

@@ -152,8 +152,8 @@ optional:
 
 | Key           | Runs                                                   |
 |---------------|--------------------------------------------------------|
-| `onPageEnter` | Before the page's queries, when the page loads; may move the URL or restore choices |
-| `onChoices`   | Each time the user makes a choice                      |
+| `onPageEnter` | Before the page's queries, when the page loads; may move the URL or restore the user's order and filters |
+| `onChoices`   | Each time the user changes the order or a filter        |
 | `handlers`    | The page's declared requests, by request name          |
 | `crud`        | The requests Loadbare provides, by query name          |
 
@@ -165,14 +165,11 @@ name:
 | `name`   | The request name, from `lb-request`                      |
 | `query`  | The query the request is for                             |
 | `key`    | The key of the row the request is for                    |
-| `keys`   | The keys of the rows selected, in place of `key`         |
 | `rows`   | A form's nested rows, by query: each `key` and `values`  |
 | `values` | The gathered control values, by column                   |
 
 The hub sends `query`, `key` and `values` when it finds them; see
-[Gathering](./data-binding.md#gathering). It sends `keys` for a request that
-acts on the rows the user selected; see
-[Selecting rows](./data-binding.md#selecting-rows).
+[Gathering](./data-binding.md#gathering).
 
 ### onPageEnter
 
@@ -193,34 +190,41 @@ loads there in the same round trip, and that load does not follow
 `onPageEnter` again. A `url()` leading to the parms already in hand is
 ignored. See [Moving the URL](#moving-the-url).
 
-It may return `choices()`, alone or beside `url()`, to restore the user's
-[choices](./data-binding.md#choices) for the page:
+It may return `sort()` and `filters()`, alone or beside `url()`, to restore
+the user's [order and filters](./data-binding.md#sort-and-filters) for the
+page:
 
 ```ts
 // src/pages/directory.requests.ts
-import { choices, url, type Requests } from "@loadbare/app/server";
+import { sort, filters, url, type Requests } from "@loadbare/app/server";
 
 export const requests: Requests = {
   onPageEnter: async (ctx) => {
     const saved = await ctx.db.savedView("directory");
-    if (saved) return { ...url(saved.parms), ...choices(saved.choices) };
+    if (saved) {
+      return {
+        ...url(saved.parms),
+        ...sort(saved.order),
+        ...filters(saved.filters),
+      };
+    }
   },
-  onChoices: (ctx, chosen) => ctx.db.saveChoices("directory", chosen),
+  onChoices: (ctx, change) => ctx.db.saveChoices(change),
 };
 ```
 
-The page load answers `lb-choices` first, so the rows land by the choices.
-When `url()` moves the page, the choices arrive with the load at the new
-URL. `choices()`, like `url()`, takes columns whose values are strings, at
-least one of them; anything else is reported on the server console and
-ignored.
+The page load answers `lb-sort` and `lb-filters` first, so the rows land by
+the order and the filters. When `url()` moves the page, the choices arrive
+with the load at the new URL. `sort()` and `filters()`, like `url()`, take
+columns whose values are strings, at least one of them; anything else is
+reported on the server console and ignored.
 
 ### onChoices
 
-`onChoices` runs each time the user makes a choice, with every choice made
-on the page, by column, as strings. It is how an application keeps them for
-`onPageEnter` to restore, and answers nothing, by convention. Whatever it
-returns lands. A page without it is not told.
+`onChoices` runs each time the user changes the order or a filter, with the
+query and its new `sort` or `filters`, as strings. It is how an application
+keeps them for `onPageEnter` to restore, and answers nothing, by
+convention. Whatever it returns lands. A page without it is not told.
 
 ### handlers
 
@@ -264,12 +268,6 @@ are one vocabulary:
 | `lb-row-update` | `rowUpdate` | `query`, `key`, `values`, and `rows` from a form |
 | `lb-row-delete` | `rowDelete` | `query`, `key`   |
 
-An `lb-row-update` or `lb-row-delete` carrying `keys` runs `rowUpdate` or
-`rowDelete` once for each key, with that key, so a handler written for one
-row serves several. The patches the runs return are laid together, and the
-refresh set runs once. A `url()` returned for one of several rows is
-reported and ignored. A declared request receives `keys` as it is.
-
 `rows` holds the rows of a query nested in the form the request came from,
 by query name, each with its `key` and the `values` of its own controls; see
 [A form over a set of rows](./data-binding.md#a-form-over-a-set-of-rows).

package/docs/reference/server.md

@@ -199,7 +199,6 @@ interface HubRequest {
   name: string;
   query?: string;
   key?: string;
-  keys?: string[];
   values?: Record<string, string>;
   rows?: Record<string, { key: string; values: Record<string, string> }[]>;
 }
@@ -229,9 +228,9 @@ in `drop` are removed, and every other row is left alone. A `rows` item on
 the answer that loads the page also carries the query's declared `order`
 and `types`, which the hub keeps for every answer after it.
 
-A choice is sent as `lb-row-update` for `lb-choices`, keyed by the path,
-with every choice made on the page as `values`; see
-[Choices](./data-binding.md#choices).
+A sort or a filter is sent as `lb-row-update` for `lb-sort` or `lb-filters`,
+keyed by the query's name, with the new order or filter as `values`; see
+[Sort and filters](./data-binding.md#sort-and-filters).
 
 `createHub(pages)` builds the `Hub`, which has two calls, both answering
 with response items: `dataForPage(page, ctx, options)` for a page load, and

package/docs/roadmap.md

@@ -148,8 +148,8 @@ breaks nothing.
 
 The chrome belongs to no page, so the builder refuses an application query
 named there, and a custom element in the chrome cannot show application
-data.  `lb-url` and `lb-choices` show the pattern from the framework side,
-and an application has no equivalent.
+data.  `lb-url`, `lb-sort` and `lb-filters` show the pattern from the
+framework side, and an application has no equivalent.
 
 A chrome-level query set on `createHub` would close this, and it is additive.
 It takes its place in the [options on `createHub`](#options-on-createhub).

package/docs/testing.md

@@ -172,8 +172,8 @@ watch, and surviving a failed build.
   that refreshes its own `rows` query are refused
 - an update or delete for several rows runs once per key, lays the patches
   together, and refreshes once
-- `onPageEnter` may return `url()` or `choices()`, and `onChoices` hears
-  every choice the user makes
+- `onPageEnter` may return `url()`, `sort()` or `filters()`, and
+  `onChoices` hears every order and filter the user makes
 - a refusal carries a message, columns or both, and passes through the
   engine untouched
 
@@ -276,8 +276,9 @@ What the hub is tested for here:
   deadline, under mocked timers, and fails the way any round trip fails
 - a successful insert gathered from a form resets the form, unless the
   answer landed the new row on it
-- a path with no page reports, lands `lb-page-unknown`, and opens the
-  `lb-url-unknown` dialog; two pages for one stub report and take the first
+- a path naming a page that does not exist reports, lands `lb-page-label`
+  as null, and opens the `lb-url-unknown` dialog; two pages for one stub
+  report and take the first
 - `lb-url` lands with the path, the page's `lb-page-title` or stub as
   `lb-page-label`, and a column per query parm, and sets the document title
 - `lb-url-link` pushes state and swaps the page on a plain primary click,
@@ -296,8 +297,6 @@ What the hub is tested for here:
   queries land
 - a form pointed at a row by `commandfor` fills from the row the hub holds,
   and a row not yet entered sends no update or delete
-- ticked `lb-select` rows travel as `keys`, and the selection clears once
-  the request succeeds
 - a refusal lands its message on the element that committed and on each
   control it names
 - `lb-request-done` reaches the element that committed and its ancestors

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@loadbare/app",
   "description": "High performance web app framework for server-bound applications",
-  "version": "0.25.0",
+  "version": "0.27.0",
   "type": "module",
   "files": [
     "dist",

package/skills/loadbare-app/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: loadbare-app
-description: Build server-bound web applications with Loadbare/app. Covers the file conventions the builder finds by name (`chrome.html`, `*.page.html`, `*.queries.ts`, `*.requests.ts`, `imports.ts`, `<tag>.html`, `<tag>.browser.ts`); the `lb-*` attribute vocabulary that lands query rows on HTML and issues requests (`lb-query`, `lb-column`, `lb-show`, `lb-request`); queries declared with `row(key, run)` and `rows(key, run)`; the URL as the hub's own query `lb-url`, with `lb-url-link`, `lb-url-parm`, `lb-url-push` and `lb-url-unknown`; the user's order and filters as the hub's query `lb-choices`, read by `lb-order` and `lb-filter`; whether the page loaded and the server answers as the hub's query `lb-hub`; one form pointed at a row by the `--lb-edit`, `--lb-new` and `--lb-release` commands; rows that hold still under `lb-manual` and are placed again with `--lb-place`; build-time expansion with `exp-*` parameters, `lb-exp-slot` and `lb-exp-template`; custom elements as form-associated controls and row hosts; the Express wiring with `hubRoutes`; and the `@loadbare/widgets` library. Use whenever a task involves `@loadbare/app`, `@loadbare/widgets`, `loadbare-app-build`, an `lb-` attribute, or a page, query, request or custom element file in a Loadbare application. The model is not React, htmx or REST, and cannot be inferred from them.
+description: Build server-bound web applications with Loadbare/app. Covers the file conventions the builder finds by name (`chrome.html`, `*.page.html`, `*.queries.ts`, `*.requests.ts`, `imports.ts`, `<tag>.html`, `<tag>.browser.ts`); the `lb-*` attribute vocabulary that lands query rows on HTML and issues requests (`lb-query`, `lb-column`, `lb-show`, `lb-request`); queries declared with `row(key, run)` and `rows(key, run)`; the URL as the hub's own query `lb-url`, with `lb-url-link`, `lb-url-parm`, `lb-url-push` and `lb-url-unknown`; the user's order and filters as the hub's queries `lb-sort` and `lb-filters`, read by `lb-filter`; whether the page loaded and the server answers as the hub's query `lb-hub-status`; one form pointed at a row by the `--lb-edit`, `--lb-new` and `--lb-release` commands; rows that hold still under `lb-manual` and are placed again with `--lb-place`; build-time expansion with `exp-*` parameters, `lb-exp-slot` and `lb-exp-template`; custom elements as form-associated controls and row hosts; the Express wiring with `hubRoutes`; and the `@loadbare/widgets` library. Use whenever a task involves `@loadbare/app`, `@loadbare/widgets`, `loadbare-app-build`, an `lb-` attribute, or a page, query, request or custom element file in a Loadbare application. The model is not React, htmx or REST, and cannot be inferred from them.
 license: Apache-2.0
 metadata:
   package: "@loadbare/app"
@@ -75,7 +75,7 @@ server.ts
 The chrome carries `<lb-hub>` inside `<body>`, an empty `<main>` inside the
 hub, and `<script src="/client.js" defer>`.  Everything a user touches sits
 inside `<lb-hub>`.  The chrome belongs to no page, so it names only the
-hub's queries, `lb-url`, `lb-choices` and `lb-hub`, and sends no declared
+hub's queries, `lb-url`, `lb-sort`, `lb-filters` and `lb-hub-status`, and sends no declared
 request.
 
 A page is an HTML fragment that lands in `<main>`:
@@ -195,7 +195,10 @@ is added by a button with `commandfor` naming the nested list and
 the form's submit carries it as `{ key: "", values }`, the handler inserts
 each row with no key, and it leaves when the submit succeeds.  So a master
 and its details are one save, before or after the master is on record; never
-gate the details behind `lb-show` on the master being saved.  The form needs
+gate the details behind `lb-show` on the master being saved.  A form bound
+by Edit or New reads its nested lists again (`lb-read`) with the bound key
+as the parm named for its key column, so the details query reads that parm
+and follows the row the form is bound to; New sends it empty.  The form needs
 a submit.  A new outer
 row is filled from the nested query's last answer, whatever order they land
 in.
@@ -220,21 +223,19 @@ JSON number or is declared one: `types: { amount: "number" }` beside
 hold a place.
 
 **The user's order and filters are choices, not query parms.**  The hub
-serves a second query, `lb-choices`, keyed by `lb-path`, one column per
-choice, named by the application.  A control inside
-`lb-query="lb-choices"` with `lb-request="lb-row-update"` makes a choice.
-`lb-order="<choice>"` on the element carrying `lb-query` places its rows by
-the order that choice holds, in place of the server's while it is not
-empty.  `lb-filter="col, col"` there hides each row that does not pass the
-choice of the same name: `^=Amazon`, `>=2026-01-01 <=2026-03-31`, or plain
-text for contains.  A choice shows with no round trip, then the server's
-`onChoices(ctx, choices)` hears every choice, to keep them;
-`onPageEnter` returns `choices()` to restore them.  Choices hold until the
-page changes.  A filter that decides which rows the server sends is a query
-parm.
+serves them as two queries, `lb-sort` and `lb-filters`, one row per query
+keyed by the query's name.  `lb-sort` holds each query's order as the
+server resolved it; `lb-filters` holds each query's filter values.
+`lb-filter="col, col"` on the element carrying `lb-query` hides each row
+that does not pass its query's filter of the same name: `^=Amazon`,
+`>=2026-01-01 <=2026-03-31`, or plain text for contains.  The server's
+`onChoices(ctx, { query, sort, filters })` hears each change, to keep it;
+`onPageEnter` returns `sort()` and `filters()` to restore them.  Choices
+hold until the page changes.  A filter that decides which rows the server
+sends is a query parm.
 
 **A page that failed to load says so.**  The hub serves a third query,
-`lb-hub`, and stamps its columns on `<lb-hub>` too: `lb-load-state`
+`lb-hub-status`, and stamps its columns on `<lb-hub>` too: `lb-load-state`
 (`loading`, `loaded`, `failed`), `lb-server-state` (`reachable`, `failing`,
 `unreachable`), `lb-error` (`network`, `timeout` or the HTTP status),
 `lb-pending` and `lb-as-of`.  Show a server that is down from the chrome's
@@ -247,9 +248,10 @@ nested `<template>`, the next level or the row template; the nth breaks on
 the order's nth term, to any depth.  Contents land before the nested
 template, so put it inside the heading's element for a container and beside
 the heading for a heading row.  `<tbody>` and `<optgroup>` do not nest.  The
-heading is filled from the group's first row.  `lb-count`, `lb-sum="col"`,
-`lb-avg`, `lb-min` and `lb-max` total the rows showing in the nearest group,
-or in the whole list outside any.
+heading is filled from the group's first row.  `lb-aggregate` with `count`,
+`sum`, `avg`, `min` or `max`, and `lb-column` naming the column, totals the
+rows showing in the nearest group, or in the whole list outside any.
+`count` with no column counts the rows.
 
 **Animate with CSS.**  The hub stamps `lb-row-created`, `lb-row-changed`,
 `lb-row-moved` (its values changed and it now stands elsewhere), and
@@ -327,16 +329,6 @@ update or delete at all, silently.  So a control with
 `lb-request="lb-row-update"` saves on a row on record and only holds its
 value on a new one.  Never write script to stop such an update.
 
-**Select rows with `lb-select`, never with a column.**  An
-`<input type="checkbox" lb-select>` in a row template selects its row; the
-hub stamps `lb-row-selected`.  A request for that query naming no one row,
-such as a form outside the rows, carries the ticked rows as `keys`.
-`rowUpdate` and `rowDelete` then run once per key with no new code; a
-declared request gets `keys` itself.  With none ticked an update or delete
-is not sent.  Success clears the selection, and so does `lb-show` hiding a
-selector.  A selecting mode kept in the URL reaches the rows as a column the
-query computes from the parm.
-
 **Refuse with `refusal()`, never with a plain throw.**  `throw
 refusal("message")`, `throw refusal({ column: "message" })` or both, from
 `@loadbare/app/server`.  The whole-request message lands as the
@@ -394,8 +386,7 @@ the element sits.
 shows, a filter the server applies, a date range: each is a query parm,
 `/accounts?acct=23&from=2026-09-09`, so a reload, a bookmark or a mailed link
 shows the same thing.  The hub serves the query `lb-url`, of kind `row`,
-keyed by `lb-path`, with `lb-page-label`, `lb-page-unknown`, and one column
-per query parm.  A control inside `lb-query="lb-url"` carrying
+keyed by `lb-path`, with `lb-page-label` and one column per query parm.  A control inside `lb-query="lb-url"` carrying
 `lb-request="lb-row-update"` writes its parm; the hub replaces the history
 entry, or pushes one when the control carries `lb-url-push`, and reloads the
 page's queries with no request to the server.  A parm the URL repeats,
@@ -439,9 +430,9 @@ whole data channel.
 
 **The developer writes `lb-*` attributes in markup, and script never
 assigns them.**  The builder refuses any `lb-` attribute other than the
-eighteen in [Attributes](references/names.md#attributes): `lb-query`,
-`lb-column`, `lb-show`, `lb-order`, `lb-filter`, `lb-manual`, `lb-group`, `lb-count`,
-`lb-sum`, `lb-avg`, `lb-min`, `lb-max`, `lb-select`, `lb-request`,
+twelve in [Attributes](references/names.md#attributes): `lb-query`,
+`lb-column`, `lb-show`, `lb-filter`, `lb-manual`, `lb-group`,
+`lb-aggregate`, `lb-request`,
 `lb-url-link`, `lb-url-parm`, `lb-url-push` and `lb-url-unknown`.  `lb-exp-slot` and
 `lb-exp-template` are expansion's, and never reach the page.  Everything
 else with the prefix is a stamp the hub or the builder writes.
@@ -527,28 +518,44 @@ The application's own definition of a tag overrides a package's.
 Read these when the summary above does not settle the question.  They ship
 with the package, so no network is needed.
 
-- [`references/overview.md`](references/overview.md) — the map of the
-  reference, by part of the application.
+[`references/overview.md`](references/overview.md) is the map of the
+reference, in the groups below.
+
+The application shell:
+
+- [`references/chrome.md`](references/chrome.md) — the chrome, the URL as
+  the query `lb-url`, and the hub's state.
+- [`references/server.md`](references/server.md) — the Express server, the
+  request context, and where the database layer fits.
+
+Building the app:
+
+- [`references/builder.md`](references/builder.md) — the builder's options,
+  what it reads, where it looks, and what it writes.
+- [`references/css.md`](references/css.md) — how stylesheets are ordered, and
+  the stamps a stylesheet selects on.
+- [`references/dev-server.md`](references/dev-server.md) — `devServer` from
+  `@loadbare/app/dev`, and the parts to assemble another from.
+
+Application pages:
+
+- [`references/page-files.md`](references/page-files.md) — what page
+  files are, queries, `onPageEnter`, `onChoices`, handlers, `crud`, refresh
+  and patch, `url()`, `sort()` and `filters()`.
 - [`references/data-binding.md`](references/data-binding.md) — landing,
   gathering, requests, conditions and request state.  Start here for
   anything in a page.
-- [`references/page-files.md`](references/page-files.md) — what page
-  files are, queries, `onPageEnter`, `onChoices`, handlers, `crud`, refresh
-  and patch, `url()` and `choices()`.
+
+Custom elements:
+
 - [`references/custom-elements.md`](references/custom-elements.md) —
   expansion, parameters, slots, destinations, and custom element code and
   when it runs.
-- [`references/chrome.md`](references/chrome.md) — the chrome, and the URL
-  as the query `lb-url`.
-- [`references/server.md`](references/server.md) — the Express server and
-  the request context.
-- [`references/builder.md`](references/builder.md) — the builder's options,
-  what it reads, and where it looks.
-- [`references/dev-server.md`](references/dev-server.md) — `devServer` from
-  `@loadbare/app/dev`, and the parts to assemble another from.
-- [`references/css.md`](references/css.md) — how stylesheets are ordered.
 - [`references/widgets.md`](references/widgets.md) — the basic widget
   library as a package; each widget is in the loadbare-widgets skill.
+
+Names:
+
 - [`references/names.md`](references/names.md) — every name Loadbare
   owns, the constants, and the section defining each.  Check a name here
   before designing around something the other references do not mention.

package/skills/loadbare-app/references/chrome.md

@@ -101,7 +101,6 @@ server's row lands, so a chrome shows where the page is with no code:
 |-------------------|---------------------------------------------------------|
 | `lb-path`         | The path, such as `/members`. The row's key             |
 | `lb-page-label`   | The page's title, or its stub when it has none          |
-| `lb-page-unknown` | `true` when no page's stub matches the path             |
 | Any other name    | The query parm of that name, or empty when it is absent |
 
 The path names a page, never a resource: `/accounts/42` is not a way to
@@ -116,9 +115,9 @@ page file carries; see [page files](./page-files.md#the-page-title). The hub
 sets the document title to `lb-page-label` whenever it is not null, so the
 tab and the browser history show the page.
 
-`lb-url` is one of two queries a page may use that the server does not
-declare. The other is [`lb-choices`](./data-binding.md#choices). A page
-names either the same way, anywhere inside the hub.
+`lb-url` is one of the queries a page may use that the server does not
+declare. The others are `lb-sort`, `lb-filters` and `lb-hub-status`. A page
+names any the same way, anywhere inside the hub.
 
 ### Where focus starts
 
@@ -223,8 +222,8 @@ pushes one instead when the element carrying `lb-request` also carries
 The hub answers the request itself, with no round trip, then reloads the
 page's queries at the new URL. The page stays in place, and rows that come
 back keep their place. A request that leaves the URL as it was does
-nothing. `lb-page-label` and `lb-page-unknown` are the hub's, and a request
-never sets them.
+nothing. `lb-page-label` is the hub's, and a request
+never sets it.
 
 A request that gives `lb-path` a new value enters that page, pushes a
 history entry, and the new URL carries only the query parms the request
@@ -288,8 +287,8 @@ it; a per-session database role means an id outside the caller's reach
 finds nothing.
 
 An order or a filter the hub applies to rows the page already holds is not
-a query parm. It is a [choice](./data-binding.md#choices), which holds until
-the page changes.
+a query parm. It is a [sort or a filter](./data-binding.md#sort-and-filters),
+which holds until the page changes.
 
 The hub sends the query parms with every round trip, and the server hands
 them to `contextFor`; see [the Express server](./server.md#database-layer).
@@ -308,8 +307,7 @@ show the path:
 </dialog>
 ```
 
-When no page's stub matches the path, `lb-page-unknown` is `true`,
-`lb-page-label` is null, `<main>` keeps the page it had, the hub calls
+When the path names a page that does not exist, `lb-page-label` is null, `<main>` keeps the page it had, the hub calls
 `showModal()` on the dialog, and reports the path to the console. A chrome
 with no dialog shows nothing. `lb-url` lands before the page is looked up,
 so the dialog shows the path by naming it like any other element.

package/skills/loadbare-app/references/css.md

@@ -69,7 +69,6 @@ in the stamp, so the selector reads the number and not its text.  See
 | Select               | For                                             |
 |----------------------|-------------------------------------------------|
 | `[lb-row-live]`      | Every live row of a list                        |
-| `[lb-row-selected]`  | A row its `lb-select` checkbox ticks            |
 | `[lb-row-editing]`   | The row a pointed form is editing               |
 | `[lb-key-value="…"]` | One row, by its key                             |
 | `[hidden]`           | A row a filter hides; the browser hides it      |
@@ -86,11 +85,10 @@ landed inside a list, such as a total in a table's foot, carries a key and
 is not one of the list's rows.
 
 ```css
-[lb-row-selected] { background: var(--selected); }
 [lb-row-editing] { outline: 2px solid var(--accent); }
 ```
 
-See [Rows](./data-binding.md#rows), [Selecting rows](./data-binding.md#selecting-rows)
+See [Rows](./data-binding.md#rows)
 and [Editing a row in one form](./data-binding.md#editing-a-row-in-one-form).
 
 ### A group
@@ -179,18 +177,19 @@ form:not([lb-key-value=""]) .save-new { display: none; }
 
 See [Editing a row in one form](./data-binding.md#editing-a-row-in-one-form).
 
-### The user's choices
+### The user's order and filters
 
-An order or a filter the user chose is a column of `lb-choices`, so the
-element showing it carries it as `lb-column-value`.  Style anything else by
-it with `:has()`:
+The order the user chose is the `order` column of `lb-sort`, and a filter
+is a column of `lb-filters`, so the element showing either carries it as
+`lb-column-value`. Style anything else by it with `:has()`:
 
 ```css
-table:has([lb-column="accounts_order"][lb-column-value="-balance"])
-  th.balance::after { content: "▼"; }
+:has([lb-column="name"][lb-column-value="^=Amazon"]) th.name::after {
+  content: "🔍";
+}
 ```
 
-See [Choices](./data-binding.md#choices).
+See [Sort and filters](./data-binding.md#sort-and-filters).
 
 ### Content shown by condition
 

package/skills/loadbare-app/references/custom-elements.md

@@ -572,18 +572,21 @@ missing a field its name needs, and stamps the dispatching element with
 
 Let the event bubble, so an ancestor can stop it before the hub sends it.
 
-A request with `lb-row-update` for `lb-url` or `lb-choices` is keyed by the
-path, so an element anywhere on the page may set a query parm or make a
-[choice](./data-binding.md#choices) without sitting inside the query:
+A request with `lb-row-update` for `lb-url` is keyed by the path; one for
+`lb-sort` or `lb-filters` is keyed by the query's name. An element anywhere
+on the page may set a query parm or make a
+[sort or a filter](./data-binding.md#sort-and-filters) without sitting
+inside the query:
 
 ```ts
-import { CHOICES_QUERY, LB_EVENT_NAME, REQUEST_ROW_UPDATE } from "@loadbare/app/constants";
+import { SORT_QUERY, LB_EVENT_NAME, REQUEST_ROW_UPDATE } from "@loadbare/app/constants";
 import type { HubRequest } from "@loadbare/app/types";
 
 const detail: HubRequest = {
   name: REQUEST_ROW_UPDATE,
-  query: CHOICES_QUERY,
-  values: { ledger_order: "-amount" },
+  query: SORT_QUERY,
+  key: "ledger",
+  values: { order: "-amount" },
 };
 this.dispatchEvent(new CustomEvent(LB_EVENT_NAME, { bubbles: true, detail }));
 ```
@@ -616,8 +619,8 @@ listener. Import its name as `LB_DONE_EVENT_NAME`.
 `items` is every response item that landed because of the request, in
 order. `refusal` is set beside `error` when the handler refused the
 request, holding its `message` and `columns`. An answer that moved the URL contributes its `lb-url` item, which
-carries a key only the server knew, and the page load. A choice contributes
-the row of `lb-choices` it made. `error` is set when
+carries a key only the server knew, and the page load. A sort or a filter contributes
+the row of `lb-sort` or `lb-filters` it made. `error` is set when
 the round trip failed, and then nothing landed. A new row's key is in the
 answer only when the handler returned it in a patch: a refresh sends all
 rows, and nothing marks which one is new.