@heroiclands/package-build 20.3.0 → 20.4.0

package/engine/content-links.mjs

@@ -27,9 +27,9 @@
  *    written target is a *partial* address — the segments it omits are
  *    wildcards, and the package it omits is this one — so a target resolving to
  *    *several* notes is an ambiguity rather than a first match, and is reported
- *    naming every candidate (#59).
+ *    naming every candidate.
  * 3. **An unlabelled link.** `[[x]]` addresses nothing: the alias namespace it
- *    used to name is retired (#180), and a shortcode is an address rather than
+ *    once named is retired, and a shortcode is an address rather than
  *    prose, so the link has neither a resolvable target nor text to show. The
  *    correction is always `[[type-shortcode|Text]]`.
  * 4. **A wikilink authored in frontmatter.** Both builds walk a note's *body*
@@ -49,7 +49,7 @@
  * document is reachable from the book's root" — is a statement about what one
  * package publishes, not about the note format, so it belongs with the
  * publishing it describes; so does a retired hostname. Both are served by the
- * link graph returned here rather than implemented here (#20).
+ * link graph returned here rather than implemented here.
  *
  * @module
  */
@@ -61,7 +61,7 @@ import { matchAllOutsideCode } from "./code-fences.mjs";
 import { expandContentTables } from "./content-tables.mjs";
 import { collectAnchors } from "./anchors.mjs";
 // The corpus, and everything derived from it, read from the one place that
-// derives it (#243). Nothing in the index's own import graph reaches this
+// derives it. Nothing in the index's own import graph reaches this
 // module, so this is a plain static import rather than the deferred one
 // `sql-tables` needs to keep out of the compilers' cycle.
 import { authoredFrontmatter, indexRecordsFor, isNoteRecord, noteFile } from "./content-index.mjs";
@@ -88,7 +88,7 @@ import { readQualifier } from "./wikilinks.mjs";
  * Every `{#anchor}` a note declares on a heading.
  *
  * **Read from the content index's reader, not a second one.** This module kept
- * its own until #243, and the two disagreed: it matched `{#([a-z0-9-]+)}` while
+ * its own, and the two disagreed: it matched `{#([a-z0-9-]+)}` while
  * {@link module:engine/content-index.collectAnchors} matches `{#([^}]+)}`, so
  * an anchor with a capital in it — `{#CalendarFormat}` — existed for the index
  * and for the compiler and did not exist for the link checker. Nothing links to
@@ -110,7 +110,7 @@ export function anchorsOf(body) {
  * Read a content tree into the index a link resolves against.
  *
  * **The corpus comes from the content index, not from a walk of this module's
- * own** (#243). Every pass used to answer "which files are the content?" for
+ * own**. Every pass used to answer "which files are the content?" for
  * itself and throw the answer away; this one now reads
  * {@link module:engine/content-index.indexRecordsFor}, which is the same
  * derivation the published artifact and the compilers are driven from. So a
@@ -118,7 +118,7 @@ export function anchorsOf(body) {
  * anchors it resolves against are the ones every other pass will emit — rather
  * than a second derivation that agrees with them only by inspection. That was
  * not hypothetical: this module carried its own anchor reader until the anchor
- * half of #243, and the two disagreed about which anchors existed.
+ * anchor half, and the two disagreed about which anchors existed.
  *
  * **The file is opened for its bytes and nothing else.** The index deliberately
  * carries no note *body*, and a link lives in the body — so each note is read
@@ -138,7 +138,7 @@ export function anchorsOf(body) {
  * @param {string} contentBase - Root of the content tree.
  * @param {object} [opts]
  * @param {object} [opts.config] - The resolved build configuration, whose
- *   fetched dependency indexes foreign addresses resolve through (#239), and
+ *   fetched dependency indexes foreign addresses resolve through, and
  *   whose `contentPackage` every local address is built from. Omitted, the
  *   ambient configuration is resolved and no cross-package address resolves.
  * @param {readonly string[]} [opts.skipDirectories] - The walk's scope, passed
@@ -162,10 +162,10 @@ export function buildLinkIndex(
 
     // The one package every note in this tree belongs to. Taken from the
     // configuration this build resolved — never from a note (`package:` is
-    // retired, so there is no second source an address could disagree with,
-    // #56) and never from the ambient one, which is a different configuration
+    // retired, so there is no second source an address could disagree with)
+    // and never from the ambient one, which is a different configuration
     // whenever a test injects one, `PACKAGE_BUILD_CONFIG` names one, or the
-    // command runs from a worktree (#243).
+    // command runs from a worktree.
     const resolved = config ?? loadPackConfig();
     const pkg = resolved.contentPackage;
 
@@ -197,12 +197,12 @@ export function buildLinkIndex(
         notes.push(note);
 
         // The anchors the index recorded, rather than a second reading of the
-        // same headings — the disagreement #243's anchor half removed.
+        // same headings — the disagreement the anchor half removes.
         anchors.set(note, new Set((record.anchors ?? []).map((a) => a.slug)));
 
         if (typeof fm.shortcode === "string" && fm.shortcode) {
             // Canonical addresses only. Every written target expands to one
-            // before lookup (#336), so there is nothing left for a short key to
+            // before lookup, so there is nothing left for a short key to
             // answer — and the short key was harmful: `type/shortcode` is
             // system-blind, set with a plain `Map.set`, so two notes in one
             // package sharing a `(type, shortcode)` across systems silently
@@ -245,7 +245,7 @@ export function buildLinkIndex(
     /** The searchable universe a `dataview` table draws its rows from. */
     const tableDocs = notes.map((n) => ({
         // Package present for a `WHERE … package = "…"` clause, synthesised
-        // rather than authored — see {@link searchableFrontmatter} (#56).
+        // rather than authored — see {@link searchableFrontmatter}.
         fm: searchableFrontmatter(n.fm, pkg),
         path: n.rel,
         tld: n.rel.split("/")[0],
@@ -259,14 +259,14 @@ export function buildLinkIndex(
      * @returns {Array<{target: string, anchor: string, text: string,
      *   occurrence: number, labelled: boolean}>} `target` is `""` for a
      *   same-page `[[#anchor]]`; `labelled` says whether the link carries the
-     *   `|` every link must have (#180).
+     *   `|` every link must have.
      */
     function linksOf(note) {
         let body = note.body;
         if (/^[ \t]*(?:`{3,}|~{3,})[ \t]*(?:dataview|sql)\b/im.test(body)) {
             body = expandContentTables(body, {
                 // Unfiltered: every note in the tree is this package's, so
-                // there is no other package's note to exclude (#56).
+                // there is no other package's note to exclude.
                 docs: tableDocs,
                 linkable: (d) => Boolean(d.fm.shortcode),
                 source: note.file,
@@ -316,7 +316,7 @@ export function buildLinkIndex(
      * Every indexed entry an address names, matching only the segments it
      * supplies.
      *
-     * This is the whole of #59's resolution rule in one place: a written
+     * This is the whole resolution rule in one place: a written
      * address is a *partial* one, unsupplied segments are wildcards, and the
      * caller requires exactly one hit. Nothing here decides an ambiguity — zero
      * and many are different findings with different fixes, so the count is
@@ -354,7 +354,7 @@ export function buildLinkIndex(
     function resolveAddress(target, keyPath) {
         const qualified = readQualifier(target, types, packages);
         if (!qualified || qualified.reason) return undefined;
-        // Every omitted segment defaults from where the link is written (#336),
+        // Every omitted segment defaults from where the link is written,
         // so the target expands to exactly one canonical address and this is a
         // plain lookup. There is no candidate set, and therefore no single-hit
         // rule and no ambiguity to report.
@@ -370,13 +370,13 @@ export function buildLinkIndex(
      * Every foreign manifest entry an address names, in package order.
      *
      * A written target is a **partial** address, so this matches on the
-     * segments it supplies and wildcards the rest (#59). A target naming a
+     * segments it supplies and wildcards the rest. A target naming a
      * package necessarily names its system too — omission runs left to right —
      * so the fully qualified form matches at most one entry; a shorter one
      * names no package, and resolves against any foreign package that
      * publishes it. Either way only exactly one hit resolves. Two claimants make it ambiguous, which is a different finding
      * from resolving nowhere and has a different fix, so the count is returned
-     * rather than collapsed here (#184).
+     * rather than collapsed here.
      *
      * @param {string} target - The link target.
      * @returns {object[]} The foreign entries, each carrying its `package`.
@@ -384,7 +384,7 @@ export function buildLinkIndex(
     function foreignHits(target, keyPath) {
         const q = readQualifier(target, types, packages);
         if (!q || q.reason) return [];
-        // An omitted package means *this* package (#336), so a short form
+        // An omitted package means *this* package, so a short form
         // addresses nothing foreign and never reaches a dependency's index.
         // Reaching another package is the fully qualified form's job, and
         // saying so is the whole point: a link that resolved into `sohl` only
@@ -428,7 +428,7 @@ export function buildLinkIndex(
         /**
          * Resolve a link target the way both builds do, or `undefined`. Every
          * link is an address, so this is {@link resolveAddress} under the name
-         * the walkers use (#180).
+         * the walkers use.
          */
         resolve: resolveAddress,
         resolveAddress,
@@ -453,7 +453,7 @@ export function buildLinkIndex(
 const SITE_HOST = /^(?:[a-z0-9-]+\.)*heroiclands\.org$/i;
 
 /**
- * Every package landing this build can name, as `package` → base (#87).
+ * Every package landing this build can name, as `package` → base.
  *
  * **A landing needs no manifest, and that is what makes it work.** The link
  * manifest indexes content notes, and a homepage is deliberately not one — it
@@ -578,13 +578,13 @@ function readAddress(url, packages) {
  * **What is checkable, stated plainly.** Only an address into this site is, and
  * only against facts this build already holds:
  *
- * - A **retired content type** in the path. The engine knows what used to exist
+ * - A **retired content type** in the path. The engine knows the retired names
  *   and what replaced it, so this is a fact rather than a guess — and it is
  *   exactly the SoHL defect.
  * - A **hardcoded absolute URL** into this package's own prefix, or into one a
  *   a fetched index names. Every one of them has a better form to write, which
  *   is why every one is reported — including a bare `/<package>/`, which names
- *   another package's landing (#87).
+ *   another package's landing.
  *
  *   That last case was exempt until the better form was identified, on the
  *   reasoning that a landing is in no link manifest so nothing could resolve it.
@@ -658,7 +658,7 @@ export function auditHomepageLinks(index) {
             // Landings first, and by the roster rather than by the manifest
             // package set: a landing is addressable in a repository that
             // has fetched no index at all, which is the case the fence creates
-            // and the case this rule exists for (#87).
+            // and the case this rule exists for.
             const landing = landingTarget(url, bases);
             if (landing) {
                 report(
@@ -749,7 +749,7 @@ export function auditHomepageLinks(index) {
  *
  * **How the link is *written* is a separate finding from where it points**, and
  * the two are kept apart because the corrections differ. An unlabelled link
- * (#180) has to become `[[type-shortcode|Text]]`; a labelled one whose target
+ * has to become `[[type-shortcode|Text]]`; a labelled one whose target
  * resolves nowhere has a shortcode to fix. Reporting a bare `[[Name]]` as a
  * dead address would send an author hunting for a note that was never named.
  *
@@ -761,7 +761,7 @@ export function auditHomepageLinks(index) {
  *   carries a `reason` from {@link LINK_FINDING_REASONS} —
  *   `"not-an-address"`, `"unknown-type"`, `"ambiguous"` (with the claiming
  *   `packages`), or `"unresolved"` — and every one of them is an **error**:
- *   the three resolvers agree on severity for every class (#184).
+ *   the three resolvers agree on severity for every class.
  */
 export function auditLinks(index) {
     const { notes, anchors, linksOf, resolve, manifestHit, isAddress } = index;
@@ -792,7 +792,7 @@ export function auditLinks(index) {
     for (const note of notes) {
         for (const { target, anchor, text, occurrence, labelled } of linksOf(note)) {
             // The label is required whatever the link part is, an anchor
-            // included — so this is tested before the same-page form (#180).
+            // included — so this is tested before the same-page form.
             if (!labelled) {
                 unlabelledLinks.push({
                     note,
@@ -824,7 +824,7 @@ export function auditLinks(index) {
                 // Two packages publish the short address, so it names neither.
                 // Reported as its own class: "no document has that identity" is
                 // false here — two do — and the fix is the qualified form
-                // rather than a corrected shortcode (#184).
+                // rather than a corrected shortcode.
                 deadAddresses.push({
                     ...at,
                     reason: "ambiguous",

package/engine/content-lint.mjs

@@ -15,8 +15,8 @@
  * Linting a content tree's **addresses** — the rules every package's notes are
  * authored against, wherever those notes live.
  *
- * These rules used to live in the SoHL repository's `utils/`, which had two
- * consequences and no upside (#20). `thalorna` and `kethira` notes were checked
+ * These rules do not live in a consumer's `utils/`, which has two
+ * consequences and no upside. `thalorna` and `kethira` notes were checked
  * by nothing at all, so the packages most likely to carry authoring mistakes
  * were the ones nothing inspected. And one rule with two implementations can
  * disagree without anything detecting it, which the canonical-separator
@@ -30,28 +30,24 @@
  *    being the only hyphen in the string.
  * 2. **Uniqueness** — `(type, shortcode)` names one note.
  * 3. **The package's own address** — exactly one note claims `/<package>/`,
- *    which is {@link checkHomepageCount} (#52). It belongs here for the same
+ *    which is {@link checkHomepageCount}. It belongs here for the same
  *    reason the other two do: it is a statement about which note holds which
  *    address, it needs no `site:` configuration to decide, and a package with
  *    no front page is misconfigured whether or not anyone runs a site build.
  * 4. **Vacated addresses** — a `renamedFrom:` entry names an address this note
- *    used to hold and nothing holds now (#278). It is the same statement as
+ *    once held and nothing holds now. It is the same statement as
  *    rule 2 read backwards, and it needs the same whole-tree view: an entry can
  *    only be checked against every *other* note's address, and two notes
  *    claiming one predecessor is the uniqueness rule applied to the past.
  *
  * **Nothing here writes.** A check reports and an author fixes.
  *
- * **A third rule was retired (#79).** Every note used to be required to repeat
- * its own `type-shortcode` address in the top-level `aliases:` list. That
- * served exactly one reader — **Obsidian**, so `[[type-shortcode]]` resolved in
- * the editor — and nothing else ever read it: both resolvers parse the hyphen
- * qualifier themselves. The project no longer authors in Obsidian, so the rule
- * required a line of frontmatter per note for a reader that does not exist. The
- * field itself is retired now (#180), refused from `retired-fields.mjs`. Removing it was
- * verified output-neutral beforehand: across 1,735 stripped notes,
- * `package compile` produced byte-identical `build/packs-json` and the site
- * build byte-identical `site/content`.
+ * **There is deliberately no third rule** requiring every note to repeat its
+ * own `type-shortcode` address in a top-level `aliases:` list. It would serve
+ * exactly one reader — **Obsidian**, so `[[type-shortcode]]` resolves in the
+ * editor — and nothing in the build reads it: both resolvers parse the hyphen
+ * qualifier themselves. The field is retired, refused from
+ * `retired-fields.mjs`.
  *
  * **What is deliberately absent.** Corpus reachability — "every Rules document
  * is reachable from the book's root" — is a statement about what one package
@@ -67,7 +63,7 @@ import path from "node:path";
 import { ADDRESS_SEGMENT_PATTERN } from "./address-charset.mjs";
 import { positionInFrontmatter } from "./diagnostics.mjs";
 import { assertStatedScope } from "./helpers.mjs";
-// The corpus, read from the one pass that derives it (#243).
+// The corpus, read from the one pass that derives it.
 import { authoredFrontmatter, indexRecordsFor, isNoteRecord, noteFile } from "./content-index.mjs";
 import { checkHomepageCount, isHomepage } from "./homepage.mjs";
 import { declaresRenamedFrom, renamedFrom, renamedFromEntries } from "./note-renames.mjs";
@@ -78,7 +74,7 @@ import { declaresRenamedFrom, renamedFrom, renamedFromEntries } from "./note-ren
  * This is {@link ADDRESS_SEGMENT_PATTERN}, not a second copy of it. A shortcode
  * is the last segment of a canonical address, and the rule it is held to is the
  * rule *every* segment is held to — so the two are one constant rather than two
- * free to drift apart (#59). The name survives because this is where the rule
+ * free to drift apart. The name survives because this is where the rule
  * is applied to a note.
  *
  * Case is deliberately **not** constrained: hundreds of authored shortcodes are
@@ -112,7 +108,7 @@ export function isValidShortcode(value) {
  * `Templates/`, a `README`, a repository's own `CLAUDE.md` — has no type, is
  * neither addressed nor addressable, and would fail rules it can never satisfy.
  *
- * **Read from the index, not from a walk of this pass's own** (#243). The
+ * **Read from the index, not from a walk of this pass's own**. The
  * `lint` command already derives the index — its link check and its `sql`
  * tables are built from it — and then walked the tree a second time to get
  * here, so one command held two answers to "which files are the corpus?" and
@@ -162,7 +158,7 @@ function collectNotes(contentBase, { skipDirectories, config, records, problems
 }
 
 /**
- * What one note's `renamedFrom:` says, checked against itself (#278).
+ * What one note's `renamedFrom:` says, checked against itself.
  *
  * The entries a note can be wrong about on its own: a value that is not a
  * shortcode, one naming the address the note holds *now*, one written twice.
@@ -276,7 +272,7 @@ function checkRenamedFrom({ fm, file }, raw) {
  * @param {object} [opts.config] - The resolved build configuration, which the
  *   corpus is derived against.
  * @param {readonly object[]} [opts.records] - Index records the caller already
- *   derived, so a command reads one corpus (#243).
+ *   derived, so a command reads one corpus.
  * @param {object[]} [opts.problems] - Collects the notes the index cannot
  *   record, instead of letting one of them silence the lint.
  * @returns {{findings: Array<{file: string, line?: number, column?: number,
@@ -348,17 +344,17 @@ export function lintContentTree(
     // what a tree that failed to check out produces — so the lint would go
     // green on the one state it most needs to catch.
     //
-    // The state that catches is an **empty walk**, not an empty key set (#77).
+    // The state that catches is an **empty walk**, not an empty key set.
     // Notes may be keyless: a folder document carries no `shortcode`, and a
     // tree of them is populated, correct, and unkeyed. Reporting that as a
     // missing checkout trains its author to stop reading the output — the one
     // thing this guard needs them to do. A tree holding notes is therefore a
     // tree; only a tree holding none is the absent one.
     //
-    // The homepage used to be the headline example, because it was addressed
+    // The homepage is not the headline example, though it was once addressed
     // by the package rather than by a slug — so a `publish.site: homepage`
     // package had a tree with exactly one note and no key at all. It carries an
-    // address like every other note now (#182); the guard is unchanged, because
+    // address like every other note now; the guard is unchanged, because
     // what it reads was never the key count.
     if (notes.length === 0) {
         findings.push({
@@ -401,8 +397,8 @@ export function lintContentTree(
         }
     }
 
-    // The two questions about a declared rename that need the whole tree
-    // (#278). Both are the uniqueness rule above, applied to the past: an
+    // The two questions about a declared rename that need the whole tree.
+    // Both are the uniqueness rule above, applied to the past: an
     // address has one holder, so it has one successor and it cannot be both
     // vacated and occupied.
     for (const [claim, claimants] of claimedPredecessors) {

package/engine/content-package.mjs

@@ -16,7 +16,7 @@
  * ships them — read from the repository's `package-build.config.yaml`.
  *
  * Both values are **derived**, not declared: `config.mjs` is the single place
- * the configuration is resolved (#1508). This module survives as the import
+ * the configuration is resolved. This module survives as the import
  * path the link resolver and the compilers have always used, so that the values
  * can still be mocked in one place and so no consumer has to learn a new
  * spelling for them.
@@ -35,13 +35,11 @@ import { loadPackConfig } from "./pack-config.mjs";
  * repository's identity in the address space, not a switch — and never dead
  * configuration, whatever else changes.
  *
- * It was also, until #56, a **selector**: a note declared the same value in its
- * `package:` frontmatter and the compilers kept the ones that matched. Every
- * content tree is single-package — each is single-sourced in the repository that
- * ships it — so the field restated this constant once per note while a value
- * that matched nothing filtered the whole tree out in silence. That field is
- * retired and declaring it now fails the build; this value stays, here, where
- * it is declared once.
+ * It is not a **selector**. Every content tree is single-package — each is
+ * single-sourced in the repository that ships it — so a `package:` field on a
+ * note would restate this constant once per note, and a value matching nothing
+ * would filter the whole tree out in silence. That field is refused, and this
+ * value stays here, declared once.
  *
  * Stable across compilation targets. If this content were ever compiled for a
  * second game system, it would still be published as `sohl` — only the Foundry
@@ -65,7 +63,7 @@ export function contentPackage() {
  * here: a note is published under `sohl` and its documents are addressed as
  * `Compendium.sohl.<pack>.<Type>.<id>`. In `sohl-thalorna` the two differ
  * (`thalorna` vs `sohl-thalorna`), which is why they are separate values rather
- * than one — treating them as interchangeable is what #1498 was.
+ * than one — treating them as interchangeable is the mistake.
  *
  * Configured rather than read from the manifest so the link resolver stays
  * filesystem-free and unit-testable. `assertPackageIdMatchesManifestFile` in

package/engine/content-slug.mjs

@@ -17,9 +17,9 @@
  * {@link slugify} reduces a piece of prose — a heading, a document name — to a
  * URL-safe token. It is **not** how a page is addressed: a note's URL is its
  * address, `type-shortcode`, derived in `engine/content-address.mjs` and
- * touching no display string at all (#181).
+ * touching no display string at all.
  *
- * That used to be the other way round. This module carried a `contentSlug` that
+ * It is not the other way round: a `contentSlug` here that
  * derived a page's URL from `name.full`, abbreviating it through a table of 200
  * words so the result stayed short, and a `findSlugCollisions` to catch the two
  * notes that would then claim one URL. Its own header justified the readability

package/engine/content-tables.mjs

@@ -59,7 +59,7 @@
 
 // The fence syntax is stated once, in `code-fences.mjs`, so the scanner that
 // *skips* code and the one that expands a `dataview` block cannot disagree
-// about where a block begins and ends (#1505).
+// about where a block begins and ends.
 import { FENCE_LINE } from "./code-fences.mjs";
 
 /** What a cell shows when its expression resolves to nothing. */
@@ -1084,7 +1084,7 @@ export function renderContentTable(spec, rows, linkable, self) {
  *   reason: string, line: number}>, lineMap: Array<{line: number,
  *   generated: boolean}>}} `lineMap` is parallel to the emitted lines and says
  *   which authored line each came from, so a diagnostic about the expanded
- *   body can name an authored position (#17). An `errors` entry carries the
+ *   body can name an authored position. An `errors` entry carries the
  *   0-based line of the directive that failed, for the same reason.
  */
 /**
@@ -1121,12 +1121,12 @@ export function expandContentTables(
     let sqlOrdinal = 0;
     // One entry per `dataview` directive still authored, so a caller can say how
     // much of the corpus is still on the retiring language without this pass
-    // failing a build over it (#246).
+    // failing a build over it.
     const warnings = [];
     const lines = String(markdown ?? "").split("\n");
     const out = [];
     // Which authored line each emitted line came from, so a later pass can
-    // report an authored position for text this one moved (#17). A generated
+    // report an authored position for text this one moved. A generated
     // row has no authored line of its own, so it is blamed on the directive
     // that produced it — the thing an author can actually edit — and marked,
     // because its columns mean nothing.
@@ -1203,8 +1203,7 @@ export function expandContentTables(
             line: i,
             column: indent.length + 1,
             reason:
-                "`dataview` content tables are being replaced by `sql` over the " +
-                "content index (#246)",
+                "`dataview` content tables are being replaced by `sql` over the " + "content index",
         });
         // `dataview allow-empty` says a table selecting nothing is the intended
         // state. Spelled on the fence rather than in the query, because it is a
@@ -1219,7 +1218,7 @@ export function expandContentTables(
             // a header with nothing under it makes that indistinguishable from
             // a category that is legitimately empty. Eight tables in `sohl`'s
             // `Rules/Bestiary.md` published that way for months after the
-            // `creature` → `being` rename, and no build said a word (#223).
+            // `creature` → `being` rename, and no build said a word.
             if (rows.length === 0 && !allowEmpty) {
                 errors.push({
                     source,
@@ -1239,7 +1238,7 @@ export function expandContentTables(
                 directive: block.join("\n"),
                 reason: err.message,
                 // The fence's own line, so a table error is as locatable as
-                // everything else the build reports (#17).
+                // everything else the build reports.
                 line: i,
             });
             block.forEach((text, k) => emit(text, i + k));

package/engine/content-tree.mjs

@@ -20,7 +20,7 @@
  * notices — the LevelDB packs are written, the deploy mirrors them, and the
  * defect surfaces as "my compendiums are blank" long after the build went green.
  *
- * `assets/content/` is this repository's own source (#1445), but an empty or
+ * `assets/content/` is this repository's own source, but an empty or
  * partial tree is still possible — a bad checkout, or a sparse clone. This
  * counts what is actually there so the build can refuse.
  */