@vernikr/size-report 2.8.0 → 2.8.2

package/README.md

@@ -10,7 +10,7 @@ shows.
 
 ## Status
 
-**Release 2.8.0 (2026-09-18).** The tool lives as a package of its own: the registry name is
+**Release 2.8.2 (2026-09-18).** The tool lives as a package of its own: the registry name is
 `@vernikr/size-report` (published by tag from CI, with no secret). A project may keep no settings at
 all: without a config file the tool derives them from the project itself and says so in one line,
 and `--init` pins what was derived into a file. The report is **one file**, the self-contained page
@@ -19,6 +19,41 @@ is installed and on the first run. The version is in the manifest, and every rel
 the journal — `worklog/` for today's entries, `worklog/archive/WORKLOG.md` for the earlier ones:
 what changes in the numbers is measured rather than retold.
 
+2.8.2 is about the page's own sources and the checks that guard them, and its figures are measured rather than retold.
+**The four page suites that went quiet with the `<table>` are alive again against the window:** `test/page-view.test.js`,
+`page-cols`, `page-tree` and `page-choice` read the grid and the panel they guard rather than markup that no longer
+exists, and what they promise is what they hold — the pasted program with no second calculation, the sparse block, the
+recount by the choice, the order of the columns, the tree's folds and its memory, the link's refusals. **Their readers
+are no longer each suite's own:** `tools/page-harness.js` keeps one set of them (a file's path at HEAD, the rows the
+window built, the numbers of a row and its captions, a folder's and a category's switch, the place the shell stands at),
+and the copies the suites carried left with it. **And the page's chapters shed the duplication the same request
+found:** the choice's record and the folded tree share one reading and one writing of the browser's memory
+(`appLoad`/`appKeep`), a folder's two figures come from one walk of its subtree (`appSub`), the three walks over the
+metrics and the files of a record became the panels' one question asked twice (`appReach`), and the three paths of a
+click became one drawing (`appChanged`) — while two rules that never took effect went with them (a dead `.cap` of the
+styling, an undefined colour under the folding sign). Measured in bytes for the same history: the chapters **−745 B**
+(37 lines), the suites **−18 462 B** (251 lines), the harness **+4 328 B** — the tree loses **14 879 B and 220 lines**,
+and the artifact **85 730 → 84 991 B**, its program and its styling being exactly what the chapters are. The checks go
+89 → **86** in the fast profile and 194 → **191** in the full one: what a reader of the page does is one place now
+rather than five, and a check that read the table it no longer has is not a check. The figures and the reasoning stand
+in `worklog/0210-page-suites-on-the-window.md`.
+
+2.8.1 is the drawing of the page put right after its table became a window, and its figures are measured rather than
+retold. **The panel and the table were sharing one class:** the table's rows were styled by a bare `.row` while the
+panel's own rows are `.panel .row`, so the table's rule took the metrics row and the three method lines out of the flow
+and painted them over one another — every rule of the shared part now hangs off `#grid`, and a check reads the selector
+list of that sheet rather than a sample of the page. **The numbers were placed from the grid's left edge while the commit
+column is pinned over it**, which hid the first column — the overall total — completely; they begin at the column's right
+edge now, a 220px figure written in the script and in the styling and held together like the three beside it. **The order
+of the columns comes from the numbers rather than from the commit's list of paths**: a commit can touch a file without
+moving it — this package's own attachment to itself, 2.7.0 → 2.8.0, is one character for another — and a column of empty
+cells standing in front of the table is what a reader calls a broken order, so a file's newest move decides its place;
+the engine's mark `last` stays in `--data` while the page's block no longer carries it. **One border and one height:**
+every line of the table is 1px of one colour (the header's two lines were 2px and another shade) and the header is two rows
+of the table's own height, while a file's name is centred over its group. The artifact grows 351 B for it — 85 495 B
+against 85 144 B of one history. The checks go 88 → **89** in the fast profile and 193 → **194** in the full one; the
+figures and the reasoning stand in `worklog/0209-page-drawing-order.md`.
+
 2.8.0 is about what the report costs whoever opens it, and its figures are measured rather than retold.
 **The table is a window of itself:** every row and every column in sight is built, plus four beyond each edge so that
 the edge of the window is never seen empty, while the rest of the table exists as the extent of the scrolled box and
@@ -33,11 +68,10 @@ stripe over a drawing is gone with the freeze it was drawn for**: a switch costs
 for an indicator to indicate, and `src/page/work.js` left the tree with it. A virtualizer library was measured and not
 taken — `@tanstack/virtual-core` is ~6.7 kB gzip and headless, `virtua`'s grid is experimental and `Clusterize.js`
 knows rows and not columns — because each would be vendored into the artifact, which the report then measures as its own
-bytes. **The checks of the old table are deactivated while it is rebuilt:** `test/page-view.test.js`, `page-cols`,
-`page-tree` and `page-choice` skip every check with its reason at the top of the file, and this document names them
-where they are the promise-holders of what they described; `test/page-grid.test.js` is what guards the window meanwhile.
-The figures and the reasoning stand in `worklog/0208-table-window.md`. The checks grow with the work: 81 → **88** in the
-fast profile and 186 → **193** in the full one.
+bytes. The checks of the old table went quiet with it, each naming its reason, and 2.8.2 brought them back against the
+window; `test/page-grid.test.js` is what guards the window itself. The figures and the reasons stand in
+`worklog/0208-table-window.md`. The checks grow with the work: 81 → **88** in the fast profile and 186 → **193**
+in the full one.
 
 2.7.0 is about the page and what a reader does with it, and its figures are measured rather than retold.
 **The report's address stays clean:** a switch writes the record into the browser's memory and nothing into the
@@ -237,11 +271,10 @@ commits and installs hooks; the reason for each expensive file is named line by
 
 | Run | Command | Checks |
 |---|---|---|
-| Fast — every edit | `pnpm test` | **88 of 193** |
-| Full — release and CI | `pnpm test:all` | **193** |
+| Fast — every edit | `pnpm test` | **86 of 191** |
+| Full — release and CI | `pnpm test:all` | **191** |
 
-No check is lost or weakened: the full run starts all 186 with the same files, the fast one takes part
-of them. The default is the full run — a file becomes fast only explicitly and with a reason — so new
+No check is lost or weakened: the full run starts every file, the fast one takes part of them. The default is the full run — a file becomes fast only explicitly and with a reason — so new
 expensive work cannot quietly move into the fast one. Two declarations guard that:
 `test/suites.test.js` (every file classified, and a reason for each) and the documentation guard
 `test/docs-numbers.test.js` (the numbers in the table above).
@@ -367,10 +400,14 @@ a *single* cell of this repository's report, 539 ms for 6 000 (`probes/step-12-c
 table is **2 460 nodes and 0.15 GB**, a hundredth of the nodes and a tenth of the memory, and the whole-table scroll
 pass that took 36 s of task time over 60 steps takes **1.1 s over 251** (`worklog/0208-table-window.md`). **The columns
 are one width and fixed, 70px each**: the numbers are short and of one kind, and a width that came out of the text is a
-measurement of every cell of the column — the very cost this step removed. A file's name over its group is cut with an
-ellipsis rather than wrapped (the header is one line high and the whole name stands in the tooltip). The geometry is
-three figures — a column, a row, the header — written in the styling and in the script that counts the window's ordinals
-in them, and `test/page-grid.test.js` reads both and holds them together.
+measurement of every cell of the column — the very cost this step removed. A file's name stands centred over its group
+and is cut with an ellipsis rather than wrapped — the whole name stays in the tooltip. The header is two lines of one
+row each, the numbers begin at the
+right edge of the pinned commit column rather than under it, and every line of the table — under a row, under a header
+cell, along a group's left edge — is one pixel of one colour: a heavier line would promise a hierarchy to work out
+rather than read. The geometry is four figures — a column, a row, the header, the pinned column — written in the styling
+and in the script that counts the window's ordinals in them, and `test/page-grid.test.js` reads both and holds them
+together.
 
 **A click builds the window again, and that is cheap now.** A file switched off is simply not among the columns that
 are built, and a metric switched off not among the metrics: there is nothing to hide and nothing to carry, and the
@@ -387,15 +424,16 @@ virtualizes rows out of a string of all of them and knows nothing of columns —
 the artifact, whose bytes this very tool measures. What is left to write after any of them is what the chapter is: the
 window, the cells, the header and the pinned column.
 
-**The columns the last commit touched come first.** The report is rebuilt after every commit, and a
-reader's first question is what that edit brought. The mark comes from the history rather than from the
-numbers — an edit that changed no size is an edit too — and it is taken from the last commit that
-touched at least one column, counting back from the top: a commit that went past the columns, above all
-the report itself, which the hook commits, is skipped, or the mark would depend on the report's own
-commit, the same run would give different bytes and the hook would commit the report a second time.
-Inside each part the order stays as it comes from the settings (the sort is stable): the order of the
-columns is what the reader is used to, and his choice of files does not rearrange it
-(`test/page-grid.test.js`, the contract's `last` field).
+**The columns whose numbers last moved come first.** The report is rebuilt after every commit, and a
+reader's first question is what that edit brought. The mark is taken from the numbers rather than from
+the commit's list of paths, and that is the whole of the difference: a commit can touch a column without
+moving it — a version bumped inside a line of the same length, this package's own attachment to itself is
+one — and a column of empty cells standing in front of the table is what a reader calls a broken order.
+The rest follows in the settings' order (the sort is stable), so the order of the columns is what the
+reader is used to, and his choice of files does not rearrange it (`src/page/table.js`; the rule is counted
+from the contract's own rows in `test/page-grid.test.js`). The engine still answers with `last` — the
+columns the newest commit touched — in `--data`; the page no longer reads it, and the block it carries no
+longer holds it.
 
 **On a wide window the panel stands to the left of the table and takes no room from the numbers** (from
 900px, `src/page/app.css`). That is not decoration: a desktop has much side room and little vertical
@@ -578,13 +616,13 @@ acceptance for each.
 | `src/size-table.js` | The package's entry point: a re-export of the public API (55 names) and no calculation of its own |
 | `src/derived.js` | The report's shared calculation: totals, deltas, a cell, a commit's caption — one for the engine and the page's program |
 | `src/css.js` | Reading the styling from disk: which sets of styles exist and what role each has |
-| `src/table.css` | The report's table: the geometry of the window — one width per column, one height per row, the header — the sticky header and commit column, a file's caption cut with an ellipsis, the colour of deltas |
+| `src/table.css` | The report's table: the geometry of the window — one width per column, one height per row, the two lines of the header, the pinned commit column — the sticky header and commit column, one 1px line of one colour for every border, a file's caption centred over its group and cut with an ellipsis, the colour of deltas |
 | `src/page/app.css` | The page's styling on top of the shared part: the panel with the file tree and its sticky row of categories (a column on the left on a wide screen, the page fitting the window), the empty states, a narrow window |
 | `src/page/payload.js` | The page's block in sparse form, and the one place that unrolls it back: the history as changes (a file's appearance, its moves, its disappearance) turned into the snapshots the calculation and the table already speak — a value that did not move is one object shared by the rows that hold it |
 | `src/page/state.js` | The page's state: the report's data (the block unrolled by the payload chapter), the view of the checkboxes, the pointer "which path is which column", the unfolded folders, the record's passport, the browser's memory and the link that is read out of the address — a chapter of the page's program |
 | `src/page/dom.js` | The page's nodes: the small helpers of markup (`appEl`, `appBox`) — one set for the panel and the table alike |
 | `src/page/panel.js` | The panel of choices: the switches of metrics and files, the categories, the tree of the project's paths (files outside the report keep a checkbox off with a reason and stand after the rest, and a hidden name after every visible one; the tree opens folded and folders carry a sign that hides the subtree by a class rather than by a rebuild); built once, with the fields of the switches and of the folders and categories written where they stand |
-| `src/page/table.js` | The page's table as a window: the rows and the columns the reader can see (plus four beyond each edge), a cell, a commit's caption, the header, the empty states and the two figures of the window — markup over the shared calculation, with the totals counted per row from the choice, the geometry in pixels that the styling mirrors, and the reason a library was not taken |
+| `src/page/table.js` | The page's table as a window: the rows and the columns the reader can see (plus four beyond each edge), a cell, a commit's caption, the header, the empty states and the order of the columns — markup over the shared calculation, with the totals counted per row from the choice, the geometry in pixels that the styling mirrors, and the reason a library was not taken |
 | `src/page/app.js` | Assembling and starting the page: the first drawing, then a switch that builds the window again and writes the fields it reached without making a node of the panel; an anchor change; pasted into the assembled page |
 | `src/page/build.js` | Assembling the page: data, styling and program in one file with no external references — the pasted text is **squeezed** on the way in (comments and indentation out, the same stripping the `min` metric counts) while the sources keep them, and the result is guarded by the stripper's own `assertCompilable` |
 | `src/git.js` | The only border where git is called: the pinned settings, blobs by the batch, the history, the comparison with the working tree |
@@ -617,7 +655,7 @@ acceptance for each.
 | `test/api.test.js` | The package's public API: the list of names is frozen, and splitting the engine may not change it |
 | `eslint.config.js` | The rules of formatting: the same as the consumer project's, plus a ban on gluing operators into one line (`pnpm run lint`, `pnpm run lint:strict`) |
 | `tools/harness.js` | The harness of the checks: paths, clones of the fixture (including one shared per suite and one with CRLF), running the tool, reading refusals, hashes |
-| `tools/page-harness.js` | The harness of the contract and page checks: the contract data, the assembled page, reading it in a real DOM, the panel's switches, the page's calculation and its decoder evaluated from their sources, the block unpacked, and the platform's unpacker put into jsdom (which has none) — one for seven suites |
+| `tools/page-harness.js` | The harness of the contract and page checks: the contract data, the assembled page, reading it in a real DOM, one set of readers for every page suite (a file's path at HEAD, the rows the window built and their numbers, the captions over them, the order of the columns, a folder's and a category's switch, the place the shell stands at), the page's calculation and its decoder evaluated from their sources, the block unpacked, and the platform's unpacker put into jsdom (which has none) — one for seven suites |
 | `tools/suites.js` | The split of the suite: which files go into the fast run (with a reason for each) and why every dear one is in the full run |
 | `tools/run-tests.js` | Running the suite (`pnpm test`, `pnpm test:all`, `pnpm run suites:measure`): each file's duration measured on its own, and the counts of checks adding up |
 | `tools/docs-facts.js` | Reading facts out of the documentation — one layer for the four checks of the documentation guard: what a document names (paths, calls, section addresses) against what the repository holds |
@@ -633,11 +671,11 @@ acceptance for each.
 | `test/refusals-catalog.test.js` | The guard of the refusal catalogue: every refusal site in the sources has an entry, every entry declares its advice, and refusals handed to another check are really accepted by it (the named file and line are checked) |
 | `test/contract-data.test.js` | The data contract: the numbers against the reference, the set of fields against the derived quantities, the metric's method against the way the numbers were counted — and the round trip through the page's sparse block, which restores the contract whole and twice over the same bytes |
 | `test/contract-derived.test.js` | The derived quantities against the artifact's numbers: a row's totals, a cell's delta and the delta of a total — on the code that lies in the tree |
-| `test/page-grid.test.js` | The grid of the page as a window: what the reader sees is built and no more, the geometry of the styling against the script's, the rows and the columns that a scroll builds and drops, a number under its own caption, a file and a metric switched off, and every row of the window against the engine's own calculation |
-| `test/page-view.test.js` | The assembled page: pasted with no copy of the calculation, self-contained, the empty states, the styling, the switches, a click that makes no table and the carried totals against the engine's own sums — **deactivated** while the table is rebuilt, every check skipped with its reason in the file |
-| `test/page-tree.test.js` | The panel's file tree: folders by the project's paths, three states, the subtree, files and folders outside the report (a checkbox off, a place after the rest), the hidden names at the end of a level, the tree that opens folded and the unfolding the memory keeps, folding without a rebuild and a scroll a click does not touch — **deactivated** with the table, the checks skipped with their reason |
-| `test/page-choice.test.js` | The reader's choice and the work a click starts: the memory and a revisit, someone else's report, a foreign and a broken record, an address that stays clean, a link read at opening and on an open page, and the drawing of a long switch in a task of its own behind the stripe — **deactivated**: the choice and the link are the same, while the counts and the stripe are not |
-| `test/page-cols.test.js` | The fixed layout the page carries: a column's width is counted from the model rather than measured in a laid-out cell, the clip keeps a caption inside its column, the sticky header and commit column keep their edges, and the table names its own width — **deactivated** with the table: the columns are one fixed width now |
+| `test/page-grid.test.js` | The grid of the page as a window: what the reader sees is built and no more, the geometry of the styling against the script's, the rows and the columns that a scroll builds and drops, a number under its own caption, a file and a metric switched off, every row of the window against the engine's own calculation, and the drawing's own rules — the order of the columns by the numbers, one border, the header's rows of one height, and the panel out of the shared styling's reach |
+| `test/page-view.test.js` | The assembled page: pasted with no copy of the calculation, self-contained, the sparse block, the recount by the choice, every total of the window against the engine's own sums, no mark of precision left on a cell, the shared styling pasted once and the delta colour set once, the empty states, and the switches' focus |
+| `test/page-tree.test.js` | The panel's file tree: folders by the project's paths, three states, the subtree, files and folders outside the report (a checkbox off, a place after the rest), the hidden names at the end of a level, the tree that opens folded and the unfolding the memory keeps, folding without a rebuild and a scroll a click does not touch |
+| `test/page-choice.test.js` | The reader's choice: the memory and a revisit, someone else's report, a foreign and a broken record, an address that stays clean, a link read at opening and on an open page, and a host without an unpacker that is told so in words |
+| `test/page-cols.test.js` | The columns of the grid: their order by the newest row a file's numbers moved in, a caption over exactly the metrics of its group, and a choice that moves no other column |
 | `test/module.test.js` | A module under a `.js` extension: measured without touching the settings; the stripper's guard is alive (proved by mutation) and does not accuse the innocent |
 | `test/guard.test.js` | Parsing a module: it goes through a thread, both paths give one verdict, the fallback works with the thread's file away, and hundreds of parses are cheaper than a launch |
 | `test/runner.test.js` | Reading a process's output: chunks are glued as buffers rather than appended to a string — a multi-byte character at a chunk border does not turn into two replacement characters |
@@ -717,7 +755,7 @@ The same release can be taken by a reference to the repository — installation
 registry, but stays tied to a revision:
 
 ```bash
-pnpm add -D github:vernikr/size-report#v2.8.0
+pnpm add -D github:vernikr/size-report#v2.8.2
 ```
 
 With no network (or nothing to fetch from codeload) — the tarball: `pnpm pack` in the package clone, then
@@ -729,7 +767,7 @@ the branch moves on the installation fails with `Could not resolve <sha> to a co
 observation rather than reasoning: the short pin `6530237` installed while `main` stood on it and stopped
 working at the very next commit, while the same sha in full installed. A branch name (`#main`) and a tag
 are both accepted, but a branch is a moving target and a tag is constant: this release stands on the tag
-`v2.8.0`, which is also the one in the example (forty characters work as well, but they have to be copied
+`v2.8.2`, which is also the one in the example (forty characters work as well, but they have to be copied
 out of the history by eye).
 
 The revision in the example is a part of the claim rather than decoration: what is described below is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vernikr/size-report",
-  "version": "2.8.0",
+  "version": "2.8.2",
   "author": "vernikr",
   "repository": {
     "type": "git",
@@ -65,7 +65,7 @@
     "report"
   ],
   "devDependencies": {
-    "@vernikr/size-report": "2.7.0",
+    "@vernikr/size-report": "2.8.1",
     "c8": "10",
     "dependency-cruiser": "17",
     "eslint": "^9.18.0",

package/src/page/app.css

@@ -14,7 +14,10 @@
   --pad: clamp(16px, 3vw, 34px);
   --radius: 10px;
   --muted: rgba(127, 127, 127, .85);
-  --line: rgba(127, 127, 127, .32);
+  /* The same grey as the table's own lines (`--grid-line` of `src/table.css`): the frame around the numbers and the rows
+   * inside it are one drawing, and a second grey for the chrome is what makes a page look assembled from two. The two
+   * declarations are held together by the check that reads the borders of both sheets. */
+  --line: rgba(127, 127, 127, .25);
   --tint: rgba(127, 127, 127, .07);
 }
 
@@ -42,7 +45,7 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
 }
 .panel fieldset { margin: 0; padding: 0; border: 0; }
 .panel fieldset + fieldset { margin-top: 10px; }
-.panel legend, .panel .cap {
+.panel legend {
   padding: 0;
   color: var(--muted);
   font-size: 11px;
@@ -50,7 +53,6 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
   text-transform: uppercase;
   letter-spacing: .07em;
 }
-.panel .cap { display: block; margin-bottom: 4px; }
 .panel .row { display: flex; flex-wrap: wrap; gap: 3px 6px; align-items: center; }
 /* The way of counting is visible text under the switches: the token dictionary and the way of compression come from the
  * settings of the run rather than from a checkbox, so pointing a mouse is not enough — the reader has to see what produced
@@ -88,7 +90,7 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
   cursor: pointer;
   user-select: none;
 }
-.panel .tree li > .fold:hover { color: var(--ink); }
+.panel .tree li > .fold:hover { color: CanvasText; }
 
 /* A switch is a label around an input: one label and one click target, which is why a mouse, the keyboard (`Space` on the
  * input) and assistive technology all reach it. */
@@ -128,11 +130,7 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
 /* Numbers are denser than the page's text: there are more of them, they are shorter, and they are read by their digits. */
 #grid { font-size: 12.5px; }
 
-/* There is no stripe of progress over the page any longer, and that is a measurement rather than an omission: it stood
- * over the browser's relayout of the whole table, and the table is built as a window now — a switch costs a few
- * milliseconds (`src/page/table.js`), so an indicator would be a promise the page does not keep.
- *
- * The message about a link that came in stands above the table, so that it cannot be missed, while it does not push the
+/* The message about a link that came in stands above the table, so that it cannot be missed, while it does not push the
  * table away: one line in the place of the page. Its colour is the system one (the accent), for the page keeps no colours
  * of its own. */
 .notice {
@@ -231,7 +229,8 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
   h1 { font-size: 18px; }
   #grid { font-size: 12px; }
   .shell { max-height: calc(100vh - 260px); }
-  /* The commit column needs no rule of its own here any more: its width is the measure `--clip` of the shared part
-   * (`src/table.css`), and on a narrow screen that measure stands as it is. A shorter one would be `--clip: 150px`
-   * here — the adaptation the shared part cannot make for itself. */
+  /* The commit column keeps its width on a narrow screen, and that is deliberate rather than forgotten: the numbers
+   * are placed beside it by the script (`APP_COMMIT`), so a narrower column here would leave a band of empty grid
+   * between the two — one number would have to be read from the styling by the script, which is a second copy of a
+   * geometry the check holds together (`test/page-grid.test.js`). */
 }

package/src/page/app.js

@@ -4,15 +4,11 @@ import { appState, appTable, appWindow } from './table.js';
 import { appPanel, appPanelAll, appPanelState } from './panel.js';
 
 /* Assembling the report: the table is a window of the grid (`appWindow` of the table chapter) and nothing is built
- * that the reader cannot see. Two paths and no third, as before: `appPaint` draws the whole view (the first drawing, a
- * record from the browser's memory, a link in the address), while a click on a box does the same work for the choice
- * it made — and the difference between them is only how much of the view moved.
- *
- * What a click costs now: the window of rows and columns is built again — a few hundred cells, measured at 1–5 ms on
- * this repository's report — instead of a class on every node of a column of a table the browser lays out whole. The
- * stripe that used to stand over a long drawing (`src/page/work.js`) is gone with the reason for it: a switch no
- * longer has anything to wait for, and an indicator over work that is over before it could be painted would be a
- * promise the page does not keep.
+ * that the reader cannot see. Two paths and no third: `appPaint` draws the whole view (the first drawing, a record from
+ * the browser's memory, a link in the address), while a click on a box does the same work for the choice it made — the
+ * difference between them is only how much of the view moved. Neither has anything to wait for: a switch builds the
+ * window of the grid, a few hundred cells and milliseconds, so the page needs no indicator and keeps no promise it
+ * cannot measure.
  */
 
 // The table's window: made once, at the first drawing.
@@ -42,38 +38,36 @@ export function appPaint() {
   appWrite();
 }
 
-/* One file switched by the reader: the view, the window (its column is simply not among the columns that are built),
- * the fields it shows in. The message about a link fades here: by this action the reader has read it. */
-export function appSwitch(i, on) {
-  if (appView.files[i] === on) return;
-  appView.files[i] = on;
+/* One drawing after a click, whatever was clicked: the window of the grid (the columns of what is switched off are
+ * simply not among the columns that are built), the counts of the empty states, the fields the choice really reached
+ * (`touched` — a whole group is one click, and a field that did not move is not written) and the memory. The message
+ * about a link fades here: by this action the reader has read it. */
+function appChanged(touched) {
   appWindow(appCache, true);
   appCounts();
-  appPanelState([i]);
+  if (touched.length > 0) appPanelState(touched);
   appWrite();
   appNotice('');
 }
 
-/* A group switched at once — a folder or a category: the same work per file, then the fields of the files the choice
- * really reached (switching a folder on when a part of it was already on touches only the rest, and a field that did
- * not move is not written). The columns of the whole group leave or enter the window together. */
+// One file switched by the reader. A switch that changes nothing is not a change: the click costs no drawing.
+export function appSwitch(i, on) {
+  if (appView.files[i] === on) return;
+  appView.files[i] = on;
+  appChanged([i]);
+}
+
+/* A group switched at once — a folder or a category: the same work per file, and the fields of the files the choice
+ * really reached (switching a folder on when a part of it was already on touches only the rest). */
 export function appSwitchGroup(indexes, on) {
   const touched = indexes.filter((i) => appView.files[i] !== on);
   touched.forEach((i) => { appView.files[i] = on; });
-  appWindow(appCache, true);
-  appCounts();
-  appPanelState(touched);
-  appWrite();
-  appNotice('');
+  appChanged(touched);
 }
 
-/* One metric switched: the columns of that metric are not among the columns that are built any longer, so this is the
- * same drawing as a file's switch. The metric's own field is the box the reader just clicked. */
+/* One metric switched. Only the panel's metric box shows it, and that box is the one the reader just clicked. */
 export function appSwitchMetric() {
-  appWindow(appCache, true);
-  appCounts();
-  appWrite();
-  appNotice('');
+  appChanged([]);
 }
 
 /* The first drawing: the choice is already in the view (the link and the memory are applied above), the panel is

package/src/page/build.js

@@ -126,11 +126,13 @@ function uiText(page, loc) {
  * one (`src/page/payload.js`, `appDecode`), so the two places it is read are the encoder here and the decoder there.
  * `test/contract-data.test.js` holds the round trip between them.
  *
- * What the block leaves out besides the sparse form is the list of skipped commits: it changes with the report's own
- * commit (one with nothing to say lands in the list), and the file would stop being a **fixed point** — a rebuild
- * after its own commit would yield different bytes and the hook would commit the report forever. The page has no use
- * for the list at all: it does not show it. It stays available to the reader — `--data`, `--json` and `explain`
- * answer from the same run.
+ * What the block leaves out besides the sparse form are two facts the page does not read. The list of skipped commits
+ * changes with the report's own commit (one with nothing to say lands in the list), and the file would stop being a
+ * **fixed point** — a rebuild after its own commit would yield different bytes and the hook would commit the report
+ * forever; the page does not show it. The other is `last`, the columns the newest commit touched: the page orders the
+ * columns by the numbers themselves, which is a different fact (`src/page/table.js` says why), and the block would
+ * carry a list nothing asks for. Both stay available to the reader — `--data`, `--json` and `explain` answer from the
+ * same run.
  *
  * How much this is worth: the artifact of this repository carried 1 370 627 B of data as a snapshot per commit — 95 %
  * of the whole file — while nine tenths of the cells repeat the row above; the same history as changes is about 84 000
@@ -139,7 +141,7 @@ function uiText(page, loc) {
 /* The block's fields, in the order the encoder writes them. The shape is closed: a field added here has to be read in
  * the decoder, and the page's checks compare the block with this list rather than with a description of it. */
 export const PAGE_KEYS = ['schema', 'tool', 'report', 'hrefPrefix', 'strs', 'metrics', 'cats', 'files',
-  'catalog', 'rows', 'last', 'hist'];
+  'catalog', 'rows', 'hist'];
 
 /* The texts of the block, each written once. The dictionary is extended in the order of the walk `pagePayload` makes
  * — files in the column order, rows in the history order — and the order of the first appearance is what decides an
@@ -227,10 +229,8 @@ export function pagePayload(data) {
       r.section === null ? null : dict.of(r.section.head),
       r.section !== null && r.section.added ? 1 : 0,
       r.href === null ? null : dict.of(r.href.slice(prefix.length))]),
-    last: [],
     hist: history(keys, data.files, data.rows)
   };
-  data.last.forEach((on, i) => { if (on) out.last.push(i); });
   return out;
 }
 

package/src/page/panel.js

@@ -22,19 +22,18 @@ function appUnmeasuredBox(entry) {
     + (entry.why === 'rule' ? appUi.notMeasuredRule : appUi.notMeasuredChoice));
 }
 
-/* Every measured file of a subtree — what a folder's switch controls: a file outside the report has nothing to
- * switch. */
-function appIndexes(node) {
-  const out = node.files.slice();
-  node.dirs.forEach((sub) => { out.push(...appIndexes(sub)); });
-  return out;
-}
-
-/* How many files a subtree holds — including the ones that made it into no report. */
-function appCount(node) {
-  let n = node.files.length + node.others.length;
-  node.dirs.forEach((sub) => { n += appCount(sub); });
-  return n;
+/* A subtree in the two figures its folder shows: the measured files its checkbox controls, and how many files the
+ * folder holds at all — including the ones that made it into no report. One walk, because the two are asked together
+ * (a folder of five files with two measured reads "2/5"). */
+function appSub(node) {
+  const idx = node.files.slice();
+  let total = node.files.length + node.others.length;
+  node.dirs.forEach((sub) => {
+    const inner = appSub(sub);
+    idx.push(...inner.idx);
+    total += inner.total;
+  });
+  return { idx: idx, total: total };
 }
 
 /* A tree node: the measured files (columns), the project's other files and the subfolders. */
@@ -48,8 +47,9 @@ function appNode() {
  * without a single measured file stays in place with its checkbox off and unavailable: there is nothing to switch on
  * in it. */
 function appDirHead(name, here, sub) {
-  const idx = appIndexes(sub);
-  const total = appCount(sub);
+  const own = appSub(sub);
+  const idx = own.idx;
+  const total = own.total;
   const label = name + '/';
   let head;
   if (idx.length === 0) {
@@ -141,13 +141,14 @@ function appLeaf(leaf) {
 function appTreeList(node, prefix) {
   const list = appEl('ul', 'tree');
   const dirs = [...node.dirs.keys()].sort(appName)
-    .map((name) => ({ name: name, sub: node.dirs.get(name), inReport: appIndexes(node.dirs.get(name)).length > 0 }));
+    .map((name) => ({ name: name, sub: node.dirs.get(name), inReport: appSub(node.dirs.get(name)).idx.length > 0 }));
   const leaves = appLeaves(node);
   const inside = leaves.filter((leaf) => leaf.entry === null);
+  const outside = leaves.filter((leaf) => leaf.entry !== null);
   dirs.filter((d) => d.inReport).forEach((d) => list.appendChild(appDir(d.name, d.sub, prefix)));
   inside.forEach((leaf) => list.appendChild(appLeaf(leaf)));
   dirs.filter((d) => !d.inReport).forEach((d) => list.appendChild(appDir(d.name, d.sub, prefix)));
-  leaves.filter((leaf) => leaf.entry !== null).forEach((leaf) => list.appendChild(appLeaf(leaf)));
+  outside.forEach((leaf) => list.appendChild(appLeaf(leaf)));
   return list;
 }
 
@@ -237,10 +238,10 @@ function appRowBoxes(box) {
 }
 
 // A folder's field from its files: all on — checked, some — the third state, none — simply unchecked.
-function appDirState(box) {
-  const boxes = appRowBoxes(box);
+function appDirState(path) {
+  const boxes = appRowBoxes(appFields.dir[path]);
   const on = boxes.filter((b) => b.checked).length;
-  const input = box.querySelector('input');
+  const input = appFields.dir[path].querySelector('input');
   input.checked = on === boxes.length;
   input.indeterminate = on > 0 && on < boxes.length;
 }
@@ -267,29 +268,17 @@ function appDirPath(path) {
   return parts.slice(0, -1).map((_part, i) => parts.slice(0, i + 1).join('/'));
 }
 
-/* A click reaches a folder's field through the files below it: every folder on the path of a switched file shows the
- * share of what is left on. A folder without measured files has a field of its own too — it is off and unavailable,
- * which is not the reader's state and must not be overwritten here. */
-function appDirsOf(indexes) {
-  const seen = {};
-  indexes.forEach((i) => {
-    appDirPath(appFileAt(i)).forEach((path) => {
-      if (seen[path] === true) return;
-      seen[path] = true;
-      if (appFields.dir[path] !== undefined) appDirState(appFields.dir[path]);
-    });
-  });
-}
-
-// The same for the quick buttons of the categories: every category one of the switched files belongs to.
-function appCatsOf(indexes) {
+/* A click reaches the fields of a folder and of a category through the files below them — one walk for both, because
+ * it is one question: which groups the reader sees hold a switched file, and what do they show now. A field that is not
+ * there is left alone: a folder without measured files has a box of its own, off and unavailable, which is not the
+ * reader's state. */
+function appReach(indexes, fields, namesOf, stateOf) {
   const seen = {};
-  indexes.forEach((i) => {
-    const key = appData.files[i].category;
-    if (seen[key] === true || appFields.cat[key] === undefined) return;
-    seen[key] = true;
-    appCatState(key);
-  });
+  indexes.forEach((i) => namesOf(i).forEach((name) => {
+    if (seen[name] === true || fields[name] === undefined) return;
+    seen[name] = true;
+    stateOf(name);
+  }));
 }
 
 /* What a click changed, written where it stands: the files' own boxes, then the fields of the folders and categories
@@ -299,8 +288,8 @@ export function appPanelState(indexes) {
     const input = appFields.file[i];
     if (input !== undefined) input.checked = appView.files[i] === true;
   });
-  appDirsOf(indexes);
-  appCatsOf(indexes);
+  appReach(indexes, appFields.dir, (i) => appDirPath(appFileAt(i)), appDirState);
+  appReach(indexes, appFields.cat, (i) => [appData.files[i].category], appCatState);
 }
 
 /* The whole panel from the view: what a link, a record from the memory and the first drawing need. The metric boxes
@@ -309,5 +298,5 @@ export function appPanelAll() {
   appData.categories.forEach((c) => appCatState(c.key));
   appData.metrics.forEach((m) => { appFields.metric[m.key].checked = appView.metrics[m.key] === true; });
   appData.files.forEach((_f, i) => { appFields.file[i].checked = appView.files[i] === true; });
-  Object.keys(appFields.dir).forEach((path) => appDirState(appFields.dir[path]));
+  Object.keys(appFields.dir).forEach((path) => appDirState(path));
 }

package/src/page/payload.js

@@ -15,7 +15,9 @@
  * moved (deltas against its own previous record) or disappeared, and this chapter puts the snapshots back
  * together. The whole history walk is O(number of changes) rather than O(rows × files).
  *
- * The model after `appDecode` is exactly `--data`: the calculation (`rowModel`, `totalsOf`, `cellParts`,
+ * The model after `appDecode` is exactly `--data` but for one field: the history's mark `last` (the columns the
+ * newest commit touched) is not carried, because the page orders its columns by the numbers rather than by the
+ * commit's list of paths (`src/page/table.js`). The calculation (`rowModel`, `totalsOf`, `cellParts`,
  * `valueParts`), the table and the panel know nothing about the sparse form, so there is no second way to
  * count a row. A value that did not move is **one object shared by the rows that hold it** — the heap keeps
  * the distinct numbers rather than a copy per commit — and because every consumer reads `v[metric]` and
@@ -149,8 +151,6 @@ function appRowOf(p, r, values) {
 export function appDecode(p) {
   const keys = p.metrics.map((m) => appText(p, m[0]));
   const hist = appUnroll(p, keys);
-  const last = p.files.map(() => false);
-  p.last.forEach((i) => { last[i] = true; });
   return {
     schema: p.schema,
     tool: p.tool,
@@ -162,7 +162,6 @@ export function appDecode(p) {
       paths: f[2].map((i) => p.strs[i]), category: appText(p, f[3]), categoryBy: appText(p, f[4]) })),
     catalog: p.catalog.map((e) => ({ path: appText(p, e[0]), why: appText(p, e[1]) })),
     rows: p.rows.map((r, ri) => appRowOf(p, r, hist.rows[ri])),
-    now: hist.now,
-    last: last
+    now: hist.now
   };
 }

package/src/page/state.js

@@ -106,15 +106,16 @@ function appPassport() {
   return appPassportValue;
 }
 
-/* One record of the choice for everything: it goes both into the memory and into the address, so there are no two formats
- * of one state. Only what is switched off is kept, by name: "switched on" and "no record" are the same state, which is
- * why turning every checkbox back on removes the record instead of leaving a trace indistinguishable from a choice. */
+/* One record of the choice: only what is switched off is kept, by name. "Switched on" and "no record" are the same
+ * state, hence `null` rather than an empty record — turning every checkbox back on removes the record instead of leaving
+ * a trace indistinguishable from a choice. */
 function appRecord() {
   const metrics = {};
   const files = {};
   appData.metrics.forEach((m) => { if (!appView.metrics[m.key]) metrics[m.key] = false; });
   appData.files.forEach((_f, i) => { if (!appView.files[i]) files[appFileAt(i)] = false; });
-  return { v: 1, passport: appPassport(), metrics: metrics, files: files };
+  const empty = Object.keys(metrics).length === 0 && Object.keys(files).length === 0;
+  return empty ? null : { v: 1, passport: appPassport(), metrics: metrics, files: files };
 }
 
 // Whether a record is ours and of the right format — one rule for the memory and the address alike.
@@ -122,24 +123,40 @@ function appRecordOk(rec) {
   return rec !== null && typeof rec === 'object' && rec.v === 1 && rec.passport === appPassport();
 }
 
-/* The record goes into the browser's memory and nowhere else: it is written on the click itself, which is what survives
- * a closing, and the page's address keeps a clean tail — the report is a local page whose address is copied as it is,
- * and a reader's choice belongs in the browser that made it rather than in the tab's title bar. What a link sent from an
- * earlier release holds is still read (`appLinkUse`), and it is not written into the reader's memory: what came in is
- * not his choice until he changes something. */
-export function appWrite() {
-  if (appTransient) return;
-  const rec = appRecord();
-  const empty = Object.keys(rec.metrics).length === 0 && Object.keys(rec.files).length === 0;
+/* A record into the browser's memory or out of it, and what is read back from it: the two halves of the memory, written
+ * once, because the page keeps two records of the same kind under two keys — the choice and the unfolded tree — and
+ * their rules are one. Nothing but the browser's memory is written: it is written on the click itself, which is what
+ * survives a closing, and the page's address keeps a clean tail — the report is a local page whose address is copied as
+ * it is, and a reader's choice belongs in the browser that made it rather than in the tab's title bar. What a link sent
+ * from an earlier release holds is still read (`appLinkUse`), and it is not written into the reader's memory: what came
+ * in is not his choice until he changes something. */
+function appKeep(key, rec) {
   try {
-    if (empty) window.localStorage.removeItem(appKey);
-    else window.localStorage.setItem(appKey, JSON.stringify(rec));
+    if (rec === null) window.localStorage.removeItem(key);
+    else window.localStorage.setItem(key, JSON.stringify(rec));
   } catch (_e) {
     /* There is no memory (the browser grants this page none): the choice will not survive a closing, while the numbers
      * and the markup do not depend on it. */
   }
 }
 
+export function appWrite() {
+  if (!appTransient) appKeep(appKey, appRecord());
+}
+
+/* What the browser saved under a key: its absence, a foreign record, a broken one and a record of another report amount
+ * to the same thing here — nothing to read. `JSON.parse` of a missing value answers `null`, so the two absences need no
+ * telling apart. */
+function appLoad(key) {
+  let rec = null;
+  try {
+    rec = JSON.parse(window.localStorage.getItem(key));
+  } catch (_e) {
+    return null;
+  }
+  return appRecordOk(rec) ? rec : null;
+}
+
 /* A reset to "everything on": the border between "this is no longer in the report" and "switched off" is the record
  * rather than a missing value. A link carries the sender's whole choice, which is why it is applied to a clean view
  * rather than on top of someone else's. */
@@ -174,15 +191,12 @@ function appLinkRead() {
 }
 
 /* How many names in the link are unknown to this report: the reader has to be told about them — otherwise he would look
- * in the table for something that was never there. */
+ * in the table for something that was never there. The two tables the model already holds answer it: a file by its path
+ * at HEAD (`appMeasured`) and a metric by its key (`appMetric`), the same names a record is written in (`appFileAt`). */
 function appUnknown(rec) {
-  const known = {};
-  const metricKeys = {};
-  appData.files.forEach((_f, i) => { known[appFileAt(i)] = true; });
-  appData.metrics.forEach((m) => { metricKeys[m.key] = true; });
   let n = 0;
-  Object.keys(rec.metrics || {}).forEach((k) => { if (!metricKeys[k]) n++; });
-  Object.keys(rec.files || {}).forEach((k) => { if (!known[k]) n++; });
+  Object.keys(rec.metrics || {}).forEach((k) => { if (appMetric[k] === undefined) n++; });
+  Object.keys(rec.files || {}).forEach((k) => { if (appMeasured[k] === undefined) n++; });
   return n;
 }
 
@@ -213,23 +227,9 @@ export function appLinkUse() {
   return 'none';
 }
 
-/* Reading: only a record of ours — of our format version and our passport. Another report's record lies under another key,
- * while a foreign, outdated or broken one amounts to its absence. */
+// Reading: the reader's own choice, as he left it — another report's record lies under another key.
 export function appRead() {
-  let text = null;
-  try {
-    text = window.localStorage.getItem(appKey);
-  } catch (_e) {
-    return null;
-  }
-  if (text === null) return null;
-  let rec = null;
-  try {
-    rec = JSON.parse(text);
-  } catch (_e) {
-    return null;
-  }
-  return appRecordOk(rec) ? rec : null;
+  return appLoad(appKey);
 }
 
 /* Applying goes by name: a file is recognised by its path, a metric by its key. A name the report does not hold matches
@@ -248,37 +248,22 @@ export function appApply(rec) {
  * what the onlooker looks at rather than about which numbers are read, which is why it never goes into a link and never
  * leaves the browser. The tree opens folded, so **the unfolded folders are what is kept** (`true`) — the default is the
  * absence of the name, the same way "switched on" is the absence of a choice. A folder's name is its path ("src/page"),
- * so a vanished name simply means nothing, and unfolding nothing is the state the page opens in: then the record is not
- * kept at all rather than being kept empty. `appFoldKey` is set with the model (`appBoot`), for the reason the key
- * itself is. */
+ * so a vanished name simply means nothing. `appFoldKey` is set with the model (`appBoot`), for the reason the key itself
+ * is. */
 export function appFoldRead() {
-  let text = null;
-  try {
-    text = window.localStorage.getItem(appFoldKey);
-  } catch (_e) {
-    return;
-  }
-  if (text === null) return;
-  let rec = null;
-  try {
-    rec = JSON.parse(text);
-  } catch (_e) {
-    return;
-  }
-  if (!appRecordOk(rec)) return;
+  const rec = appLoad(appFoldKey);
+  if (rec === null) return;
   const open = rec.open || {};
   Object.keys(open).forEach((p) => { if (open[p] === true) appView.open[p] = true; });
 }
 
+/* What a folder's sign does with the memory: the unfolded folders are what is kept (`true`), so a tree folded whole is
+ * the absence of the record — the default — and the record goes away with the last unfolded folder. */
 export function appFoldSet(path, open) {
   if (open) appView.open[path] = true;
   else delete appView.open[path];
-  const rec = { v: 1, passport: appPassport(), open: Object.assign({}, appView.open) };
-  try {
-    if (Object.keys(rec.open).length === 0) window.localStorage.removeItem(appFoldKey);
-    else window.localStorage.setItem(appFoldKey, JSON.stringify(rec));
-  } catch (_e) {
-    /* There is no memory: what is unfolded will not survive a closing, while the view does not depend on it — the tree
-     * is unfolded exactly the way the reader unfolded it just now. */
-  }
+  const names = Object.keys(appView.open);
+  appKeep(appFoldKey, names.length === 0
+    ? null
+    : { v: 1, passport: appPassport(), open: appView.open });
 }

package/src/page/table.js

@@ -13,7 +13,8 @@ import { appData, appUi, appView } from './state.js';
  * to build less rather than to promise the browser will skip it. A grid of `position: absolute` rows has no layout to
  * be redone: a row is placed by its `top`, a column by the `left` of the group of cells that starts it, and the
  * browser never measures a cell to decide a width — every column is `--col` wide (70px), which is what the numbers
- * need and no more (the counted widths this step replaced were 47–70px).
+ * need and no more (the counted widths this step replaced were 47–70px), and they begin at the right edge of the
+ * pinned commit column (`APP_COMMIT`) rather than under it.
  *
  * **Why not a library.** A virtualizer for two axes is not a solved problem for a page like this one — measured from
  * the tarballs, `@tanstack/virtual-core` is ~6.7 kB gzip and headless (the rows and columns are two virtualizers and
@@ -37,10 +38,12 @@ import { appData, appUi, appView } from './state.js';
  */
 
 /* The geometry in pixels: written here and read by the styling (`src/table.css`), which is one copy too many — hence
- * `test/page-grid.test.js` holds the two together, and the report says the same numbers in its journal. */
+ * `test/page-grid.test.js` holds the two together, and the report says the same numbers in its journal. The header is
+ * two lines of one row each, and the commit column is as wide as the styling pins it. */
 export const APP_COL = 70;
 export const APP_ROW = 25;
-export const APP_HEAD = 44;
+export const APP_HEAD = APP_ROW * 2;
+export const APP_COMMIT = 220;
 
 /* How much more than the visible window is built, in rows and in columns. A window that ends exactly at the edge of
  * the shell shows an empty band while the browser scrolls a notch; four rows and four columns of slack are cheaper
@@ -53,15 +56,41 @@ export const APP_OVER = 4;
 export const APP_MIN_ROWS = 24;
 export const APP_MIN_COLS = 10;
 
-/* The order of the columns: the files the last commit touched come first — the report is rebuilt after every
- * commit, and a reader's first question is what that edit brought. Inside each part the order is the settings', and
- * it depends on the files rather than on the choice: that is what lets a column be switched off without moving the
- * others. */
+/* The order of the columns: the files whose numbers last moved come first, and the older the move the further right the
+ * column stands. A reader opens the report after a commit, and what he looks for is what that edit brought — while the
+ * rest may as well be ordered by the settings, which is the order of the ties.
+ *
+ * The mark is taken from the numbers rather than from the history's list of paths, and that is the whole of the
+ * difference: a commit can touch a column without moving it (a version bumped inside a line of the same length, this
+ * package's own attachment to itself is one), and a column of empty cells standing in front of the table is what a
+ * reader sees as a broken order. The list of paths is the engine's (`--data`), which is where a fact about a commit
+ * belongs; what stands here is a fact about the numbers.
+ *
+ * The order depends on the files rather than on the choice: that is what lets a column be switched off without moving
+ * the others. Counted once per document — the model does not change while the page is open — because every window the
+ * reader scrolls to asks for it. */
+function appRank() {
+  const rank = appData.files.map(() => -1);
+  let was = null;
+  appData.rows.forEach((row, i) => {
+    /* The rows of a file are the same object until it moves (`src/page/payload.js`), so one comparison per file and
+     * row says whether the file appeared, moved or went away at this commit — the three cases a cell is not empty. */
+    row.values.forEach((v, j) => { if (was === null || was[j] !== v) rank[j] = i; });
+    was = row.values;
+  });
+  return rank;
+}
+
+let appOrderValue = null;
+
 export function appOrder() {
-  const files = [];
-  appData.files.forEach((_f, i) => files.push(i));
-  files.sort((a, b) => (appData.last[a] === true ? 0 : 1) - (appData.last[b] === true ? 0 : 1));
-  return files;
+  if (appOrderValue === null) {
+    const rank = appRank();
+    const files = [];
+    appData.files.forEach((_f, i) => files.push(i));
+    appOrderValue = files.sort((a, b) => rank[b] - rank[a]);
+  }
+  return appOrderValue;
 }
 
 /* The files whose columns are built, in the order of the columns: what is switched off is not among them, which is
@@ -141,7 +170,9 @@ function appRow(cache, r, span) {
   else commit.appendChild(appCommit(appData.rows[i]));
   row.appendChild(commit);
   const cells = appEl('div', 'cells');
-  cells.style.left = (span.c0 * APP_COL) + 'px';
+  /* The numbers stand beside the commit column rather than under it: the column is pinned over the content, so what the
+   * grid holds begins where the column ends. */
+  cells.style.left = (APP_COMMIT + span.c0 * APP_COL) + 'px';
   for (let c = span.c0; c <= span.c1; c++) cells.appendChild(appCell(model, c, now, cache));
   row.appendChild(cells);
   return row;
@@ -173,7 +204,7 @@ function appHead(cache, span) {
   const count = cache.keys.length;
   const g0 = Math.floor(span.c0 / count);
   const g1 = Math.floor(span.c1 / count);
-  const left = (g0 * count * APP_COL) + 'px';
+  const left = (APP_COMMIT + g0 * count * APP_COL) + 'px';
   const head = appEl('div', 'head');
   head.appendChild(appEl('div', 'c-commit', appUi.commit));
   const groups = appEl('div', 'hgroups');
@@ -214,7 +245,7 @@ export function appSpan(cache) {
   cache.slot = cache.list.map((i) => cache.rank[i]);
   const cols = count * (cache.list.length + 1);
   const rows = appData.rows.length + 1;
-  cache.grid.style.width = (cols * APP_COL) + 'px';
+  cache.grid.style.width = (APP_COMMIT + cols * APP_COL) + 'px';
   cache.grid.style.height = (APP_HEAD + rows * APP_ROW) + 'px';
   if (count === 0) return { r0: 0, r1: -1, c0: 0, c1: -1 };
   const high = shell.clientHeight || APP_MIN_ROWS * APP_ROW;
@@ -237,11 +268,11 @@ export function appWindow(cache, redraw) {
   const was = cache.win;
   cache.win = span;
   if (redraw === true || was === null || was.c0 !== span.c0 || was.c1 !== span.c1) {
-    const head = cache.grid.querySelector('.head');
-    if (head !== null) head.remove();
-    cache.grid.insertBefore(appHead(cache, span), cache.grid.firstChild);
+    /* The grid holds the header and the rows of the window and nothing else, so the whole of it is thrown away rather
+     * than tracked piece by piece — and the rows that are made below say in the map that they are there. */
+    cache.grid.textContent = '';
     cache.rows.clear();
-    [...cache.grid.querySelectorAll('.row')].forEach((row) => row.remove());
+    cache.grid.appendChild(appHead(cache, span));
     for (let r = span.r0; r <= span.r1; r++) appPlace(cache, r, span);
     return;
   }

package/src/table.css

@@ -1,25 +1,29 @@
 /* The report's table: a grid of plain elements rather than a `<table>`, and only the part of it the reader looks at is
  * built (`src/page/table.js` says why, and what was measured).
  *
- * Three figures are the whole geometry — a metric column, a row and the header — and they are written twice, here and
- * in the script that counts the window's ordinals in them. Two copies of a number are two answers waiting to happen,
- * hence `test/page-grid.test.js` reads these three declarations and holds the script to them. The fourth, the commit
- * column's width, is the styling's alone: the script places the numbers from the left edge of the grid, and the caption
- * is pinned over them.
+ * Everything here hangs off `#grid`, and that is not a habit: this sheet is the package's **shared** part (`src/css.js`)
+ * while the page brings a `.panel .row` of its own, and an unscoped rule for the table's rows took that row out of the
+ * flow with it (the panel's switches stood on top of one another until the rules were scoped).
+ *
+ * Four figures are the whole geometry — a metric column, a row, the header and the commit column — and they are written
+ * twice, here and in the script that counts the window's ordinals in them. Two copies of a number are two answers waiting
+ * to happen, hence `test/page-grid.test.js` reads these four declarations and holds the script to them.
+ *
+ * One border: 1px of one colour — a row's bottom edge, a group's left edge, the lines of the header. A heavier line or a
+ * second colour would promise a hierarchy to be worked out rather than read.
  *
  * One type face for the whole table; numbers line up by their digits thanks to tabular-nums rather than through a
- * monospaced font. Every column is the same width and fixed: the numbers are short and of one kind, and a width that
- * came out of the text would have to be measured over every cell of the column — the very cost this step removed.
- * A file's caption over its group is cut with an ellipsis rather than wrapped (`appCaption`), because the header is one
- * line high and the grid is built of rows of one height.
+ * monospaced font. Every column is the same width and fixed: the numbers are short and of one kind, and a width that came
+ * out of the text would have to be measured over every cell of the column — the very cost this step removed. The header is
+ * two lines of one row each — `--head` is exactly two `--row` — and a name too long for its group is cut with an ellipsis
+ * rather than wrapped (`appCaption`) or run over its neighbour.
  */
 #grid {
   --col: 70px;
   --row: 25px;
-  --head: 44px;
+  --head: 50px;
   --commit: 220px;
   --grid-line: rgba(127, 127, 127, .25);
-  --grid-edge: rgba(127, 127, 127, .35);
   position: relative;
   font-variant-numeric: tabular-nums;
 }
@@ -28,8 +32,8 @@
  * painting — no layout and no script — while the width of the content gives the scrollbar its length and the script its
  * ordinals. The cells of a row are one grid of fixed tracks (`grid-auto-columns`): a cell cannot change the width of a
  * column, and it cannot push its neighbour. */
-.row { position: absolute; left: 0; width: 100%; height: var(--row); }
-.cells {
+#grid .row { position: absolute; left: 0; width: 100%; height: var(--row); }
+#grid .cells {
   position: absolute;
   top: 0;
   display: grid;
@@ -37,32 +41,42 @@
   grid-auto-columns: var(--col);
   height: var(--row);
 }
-.cells > span, .hgroups > span, .hmetrics > span { box-sizing: border-box; white-space: nowrap; }
-.cells > span { padding: 2px 4px; line-height: 20px; border-bottom: 1px solid var(--grid-line); }
-.num { text-align: right; }
+#grid .cells > span, #grid .hgroups > span, #grid .hmetrics > span { box-sizing: border-box; white-space: nowrap; }
+/* Two pixels of padding and a line of twenty: with the border, a cell is one `--row` high — the same for the header's
+ * cells as for the numbers, or the header would be a band of another rhythm. */
+#grid .cells > span {
+  padding: 2px 4px;
+  line-height: 20px;
+  border-bottom: 1px solid var(--grid-line);
+}
+#grid .num { text-align: right; }
 /* The left edge of a group — the total, and every file — is carried by the group's first metric. One class instead of
  * the four rules of "which metric is switched on": the window is built out of the files that are on, so which column
  * stands first in a group is the page's own answer rather than something the styling has to work out. */
-.cells > .g, .hmetrics > .g, .hgroups > .gh { border-left: 1px solid var(--grid-edge); }
+#grid .cells > .g, #grid .hmetrics > .g, #grid .hgroups > .gh { border-left: 1px solid var(--grid-line); }
 
 /* The header: one row of groups (the total and the files) over one row of metrics, stuck to the top edge of the shell,
  * and the commit column stuck to its left edge. Both carry an opaque background (Canvas), or the numbers would show
- * through them while the reader scrolls. */
-.head { position: sticky; top: 0; left: 0; z-index: 3; height: var(--head); background: Canvas; }
-.hgroups, .hmetrics { position: absolute; display: grid; grid-auto-flow: column; grid-auto-columns: var(--col); }
-.hgroups { top: 0; height: 22px; }
-.hmetrics { top: 22px; height: 22px; }
-.hgroups > span, .hmetrics > span { padding: 0 4px; line-height: 20px; border-bottom: 2px solid var(--grid-edge); }
-.hgroups > span { text-align: left; }
-/* A file's name is one line of a fixed room: a name that does not fit is cut with an ellipsis (`appCaption` puts the
- * whole of it into the tooltip) rather than wrapped — the grid is rows of one height — or run over its neighbour. */
-.hgroups > span { overflow: hidden; text-overflow: ellipsis; }
-.hmetrics > span { text-align: center; color: CanvasText; }
+ * through them while the reader scrolls. The two lines are placed by `top` and are one row high each, so the header
+ * aligns with the table below it rather than standing a size of its own. */
+#grid .head { position: sticky; top: 0; left: 0; z-index: 3; height: var(--head); background: Canvas; }
+#grid .hgroups, #grid .hmetrics { position: absolute; display: grid; grid-auto-flow: column; grid-auto-columns: var(--col); }
+#grid .hgroups { top: 0; height: var(--row); }
+#grid .hmetrics { top: var(--row); height: var(--row); }
+#grid .hgroups > span, #grid .hmetrics > span {
+  padding: 2px 4px;
+  line-height: 20px;
+  border-bottom: 1px solid var(--grid-line);
+}
+/* A file's name stands over its group of metrics and is centred on it: the group is a column of numbers, and a caption
+ * that began at its left edge would carry the eye to the wrong place. */
+#grid .hgroups > span { text-align: center; overflow: hidden; text-overflow: ellipsis; }
+#grid .hmetrics > span { text-align: center; color: CanvasText; }
 
-/* The commit column: a sticky cell of every row, so the commit a number belongs to is in sight while the reader
- * scrolls sideways. Its width is fixed, and a caption longer than it is clipped — the whole subject stands in the
- * tooltip. */
-.c-commit {
+/* The commit column: a sticky cell of every row, so the commit a number belongs to is in sight while the reader scrolls
+ * sideways. Its width is fixed and is the script's `APP_COMMIT` as well — the numbers are placed from the left edge of
+ * the grid *beside* the column, and a caption longer than it is clipped (the whole subject stands in the tooltip). */
+#grid .c-commit {
   position: sticky;
   left: 0;
   z-index: 2;
@@ -79,24 +93,24 @@
   white-space: nowrap;
   border-bottom: 1px solid var(--grid-line);
 }
-.c-commit a { color: inherit; }
-.head .c-commit { z-index: 6; height: var(--head); line-height: var(--head); border-bottom-width: 2px; }
+#grid .c-commit a { color: inherit; }
+#grid .head .c-commit { z-index: 6; height: var(--head); line-height: var(--head); }
 /* This block fills the commit column: the cell clips what does not fit, and the subject is what gives way (the flex
  * item of `flex: 1 1 auto`), while the date and the journal mark keep their own width. */
-.clip { display: flex; align-items: baseline; gap: 6px; width: 100%; }
-.when { flex: none; opacity: .7; }
-.subj { flex: 1 1 auto; min-width: 0; overflow: hidden; text-overflow: ellipsis; display: block; }
-.subj.plain { opacity: .7; }
-.sect { flex: none; opacity: .7; font-size: 11px; text-decoration: none; border-bottom: 1px dotted currentColor; }
+#grid .clip { display: flex; align-items: baseline; gap: 6px; width: 100%; }
+#grid .when { flex: none; opacity: .7; }
+#grid .subj { flex: 1 1 auto; min-width: 0; overflow: hidden; text-overflow: ellipsis; display: block; }
+#grid .subj.plain { opacity: .7; }
+#grid .sect { flex: none; opacity: .7; font-size: 11px; text-decoration: none; border-bottom: 1px dotted currentColor; }
 /* Growth green, fall red — by agreement with whoever asked for the report (growth is "more logic" rather than alarm). */
-.up { color: #1e8449; }
-.down { color: #c0392b; }
-.miss { opacity: .5; }
-/* The top row holds the current sizes: it is also what explains what the deltas below refer to. */
-.row.now > .c-commit { font-weight: 600; }
-.row.now > .c-commit, .row.now > .cells > span { border-bottom-width: 2px; }
+#grid .up { color: #1e8449; }
+#grid .down { color: #c0392b; }
+#grid .miss { opacity: .5; }
+/* The top row holds the current sizes: it is also what explains what the deltas below refer to — by its weight rather
+ * than by a heavier line, which would be a second border among the rows. */
+#grid .row.now > .c-commit { font-weight: 600; }
 /* A row's highlight is laid over rather than swapped in: the sticky column has to stay opaque, or numbers show through
  * it while the reader scrolls sideways. */
-.row:hover > .c-commit, .row:hover > .cells > span {
+#grid .row:hover > .c-commit, #grid .row:hover > .cells > span {
   background-image: linear-gradient(rgba(127, 127, 127, .08), rgba(127, 127, 127, .08));
 }