@loadbare/app 0.26.0 → 0.27.0

package/skills/loadbare-app/SKILL.md

@@ -183,7 +183,7 @@ from it.
 
 **A column never holds rows.**  Master-detail is a `row` query and a `rows`
 query under two names.  Many masters with their details is one `rows` query
-of joined rows, ordered by the master first.  A
+of joined rows, ordered by the master first and shown in groups.  A
 query nested inside another query's row template receives the same rows in
 every outer row; use it for a picker, never for per-row detail.  Inside a
 form, the live rows of a query nested in the form's own are gathered as
@@ -243,10 +243,20 @@ stylesheet, `lb-hub[lb-load-state="failed"] .load-failed`, rather than
 leaving an empty page; see
 [`references/chrome.md`](references/chrome.md#the-hubs-state).
 
+**Groups are templates.**  A `<template lb-group>` holds a heading and one
+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-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
 `lb-row-requested` for this page's request, and marks a
-leaving row `lb-row-leaving`, removing it once
+leaving row or group `lb-row-leaving` or `lb-group-leaving`, removing it once
 its animations end.  Scrolling to a row is script, in `lbRowsLanded`.
 
 **Every request has one shape.**  `lb-request` names the request, and the
@@ -376,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,
@@ -421,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
-ten in [Attributes](references/names.md#attributes): `lb-query`,
-`lb-column`, `lb-show`, `lb-filter`, `lb-manual`,
-`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.

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

@@ -91,6 +91,17 @@ is not one of the list's 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
+
+Each top-level element of a group carries `lb-group-live`, the column it
+breaks on as `lb-group-column`, and its value there as `lb-group-value`:
+
+```css
+[lb-group-column="category"][lb-group-value="Income"] { color: var(--income); }
+```
+
+See [Groups](./data-binding.md#groups).
+
 ### What just happened to a row
 
 The hub stamps what its last landing did, so a stylesheet animates with
@@ -102,7 +113,7 @@ nothing else:
 | `[lb-row-changed]`             | A row whose values changed                     |
 | `[lb-row-moved]`               | A row whose values changed and now stands elsewhere; it carries `lb-row-changed` too |
 | `[lb-row-requested]`           | Any of the three, done by this page's request, as `created`, `changed` or `moved` |
-| `[lb-row-leaving]` | A row on its way out; the hub removes it when its animations end |
+| `[lb-row-leaving]`, `[lb-group-leaving]` | A row or group on its way out; the hub removes it when its animations end |
 
 ```css
 [lb-row-created] { animation: arrive 200ms; }
@@ -166,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

@@ -268,7 +268,7 @@ Each direction has one mechanism for each kind of message:
 
 | Direction      | What                                       | How                         | Today |
 |----------------|--------------------------------------------|-----------------------------|-------|
-| Hub to element | State that lasts                           | An attribute the hub stamps | `lb-column-value`, `lb-key-value`, `lb-query-row-count`, `lb-query-unplaced-count`, `lb-query-order`, `lb-row-*`, `lb-request-pending`, `lb-request-error`, `lb-request-refused` |
+| Hub to element | State that lasts                           | An attribute the hub stamps | `lb-column-value`, `lb-key-value`, `lb-query-row-count`, `lb-query-unplaced-count`, `lb-query-order`, `lb-group-*`, `lb-row-*`, `lb-request-pending`, `lb-request-error`, `lb-request-refused` |
 | Hub to element | State the platform already names           | A property                  | A control's `value` |
 | Hub to element | What the hub did                           | An optional `lb` method     | `lbAttached`, `lbRowsLanded`, `lbRequestDone`, `lbDetached` |
 | Hub to element | A moment an element started                | A bubbling event            | `lb-request-done` |
@@ -315,11 +315,11 @@ customElements.define("note-popup", NotePopup);
 | `lbRequestDone(detail, origin)` | After a request committed by the element, or inside it, has finished |
 | `lbDetached()`                  | Once, after it removes the element                                |
 
-The hub places an element when it starts up the chrome, shows a page, or
-creates a live row. It places the chrome and a page as
+The hub places an element when it starts up the chrome, shows a page,
+creates a live row, or builds a group. It places the chrome and a page as
 the page's first answer lands, or once that round trip fails, so an element
 in either hears `lbAttached` with the page's data in place. It removes an
-element when a live row has finished leaving, and when it shows
+element when a live row or a group has finished leaving, and when it shows
 another page in place of the one holding it. Write setup in `lbAttached` and its undoing in
 `lbDetached`; the two pair exactly, so neither guards against running
 twice.
@@ -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.
@@ -633,7 +636,8 @@ had there hears the event, and no custom element the hub has removed hears
 
 The hub lands every row template itself, places every row by the query's
 order (see [Placing by hand](./data-binding.md#placing-by-hand)
-for when it does not). A
+for when it does not), and builds every group the markup's group templates describe; see
+[Order](./data-binding.md#order) and [Groups](./data-binding.md#groups). A
 plain element carrying `lb-query` with a row template inside it needs no
 code, so a custom element holds rows only to do something with them once
 they land.
@@ -661,7 +665,8 @@ Everything else is the hub's:
 | Cloning     | Clones the row template once per new key                 |
 | Matching    | Fills the live row already showing that key, when its values changed |
 | Placing     | Places every live row by the user's order or the query's, and leaves them where they stand for an answer under `lb-manual` |
-| Filtering   | Hides a row the user's filter does not pass |
+| Filtering   | Hides a row the user's filter does not pass, and a group whose rows are all hidden |
+| Grouping    | Builds a group where the order breaks, keeps it while its run goes on, and removes it with its last row |
 | Removing    | Marks the live rows the response says are gone as leaving, and removes them |
 | Stamping    | Stamps each live row with `lb-row-live`, `lb-key-value`, and what happened to it |
 | Counting    | Stamps `lb-query-row-count` with the number of live rows showing, `lb-query-unplaced-count` with the number out of place, and `lb-query-order` with the order placing them |

package/skills/loadbare-app/references/data-binding.md

@@ -2,7 +2,7 @@
 
 A page shows server data by naming queries and columns in its HTML, and asks
 the server to change that data by naming requests. The developer writes
-fourteen `lb-` attributes. The server declares every query a page may show and
+ten `lb-` attributes. The server declares every query a page may show and
 every request it may send, and refuses anything it has not declared.
 
 Everything is a query. A query is a name for rows, of kind `row` or `rows`,
@@ -46,8 +46,9 @@ each with its key, and permits the three requests on `roster`; see
 | `lb-query`       | Any element                   | The query whose rows land in it                |
 | `lb-column`      | Any element                   | The column it shows, and the column it gathers |
 | `lb-show`        | Any element but `<template>`  | The column that decides whether it is present  |
-| `lb-order`       | An element with `lb-query`    | The choice holding the user's order; see [Order](#order) |
-| `lb-filter`      | An element with `lb-query`    | The columns a choice filters; see [Filters](#filters) |
+| `lb-filter`      | An element with `lb-query`    | The columns the user may filter; see [Filters](#filters) |
+| `lb-group`       | A `<template>`                | Nothing: it marks a group template; see [Groups](#groups) |
+| `lb-aggregate`   | Any element                   | The function it applies to `lb-column`; see [Aggregates](#aggregates) |
 | `lb-request`     | Any element                   | The request it sends when it commits           |
 | `lb-url-link`    | An `<a>`                      | A link between pages; see [chrome](./chrome.md#links) |
 | `lb-url-parm`    | An `<a lb-url-link>` in a row | Columns of the row its `href` carries as parms; see [chrome](./chrome.md#a-link-from-a-row) |
@@ -65,8 +66,9 @@ builder writes a stamp, and a stylesheet or a custom element reads it.
 | `lb-query-row-count` | The number of live rows an element shows           |
 | `lb-query-unplaced-count` | The number of them out of place; see [Placing by hand](#placing-by-hand) |
 | `lb-query-order`     | The order placing them; see [Order](#order)        |
+| `lb-group-live`, `lb-group-column`, `lb-group-value` | A group, the column it breaks on, and its value; see [Groups](#groups) |
 | `lb-row-created`, `lb-row-changed`, `lb-row-moved`, `lb-row-requested`, `lb-row-unplaced` | What happened to a row; see [What happened to a row](#what-happened-to-a-row) |
-| `lb-row-leaving` | A row on its way out      |
+| `lb-row-leaving`, `lb-group-leaving` | A row or group on its way out      |
 | `lb-row-editing`     | The row a form is pointed at; see [Editing a row in one form](#editing-a-row-in-one-form) |
 | `lb-request-pending` | The element's request is in flight                 |
 | `lb-request-error`   | The element's last request failed                  |
@@ -86,7 +88,8 @@ elements as the page needs.
 
 What lands depends on the query's kind and on whether the element holds a
 row template, which is the first `<template>` among its descendants outside
-any nested `lb-query`:
+any nested `lb-query`, or, when that template is a [group
+template](#groups), the innermost template inside it:
 
 | Kind   | Row template | The hub                                |
 |--------|--------------|----------------------------------------|
@@ -178,7 +181,7 @@ or `""`:
 
 A checkbox lands what it sends, so it shows the same state after a round
 trip through a query whose values are strings, such as `lb-url` or
-`lb-choices`. A query parm the URL does not carry lands as `""`, so the
+`lb-filters`. A query parm the URL does not carry lands as `""`, so the
 checkbox is unchecked. Unchecked sends `"false"` rather than nothing, so a
 flag can be set back. A checkbox carrying a `value` attribute is not a flag
 but one of a set, holding a query parm the URL repeats; see
@@ -264,25 +267,22 @@ roster: rows("id", (ctx) => ctx.db.members(), { order: "team,name" }),
 With no order, rows show in the order they arrived, and a patch's new rows
 go last.
 
-The user's order replaces the server's. Write `lb-order` on the element
-carrying `lb-query`, naming a column of [`lb-choices`](#choices). That
-column holds an order written the same way, and while it is empty the
-server's order places the rows:
+The user's order replaces the server's. The hub serves the query
+[`lb-sort`](#sort-and-filters), one row per `rows` query, keyed by the
+query's name, whose `order` column holds an order written the same way.
+While it is empty, the server's order places the rows:
 
 ```html
-<div lb-query="lb-choices">
-  <select lb-column="roster_order" lb-request="lb-row-update">
-    <option value="">By team</option>
-    <option value="name">By name</option>
-    <option value="-joined">Newest first</option>
-  </select>
-</div>
-
-<ul lb-query="roster" lb-order="roster_order">
+<ul lb-query="roster">
   <template><li lb-column="name"></li></template>
 </ul>
 ```
 
+A control makes a choice by sending `lb-row-update` for `lb-sort`, keyed by
+the query's name; the `<lb-table>` widget's sortable headings do this for
+each column. The hub places the rows again from the ones it already holds,
+and tells the server through `onChoices`.
+
 | Values               | Compare                                      |
 |----------------------|----------------------------------------------|
 | Two numbers          | Numerically                                  |
@@ -314,7 +314,7 @@ user works through them. It names `order`, `filter` or both, separated by a
 space:
 
 ```html
-<lb-table lb-query="entries" lb-order="entries_order"
+<lb-table lb-query="entries"
           lb-filter="description, is_unmatched" lb-manual="order filter">
 ```
 
@@ -325,7 +325,8 @@ form `--lb-edit` pointed at a row, or a form elsewhere on the page.
 | The answer                             | Under `lb-manual`, the row                        | Side     |
 |----------------------------------------|---------------------------------------------------|----------|
 | Changes a column the order reads       | Stays where it stands                             | `order`  |
-| Creates a row                          | Goes last                                         | `order`  |
+| Creates a row                          | Goes after the last row of its group, or last of all | `order`  |
+| Changes the column its group breaks on | Stays under its group's heading                   | `order`  |
 | Changes a row so the filter hides it   | Stays showing                                     | `filter` |
 | Drops a row                            | Leaves, under either side                         |          |
 
@@ -374,21 +375,22 @@ the move.
 
 Write `lb-filter` on the element carrying `lb-query`, naming the columns of
 its rows the user may filter, separated by commas. The column of
-[`lb-choices`](#choices) of the same name holds the filter for each:
+[`lb-filters`](#sort-and-filters) of the same name holds the filter for
+each:
 
 ```html
-<div lb-query="lb-choices">
-  <input lb-column="name" lb-request="lb-row-update" placeholder="Name" />
-</div>
-
 <ul lb-query="roster" lb-filter="name, team">
   <template><li lb-column="name"></li></template>
 </ul>
 ```
 
+A filter is made by sending `lb-row-update` for `lb-filters`, keyed by the
+query's name; the `<lb-table>` widget's selection does this.
+
 A row that does not pass every filter is `hidden`. Under `lb-manual="filter"`, a row an answer changed stays
 showing until the rows are placed again; see
-[Placing by hand](#placing-by-hand). An empty
+[Placing by hand](#placing-by-hand). A group whose rows are all hidden is hidden too
+([miswart](./miswarts.md#rows-hidden-by-a-filter)). An empty
 choice filters nothing.
 
 A filter is one or more terms, each an operator followed by a value:
@@ -421,6 +423,97 @@ column that is null or missing, pass only `!=`.
 `parseFilter`, `passes` and `passesTerm` in `@loadbare/app/types` are the
 rule the hub applies.
 
+### Groups
+
+A group is a run of rows sharing the order's leading term. Write a
+`<template lb-group>` where the row template goes, holding the group's
+heading and one nested `<template>`: the next group template, or the row
+template. The nth group template breaks on the order's nth term.
+
+```html
+<ul lb-query="roster">
+  <template lb-group>
+    <li>
+      <h3 lb-column="team"></h3>
+      <ul>
+        <template><li lb-column="name"></li></template>
+      </ul>
+    </li>
+  </template>
+</ul>
+```
+
+The hub clones the group template where the order breaks, and the group's
+contents land immediately before the clone of its nested template, so the
+markup's nesting decides the shape:
+
+| The nested template is       | The group's contents land          | Example                           |
+|------------------------------|------------------------------------|-----------------------------------|
+| Inside the heading's element | Inside it                          | `<tbody>`, `<li>`, `<details>`    |
+| Beside the heading           | After the heading, as its siblings | A heading `<tr>` in one `<tbody>` |
+
+`<tbody>` and `<optgroup>` do not nest, so a table's levels below the first
+are heading rows beside their rows:
+
+```html
+<table lb-query="accounts">
+  <thead><tr><th>Account</th></tr></thead>
+  <template lb-group>
+    <tbody>
+      <tr><th scope="rowgroup" lb-column="category"></th></tr>
+      <template><tr><td lb-column="account_name"></td></tr></template>
+    </tbody>
+  </template>
+</table>
+```
+
+Content after the nested template lands after the group's rows, which is
+where a group's footer goes.
+
+A heading is filled from its group's first row as an element in a row is,
+`href`s from `lb-url-parm` included, so it may show a column other than the
+one the group breaks on. Under `lb-manual="order"`, a row an answer
+moved to another group stays under its old heading, and the heading shows
+the row as it stood, until the rows are placed again. The hub stamps each top-level
+element of a group with `lb-group-live`, `lb-group-column` and
+`lb-group-value`. A row creates its group, and a group leaves with its last
+row. When the order changes, a group whose run goes on is kept and moved,
+and a group whose run ended leaves.
+
+A group template with no nested template is reported to the console. More
+group templates than the order has terms show each extra level as one
+group, and are reported once.
+
+### Aggregates
+
+`lb-aggregate` sets an element from the rows of the nearest group around
+it, or of the whole list outside any group. It names the function, and
+`lb-column` names the column:
+
+```html
+<tr><td><span lb-aggregate="count"></span> people</td><td lb-aggregate="sum" lb-column="salary"></td></tr>
+```
+
+| `lb-aggregate` | Sets the element to                                       |
+|----------------|-----------------------------------------------------------|
+| `count`        | The number of rows; with `lb-column`, the values in it that are not null |
+| `sum`          | The sum of the column                                     |
+| `avg`          | The average of the column                                 |
+| `min`          | The least value of the column, by the [order](#order)'s comparison |
+| `max`          | The greatest, likewise                                    |
+
+An aggregate lands as a column does, with `lb-column-value`; its
+`lb-column` names the column it totals, and no row lands on it. A sum and an
+average are exact decimals, read from JSON numbers and from strings holding
+a plain decimal, as Postgres sends `numeric`. A sum has as many places as
+the most precise value, and an average up to two more. `null` and empty
+values are left out, as SQL leaves them out, and any other value is left
+out and reported once. The result lands unformatted.
+
+An aggregate covers the rows showing, so a row a filter hides is left out.
+Where the true total matters beyond what the page shows, have the server
+answer it as a row.
+
 ### What happened to a row
 
 Every change to a list is one a stylesheet can see:
@@ -433,6 +526,7 @@ Every change to a list is one a stylesheet can see:
 | `lb-row-requested` | `created`, `changed` or `moved` by this page's request |
 | `lb-row-unplaced`  | Stands where the order or the filter would not leave it |
 | `lb-row-leaving`   | A row on its way out                                   |
+| `lb-group-leaving` | A group on its way out                                 |
 
 The hub touches a row when an answer names it. `lb-row-created`,
 `lb-row-changed` and `lb-row-moved` are cleared when it next does, and one
@@ -443,8 +537,8 @@ query, and set only by a landing that answers a request from the page.
 placed again; see
 [Placing by hand](#placing-by-hand).
 
-A row that leaves loses `lb-row-live`, takes
-`lb-row-leaving` and `inert`
+A row or a group that leaves loses `lb-row-live` or `lb-group-live`, takes
+`lb-row-leaving` or `lb-group-leaving` and `inert`
 ([miswart](./miswarts.md#leaving-rows-are-inert)), and is removed once its
 animations finish, at once when there are none.
 
@@ -468,7 +562,7 @@ The hub keeps each query's last answer until the page changes, with any
 patch since applied to it. An element that names a query and arrives after
 that query's answer is filled from what was kept, at the end of the landing
 that follows its arrival. Such an element is a picker in a new live row, or
-scaffolding around rows, such as a ghost row. So
+scaffolding around rows, such as a group's heading or a ghost row. So
 a query nested in another query's rows need not land again, or land after
 the outer query, for a new outer row to show its choices.
 
@@ -477,8 +571,8 @@ and its `lbRowsLanded` runs as its rows land. See
 [Holding rows](./custom-elements.md#holding-rows).
 
 A request always goes to the server, and a query re-runs only when a
-response names it. A [choice](#choices) is the one thing landed from what
-the hub kept. A patch that
+response names it. A [sort or a filter](#sort-and-filters) is the one thing
+landed from what the hub kept. A patch that
 arrives before all of a query's rows is not kept, since it is not the whole
 of anything.
 
@@ -536,8 +630,8 @@ answered side by side. A column never holds rows.
 ```
 
 Many masters, each with its own detail, is one `rows` query of joined rows:
-each detail row carries its master's columns, ordered by the master's key
-first.
+each detail row carries its master's columns. A [group template](#groups)
+shows each master as a group, ordered by the master's key first.
 
 A query nested in another query's row template receives the same rows in
 every live row. That serves a picker offering the same choices on every
@@ -827,7 +921,7 @@ it, and sends nothing:
   Its controls start at their HTML defaults, and its `lb-show` branches are
   as for a row whose every column is null.
 - It stands after every row of the list, in the order added, and is not
-  ordered or filtered, since it holds no data. It counts in
+  ordered, filtered or aggregated, since it holds no data. It counts in
   `lb-query-row-count`.
 - The form's submit carries it in `rows`, with `key: ""`, beside the rows on
   record: an insert while the master is not on record, an update once it
@@ -907,10 +1001,10 @@ The hub sends one of these only when it has what the table lists, and
 otherwise reports to the console. An insert or an update that gathers
 nothing is not sent.
 
-For a query the hub serves, `lb-url` or `lb-choices`, the hub answers
-`lb-row-update` itself, with no round trip; see
-[Query parms](./chrome.md#query-parms) and [Choices](#choices). The third,
-`lb-hub-status`, takes no request.
+For a query the hub serves, `lb-url`, `lb-sort` or `lb-filters`, the hub
+answers `lb-row-update` itself, with no round trip; see
+[Query parms](./chrome.md#query-parms) and
+[Sort and filters](#sort-and-filters). `lb-hub-status` takes no request.
 
 A key comes from a live row, or from an element a `row` landed on, so all
 three work against either kind:
@@ -1225,28 +1319,28 @@ answers it with no round trip:
 See [The URL](./chrome.md#the-url) for its columns, links, history, and the
 unknown-page dialog.
 
-## Choices
+## Sort and filters
 
-The hub serves a second query, `lb-choices`: one row keyed by `lb-path`,
-with a column for each choice the user made for how rows show, an
-[order](#order) or a [filter](#filters). The application names the
-columns. A control inside `lb-query="lb-choices"` that sends
-`lb-row-update` makes a choice, and an element anywhere may make one by
-dispatching the `lb-request` event with `lb-row-update` for `lb-choices`,
-which the hub keys by the path; see
+The hub serves two queries for how rows show: `lb-sort` and `lb-filters`,
+one row per `rows` 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. An element makes a sort or a filter by dispatching
+`lb-request` with `lb-row-update` for `lb-sort` or `lb-filters`, keyed by
+the query's name; the `<lb-table>` widget's sortable headings and its
+selection do this; see
 [Sending a request](./custom-elements.md#sending-a-request).
 
-A choice joins the ones already made, and shows with no round trip: every
-element whose `lb-order` or `lb-filter` reads a column that changed lands
-its query's last answer again, as a round trip carrying the choice would
-have. Then the hub sends the server every choice made on the page, as
-strings, in `lb-row-update` for `lb-choices`. No element waits on it, and
-the page's [`onChoices`](./page-files.md#onchoices) runs, when it has one.
+A sort or a filter shows with no round trip: the hub places and filters the
+rows it already holds again, as a round trip carrying the choice would
+have. Then it sends the server the choice, in `lb-row-update` for `lb-sort`
+or `lb-filters`. No element waits on it, and the page's
+[`onChoices`](./page-files.md#onchoices) runs, when it has one, with the
+query and its new `sort` or `filters`.
 
 Choices hold until the page changes, and a change of query parm keeps them.
-On entering a page, every column named under `lb-query="lb-choices"` lands
-empty, unless the page's `onPageEnter` restores them. Choices are not query
-parms, and the URL does not carry them.
+On entering a page, `lb-sort` and `lb-filters` land empty, unless the
+page's `onPageEnter` restores them with `sort()` and `filters()`. Choices
+are not query parms, and the URL does not carry them.
 
 ## The markup checks
 
@@ -1254,16 +1348,18 @@ The developer writes `lb-` attributes in markup, and script never assigns
 them. The builder checks the markup of the chrome and of every page, after
 expansion, and refuses to build:
 
-- an `lb-` attribute that is not one of the fourteen the developer writes;
+- an `lb-` attribute that is not one of the ten the developer writes;
   `lb-exp-slot` and `lb-exp-template` are consumed by expansion and never
   reach the check
 - `lb-request` naming an `lb-` request other than the three Loadbare provides
 - `lb-query` naming a query the page does not declare; every page and the
-  chrome may name `lb-url` and `lb-choices`, and the chrome names no other
+  chrome may name `lb-url`, `lb-sort`, `lb-filters` and `lb-hub-status`,
+  and the chrome names no other
 - `lb-request` naming a request the page does not declare under `handlers`;
   the chrome sends none
 - one of the three requests for a query whose `crud` entry does not declare
-  it, or any but `lb-row-update` for `lb-url` or `lb-choices`; the query is
+  it, or any but `lb-row-update` for `lb-url`, `lb-sort` or `lb-filters`;
+  the query is
   a form's own when the form carries `lb-query`, and otherwise the nearest
   `lb-query` around the element
 - `lb-url-link` on anything but an `<a>`
@@ -1278,10 +1374,16 @@ expansion, and refuses to build:
 - `lb-show` on a `<template>`, or on a row template's root
 - `lb-show` with no `lb-query` around it
 - `lb-show="!"` or `lb-show="!!column"`, which reverse no column
-- `lb-order` or `lb-filter` on an element not carrying `lb-query`, or naming
-  no column
+- `lb-filter` on an element not carrying `lb-query`, or naming no column
 - `lb-manual` on an element not carrying `lb-query`, or naming anything but
   `order`, `filter` or both
+- `lb-group` on anything but a `<template>`, or on one holding no
+  `<template>` for its contents
+- `lb-aggregate` on a `<template>`, naming a function other than `count`,
+  `sum`, `avg`, `min` or `max`, or, for any but `count`, beside no
+  `lb-column`
+- `lb-count`, `lb-sum`, `lb-avg`, `lb-min` or `lb-max`, with what to write
+  instead
 - a `command` beginning `--lb-` that is not one of the four commands
 - one of the four commands with no `commandfor`
 - `--lb-new` aimed at an element the markup holds that is neither a