clearotron 0.2.4 → 0.3.0-beta.1

package/scripts/mint-names-in-force.mjs

@@ -6,7 +6,7 @@
 //
 // ── WHY THIS IS DERIVED AND NOT WRITTEN BY HAND ──────────────────────────────────────────────────
 //
-// It is the replacement half of the retired-spelling check (tracker issue 168). The DETECTION half
+// It is the replacement half of the retired-spelling check. The DETECTION half
 // needs nothing from this file: no product code reads a `PRELIM_*` name any more, so a `PRELIM_*` that
 // is set is dead whatever this list says. What the list decides is the second half of the sentence —
 // which name to tell the operator to use instead — and that is where a hand list does damage. A hand
@@ -31,6 +31,7 @@
 //   --check  exit 1 if the committed file disagrees with a fresh derivation, printing the difference
 
 import { execFileSync } from "node:child_process";
+import { publishedOf } from "../shared/reference-guard-classes.mjs";   // the published population, one helper for every minter
 import { readFileSync, writeFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
@@ -45,13 +46,26 @@ const OUT = join(REPO, "shared", "names-in-force.mjs");
  * and a name only a test mentions is not a name this build reads. Including them would mint
  * replacements for settings the product does not have. `.js` and `.ts` are in with `.mjs` because
  * the providers' own `src` directories carry non-test `.js` — a `.mjs`-only derivation has produced
- * wrong answers on this tree before (tracker issue 96).
+ * wrong answers on this tree before.
  */
 export function sourceFiles(root = REPO) {
-  const tracked = execFileSync("git", ["-C", root, "ls-files", "*.mjs", "*.js", "*.ts"], {
+  // THE PUBLISHED POPULATION, NOT THE INDEX. `git ls-files` reads the index, and an overlay run stages
+  // the withheld corpus over a clone without committing it — so minting there counted withheld names
+  // into this public floor with nothing reporting it: the number is simply too high, and the next
+  // person to re-mint from a clean checkout is shown a shrink and told to record it. Same helper as the
+  // other three minters, because two spellings of this rule disagree under the overlay and `--check`
+  // then reports a difference that is only the two instruments asking different questions.
+  //
+  // Found by deriving the population of this guard rather than listing it: the check that holds the
+  // other three named them by hand and this file was not among them, so the guard passed over the
+  // fourth caller of the defect it exists to stop.
+  const all = execFileSync("git", ["-C", root, "ls-files", "*.mjs", "*.js", "*.ts"], {
     encoding: "utf8", maxBuffer: 64 * 1024 * 1024,
   }).split("\n").filter(Boolean);
-  return tracked.filter((f) => !/(^|\/)(test|tests|bench)\//.test(f) && !/\.test\.(mjs|ts|js)$/.test(f));
+  const p = publishedOf(all, root);
+  if (p.error) { console.error(`mint-names-in-force: ${p.error}`); process.exit(2); }
+  if (p.laid) console.log(`mint-names-in-force: ${p.laid} tracked path(s) are not in HEAD — laid over this checkout, not published in it, and not counted`);
+  return p.files.filter((f) => !/(^|\/)(test|tests|bench)\//.test(f) && !/\.test\.(mjs|ts|js)$/.test(f));
 }
 
 const NAME_RE = /\bCLEAROTRON_[A-Z0-9_]+/g;
@@ -78,7 +92,7 @@ function render(names) {
 //
 // Every \`CLEAROTRON_*\` name this build reads. It exists so the retired-spelling check can name the
 // replacement for an old \`PRELIM_*\` line rather than only saying the old one is dead — see
-// shared/env-aliases.mjs and tracker issue 168. Re-mint with:
+// shared/env-aliases.mjs. Re-mint with:
 //
 //   node scripts/mint-names-in-force.mjs
 //

package/scripts/mint-reference-strip-backlog.mjs

@@ -3,7 +3,7 @@
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
 //
 // Mints `driver/test/fixtures/reference-strip-backlog.json` — the per-file floor under the repair of
-// the sentences the reference strip broke (tracker issue 185).
+// the sentences the reference strip broke.
 //
 // Run it AFTER repairing lines, never to make a red arm green: the arm it feeds refuses any count that
 // went UP, so re-minting is how a repair is recorded, not how a regression is absorbed.

package/scripts/mint-suite-census.mjs

@@ -41,6 +41,7 @@ import { CENSUS_WORKSPACES, CENSUS_ROOT_SCRIPTS, countTestSites, collectionFromM
 import { providerTestFiles } from "./test-full.mjs";
 import { withheldEntryFor, announceWithheldMode } from "../shared/withheld-paths-access.mjs";   // — withheld is a stated absence, not a loss.: the record does not ship, and without it every absence is a loss
 import { isEntrypoint } from "../shared/is-entrypoint.mjs";   // — realpath both sides, or a symlinked invocation exits 0 silently
+import { publishedOf } from "../shared/reference-guard-classes.mjs";
 
 // — say which mode this run is in, so a relaxed check is never silent.
 announceWithheldMode();
@@ -72,14 +73,44 @@ const README = [
   "RE-STAMP DELIBERATELY:  node scripts/mint-suite-census.mjs --apply",
 ];
 
+/**
+ * The tracked files matching `globs` that HEAD actually carries.
+ *
+ * `git ls-files` reads the INDEX. The private control stages a withheld corpus over a clone without
+ * committing it, so under that overlay the index holds files HEAD does not — and this census, minted
+ * on the published tree and checked against the overlaid one, reported every laid test file as an
+ * addition. The stamp was current and the check said stale, permanently, because the two runs were
+ * counting different populations rather than disagreeing about one.
+ *
+ * `publishedOf` is the discriminator the residue floor and the reference-strip backlog already use.
+ * One helper rather than three spellings: three drift, and the drift shows only under the overlay,
+ * which is the place nobody runs by accident.
+ *
+ * THE TWO CASES ARE NOT THE SAME and are not treated the same. A path in the index and absent from
+ * HEAD is LAID and is not counted. A path in HEAD and modified in the index is ordinary work in
+ * progress and is counted exactly as before — refusing that would make this refuse a normal edit.
+ * `publishedOf` filters on membership of HEAD, so a modified-but-committed file stays in.
+ *
+ * A tree with no HEAD cannot say what it published. That is a failure to look, and it exits rather
+ * than reading as "nothing is laid here", which is the permissive answer and the one that passes.
+ */
+function publishedFiles(root, globs) {
+  let all = [];
+  try {
+    all = execFileSync("git", ["-C", root, "ls-files", "--", ...globs], { encoding: "utf8" })
+      .split("\n").map((x) => x.trim()).filter(Boolean);
+  } catch { return []; }
+  if (!all.length) return [];
+  const p = publishedOf(all, root);
+  if (p.error) { console.error(`mint-suite-census: ${p.error}`); process.exit(2); }
+  if (p.laid) console.log(`mint-suite-census: ${p.laid} tracked path(s) are not in HEAD — laid over this checkout, not published in it, and not counted`);
+  return p.files.slice().sort();
+}
+
 export function buildCensus(root = ROOT) {
   const out = { _README: README, workspaces: {}, rootScripts: {} };
   for (const { ws, ext } of CENSUS_WORKSPACES) {
-    let files = [];
-    try {
-      files = execFileSync("git", ["-C", root, "ls-files", "--", `${ws}/test/*.test.${ext}`], { encoding: "utf8" })
-        .split("\n").map((s) => s.trim()).filter(Boolean).sort();
-    } catch { files = []; }
+    const files = publishedFiles(root, [`${ws}/test/*.test.${ext}`]);
     const perFile = {};
     for (const f of files) {
       const abs = join(root, f);
@@ -99,11 +130,7 @@ export function buildCensus(root = ROOT) {
   // one: these globs span two shapes (`providers/_shared/test/` and `providers/<id>/test/`), and a
   // stripped key would collide the moment two providers shipped a file of the same name.
   for (const { script, globs } of CENSUS_ROOT_SCRIPTS) {
-    let files = [];
-    try {
-      files = execFileSync("git", ["-C", root, "ls-files", "--", ...globs], { encoding: "utf8" })
-        .split("\n").map((x) => x.trim()).filter(Boolean).sort();
-    } catch { files = []; }
+    const files = publishedFiles(root, globs);
     const perFile = {};
     for (const f of files) {
       const abs = join(root, f);

package/scripts/pack-publishable.mjs

@@ -201,7 +201,7 @@ async function main() {
       : "  nothing stripped — no publish-only keys were present");
     // Prove the repo manifest still has them, here, on every pack.
     //
-    // ── WHICH KEYS THIS MAY REFUSE OVER, AND WHY IT IS NOT ALL OF THEM (tracker issue 196) ───────────
+    // ── WHICH KEYS THIS MAY REFUSE OVER, AND WHY IT IS NOT ALL OF THEM ───────────────────────────────
     //
     // This asserted every entry of STRIP_KEYS was present in the repo manifest, and `private` has not
     // been in it since publishing moved into CI — the STRIP_KEYS comment above says so in its own words.

package/scripts/preinstall-node-check.mjs

@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: AGPL-3.0-only
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
 //
-// The install refuses an unsupported Node BEFORE anything is written — tracker issue 364.
+// The install refuses an unsupported Node BEFORE anything is written.
 //
 // Three declarations already stated the requirement and none of them bound anyone: `engines.node` is a
 // WARNING unless the person installing has set `engine-strict`, `.nvmrc` is read by nvm and nothing

package/scripts/release-await-cut.mjs

@@ -55,7 +55,7 @@ import { cutDecision, versionAtHead, tagsHere } from "./release-cut-decision.mjs
  * Default bound: twenty-five minutes at thirty-second steps. Both are arguments so an arm can drive
  * the loop.
  *
- * TWENTY-FIVE, RAISED FROM FIFTEEN (tracker issue 247), because this waits for the version pull
+ * TWENTY-FIVE, RAISED FROM FIFTEEN, because this waits for the version pull
  * request's OWN CI and that is what it must clear. Measured over the first three cuts, the wait held
  * 552 s, 622 s and 686 s against a 900 s budget — rising every time, and the thing it waits on is the
  * offline suite, which grows on purpose every time anybody adds an arm. The margin was one slow queue.
@@ -139,7 +139,7 @@ const git = (args) => execFileSync("git", args, { encoding: "utf8" });
  * One read of `main`: the version it carries, whether that version is tagged, and WHICH COMMIT said so.
  *
  * THE COMMIT IS READ IN THE SAME PASS AS THE VERSION, and that is the whole point of this function
- * existing rather than being three calls at the call site (tracker issue 238). The job below used to
+ * existing rather than being three calls at the call site. The job below used to
  * check out `main` by name after this loop returned, so a commit landing in between — one that moves no
  * version, an instrument fix with no note — was packed and published under a number whose changelog
  * never described it. Nothing downstream could see it: the tip check compares VERSIONS, and the version
@@ -212,7 +212,7 @@ function main() {
     sleep: (ms) => new Promise((r) => setTimeout(r, ms)),
     now: () => Date.now() - started,
   }).catch((e) => {
-    // ── A FAILURE TO LOOK IS NOT "NOT MERGED YET" (tracker issue 208) ───────────────────────────────
+    // ── A FAILURE TO LOOK IS NOT "NOT MERGED YET" ───────────────────────────────────────────────────
     //
     // Giving up quietly is the ordinary outcome of this loop and stays exit 0: checks that went red, a
     // pull request somebody dismissed, a re-cut mid-flight. None of those is a release gone missing.

package/scripts/release-cut-decision.mjs

@@ -49,7 +49,7 @@ export function tagsHere({ run = (args) => execFileSync("git", args, { encoding:
 }
 
 /**
- * WHICH COMMIT THE QUESTION IS ABOUT — tracker issue 208, measured on run 34050690448.
+ * WHICH COMMIT THE QUESTION IS ABOUT — measured on run 34050690448.
  *
  * `versionAtHead()` reads a COMMIT rather than the working tree, deliberately, and the header above says
  * why at length. That is necessary and it was not sufficient: in the `version` job the changesets action

package/scripts/release-dist-tag.mjs

@@ -65,7 +65,7 @@ export function distTag(version, { preMode = false } = {}) {
     throw new Error(`release-dist-tag: "${version}" is not a version this can read, so the channel it `
       + "belongs on cannot be derived. Publishing it would default to `latest`.");
   }
-  // ── THE PRE-MODE OVERRIDE IS GONE, AND `preMode` NO LONGER DECIDES ANYTHING (tracker issue 230) ──
+  // ── THE PRE-MODE OVERRIDE IS GONE, AND `preMode` NO LONGER DECIDES ANYTHING ──────────────────────
   //
   // It read `if (preMode) return STABLE`, putting every pre-release on `latest` under the owner's ruling
   // of 2026-09-05. That was right while nothing installed the package and wrong once things did: nine

package/scripts/release-install-check.mjs

@@ -7,7 +7,7 @@
 //
 // ── WHAT IT IS FOR, AND WHY IT IS NOT ANOTHER MANIFEST ASSERTION ────────────────────────────────────
 //
-// Five consecutive releases published a package npm refused to install (tracker issue 180). Every
+// Five consecutive releases published a package npm refused to install. Every
 // check in the pipeline passed on every one of them, because each asked a question about the tarball
 // and none asked the only question a visitor asks: does `npm install clearotron` work.
 //

package/scripts/release-notes-lint.mjs

@@ -50,7 +50,7 @@ export const EMPTY_PHRASES = ["now correctly", "as expected", "properly"];
  * A path whose first segment is one of these is a SOURCE-TREE path — `driver/test/…`, `scripts/…` — and
  * means nothing to somebody who has never opened this repository. A path that starts at the reader's own
  * home does not: `~/.config/clearotron/` is where THEIR settings are, and telling them is the note's job.
- * Owner ruling 2026-09-05, narrowing the contract's flat ban on "file paths": what a reader types or
+ * Ruling 2026-09-05, narrowing the contract's flat ban on "file paths": what a reader types or
  * opens is allowed; our tree is not.
  *
  * Derived from the tree rather than typed, so a directory added next month is covered without anybody

package/scripts/release-publish-guard.mjs

@@ -89,7 +89,7 @@ export function refusals({ workflow, rootPkg }) {
   if (!/id-token:\s*write/.test(live)) add("the release workflow cannot request an OIDC token (`id-token: write` is gone)");
   if (!/environment:\s*npm\b/.test(live)) add("the release workflow no longer runs in the `npm` environment the publisher is registered under");
 
-  // ── AND EVERY PUBLISHING JOB CARRIES BOTH, not merely the file somewhere (tracker issue 208) ────────
+  // ── AND EVERY PUBLISHING JOB CARRIES BOTH, not merely the file somewhere ────────────────────────────
   //
   // The two checks above ask whether the strings appear ANYWHERE. That was sufficient while one job
   // published. It stopped being sufficient the moment a second publishing job was added: a workflow

package/scripts/release-version-pr-checks.mjs

@@ -134,7 +134,7 @@ export function checksVerdict({ checkRuns = [], workflowRuns = [], policy = null
 /**
  * This file's own window: 32 attempts at 15 s, or eight minutes.
  *
- * NAMED SO AN ARM CAN COUPLE THE JOB'S BUDGET TO IT (tracker issue 247). The `version` job's
+ * NAMED SO AN ARM CAN COUPLE THE JOB'S BUDGET TO IT. The `version` job's
  * `timeout-minutes` has to contain THIS wait, and the arm that claimed to check that compared the job
  * against `release-await-cut.mjs`'s constant instead — a different wait, in a different job, which this
  * job never runs. It held by luck and would have failed the moment that unrelated number was raised.
@@ -231,7 +231,7 @@ async function main() {
     console.log(seen.reason);
     return;
   }
-  // ── A PARKED RUN IS THE ORDINARY STATE OF A CUT, NOT A FAULT (tracker issue 208) ─────────────────
+  // ── A PARKED RUN IS THE ORDINARY STATE OF A CUT, NOT A FAULT ─────────────────────────────────────
   //
   // This failed the job, and failing it was worse than the thing it reported. Measured 2026-09-06:
   // a merge cut version pull request 59, its run parked awaiting approval as EVERY version branch's

package/scripts/release-version.mjs

@@ -54,7 +54,8 @@ export function groupVersion(root = ROOT) {
  * fixed group means one note commonly lands in several files unchanged.
  */
 export function assembleRoot(version, root = ROOT) {
-  const bullets = [];
+  const entries = [];
+  const seen = new Set();
   for (const w of GROUP) {
     const p = join(root, w, "CHANGELOG.md");
     if (!existsSync(p)) continue;
@@ -68,17 +69,72 @@ export function assembleRoot(version, root = ROOT) {
     const sections = text.split(/^## /m).slice(1);
     const mine = sections.find((sec) => sec.split("\n", 1)[0].trim() === version);
     if (!mine) continue;
-    for (const line of mine.split("\n")) {
-      const b = /^\s*-\s+(.*\S)\s*$/.exec(line);
+    for (const note of notesOf(mine)) {
+      const key = note.join("\n");
+      if (seen.has(key)) continue;
+      seen.add(key);
+      entries.push(...note);
+    }
+  }
+  return { version, ...group(entries) };
+}
+
+/**
+ * One version section of a workspace changelog, as the notes it holds. Each note is the list of its
+ * entries in order, and each entry opens with the group it belongs under, unless none was named.
+ *
+ * EVERY PARAGRAPH IS AN ENTRY. Changesets writes a note's first line as a bullet and indents every later
+ * line beneath it. Reading only the bullets kept each note's first line and dropped the rest without a
+ * word: the 0.2.3 page reads "Five things a first-time reader could not act on." with none of the five
+ * under it, and a dry run of 0.3.0 put 8 of the 75 sentences in eight pending notes on the page
+ * (measured 2026-09-10). So each later paragraph is an entry of its own, and so is each list item.
+ *
+ * AN ENTRY THAT NAMES NO GROUP TAKES THE GROUP OF THE ENTRY BEFORE IT. A note opens with its group, and a
+ * paragraph that opens with another group starts that group's entries: `Fixed:` two paragraphs into a
+ * `New:` note is a fix, and so is the paragraph after it that explains the fix. A note whose first line
+ * names no group gives the rest of it none either, so the whole note is refused, not only its first line.
+ */
+export function notesOf(section) {
+  const notes = [];
+  let note = null, lines = null, current = null;
+  const close = () => {
+    if (!lines) return;
+    const text = lines.join(" ");
+    lines = null;
+    const own = /^(New|Fixed|For operators):\s/.exec(text)?.[1];
+    if (own) current = own;
+    note.push(own || !current ? text : `${current}: ${text}`);
+  };
+  for (const line of section.split("\n").slice(1)) {
+    const top = /^-\s+(.*\S)\s*$/.exec(line);
+    const item = /^\s+-\s+(.*\S)\s*$/.exec(line);
+    if (top) {
+      close();
+      note = [];
+      notes.push(note);
+      current = null;
       // THE COMMIT SHA COMES OFF. Changesets' default generator prefixes every bullet with the commit
       // that carried the note, so a squashed release writes the SAME seven characters at the head of
       // every line — `- f7c1570:` seven times over, telling a reader nothing they can use. This is the
       // file a customer opens to decide whether to upgrade; the provenance they can act on is the tag
       // and the release page, both of which name that commit once.
-      if (b && !bullets.includes(b[1])) bullets.push(b[1].replace(/^[0-9a-f]{7,40}: /, ""));
+      lines = [top[1].replace(/^[0-9a-f]{7,40}: /, "")];
+    } else if (!note) {
+      continue;                              // the version heading, or anything before the first note
+    } else if (line.startsWith("#")) {
+      close();                               // `### Patch Changes`: a new set of notes starts here
+      note = null;
+    } else if (!line.trim()) {
+      close();                               // a blank line ends a paragraph
+    } else if (item) {
+      close();
+      lines = [item[1]];
+    } else {
+      (lines ??= []).push(line.trim());      // a paragraph's next line, or its first after a blank line
     }
   }
-  return { version, ...group(bullets) };
+  close();
+  return notes;
 }
 
 /**

package/scripts/render-brand-banner.mjs

@@ -14,7 +14,7 @@
 // retired it from every surface this product renders. Fronting the README with it would put a Swiss
 // firm's logo on an open-source product — the exact thing that retirement was about.
 //
-// The wordmark renders LOWERCASE (owner ruling 2026-08-21) while the name in prose does not, and it
+// The wordmark renders LOWERCASE (ruling 2026-08-21) while the name in prose does not, and it
 // renders as SVG <text> in a GENERIC monospace stack: GitHub serves a README image sandboxed, so a
 // webfont would not load and a named family the reader lacks would fall back to something unrelated.
 

package/scripts/render-check.mjs

@@ -216,7 +216,7 @@ const PROBE = `<script>
       try { parent.postMessage({probeError:String(e && e.message || e)},'*'); } catch (e2) {}
     }
   }
-  // An error in here must not read as "no measurement" — that is the ambiguity tracker issue 1155 was about.
+  // An error in here must not read as "no measurement" — that is the ambiguity this was about.
   window.addEventListener('error', function(ev){
     try { parent.postMessage({probeError:String(ev && ev.message || ev)},'*'); } catch (e) {}
   });
@@ -508,7 +508,7 @@ async function main() {
     console.log("  Expect the sideways assertion to FAIL. A clean run here means the instrument is blind.\n");
   }
   let failures = 0;
-  // A COULD-NOT-LOOK IS NOT A FAILED MEASUREMENT (tracker issue 239). Counted apart from `failures`
+  // A COULD-NOT-LOOK IS NOT A FAILED MEASUREMENT. Counted apart from `failures`
   // because the two mean different things to whoever reads the exit code: 1 says the layout is wrong,
   // 2 says nothing was measured. Merging them is how a starved runner sends a reader to look at CSS.
   let unmeasured = 0;

package/scripts/repo-writes.mjs

@@ -4,7 +4,7 @@
 //
 // ── why this exists ─────────────────────────────────────────────────────────────────────────────────
 //
-// Tracker issue 198. `health-tells-the-truth-about-the-bundle` planted a future mtime on a REAL file in
+// `health-tells-the-truth-about-the-bundle` planted a future mtime on a REAL file in
 // `portal-ui/src` to prove the staleness check fires, restored it afterwards, and went green. But
 // `node --test` runs test FILES concurrently against one shared working tree, so for the seconds that
 // plant was live, any other arm reading that path saw a tree from the future. The suite cannot

package/scripts/report-frame-check.mjs

@@ -71,7 +71,7 @@ function main() {
       "--virtual-time-budget=8000", "--dump-dom", `file://${join(work, "verify.html")}`,
     ], { encoding: "utf8", stdio: ["ignore", "pipe", "ignore"], timeout: 120000, env: browserEnv(work) });
 
-    // ── IS THIS OUR PAGE, OR CHROME'S ERROR PAGE? (tracker issue 227) ───────────────────────────────
+    // ── IS THIS OUR PAGE, OR CHROME'S ERROR PAGE? ───────────────────────────────────────────────────
     //
     // `--dump-dom` prints whatever chrome ended up showing, and a file it could not read produces the
     // interstitial — which has a `<title>` of its own. This was saved from reporting a pass only by the

package/scripts/report-screenshot.mjs

@@ -77,7 +77,7 @@ const cmd = (method, params = {}) => new Promise((r) => { const n = ++id; pendin
 
 await cmd("Page.enable");
 
-// ── IS THIS THE REPORT, OR CHROME'S OWN ERROR PAGE? (tracker issue 227) ──────────────────────────────
+// ── IS THIS THE REPORT, OR CHROME'S OWN ERROR PAGE? ──────────────────────────────────────────────────
 //
 // Chrome is launched with the file URL as an ARGUMENT, so there is no navigation response to check and
 // nothing here ever asked. When the file could not be read, Chrome showed `ERR_ACCESS_DENIED` — a page
@@ -126,7 +126,7 @@ if (typeof top !== "number") {
   console.error(`report-screenshot: no element matched ${JSON.stringify(ANCHOR)} — nothing to anchor the frame to.`);
   chrome.kill(); process.exit(1);
 }
-// ── CAN THIS BOX DRAW WHAT THE PAGE SAYS? (tracker issue 227) ───────────────────────────────────────
+// ── CAN THIS BOX DRAW WHAT THE PAGE SAYS? ───────────────────────────────────────────────────────────
 //
 // The default demo product's report carries the mark's native-script renderings — ベンクリ, ベンコリ,
 // ヴェンコリ — and they are load-bearing: the verdict sentence reads "A live Japanese class 9

package/scripts/retire-bare-refs.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 // SPDX-License-Identifier: AGPL-3.0-only
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
-// Retire bare `#NNN` tracker references from prose (tracker issue 188).
+// Retire bare `#NNN` tracker references from prose.
 //
 //   node scripts/retire-bare-refs.mjs            what would change, per file
 //   node scripts/retire-bare-refs.mjs --apply    change it

package/scripts/revisit-render-check.mjs

@@ -146,7 +146,7 @@ const server = createServer((req, res) => {
     hits.push({ epoch, route: routeKey(p, u.searchParams) })
   }
 
-  if (p === '/portal/api/me') return json(res, { email: 'staff@example-firm.com', role: 'staff', accounts: '*', accountNames: {}, allowance: null })
+  if (p === '/portal/api/me') return json(res, { email: 'manager@example-firm.com', permissions: { run: true, manage: true }, access: [{ kind: 'everything' }], accounts: '*', accountNames: {}, allowance: null })
   if (p === '/portal/admin/roster') return json(res, { customers: [{ key: KEY, name: NAME }] })
   if (p === '/portal/admin/families') return json(res, { of: {}, names: {} })
   if (p === '/portal/api/runs') return json(res, { runs: RUNS() })

package/scripts/score.mjs

@@ -646,7 +646,7 @@ function print(id, ref, run, s, delta, refPath) {
     for (const c of B.collisions)
       console.log(`    · ${c.owner}: reference "${c.entry}" is ${c.bucket}, surfaced "${c.noise}" is noise`);
   }
-  // ── SAME PROPRIETOR, DIFFERENT MARKS — REPORTED, NEVER SUPPRESSING (tracker issue 249) ───────────
+  // ── SAME PROPRIETOR, DIFFERENT MARKS — REPORTED, NEVER SUPPRESSING ───────────────────────────────
   //
   // These used to print under the line above, which tells the reader not to read the recall numbers.
   // One large filer anywhere in a matter therefore suppressed a whole run's measurement, and did: R2's