@vernikr/size-report 2.8.9 → 2.9.0

package/package.json

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

package/src/locales.js

@@ -36,7 +36,6 @@ export const LOCALES = {
       categoryFromConfig: 'из настроек',
       categoryByExtension: 'по расширению',
       all: 'все',
-      sub: '{tool} {version} · {artifact}',
       panelMethod: 'способ:',
       emptyMetrics: 'Ни одна метрика не выбрана — таблицу не из чего собрать. '
         + 'Включите хотя бы одну в панели выше: без метрик нет ни одной колонки с числом.',
@@ -49,10 +48,7 @@ export const LOCALES = {
       linkExtra: 'Часть ссылки пропущена: в этом отчёте нет {n} названных имён. '
         + 'Остальное применено.',
       unpack: 'Данные отчёта сжаты, а браузер не умеет их распаковать: в нём нет DecompressionStream. '
-        + 'Обновите браузер — таблицу показывать не из чего.',
-      note: 'Абсолютные размеры стоят один раз — в строке «{now}». Строк: {rows}: коммиты без '
-        + 'изменения объёма и коммиты, тронувшие только выключенные файлы, строк не получают. '
-        + 'Собрано из истории git: {command}.'
+        + 'Обновите браузер — таблицу показывать не из чего.'
     },
     note: {
       intro: 'Строка — коммит, колонка — файл. ',
@@ -94,7 +90,6 @@ export const LOCALES = {
       categoryFromConfig: 'from the settings',
       categoryByExtension: 'by extension',
       all: 'all',
-      sub: '{tool} {version} · {artifact}',
       panelMethod: 'method:',
       emptyMetrics: 'No metric is selected — there is nothing to build the table from. '
         + 'Turn on at least one above: without metrics there is no column holding a number.',
@@ -109,10 +104,7 @@ export const LOCALES = {
       /* The report's data lies in the file compressed and the browser unpacks it; this text is what a
        * browser without `DecompressionStream` gets instead of an empty table. */
       unpack: 'The report\u2019s data is compressed and this browser cannot unpack it: there is no '
-        + 'DecompressionStream. Update the browser — there is nothing to build the table from.',
-      note: 'Absolute sizes appear once — in the “{now}” row. Rows: {rows}: commits that change '
-        + 'no number, and commits touching only the disabled files, get no row. '
-        + 'Collected from git history: {command}.'
+        + 'DecompressionStream. Update the browser — there is nothing to build the table from.'
     },
     note: {
       intro: 'A row is a commit, a column is a file. ',

package/src/page/app.css

@@ -31,11 +31,11 @@ body {
   font: 14px/1.5 ui-sans-serif, system-ui, -apple-system, "Segoe UI", sans-serif;
   -webkit-text-size-adjust: 100%;
 }
-h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em; }
-.sub { margin: 0 0 calc(var(--gap) + 4px); color: var(--muted); font-size: 12.5px; }
+h1 { margin: 0 0 9px; font-size: 21px; font-weight: 650; letter-spacing: -.012em; }
 
 /* The panel of choices is a card: it separates the controls from the data and does not merge with the table that begins
- * below. */
+ * below. The report's heading opens it — the page has no band above the numbers, and the title belongs where the file it
+ * names is read from (see the markup in `src/page/build.js`). */
 .panel {
   margin: 0 0 var(--gap);
   padding: 12px 14px 13px;
@@ -54,10 +54,6 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
   letter-spacing: .07em;
 }
 .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
- * the number. */
-.panel .about { margin: 5px 0 0; color: var(--muted); font-size: 11.5px; }
 
 /* The file tree: nesting is shown by an indent and a level line, and a folder is a switch like a file — only its checkbox
  * answers for the whole subtree, while the number beside it says for how many files. The list is longer than the window,
@@ -155,9 +151,6 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
 }
 .state[hidden], .shell[hidden] { display: none; }
 
-.note { margin: 14px 0 0; max-width: 90em; color: var(--muted); font-size: 12px; }
-.note code { background: var(--tint); padding: 0 3px; border-radius: 3px; }
-
 /* The keyboard: the focus ring is visible on any background (the system accent colour) and shifts no layout. Journal links
  * and every switch are reachable with Tab. */
 :focus-visible { outline: 2px solid AccentColor; outline-offset: 2px; border-radius: 3px; }
@@ -169,10 +162,11 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
  *
  * The layout is a grid on `body` rather than a wrapper in the markup: the page is assembled by pasting chapters
  * (`src/page/build.js`), and adding nodes to it for the sake of styling would mean changing the page's shape in two places
- * instead of one. There are five rows, named by subject: the heading, the message about a link, the **working row**, the
- * empty state and the note. Only the working row stretches — the table gets all the remaining height and the panel no more
- * than that; the panel's own height is not "whatever came out" (it would push the table off the screen) but that same
- * working row, inside which it scrolls: a file list longer than the window is the usual case.
+ * instead of one. There are three rows, named by subject: the message about a link, the **working row** and the empty
+ * state — while the panel of choices spans them all in the left column, its heading inside it. Only the working row
+ * stretches — the table gets all the remaining height and the panel no more than that; the panel's own height is not
+ * "whatever came out" (it would push the table off the screen) but that same working row, inside which it scrolls: a file
+ * list longer than the window is the usual case.
  *
  * The threshold of 900px is the same as the adaptations' below: one border between "wide" and "narrow", or the page would
  * be left with no rule at all between two thresholds. */
@@ -185,21 +179,18 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
     overflow: auto;
     display: grid;
     grid-template-columns: minmax(230px, 300px) minmax(0, 1fr);
-    grid-template-rows: auto auto minmax(0, 1fr) auto auto;
+    grid-template-rows: auto minmax(0, 1fr) auto;
     column-gap: var(--gap);
     align-items: stretch;
   }
-  header { grid-area: 1 / 1 / 2 / -1; }
-  #notice { grid-area: 2 / 2 / 3 / 3; }
-  #shell { grid-area: 3 / 2 / 4 / 3; }
-  #state { grid-area: 4 / 2 / 5 / 3; align-self: start; }
-  #note { grid-area: 5 / 2 / 6 / 3; }
+  #notice { grid-area: 1 / 2 / 2 / 3; }
+  #shell { grid-area: 2 / 2 / 3 / 3; }
+  #state { grid-area: 3 / 2 / 4 / 3; align-self: start; }
   /* The working row runs the full height, as the table does: the panel ends where it ends. The panel scrolls rather than the
-   * page. It has no top padding here: the list drives under it, and the sticky row of categories would stand not flush with
-   * the edge but under a band of passing files. The padding has not gone anywhere — it is on the first field and travels
-   * away with it. */
-  #panel { grid-area: 2 / 1 / -1 / 2; min-height: 0; margin-bottom: 0; padding-top: 0; overflow: auto; }
-  .panel > fieldset:first-child { padding-top: 12px; }
+   * page, and its top padding is gone: the heading carries that room instead, and it travels away with the list, while the
+   * sticky row of categories stands flush with the card's edge rather than under a band of passing rows. */
+  .panel { grid-area: 1 / 1 / -1 / 2; min-height: 0; margin-bottom: 0; padding-top: 0; overflow: auto; }
+  .panel h1 { padding-top: 12px; }
   /* Here the row rather than the window sets the table's height: it needs a height rule of its own only in a narrow window,
    * where the whole page scrolls. */
   .shell { max-height: none; }
@@ -217,7 +208,7 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
   }
   /* Without metrics there is no table, and a stretched empty row has no place there: the empty state takes the free space of
    * that row rather than the band above it. */
-  body:has(#shell[hidden]) #state { grid-area: 3 / 2 / 4 / 3; }
+  body:has(#shell[hidden]) #state { grid-area: 2 / 2 / 3 / 3; }
 }
 
 /* Adaptations: the one place where the page overrides the shared geometry — because the shared part is frozen by the
@@ -226,7 +217,7 @@ h1 { margin: 0 0 3px; font-size: 21px; font-weight: 650; letter-spacing: -.012em
  * empty space under it at that single window size. */
 @media (max-width: 899px) {
   body { padding: 14px 14px 32px; }
-  h1 { font-size: 18px; }
+  h1 { font-size: 19px; }
   #grid { font-size: 12px; }
   .shell { max-height: calc(100vh - 260px); }
   /* The commit column keeps its width on a narrow screen, and that is deliberate rather than forgotten: the numbers

package/src/page/app.js

@@ -14,14 +14,6 @@ import { appPanel, appPanelAll, appPanelState } from './panel.js';
 // The table's window: made once, at the first drawing.
 let appCache = null;
 
-/* The note under the table: what a row is and how the report was made. It does not depend on the choice, so it is
- * written once — with the table rather than with every drawing of it. */
-function appNote() {
-  document.getElementById('note').textContent = appUi.note
-    .replace('{rows}', appData.rows.length)
-    .replace('{command}', appData.report.fixCommand);
-}
-
 /* What the empty states are told: how many metrics and how many files are left. The window stands there in either
  * case — the words are about what is shown. */
 export function appCounts() {
@@ -76,7 +68,6 @@ export function appSwitchMetric() {
 function appFirst() {
   appPanel();
   appCache = appTable(document.getElementById('grid'));
-  appNote();
   appPaint();
 }
 

package/src/page/build.js

@@ -1,6 +1,6 @@
 import fs from 'fs';
 import zlib from 'zlib';
-import { fill, LOCALES } from '../locales.js';
+import { LOCALES } from '../locales.js';
 import { PAGE_CSS, TABLE_CSS } from '../css.js';
 import { assertCompilable, stripCss, stripJs, stripLines } from '../strip.js';
 
@@ -71,16 +71,6 @@ export function pageScript() {
   return code;
 }
 
-/* The note under the heading: what built the report and where it lies. The path is plain text rather than a link: the
- * page opens from disk and depends on nothing. */
-function subText(data, page) {
-  return fill(page.sub, {
-    tool: data.tool.name,
-    version: data.tool.version,
-    artifact: data.report.artifact
-  });
-}
-
 /* The page's texts: column captions, panel labels, the legend and the empty states. They are the page's dictionary
  * rather than the report's: the data block carries none of them, and the report's own words live in the locale. */
 function uiText(page, loc) {
@@ -114,9 +104,7 @@ function uiText(page, loc) {
     categoryByExtension: page.categoryByExtension,
     methodLabel: page.panelMethod,
     empty: page.emptyMetrics,
-    noFiles: page.noFiles,
-    /* {command} is substituted by the page, which holds the data, while {now} is filled in here. */
-    note: page.note.replace(/\{now\}/g, loc.now)
+    noFiles: page.noFiles
   };
 }
 
@@ -208,13 +196,13 @@ export function pagePayload(data) {
   const out = {
     schema: 2,
     tool: data.tool,
-    /* The report's own words are the ones the page reads: `heading` is the artifact's `<h1>` and `journal` is null
-     * today, so neither is carried — the page builds no heading and prints no journal. */
+    /* The report's own words are the ones the page reads: `heading` is the artifact's `<h1>`, built before the block,
+     * `journal` is null today, and `fixCommand` was quoted by the note under the table, which the page no longer has —
+     * the page builds no heading, prints no journal and suggests no command. */
     report: {
       locale: data.report.locale,
       title: data.report.title,
       artifact: data.report.artifact,
-      fixCommand: data.report.fixCommand,
       showSha: data.report.showSha
     },
     hrefPrefix: prefix,
@@ -248,20 +236,23 @@ export function pagePacked(text) {
 }
 
 /* The report's page is one file: the data lies in it, the script is pasted in, there are no external references. Hence
- * it opens with a double click and works without a network. */
+ * it opens with a double click and works without a network.
+ *
+ * The page's chrome is the panel and the table, and nothing stands above the numbers: the report's heading opens the
+ * panel (the one place that holds the reader's own controls) rather than a band of its own, and neither the tool, nor the
+ * version, nor the artifact's path is printed anywhere — the file is opened from a directory whose name already says
+ * where it lies. The panel's card is the markup's and the fields inside it are the script's: `#panel` is emptied and
+ * rebuilt on every opening, which is why the heading is the card's other child rather than one more field. */
 export function pageHtml(data, cfg) {
   const loc = LOCALES[cfg.locale];
   return '<!doctype html>\n<html lang="' + esc(loc.html) + '">\n<head>\n<meta charset="utf-8">\n'
     + '<meta name="viewport" content="width=device-width, initial-scale=1">\n'
     + '<title>' + esc(data.report.title) + '</title>\n<style>\n'
     + squeezedCss(TABLE_CSS) + '\n' + squeezedCss(PAGE_CSS) + '\n</style>\n</head>\n<body>\n'
-    + '<header>\n<h1>' + esc(data.report.heading) + '</h1>\n'
-    + '<p class="sub">' + esc(subText(data, loc.page)) + '</p>\n</header>\n'
-    + '<div id="panel" class="panel"></div>\n'
+    + '<div class="panel">\n<h1>' + esc(data.report.heading) + '</h1>\n<div id="panel"></div>\n</div>\n'
     + '<p id="notice" class="notice" hidden></p>\n'
     + '<div id="shell" class="shell"><div id="grid" class="grid"></div></div>\n'
     + '<p id="state" class="state" hidden></p>\n'
-    + '<p id="note" class="note"></p>\n'
     + '<script type="application/octet-stream" id="data" data-pack="base64+gzip">'
     + pagePacked(jsonInHtml(pagePayload(data))) + '</script>\n'
     + '<script type="application/json" id="ui">' + jsonInHtml(uiText(loc.page, loc)) + '</script>\n'

package/src/page/panel.js

@@ -1,5 +1,5 @@
 import { appEl, appBox, appOffBox } from './dom.js';
-import { appData, appUi, appView, appFileAt, appFoldSet, appMeasured } from './state.js';
+import { appCatOf, appData, appUi, appView, appFileAt, appFoldSet, appMeasured } from './state.js';
 
 /* Only a file sets a file's checkbox: both a category and a folder in the tree are ways to set the same checkboxes as
  * a group and keep no state of their own. Otherwise one and the same decision would live in two places and drift
@@ -188,8 +188,12 @@ export function appPanel() {
   const metrics = appEl('fieldset');
   metrics.appendChild(appEl('legend', null, appUi.metrics));
   const mrow = appEl('div', 'row');
+  /* What a metric is and how its number was obtained stand in one place: the tooltip of the box that switches it. The
+   * token dictionary and the way of compression come from the settings of the run, and the page has nothing to switch
+   * them with, so the reader has to know with what he is counting — while the lines that said it in words under the
+   * switches took the room beside the numbers. */
   appData.metrics.forEach((m) => {
-    const box = appBox(m.label, m.note, appView.metrics[m.key], (e) => {
+    const box = appBox(m.label, m.note + ' — ' + appUi.methodLabel + ' ' + m.method, appView.metrics[m.key], (e) => {
       appView.metrics[m.key] = e.target.checked;
       appSwitchMetric();
     }, 'metric');
@@ -197,12 +201,6 @@ export function appPanel() {
     mrow.appendChild(box);
   });
   metrics.appendChild(mrow);
-  /* What produced each number is visible rather than hidden in a tooltip: the token dictionary and the way of
-   * compression are chosen by the settings of the run, the page has nothing to switch them with, and the reader needs
-   * to know this without pointing a mouse. */
-  appData.metrics.forEach((m) => {
-    metrics.appendChild(appEl('p', 'about', m.label + ' — ' + appUi.methodLabel + ' ' + m.method));
-  });
   panel.appendChild(metrics);
 
   const files = appEl('fieldset', 'files');
@@ -211,8 +209,7 @@ export function appPanel() {
    * in the wide layout, which is where the panel scrolls). */
   const cats = appEl('div', 'row cats');
   appData.categories.forEach((cat) => {
-    const idx = [];
-    appData.files.forEach((f, i) => { if (f.category === cat.key) idx.push(i); });
+    const idx = appCatOf(cat.key);
     const box = appBox(cat.label, appUi.all + ' · ' + cat.label, idx.every((i) => appView.files[i]),
       (e) => appSwitchGroup(idx, e.target.checked), 'all');
     appFields.cat[cat.key] = box.querySelector('input');
@@ -246,19 +243,14 @@ function appDirState(path) {
   input.indeterminate = on > 0 && on < boxes.length;
 }
 
-/* A category's field from its files — the same rule, taken from the data: a category's files are named by the
- * category itself (`category`), and the boxes of the tree are a different view of the same files. */
+/* A category's field from its files — the same rule, taken from the data: a category's files are named by the category
+ * itself (`appCatOf`), and the boxes of the tree are a different view of the same files. */
 function appCatState(key) {
-  let all = 0;
-  let on = 0;
-  appData.files.forEach((f, i) => {
-    if (f.category !== key) return;
-    all++;
-    if (appView.files[i] === true) on++;
-  });
+  const idx = appCatOf(key);
+  const on = idx.filter((i) => appView.files[i] === true).length;
   const input = appFields.cat[key];
-  input.checked = on === all;
-  input.indeterminate = on > 0 && on < all;
+  input.checked = on === idx.length;
+  input.indeterminate = on > 0 && on < idx.length;
 }
 
 /* The folders a file lies in: the prefixes of its path, from the root down. The tree's folders are exactly those

package/src/page/state.js

@@ -11,10 +11,12 @@ import { appDecode } from './payload.js';
  * network: the styling arrives in the same file, and the cell markup follows the rules of the shared part of the styling
  * (`clip`, a commit's caption).
  *
- * The panel remembers the reader's choice between visits ("the choice's memory" below): the record is tied to the
- * report's passport and keeps only what is switched off, by name, so someone else's record is not applied while a
- * vanished name simply means nothing. The record stays in the browser's memory and nowhere else: a report opened from
- * disk keeps a clean address, and a link made in an earlier release is still read (`appLinkUse`).
+ * The panel remembers the reader's choice between visits ("the choice's memory" below): the record is addressed by the
+ * report rather than by a build of it (`appPassport`), it keeps the fact of a whole category where the reader decided by
+ * groups and the names of the files where he decided one by one, and only what is switched off is written down — so
+ * someone else's record is not applied while a vanished name simply means nothing. The record stays in the browser's
+ * memory and nowhere else: a report opened from disk keeps a clean address, and a link made in an earlier release is
+ * still read (`appLinkUse`).
  *
  * The page draws no conclusion about how a number was obtained: the method of each metric arrives in the data, and the
  * page prints it. There is no second rule of counting here, and no vocabulary of precision either. */
@@ -44,7 +46,9 @@ let appFoldKey = null;
  * choice's record (`appFileAt`), so the tree and the reader's memory cannot drift apart.
  *
  * The key the reader's memory lives under is counted here as well, because it is the report's passport: it depends
- * on the data, and until the block is unpacked there is nothing to count it from. */
+ * on the data, and until the block is unpacked there is nothing to count it from. The addresses an earlier naming of
+ * the passport left behind go away at the same moment (`appSweep`): the report is in a position to say what is dead,
+ * and nothing of the reader's memory has been read yet. */
 export function appBoot(text) {
   appData = appDecode(JSON.parse(text));
   /* The tree is folded as it opens: a project's tree is longer than the window, and the reader's first look is at a
@@ -55,8 +59,9 @@ export function appBoot(text) {
   appMeasured = {};
   appData.metrics.forEach((m) => { appView.metrics[m.key] = true; appMetric[m.key] = m; });
   appData.files.forEach((_f, i) => { appView.files.push(true); appMeasured[appFileAt(i)] = i; });
-  appKey = 'size-report:' + appPassport();
+  appKey = APP_FORM + appPassport();
   appFoldKey = appKey + ':tree';
+  appSweep();
 }
 
 /* A link is that same choice in the address, under a name of its own: someone else's anchor on the page does not count
@@ -70,6 +75,14 @@ let appTransient = false;
 
 /* -------- the reader's memory of his choice -------- */
 
+/* The form of the memory's address: the tool's namespace, a mark of the form, then the report's identity (`appPassport`
+ * counts it). The mark stands in the address because the identity was named differently once — in the first naming the
+ * columns stood inside it, so every build of the report had an address of its own and the reader's choice was left
+ * behind at the previous one — and because the mark is what lets this release tell the addresses it writes from the
+ * addresses of that naming (`appSweep`), without pretending to know whose record lies under the older one. */
+const APP_STORE = 'size-report:';
+const APP_FORM = APP_STORE + '2:';
+
 /* The name of a file for the record is its path at HEAD, or the last of the settings when the file is already gone from
  * there: that is the name it is recognised by in the report. */
 export function appFileAt(i) {
@@ -77,6 +90,15 @@ export function appFileAt(i) {
   return f.path === null ? f.paths[0] : f.path;
 }
 
+/* The files of one category, in the order of the data: a category is a group of files as the engine named it
+ * (`category`), and the record, the boxes of the panel and their fields all ask for that group here rather than walking
+ * the files a second time. */
+export function appCatOf(key) {
+  const idx = [];
+  appData.files.forEach((f, i) => { if (f.category === key) idx.push(i); });
+  return idx;
+}
+
 /* The passport's fingerprint: an identifying mark of a record rather than protection against forgery, so 32 bits are
  * enough (FNV-1a). */
 function appHash(text) {
@@ -88,34 +110,88 @@ function appHash(text) {
   return (h >>> 0).toString(16);
 }
 
-/* The report's passport: the tool's name, the data schema, the artifact's path, the title and the column labels in the
- * report's order. It is what tells one report from another — the record's key is chosen by it, so a choice made in
- * someone else's report is not picked up. The package version and the top of the history are absent on purpose: this is
- * the same report — updating the tool does not change what a column means, while a grown history is the very history the
- * reader comes back to.
+/* The report's passport: the tool's name, the data schema, the artifact's path, the title and the oldest row of the
+ * history. It is what tells one report from another — the record's key is chosen by it, so a choice made in someone
+ * else's report is not picked up — and it is what makes the memory the report's rather than a build of it: every later
+ * build of the same report counts the same value and finds the same choice.
+ *
+ * The first four are what the report says about itself, and they are the same in a report of another project (both the
+ * artifact's path and the title are defaults there, and all `file://` pages share one memory), which is what the fifth
+ * is for: the oldest row is a commit of this history, the same in every clone and every build, and the one commit the
+ * history never moves — rows are built from the oldest commit up, so a commit appends rows and leaves that one where it
+ * stands.
+ *
+ * The package version and the top of the history are absent on purpose: updating the tool does not change what a column
+ * means, while a grown history is the very history the reader comes back to.
+ *
+ * The columns were named here once, and they are what does not belong here at all: their labels and their order move
+ * with the numbers — a project without settings pinned derives the columns on every run, ordered by size within an
+ * extension (`src/project.js`), so every commit that grew or shrank a file gave the report another passport and left the
+ * reader's choice at the old address. What a record holds are names, and a name the report no longer has means nothing
+ * (`appApply`), so the columns have nothing to guard in the passport.
  *
  * Counted once per document: it is a constant of the report, which depends on nothing the reader can change, and every
  * click asks for it (the key of the memory and the passport of the record). A second count would be a second answer
- * waiting to happen, and the labels it reads do not change while the page is open. */
+ * waiting to happen, and the block it reads does not change while the page is open. */
 let appPassportValue = null;
 function appPassport() {
   if (appPassportValue === null) {
+    const oldest = appData.rows.length === 0 ? '' : appData.rows[0].sha;
     appPassportValue = appHash([appData.tool.name, appData.schema, appData.report.artifact,
-      appData.report.title, appData.files.map((f) => f.label).join('|')].join('\n'));
+      appData.report.title, oldest].join('\n'));
   }
   return appPassportValue;
 }
 
-/* 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. */
+/* The addresses an earlier naming left in the browser: every one of them belonged to a single build of a report, and no
+ * report ever looks under them again — the memory is read under the address of the report's identity alone. A browser
+ * that has lived through a long history holds one such record per commit, so they go away, once, when a report of this
+ * release is opened.
+ *
+ * What is swept is the mark of the form rather than a claim about whose record it is: the older address was counted from
+ * the data, so the record under it cannot be attributed to a report — hence a memory left by an older release in this
+ * browser goes too, and it is one of a report that was not rebuilt since its reader last clicked (that release moved the
+ * address at the next build itself, leaving the memory behind). What this release writes is left alone: under it lies
+ * this report's memory and another report's, and the two are told apart by the identity rather than by the form. */
+function appSweep() {
+  try {
+    for (let i = window.localStorage.length - 1; i >= 0; i--) {
+      const key = window.localStorage.key(i);
+      if (key !== null && key.indexOf(APP_STORE) === 0 && key.indexOf(APP_FORM) !== 0) {
+        window.localStorage.removeItem(key);
+      }
+    }
+  } catch (_e) {
+    /* There is no memory (the browser grants this page none): there is nothing to sweep either. */
+  }
+}
+
+/* One record of the choice: the facts of the groups where the reader decided by groups, the names of the files where he
+ * decided one by one, and only what is switched off.
+ *
+ * A category whose box is wholly off — or wholly on — is written down as that fact rather than as the state of every
+ * file in it: `cats` names the group and says where it stands, so a file that joins the category later is switched with
+ * it, which is exactly what the reader asked for when he switched the group, and the record does not grow with the
+ * project. A category in the third state cannot speak for his choice — the choice was made file by file — and the files
+ * he switched off go into the record by name (`files`), as they did before this chapter knew categories; such a category
+ * is **absent** from `cats`, which is how the record distinguishes "a group fact" from "no group fact to state".
+ *
+ * "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 cats = {};
   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; });
-  const empty = Object.keys(metrics).length === 0 && Object.keys(files).length === 0;
-  return empty ? null : { v: 1, passport: appPassport(), metrics: metrics, files: files };
+  appData.categories.forEach((c) => {
+    const idx = appCatOf(c.key);
+    const on = idx.filter((i) => appView.files[i] === true).length;
+    if (on === idx.length || on === 0) { cats[c.key] = on === idx.length; return; }
+    idx.forEach((i) => { if (appView.files[i] !== true) files[appFileAt(i)] = false; });
+  });
+  const empty = Object.keys(metrics).length === 0 && Object.keys(files).length === 0
+    && Object.keys(cats).every((key) => cats[key] === true);
+  return empty ? null : { v: 1, passport: appPassport(), metrics: metrics, cats: cats, files: files };
 }
 
 // Whether a record is ours and of the right format — one rule for the memory and the address alike.
@@ -232,13 +308,24 @@ export function appRead() {
   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
- * nothing (a column was pointed at another path, a metric was dropped from the settings), while files and metrics that
- * appeared stay switched on — the way someone opening the page for the first time sees them. */
+/* Applying goes by name: a file is recognised by its path, a metric by its key, a category by the key the engine gave
+ * it. A name the report does not hold matches nothing (a column was pointed at another path, a metric was dropped from
+ * the settings), while files, categories and metrics that appeared stay switched on — the way someone opening the page
+ * for the first time sees them.
+ *
+ * A category's fact is applied to the files of that category as they are now, and the names are applied after it: the
+ * file-by-file decision is the finer one and stands last, and a record of an earlier release — which knew no categories
+ * and wrote only names — is applied by its names exactly as it was. */
 export function appApply(rec) {
   const metrics = rec.metrics || {};
+  const cats = rec.cats || {};
   const files = rec.files || {};
   appData.metrics.forEach((m) => { if (metrics[m.key] === false) appView.metrics[m.key] = false; });
+  appData.categories.forEach((c) => {
+    const on = cats[c.key];
+    if (on !== true && on !== false) return;
+    appCatOf(c.key).forEach((i) => { appView.files[i] = on; });
+  });
   appData.files.forEach((_f, i) => { if (files[appFileAt(i)] === false) appView.files[i] = false; });
 }
 

package/templates/README.md

@@ -40,7 +40,8 @@ What is worth knowing about the template's values:
   without the optional dependencies, a platform that has none) the tool still works, but says that the
   numbers were counted another way, and returns **code 4** — that is a named different count rather than an
   error of the settings.
-- `fixCommand` — the command the report's signature and the refusals quote. In the template it is
+- `fixCommand` — the command the refusals quote and the contract hands to an agent (the page prints
+  nothing of it). In the template it is
   `node node_modules/@vernikr/size-report/bin/size.js --write` — the path to the installed package inside
   the project. **The package name as a command cannot stand here:** `npx <name>` in a project without the
   installed package goes to the registry and pulls the package over the network, so the advice that is meant