@loadbare/app 0.25.0 → 0.26.0

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>`:
@@ -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 and shown in groups.  A
+of joined rows, ordered by the master first.  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
@@ -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
@@ -242,19 +243,10 @@ 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-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.
-
 **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 or group `lb-row-leaving` or `lb-group-leaving`, removing it once
+leaving row `lb-row-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
@@ -327,16 +319,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
@@ -439,9 +421,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`,
+ten in [Attributes](references/names.md#attributes): `lb-query`,
+`lb-column`, `lb-show`, `lb-filter`, `lb-manual`,
+`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 +509,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/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,24 +85,12 @@ 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
-
-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
@@ -115,7 +102,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]`, `[lb-group-leaving]` | A row or group on its way out; the hub removes it when its animations end |
+| `[lb-row-leaving]` | A row on its way out; the hub removes it when its animations end |
 
 ```css
 [lb-row-created] { animation: arrive 200ms; }

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-group-*`, `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-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,
-creates a live row, or builds a group. It places the chrome and a page as
+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 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 or a group has finished leaving, and when it shows
+element when a live row 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.
@@ -633,8 +633,7 @@ 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), and builds every group the markup's group templates describe; see
-[Order](./data-binding.md#order) and [Groups](./data-binding.md#groups). A
+for when it does not). 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.
@@ -662,8 +661,7 @@ 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, 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 |
+| Filtering   | Hides a row the user's filter does not pass |
 | 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
-eighteen `lb-` attributes. The server declares every query a page may show and
+fourteen `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`,
@@ -48,10 +48,6 @@ each with its key, and permits the three requests on `roster`; see
 | `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-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-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) |
@@ -69,11 +65,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`, `lb-group-leaving` | A row or group on its way out      |
+| `lb-row-leaving` | A row 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)  |
@@ -92,8 +86,7 @@ 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`, or, when that template is a [group
-template](#groups), the innermost template inside it:
+any nested `lb-query`:
 
 | Kind   | Row template | The hub                                |
 |--------|--------------|----------------------------------------|
@@ -332,8 +325,7 @@ 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 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`  |
+| Creates a row                          | Goes last                                         | `order`  |
 | Changes a row so the filter hides it   | Stays showing                                     | `filter` |
 | Drops a row                            | Leaves, under either side                         |          |
 
@@ -394,11 +386,9 @@ its rows the user may filter, separated by commas. The column of
 </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 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
+[Placing by hand](#placing-by-hand). An empty
 choice filters nothing.
 
 A filter is one or more terms, each an operator followed by a value:
@@ -431,96 +421,6 @@ 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-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:
-
-```html
-<tr><td><span lb-count></span> people</td><td lb-sum="salary"></td></tr>
-```
-
-| Attribute      | 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
-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:
@@ -533,7 +433,6 @@ 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
@@ -544,8 +443,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 or a group that leaves loses `lb-row-live` or `lb-group-live`, takes
-`lb-row-leaving` or `lb-group-leaving` and `inert`
+A row that leaves loses `lb-row-live`, takes
+`lb-row-leaving` and `inert`
 ([miswart](./miswarts.md#leaving-rows-are-inert)), and is removed once its
 animations finish, at once when there are none.
 
@@ -569,7 +468,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 group's heading or a ghost row. So
+scaffolding around rows, such as 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.
 
@@ -637,8 +536,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. A [group template](#groups)
-shows each master as a group, ordered by the master's key first.
+each detail row carries its master's columns, 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
@@ -753,8 +652,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
@@ -929,7 +827,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, filtered or aggregated, since it holds no data. It counts in
+  ordered or filtered, 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
@@ -1012,7 +910,7 @@ 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.
+`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 +1016,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 +1064,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 +1193,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.
@@ -1392,7 +1254,7 @@ 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 fourteen 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
@@ -1420,16 +1282,11 @@ expansion, and refuses to build:
   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`
 - 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>`

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

@@ -68,7 +68,7 @@ gathered.
 ## Rows hidden by a filter
 
 **What.**  A row that does not pass the user's filter gets the `hidden`
-attribute, and so does a group whose rows are all hidden.
+attribute.
 
 **Rule broken.**  The hub writes only its own stamps, which always
 begin with `lb-`.
@@ -78,7 +78,7 @@ over rows already on the page needs no round trip, and `hidden` is HTML's
 own word for an element that is present but not shown.  A stamp of our
 own would make every stylesheet restate what the browser already does.
 
-**Why it terminates.**  It applies only to live rows and groups under a
+**Why it terminates.**  It applies only to live rows under a
 filter.
 
 ## Leaving rows are inert