@loadbare/app 0.25.0 → 0.27.0

package/docs/reference/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/docs/reference/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/docs/reference/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.

package/docs/reference/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
-eighteen `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,12 +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-count`       | Any element                   | Nothing: it shows a count of rows; see [Aggregates](#aggregates) |
-| `lb-sum`, `lb-avg`, `lb-min`, `lb-max` | Any element | The column aggregated; see [Aggregates](#aggregates) |
-| `lb-select`      | A checkbox in a row template  | Nothing: it selects its live row; see [Selecting rows](#selecting-rows) |
+| `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) |
@@ -73,7 +70,6 @@ builder writes a stamp, and a stylesheet or a custom element reads it.
 | `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`, `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-row-selected`    | A row whose `lb-select` is ticked                  |
 | `lb-request-pending` | The element's request is in flight                 |
 | `lb-request-error`   | The element's last request failed                  |
 | `lb-request-refused` | The handler refused it; see [Refusals](#refusals)  |
@@ -185,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
@@ -271,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                                  |
@@ -321,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">
 ```
 
@@ -382,20 +375,19 @@ 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 row that does not pass every filter is `hidden`, and a ticked `lb-select`
-in it is cleared. Under `lb-manual="filter"`, a row an answer changed stays
+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). A group whose rows are all hidden is hidden too
 ([miswart](../miswarts.md#rows-hidden-by-a-filter)). An empty
@@ -494,23 +486,24 @@ group, and are reported once.
 
 ### Aggregates
 
-`lb-count`, `lb-sum="col"`, `lb-avg="col"`, `lb-min="col"` and
-`lb-max="col"` set an element from the rows of the nearest group around it,
-or of the whole list outside any group:
+`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-count></span> people</td><td lb-sum="salary"></td></tr>
+<tr><td><span lb-aggregate="count"></span> people</td><td lb-aggregate="sum" lb-column="salary"></td></tr>
 ```
 
-| Attribute      | Sets the element to                                       |
+| `lb-aggregate` | Sets the element to                                       |
 |----------------|-----------------------------------------------------------|
-| `lb-count`     | The number of rows                                        |
-| `lb-sum="col"` | The sum of `col`                                          |
-| `lb-avg="col"` | The average of `col`                                      |
-| `lb-min="col"` | The least value of `col`, by the [order](#order)'s comparison |
-| `lb-max="col"` | The greatest, likewise                                    |
-
-An aggregate lands as a column does, with `lb-column-value`. A sum and an
+| `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
@@ -578,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.
 
@@ -753,8 +746,7 @@ Every request has one shape:
 ```
 
 The hub takes `query`, `key` and `values` from where the element sits, and
-sends each when it has one. A request acting on several rows carries `keys`
-in place of `key`; see [Selecting rows](#selecting-rows). The server runs the handler for the name and
+sends each when it has one. The server runs the handler for the name and
 answers with response items, which land like any others.
 
 ### Committing
@@ -1009,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`, 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:
@@ -1118,6 +1110,27 @@ The rows a form's answer lands are placed by the list's `lb-manual`, as any
 answer's are, whether the form was pointed by Edit or by New; see
 [Placing by hand](#placing-by-hand).
 
+A list nested in the form follows the row the form is bound to. When Edit
+or New binds the form, the hub drops the list's rows not yet entered and
+asks the server for the list's query again, as the request `lb-read`, with
+the bound row's key added to the query string as the parm named for the
+form's key column. `contextFor` receives it among the parms, and the query
+reads it as it reads any parm, so one query serves a master the URL names
+and a master Edit binds. New sends the parm empty, and the query answers
+with no rows:
+
+```ts
+function contextFor(req: Request, parms: URLSearchParams): HubContext {
+  return { db: openDb(), paycheck: parms.get("paycheck_id") ?? "" };
+}
+
+deductions: rows("id", (ctx) => ctx.db.deductionsFor(ctx.paycheck)),
+```
+
+A form with no list inside it sends nothing when it is bound. An answer
+that returns after the form is bound to another row, or after the page
+moved on, lands nothing.
+
 A successful request from the form lets it go, as Cancel does: the form
 empties, its controls return to their defaults, and the stamps go. A failed
 one leaves the form as the user had it, to correct.
@@ -1145,63 +1158,6 @@ outside a live row of the form's query, Edit for a key the hub holds no row
 for, and any of these three commands aimed at an element that is not a form
 carrying `lb-query`.
 
-### Selecting rows
-
-A checkbox carrying `lb-select` in a row template selects the live row it
-sits in. It is not a column: it carries no `lb-column`, lands nothing and
-is not gathered. The hub stamps the row `lb-row-selected` while it is
-ticked.
-
-A request for the query that names no one row then acts on the rows
-selected, and carries their keys as `keys`:
-
-```html
-<tbody lb-query="transactions">
-  <template>
-    <tr>
-      <td><input type="checkbox" lb-select lb-show="selecting" /></td>
-      <td lb-column="description"></td>
-      <td lb-column="amount"></td>
-    </tr>
-  </template>
-</tbody>
-
-<form lb-query="transactions" lb-request="lb-row-update">
-  <lb-picker lb-query="accounts" lb-column="acct" exp-label="Account" exp-column="name"></lb-picker>
-  <button type="submit">Apply</button>
-  <button type="button" lb-request="lb-row-delete">Delete</button>
-</form>
-```
-
-```json
-{ "name": "lb-row-update", "query": "transactions", "keys": ["4", "9"], "values": { "acct": "12" } }
-```
-
-| Request          | With rows selected                     | With none ticked     |
-|------------------|----------------------------------------|----------------------|
-| `lb-row-update`  | Sent with `keys`                       | Not sent             |
-| `lb-row-delete`  | Sent with `keys`                       | Not sent             |
-| A declared one   | Sent with `keys`                       | Sent with `keys: []` |
-| `lb-row-insert`  | Sent as ever; the selection is not its | Sent as ever         |
-
-An update or delete with nothing ticked has nothing to act on, and nothing
-is reported. A request from inside a row still names that row alone. The
-server runs the page's `rowUpdate` or `rowDelete` once for each key, as for
-each row alone, and refreshes once; see [crud](./page-files.md#crud).
-
-After the request succeeds, the hub clears the selection. A failed one
-leaves it, to try again.
-
-Only a checkbox that is showing counts. Turning a selector off with
-`lb-show` also clears its tick, so leaving a selecting mode abandons the
-selection rather than keeping it out of sight. With every selector off, a
-request for the query is an ordinary one again.
-
-Which rows are selected, and whether the page is in a selecting mode, is
-interaction state. A mode the URL keeps, such as `?selecting=1`, reaches
-the rows as a column the query computes from the parm, which `lb-show`
-reads.
-
 ### Declared requests
 
 A request name the page declares under `handlers` runs the application's
@@ -1331,7 +1287,7 @@ returns its controls to their defaults, and the hub removes
 `lb-column-value` from each of them. A cancelled reset keeps both.
 
 A page load that fails lands nothing and is reported to the console, and
-the query `lb-hub` says so; see [The hub's state](./chrome.md#the-hubs-state).
+the query `lb-hub-status` says so; see [The hub's state](./chrome.md#the-hubs-state).
 A load
 started by a request for `lb-url` stamps the element that sent it, as any
 request stamps its element.
@@ -1363,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
 
@@ -1392,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 eighteen 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>`
@@ -1416,20 +1374,21 @@ 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-select` on anything but `<input type="checkbox">`, outside a row
-  template, or beside `lb-column` or `lb-request`
+- `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
   `<form>` nor a list carrying `lb-query` nested directly in a form's own
   query
-- `lb-group` on anything but a `<template>`, or on one holding no
-  `<template>` for its contents
-- an aggregate on a `<template>`, or any but `lb-count` naming no column
 - a chrome without exactly one `<lb-hub>` and exactly one `<main>`, a
   `<main>` outside `<lb-hub>`, or a `<main>` holding anything but whitespace
 - a page carrying an `<lb-hub>` or a `<main>`