@loadbare/app 0.25.0 → 0.26.0

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

@@ -14,10 +14,9 @@ that declares a query, a handler or a `crud` entry whose name begins with
 
 | Flag       | Default | Names                                     | Defined in                                          |
 | ---------- | ------- | ----------------------------------------- | --------------------------------------------------- |
-| `--src`    | `src`   | The application's own tree, scanned whole | [Running the builder](./builder.md#running-the-builder) |
-| `--out`    | `dist`  | Where the builder writes                  | [Running the builder](./builder.md#running-the-builder) |
-| `--watch`  | off     | Rebuild on change under `--src`           | [Running the builder](./builder.md#running-the-builder) |
-| `--minify` | off     | Minify `client.js` and `app.css`          | [Running the builder](./builder.md#running-the-builder) |
+| `--src`    | `src`   | The application's own tree, scanned whole | [Running the builder](./builder.md) |
+| `--out`    | `dist`  | Where the builder writes                  | [Running the builder](./builder.md) |
+| `--minify` | off     | Minify `client.js` and `app.css`          | [Running the builder](./builder.md) |
 
 ## Reserved file names
 
@@ -66,7 +65,7 @@ A widget package declares these.  An application never does.
 
 ## Attributes
 
-The developer writes eighteen attributes in pages and the chrome, and the
+The developer writes fourteen attributes in pages and the chrome, and the
 builder refuses any other `lb-` attribute there.  `lb-exp-slot` and
 `lb-exp-template` are written for expansion, which removes them before the
 check.  The hub and the builder write the rest, as stamps, and script never
@@ -80,9 +79,6 @@ assigns one.
 | `lb-order`           | Developer       | [Order](./data-binding.md#order)                                 |
 | `lb-filter`          | Developer       | [Filters](./data-binding.md#filters)                             |
 | `lb-manual`          | Developer       | [Placing by hand](./data-binding.md#placing-by-hand)             |
-| `lb-group`           | Developer       | [Groups](./data-binding.md#groups)                               |
-| `lb-count`, `lb-sum`, `lb-avg`, `lb-min`, `lb-max` | Developer | [Aggregates](./data-binding.md#aggregates)       |
-| `lb-select`          | Developer       | [Selecting rows](./data-binding.md#selecting-rows)               |
 | `lb-request`         | Developer       | [Requests](./data-binding.md#requests)                           |
 | `lb-url-link`        | Developer       | [Links](./chrome.md#links)                                       |
 | `lb-url-parm`        | Developer       | [A link from a row](./chrome.md#a-link-from-a-row)               |
@@ -96,11 +92,9 @@ assigns one.
 | `lb-query-row-count` | Hub             | [Counting rows](./data-binding.md#counting-rows)                 |
 | `lb-query-unplaced-count`, `lb-row-unplaced` | Hub | [Placing by hand](./data-binding.md#placing-by-hand) |
 | `lb-query-order`     | Hub             | [Order](./data-binding.md#order)                                 |
-| `lb-group-live`, `lb-group-column`, `lb-group-value` | Hub | [Groups](./data-binding.md#groups)                       |
 | `lb-row-created`, `lb-row-changed`, `lb-row-moved`, `lb-row-requested` | Hub | [What happened to a row](./data-binding.md#what-happened-to-a-row) |
-| `lb-row-leaving`, `lb-group-leaving` | Hub | [What happened to a row](./data-binding.md#what-happened-to-a-row) |
+| `lb-row-leaving` | Hub | [What happened to a row](./data-binding.md#what-happened-to-a-row) |
 | `lb-row-editing`     | Hub             | [Editing a row in one form](./data-binding.md#editing-a-row-in-one-form) |
-| `lb-row-selected`    | Hub             | [Selecting rows](./data-binding.md#selecting-rows)               |
 | `lb-request-pending` | Hub             | [Request state](./data-binding.md#request-state)                 |
 | `lb-request-error`   | Hub             | [Request state](./data-binding.md#request-state)                 |
 | `lb-request-refused` | Hub             | [Refusals](./data-binding.md#refusals)                           |
@@ -116,9 +110,9 @@ them, and a page declares none.
 
 | Query        | Kind  | Key       | Columns                                                         | Defined in                            |
 | ------------ | ----- | --------- | --------------------------------------------------------------- | ------------------------------------- |
-| `lb-url`     | `row` | `lb-path` | `lb-path`, `lb-page-label`, `lb-page-unknown`, every query parm | [The URL](./chrome.md#the-url)        |
+| `lb-url`     | `row` | `lb-path` | `lb-path`, `lb-page-label`, every query parm                    | [The URL](./chrome.md#the-url)        |
 | `lb-choices` | `row` | `lb-path` | `lb-path`, every choice                                         | [Choices](./data-binding.md#choices)  |
-| `lb-hub`     | `row` | `lb-path` | `lb-path`, `lb-load-state`, `lb-server-state`, `lb-error`, `lb-pending`, `lb-as-of` | [The hub's state](./chrome.md#the-hubs-state) |
+| `lb-hub-status` | `row` | `lb-path` | `lb-path`, `lb-load-state`, `lb-server-state`, `lb-error`, `lb-pending`, `lb-as-of` | [The hub's state](./chrome.md#the-hubs-state) |
 
 No query parm is reserved: a column of `lb-url` whose name begins with
 `lb-` is never a query parm.
@@ -202,13 +196,6 @@ imports them rather than writing a string.
 | `ATTR_QUERY_ROW_COUNT`    | `lb-query-row-count`                    |
 | `ATTR_QUERY_UNPLACED_COUNT` | `lb-query-unplaced-count`             |
 | `ATTR_QUERY_ORDER`        | `lb-query-order`                        |
-| `ATTR_GROUP`              | `lb-group`                              |
-| `ATTR_GROUP_LIVE`         | `lb-group-live`                         |
-| `ATTR_GROUP_COLUMN`       | `lb-group-column`                       |
-| `ATTR_GROUP_VALUE`        | `lb-group-value`                        |
-| `LIVE_GROUP`              | `[lb-group-live]`, the selector for a group's element |
-| `ATTR_COUNT`, `ATTR_SUM`, `ATTR_AVG`, `ATTR_MIN`, `ATTR_MAX` | `lb-count`, `lb-sum`, `lb-avg`, `lb-min`, `lb-max` |
-| `AGGREGATES`              | All five aggregate attributes           |
 | `ORDER_DESCENDING`        | `-`, written before a column in an order |
 | `COLUMN_TYPES`            | `number`, `boolean`, `text`             |
 | `CHOICES_QUERY`           | `lb-choices`                            |
@@ -224,7 +211,6 @@ imports them rather than writing a string.
 | `REQUESTED_CREATED`, `REQUESTED_CHANGED`, `REQUESTED_MOVED` | `created`, `changed`, `moved` |
 | `ATTR_ROW_UNPLACED`       | `lb-row-unplaced`                       |
 | `ATTR_ROW_LEAVING`        | `lb-row-leaving`                        |
-| `ATTR_GROUP_LEAVING`      | `lb-group-leaving`                      |
 | `ATTR_REQUEST`            | `lb-request`                            |
 | `LB_EVENT_NAME`           | `lb-request`, the event every request travels as |
 | `LB_DONE_EVENT_NAME`      | `lb-request-done`                       |
@@ -236,13 +222,12 @@ imports them rather than writing a string.
 | `LB_COMMANDS`             | All four commands                       |
 | `LB_COMMAND_PREFIX`       | `--lb-`                                 |
 | `ATTR_ROW_EDITING`        | `lb-row-editing`                        |
-| `ATTR_SELECT`             | `lb-select`                             |
-| `ATTR_ROW_SELECTED`       | `lb-row-selected`                       |
 | `LB_RESERVED_PREFIX`      | `lb-`                                   |
 | `REQUEST_ROW_INSERT`      | `lb-row-insert`                         |
 | `REQUEST_ROW_UPDATE`      | `lb-row-update`                         |
 | `REQUEST_ROW_DELETE`      | `lb-row-delete`                         |
 | `LB_ROW_REQUESTS`         | All three request names                 |
+| `REQUEST_READ`            | `lb-read`, the hub's own read of a bound form's lists; markup never writes it |
 | `LB_METHODS`              | The four reserved methods               |
 | `BROWSER_LIFECYCLE`       | The browser callbacks the build refuses |
 | `KIND_ROW`                | `row`                                   |
@@ -250,8 +235,7 @@ imports them rather than writing a string.
 | `URL_QUERY`               | `lb-url`                                |
 | `URL_COLUMN_PATH`         | `lb-path`                               |
 | `URL_COLUMN_PAGE_LABEL`   | `lb-page-label`                         |
-| `URL_COLUMN_PAGE_UNKNOWN` | `lb-page-unknown`                       |
-| `HUB_QUERY`               | `lb-hub`                                |
+| `HUB_QUERY`               | `lb-hub-status`                         |
 | `HUB_COLUMN_LOAD_STATE`   | `lb-load-state`                         |
 | `HUB_COLUMN_SERVER_STATE` | `lb-server-state`                       |
 | `HUB_COLUMN_ERROR`        | `lb-error`                              |
@@ -268,7 +252,7 @@ imports them rather than writing a string.
 | `ATTR_EXP_TEMPLATE`       | `lb-exp-template`                       |
 | `ATTR_PAGE`               | `lb-page`                               |
 | `ATTR_PAGE_TITLE`         | `lb-page-title`                         |
-| `DEVELOPER_ATTRIBUTES`    | The eighteen attributes a developer writes |
+| `DEVELOPER_ATTRIBUTES`    | The fourteen attributes a developer writes |
 | `HUB_TAG_NAME`            | `lb-hub`                                |
 | `LB_ENDPOINT`             | `/lb`                                   |
 | `LB_REQUEST_TIMEOUT_MS`   | `10000`                                 |

package/docs/reference/page-files.md

@@ -165,14 +165,11 @@ name:
 | `name`   | The request name, from `lb-request`                      |
 | `query`  | The query the request is for                             |
 | `key`    | The key of the row the request is for                    |
-| `keys`   | The keys of the rows selected, in place of `key`         |
 | `rows`   | A form's nested rows, by query: each `key` and `values`  |
 | `values` | The gathered control values, by column                   |
 
 The hub sends `query`, `key` and `values` when it finds them; see
-[Gathering](./data-binding.md#gathering). It sends `keys` for a request that
-acts on the rows the user selected; see
-[Selecting rows](./data-binding.md#selecting-rows).
+[Gathering](./data-binding.md#gathering).
 
 ### onPageEnter
 
@@ -264,12 +261,6 @@ are one vocabulary:
 | `lb-row-update` | `rowUpdate` | `query`, `key`, `values`, and `rows` from a form |
 | `lb-row-delete` | `rowDelete` | `query`, `key`   |
 
-An `lb-row-update` or `lb-row-delete` carrying `keys` runs `rowUpdate` or
-`rowDelete` once for each key, with that key, so a handler written for one
-row serves several. The patches the runs return are laid together, and the
-refresh set runs once. A `url()` returned for one of several rows is
-reported and ignored. A declared request receives `keys` as it is.
-
 `rows` holds the rows of a query nested in the form the request came from,
 by query name, each with its `key` and the `values` of its own controls; see
 [A form over a set of rows](./data-binding.md#a-form-over-a-set-of-rows).
@@ -386,8 +377,6 @@ A change that seems to need a refresh usually has a patch:
   [order](./data-binding.md#order), or leaves it where it stands under the
   list's [`lb-manual`](./data-binding.md#placing-by-hand); a refresh would do
   the same.
-- A group that appears or goes: the hub makes a group with its first row
-  and removes it with its last, so no row stands in for an empty one.
 - A row whose other columns change with the edit: re-read the row and patch
   it.
 - Rows the database removes with a deleted one: select their keys before the

package/docs/reference/server.md

@@ -199,7 +199,6 @@ interface HubRequest {
   name: string;
   query?: string;
   key?: string;
-  keys?: string[];
   values?: Record<string, string>;
   rows?: Record<string, { key: string; values: Record<string, string> }[]>;
 }

package/docs/testing.md

@@ -210,12 +210,11 @@ evidence here.
   is not counted
 - the order and the filter place all rows and a patch alike, except where
   the list's `lb-manual` leaves a side to the user, which keeps its rows
-  standing and stamped until they are placed again; groups come and go with
-  their rows to any depth, aggregates follow every landing, and every change
+  standing and stamped until they are placed again, and every change
   leaves a stamp a stylesheet can see (`lb-order.test.ts`)
 - a filter's text reads and passes values as documented, and a choice of
   order or filter places the rows already landed again, hiding rows and
-  groups and leaving them out of counts and aggregates (`lb-choices.test.ts`)
+  leaving them out of counts (`lb-choices.test.ts`)
 - `lb-show` moves an element into a template and back, and landing reaches
   inside it
 - a row whose values arrive as it already shows them is not filled again,
@@ -296,8 +295,6 @@ What the hub is tested for here:
   queries land
 - a form pointed at a row by `commandfor` fills from the row the hub holds,
   and a row not yet entered sends no update or delete
-- ticked `lb-select` rows travel as `keys`, and the selection clears once
-  the request succeeds
 - a refusal lands its message on the element that committed and on each
   control it names
 - `lb-request-done` reaches the element that committed and its ancestors

package/package.json

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