@heroiclands/package-build 20.3.0 → 20.4.0

package/sohl/items.mjs

@@ -19,14 +19,14 @@
  * note, looking its subtype up in the system's map, dispatching to the
  * consumer's registry, merging the authored `sohl.system` block, checking what
  * was emitted against the receiving schema, and writing the envelope. That was
- * all here until a second system needed it (#139), and it reached its
+ * all here until a second system needed it, and it reached its
  * system-specific facts through one constant read off SoHL's own map — which is
  * why lifting it cost a subclass rather than a rewrite.
  *
  * What stays:
  *
  * - **The map**, declared in `document-subtypes.mjs` and named here, which
- *   decides which notes this pass claims and what each one becomes (#79).
+ *   decides which notes this pass claims and what each one becomes.
  * - **`commonSystem`** — `shortcode`, `templatePriority`, `actionDefs`, `notes` and
  *   `docHtml`, which SoHL's compiler writes on every item of every type and no
  *   field declaration states.
@@ -44,13 +44,27 @@ import { SOHL_DOCUMENT_SUBTYPES } from "./document-subtypes.mjs";
 export class Items extends SystemItemCompiler {
     /**
      * SoHL's note-type → document-subtype map — the one declaration that says
-     * which block this pass reads, which notes it claims, and what each becomes
-     * (#58/#79).
+     * which block this pass reads, which notes it claims, and what each becomes.
      *
      * @type {import("../engine/document-subtypes.mjs").DocumentSubtypeMap}
      */
     static documentSubtypes = SOHL_DOCUMENT_SUBTYPES;
 
+    /**
+     * The `system` keys this pass derives from the note.
+     *
+     * `docHtml` holds the `@UUID` of the JournalEntry the note's prose compiled
+     * into, so a note writing prose there ships a string where every reader
+     * expects a pointer. `notes` is a play-time scratchpad the compiler writes
+     * empty, so an authored one ships a note's content as a GM's jottings.
+     *
+     * @type {readonly {key: string, from: string}[]}
+     */
+    static derivedSystemKeys = Object.freeze([
+        { key: "docHtml", from: "the note's own body" },
+        { key: "notes", from: "the note's own body" },
+    ]);
+
     /**
      * The `system.*` fields SoHL writes on every item, whatever its type:
      * shortcode, templatePriority, actionDefs, notes, docHtml.
@@ -65,8 +79,8 @@ export class Items extends SystemItemCompiler {
         return {
             shortcode: fm.shortcode,
             // Required nullable number: a priority, or `null` for a document
-            // that is not a template (#126 / archetype contract #604). The
-            // field was `system.archetype` until #266 / sohl#1836; the receiving
+            // that is not a template (the archetype contract).
+            // `system.archetype` is the legacy spelling; the receiving
             // schema declares only the new name, so the emitted key moves with
             // it — an undeclared `system` key is discarded at construction
             // without a warning.

package/sohl/kb-passes.mjs

@@ -12,12 +12,12 @@
  */
 
 /**
- * The `sohl` knowledgebase's own body passes (#63).
+ * The `sohl` knowledgebase's own body passes.
  *
  * `content-build site` publishes a content tree as a website, and almost all of
  * that job is the same for every package. These two rewrites are not: they are
  * driven by a TypeDoc symbol map and a repository layout only this package has,
- * and #63 rules them explicitly per-consumer.
+ * and they are ruled explicitly per-consumer.
  *
  * They live here rather than in a script in the consuming repository for the
  * same reason `sohl/item-builders.mjs` and `sohl/being-info.mjs` do: a
@@ -33,7 +33,7 @@
  * broken link or a failed build for a syntax example in prose would not be.
  *
  * Building the bundle is a different matter: a `symbolMap` that is configured
- * and cannot be used fails, loudly, before a page is rendered (#75). Degrading
+ * and cannot be used fails, loudly, before a page is rendered. Degrading
  * a tag the map does not know is a judgement about *prose*; degrading every tag
  * on the site because the map was never read is a build that lied.
  *
@@ -58,12 +58,12 @@ import log from "loglevel";
  * with no symbols: a bare `catch` returned `{}` for all five. Nothing then
  * compares an emitted page against what its source asked for, so the first
  * observer of a broken map was a reader who clicked nothing, because every
- * `{@link}` on the published site had quietly become a code span (#75).
+ * `{@link}` on the published site had quietly become a code span.
  *
  * The path is resolved against the **repository root**, never the process cwd.
  * `site.passOptions.symbolMap` is authored repo-relative, so a cwd-relative
  * read misses the moment `content-build site` is driven from anywhere but the
- * repository root — which is exactly how #51's end-to-end verification, running
+ * repository root — which is exactly how the end-to-end verification, running
  * through `PACKAGE_BUILD_CONFIG` from outside the tree, found this.
  *
  * @param {string|undefined} file - Path to the map, if configured.

package/sohl/note-schemas.mjs

@@ -13,7 +13,7 @@
 
 /**
  * What every SoHL content type may write under `sohl:` — the vocabulary the
- * frontmatter linter checks a note against (#19).
+ * frontmatter linter checks a note against.
  *
  * **Item types need no declaration here.** {@link ITEM_FIELDS} already is one,
  * and it is the same list the compiler obeys, so an item's schema and its
@@ -26,7 +26,7 @@
  * nothing here builds anything, and claiming an emitted path they do not
  * produce would be a lie in the one place a reader would trust it. When one of
  * those compilers becomes declarative, its entry here becomes the builder, the
- * way `ITEM_FIELDS` did (#22).
+ * way `ITEM_FIELDS` did.
  *
  * **Every consumer loads all of it.** An adventure module authors the full
  * vocabulary — a specific skill, a magic sword, an NPC, a custom beast is the
@@ -94,7 +94,7 @@ const MACRO_FIELDS = Object.freeze([
  * vehicle two `data` properties and no `sohl:` field of its own, and the
  * closed `data:` container is where `engine/note-vocabulary.mjs` holds them.
  * Declaring the type with no fields distinguishes a type with no vocabulary
- * from a type that is unknown, which are different findings (#231).
+ * from a type that is unknown, which are different findings.
  *
  * It is here rather than in the engine because a vehicle is a SoHL actor —
  * the specification maps it to `sohl` and marks it NA for hm3.
@@ -139,7 +139,7 @@ const BEING_FIELDS = Object.freeze([
 
 /**
  * A map note — one type whose `battlemap` / `localmap` / `regionalmap`
- * subType decides the derived canvas (#174). Compiled into a
+ * subType decides the derived canvas. Compiled into a
  * Foundry Scene.
  *
  * The three differ only in derived canvas defaults, which is the map compiler's
@@ -148,8 +148,8 @@ const BEING_FIELDS = Object.freeze([
  *
  * `img` is the one required field — the compiler refuses a map note without it,
  * since a scene with no background is not a map. It was spelled `image` and
- * read from the `sohl:` block until #142, which read both while the trees were
- * swept; that retirement has since completed and `image` is gone (#149).
+ * read from the `sohl:` block; both were read while the trees were
+ * swept; that retirement has since completed and `image` is gone.
  *
  * @type {readonly import("../engine/field-spec.mjs").FieldSpec[]}
  */
@@ -332,7 +332,7 @@ const PRESENTATION_FIELDS = Object.freeze({
  * one vocabulary rather than two. They are declared there rather than here
  * because they are note-format knowledge — a `homepage` carries no `system`
  * block and would mean the same thing for a game system that is not SoHL — and
- * because a package declaring no `itemBuilders` never reaches this file (#51).
+ * because a package declaring no `itemBuilders` never reaches this file.
  *
  * @type {Readonly<Record<string, readonly import("../engine/field-spec.mjs").FieldSpec[]>>}
  */

package/sohl/skill-base.mjs

@@ -13,7 +13,7 @@
 
 /**
  * Build-time Skill Base evaluation — the small part of SoHL's `SafeExpression`
- * needed to compile a skill's opening mastery level into the pack (#46).
+ * needed to compile a skill's opening mastery level into the pack.
  *
  * A skill's `skillBaseFormula` is a `SafeExpression` in the `skill.base` scope:
  * an expression over one binding, `attr` (attribute scores by shortcode), with

package/types/content-config.d.mts

@@ -49,7 +49,7 @@ export namespace DEFAULT_PATHS {
 /**
  * The Foundry document types a compendium pack may hold. This is the set the
  * toolchain is able to compile a pack of; a document type Foundry supports but
- * this toolchain does not compile is deliberately absent (see #1501 — playlists
+ * this toolchain does not compile is deliberately absent (playlists
  * and roll tables are out of scope).
  *
  * @satisfies {readonly PackDocumentType[]}
@@ -68,15 +68,11 @@ export const PACK_DOCUMENT_TYPES: readonly ["Actor", "Adventure", "Item", "Journ
  * key is **refused**, at the line it was written on, with a message that says
  * the mechanism is gone rather than naming a value to correct.
  *
- * **What `landing` did (#204).** It named which note addressed a whole section
+ * **`landing` is one such key.** It named which note addressed a whole section
  * rather than a page within one — a *landing page*, which therefore had no slug
- * of its own. #203 retired the second of its two rules and #204 retired the
- * concept both rules chose between: a section is a Hugo content directory that
- * the note format does not carry, a page's address names no directory, and so
- * no note lands anything. The key outlived its mechanism by one release only
- * because both publishing consumers still declared the then-true
- * `landing: readme`, and neither breaking them over a correct statement nor
- * accepting the key in silence was acceptable. Neither declares it now.
+ * of its own. There are no sections to address: a section is a Hugo content
+ * directory the note format does not carry, a page's address names no
+ * directory, and so no note lands anything.
  *
  * @type {Readonly<Record<string, string>>}
  */
@@ -89,7 +85,7 @@ export const RETIRED_ADDRESS_KEYS: Readonly<Record<string, string>>;
  * `thalorna`, whose site is nothing but its content. It is not the package's
  * own mount point: where the package itself is served is the consuming build's
  * knowledge, held in `PACKAGE_BASE` (`engine/content-address.mjs`) and prefixed at
- * resolve time, so it is never recorded here (#1465).
+ * resolve time, so it is never recorded here.
  *
  * It is the whole scheme: `landing`, the key that named which note addressed a
  * whole section, is retired with the sections themselves — see
@@ -103,7 +99,7 @@ export const DEFAULT_ADDRESS_SCHEME: Readonly<{
  *
  * Every HeroicLands package publishes something: a top-level, human-authored
  * homepage at `https://www.heroiclands.org/<contentPackage>/` saying what the
- * module is, which system it needs and how to install it (#50). So there is no
+ * module is, which system it needs and how to install it. So there is no
  * value here meaning *no web presence at all* — homepage-only is the **floor**,
  * and the default.
  *
@@ -141,7 +137,7 @@ export const SITE_MODES: readonly ["homepage", "content"];
  * How the loader hands {@link defineConfig} the system version it resolved.
  *
  * A **Symbol**, deliberately. `stats.systemVersion` is refused from an authored
- * configuration (#48), but the value still has to reach here from the loader —
+ * configuration, but the value still has to reach here from the loader —
  * which is the half that may do I/O, and which reads a system package's version
  * out of the adjacent `package.json`. A string key would be a second spelling of
  * the refused one, forgeable from YAML and reachable by `rejectUnknownKeys`; a
@@ -156,7 +152,7 @@ export const DERIVED_SYSTEM_VERSION: symbol;
  *
  * Every HeroicLands package publishes something: a top-level, human-authored
  * homepage at `https://www.heroiclands.org/<contentPackage>/` saying what the
- * module is, which system it needs and how to install it (#50). So there is no
+ * module is, which system it needs and how to install it. So there is no
  * value here meaning *no web presence at all* — homepage-only is the **floor**,
  * and the default.
  *
@@ -194,7 +190,7 @@ export type PackDocumentType = "Actor" | "Adventure" | "Item" | "JournalEntry" |
  * type** receives its document. The two are orthogonal, and both are needed
  * once a repository groups same-type documents editorially — which it may have
  * to, since a compendium UUID carries its pack name and collapsing such a
- * layout breaks every stored reference (#1566).
+ * layout breaks every stored reference.
  */
 export type PackSpec = {
     /**
@@ -304,7 +300,7 @@ export type PathsInput = {
     foreignCache?: string | undefined;
     /**
      * Where a dependency's published content
-     *     index is fetched to (#239). Inbound,
+     *     index is fetched to. Inbound,
      *     for *every* declared dependency, not
      *     only those supplying a catalogue.
      */
@@ -503,7 +499,7 @@ export type AddressSchemeInput = {
  * `fields` is what makes the type documentable: a builder function says
  * nothing about the vocabulary it consumes, so a consumer that declares its
  * fields can generate its own authoring reference and check its own notes,
- * while one that does not is simply undocumented rather than broken (#22).
+ * while one that does not is simply undocumented rather than broken.
  */
 export type ItemBuilderEntry = ((fm: object) => object) | {
     system: (fm: object) => object;
@@ -511,7 +507,7 @@ export type ItemBuilderEntry = ((fm: object) => object) | {
     fields?: readonly object[];
 };
 /**
- * One **registry** of a declared set, and the system it belongs to (#58).
+ * One **registry** of a declared set, and the system it belongs to.
  *
  * A repository shipping content for two systems declares one of these per
  * system: the accepted type vocabulary is their union, and a type both declare
@@ -570,7 +566,7 @@ export type ContentBuildConfigInput = {
      * two systems declares a **list** of
      * `{ system, builders }` registries
      * instead, and the accepted type
-     * vocabulary is their union (#58).
+     * vocabulary is their union.
      */
     itemBuilders?: Record<string, ItemBuilderEntry> | readonly ItemRegistrySpec[] | undefined;
     /**
@@ -579,8 +575,7 @@ export type ContentBuildConfigInput = {
      * the pack it belongs in with its
      * `pack:` frontmatter, and one pack of
      * the type is marked `default: true` to
-     * receive the notes that name none
-     * (#1566).
+     * receive the notes that name none.
      */
     packs: PackSpec[];
     /**
@@ -658,14 +653,13 @@ export type ContentBuildConfig = {
      * the frontmatter fields each entry
      * declared. Sparse, like `itemArt` — a type
      * absent here compiles normally and is
-     * simply undocumented (#22).
+     * simply undocumented.
      */
     itemFields: Readonly<Record<string, readonly object[]>>;
     /**
      *                                     Derived: the same builders, kept per
      *                                     declaring system. `{}` for the single
-     *                                     registry form, which names no system
-     *                                     (#58).
+     *                                     registry form, which names no system.
      */
     itemBuildersBySystem: Readonly<Record<string, Readonly<Record<string, Function>>>>;
     /**
@@ -688,7 +682,7 @@ export type ContentBuildConfig = {
      * {@link ContentBuildConfigInput.itemBuilders},
      * unioned across every declared registry, so
      * the accepted item types and the builder
-     * tables are one list (#1504).
+     * tables are one list.
      */
     itemTypes: ReadonlySet<string>;
     /**
@@ -700,6 +694,13 @@ export type ContentBuildConfig = {
      */
     docEntryTypes: ReadonlySet<string>;
     skipDirectories: readonly string[];
+    /**
+     * The
+     * fonts this package ships and the names it
+     * draws from them; empty when it declares
+     * none.
+     */
+    icons: import("./engine/content-icons.mjs").IconRegistry;
     packs: readonly Readonly<ResolvedPackSpec>[];
     /**
      * Derived: every pack directory

package/types/e2e.d.mts

@@ -220,7 +220,7 @@ export function findExecutable(name: string, { cwd, env }?: {
  *
  * Asked twice per run, and the second asking is the point: an install running
  * alongside the suite can take the runner out from under it mid-flight, which
- * is precisely the failure that reported itself as green (#153).
+ * is precisely the failure that reported itself as green.
  *
  * @param {object} opts
  * @param {readonly string[]} opts.command - The program and its arguments.
@@ -268,7 +268,7 @@ export function freshResults({ paths, since, cwd }: {
  * exit status on its own cannot call a run green, because every way of stopping
  * a runner before it starts — a corrupt install, a missing browser, a killed
  * process, the concurrent `npm ci` that surfaced this — produces a run that
- * executed nothing, and nothing is not a pass (#153).
+ * executed nothing, and nothing is not a pass.
  *
  * This can only ever make a verdict worse. A suite that failed keeps its own
  * status; a suite that passed on no evidence loses the claim. Never the other
@@ -297,7 +297,7 @@ export function suiteVerdict({ status, vanished, declared, fresh }: {
  * `MODULE_NOT_FOUND` naming nothing relevant.
  *
  * The suite is bracketed by checks rather than trusted on its exit status,
- * because a run that never started used to report as green (#153):
+ * because a run that never started used to report as green:
  *
  * - **Before.** Every executable the command needs is resolved, and a missing
  *   one is an error naming it — rather than a container stood up, a world

package/types/engine/actor-compiler.d.mts

@@ -34,7 +34,7 @@ export function deepMerge(base: any, overlay: any): any;
  * vocabulary, so a reference is translated forward through the system's map
  * before it reaches this function; see
  * {@link SystemActorCompiler#embeddedSubtype} for why the translation goes that
- * way and not the other (#140).
+ * way and not the other.
  *
  * @param {string} subType - The Foundry Item subtype.
  * @param {string} shortcode - The item's `system.shortcode`.
@@ -43,7 +43,7 @@ export function deepMerge(base: any, overlay: any): any;
 export function itemAddress(subType: string, shortcode: string): string;
 /**
  * The key one predefined item is held under **for the package that publishes
- * it** — the address a `model:` naming that package resolves through (#334).
+ * it** — the address a `model:` naming that package resolves through.
  *
  * The unqualified {@link itemAddress} stays beside it, and the two answer
  * different questions. A `model` that names no package means *this* one and
@@ -70,11 +70,12 @@ export function packagedItemAddress(pkg: string, subType: string, shortcode: str
  * A shortcode is case-sensitive and routinely mixed — `Clb`, `LtShoe`,
  * `HsTunic` — while an **address** is not: `readQualifier` normalises what it
  * reads, and every canonical address is lowercase. So the moment a `model:` is
- * read as an address (#334), `weapongear-clb` has to find the document whose
- * `system.shortcode` is `Clb`, and an exact match cannot (#346).
+ * read as an address, `weapongear-clb` has to find the document whose
+ * `system.shortcode` is `Clb`, and an exact match cannot.
  *
  * Folding is safe because the fold is already the address: no two items in any
- * published tree differ only by the case of their shortcode, and #340 will make
+ * published tree differ only by the case of their shortcode, and the rule
+ * makes
  * that impossible rather than merely true.
  *
  * **This is not {@link itemAddress}, and must not become it.** That one seeds
@@ -116,13 +117,13 @@ export function embeddedIdentity(item: object): string;
  * four corpora holds 180 items, at which 64 bits collide with probability
  * around 10⁻¹⁵.
  *
- * **It takes no index** (#268). Keying on a position meant reordering a being's
+ * **It takes no index**. Keying on a position meant reordering a being's
  * item list renumbered every id after the change, so a re-import created new
  * documents beside the old ones — while nothing about those documents had
  * changed, only their neighbours. The identity always exists or must be stated;
  * see {@link embeddedIdentity}.
  *
- * Keyed by the **document subtype**, so renaming a note type (#78) leaves every
+ * Keyed by the **document subtype**, so renaming a note type leaves every
  * embedded id where it was.
  *
  * @param {string} actorId - The owning actor's id.
@@ -186,7 +187,7 @@ export class SystemActorCompiler extends BasePackCompiler {
     foreignSourceDirs: any;
     /**
      * Every package a `model:` may name besides this one — the dependencies
-     * whose item catalogues were supplied (#334).
+     * whose item catalogues were supplied.
      *
      * @returns {Set<string>} The dependency package ids.
      */
@@ -210,7 +211,7 @@ export class SystemActorCompiler extends BasePackCompiler {
      * The Foundry Item subtype an embedded reference's `type` addresses.
      *
      * **The reference is in the note vocabulary; the address is in the
-     * document's** (#140). An actor writes `(type, shortcode)` with the type an
+     * document's**. An actor writes `(type, shortcode)` with the type an
      * author authors, while {@link itemAddress} keys the predefined items by
      * the subtype each compiled document carries — so exactly one of the two
      * sides has to translate, and it is this one. The system's map is a
@@ -230,7 +231,7 @@ export class SystemActorCompiler extends BasePackCompiler {
      * descriptor must carry enough fields to stand alone. The embedded
      * item's `_id` is regenerated deterministically from
      * `(actorId, subType, shortcode, indexKey)` so re-exports are stable —
-     * from the **document subtype**, so that renaming a note type (#78) leaves
+     * from the **document subtype**, so that renaming a note type leaves
      * every embedded id exactly where it was.
      * Returns null if the descriptor cannot be resolved.
      *
@@ -241,7 +242,7 @@ export class SystemActorCompiler extends BasePackCompiler {
      *   `null` for a stand-alone entry.
      * @param {object} [overlay] - The entry's remaining properties.
      * @param {string} indexKey - Where the reference sits, for a diagnostic.
-     *   It no longer reaches the id (#268) — it names the entry in a message.
+     *   It no longer reaches the id — it names the entry in a message.
      * @param {string} ctx - Diagnostic context (the actor's label).
      * @param {object} [at] - Where to locate a finding.
      * @param {string} [at.fmKey] - The frontmatter key the reference sits
@@ -253,7 +254,7 @@ export class SystemActorCompiler extends BasePackCompiler {
     /**
      * Read an entry's `model:` — the address of the item it is a copy of.
      *
-     * The address grammar is the wikilink one (#336), so a `model` is written at
+     * The address grammar is the wikilink one, so a `model` is written at
      * whatever length says what it means: `skill-wpnc` within this package,
      * `sohl-sohl-skill-wpnc` to reach another. The system segment defaults from
      * the block the entry sits in — `<system>.items` — which is what makes the
@@ -262,7 +263,7 @@ export class SystemActorCompiler extends BasePackCompiler {
      *
      * It replaced a top-level `shortcode:` that meant something different from
      * the `system.shortcode` beside it and could not say which package a
-     * template came from (#334).
+     * template came from.
      *
      * @param {unknown} model - The authored value.
      * @param {number} index - The entry's position, for the message.

package/types/engine/address-charset.d.mts

@@ -11,7 +11,7 @@
  */
 export function isAddressSegment(value: unknown): boolean;
 /**
- * The one charset every segment of a canonical address is held to (#59).
+ * The one charset every segment of a canonical address is held to.
  *
  * An address is a hyphen-joined tuple — `package-system-type-shortcode`, so
  * `sohl-none-doc-gear` — and it is read back by **counting segments**, with a
@@ -41,7 +41,7 @@ export function isAddressSegment(value: unknown): boolean;
  * digits only.
  *
  * Case *was* deliberately unconstrained, on the reasoning that case has no
- * bearing on the separator — which is true, and beside the point (#340).
+ * bearing on the separator — which is true, and beside the point.
  *
  * **Two names that differ only in case are two names nobody can tell apart.** A
  * shortcode is how a person names a thing when writing a reference —
@@ -53,10 +53,10 @@ export function isAddressSegment(value: unknown): boolean;
  * `sohl-sohl-weapongear-clb` and its `_id` derived from that. The authored name
  * and its address disagreed, and everything downstream keys on the address —
  * which left two notes differing only in case sharing one address, one `_id` and
- * one URL, with nothing to report it. It also forced two exceptions elsewhere:
- * #336 had to exempt the shortcode from the lowercase rule it pinned on every
- * other segment, and #346 had to fold the shortcode's case in the item catalogue
- * because an address is lowercased when read.
+ * one URL, with nothing to report it. It also forces two exceptions elsewhere:
+ * the shortcode has to be exempted from the lowercase rule pinned on every
+ * other segment, and its case has to be folded in the item catalogue because
+ * an address is lowercased when read.
  *
  * One case, one spelling, no exceptions. Every tree already complies but two,
  * and nothing in any of them collides when folded.

package/types/engine/address-diff.d.mts

@@ -57,7 +57,7 @@ export function declaredPredecessors(contentBase: any, { skipDirectories, maps,
  * @param {Map<string, {to: string, file: string}>} [opts.predecessors] - The
  *   declared renames, from {@link declaredPredecessors}. Omitted, the diff
  *   falls back to the id join alone and reports an unpinned rename as a
- *   withdrawal, which is what it did before #278.
+ *   withdrawal, which is what it did before.
  * @returns {Array<object>} One finding per departed address, in address order
  *   so two runs read the same. `kind` is `"renamed"` (with `to`, and `declared`
  *   when it was the note's word rather than an id match) or `"withdrawn"`.
@@ -105,7 +105,7 @@ export function noteFilesById(contentBase: string, { skipDirectories, config, re
  * A **declared** rename knows its note without any lookup — the declaration is
  * how it was found — and is reported at the `renamedFrom:` line rather than the
  * `shortcode:` line, because that is the line the finding is about and the one
- * the author deletes once the declaration has done its work (#278).
+ * the author deletes once the declaration has done its work.
  *
  * @param {object} finding - One finding from {@link diffItemAddresses}.
  * @param {Map<string, string>} noteFiles - From {@link noteFilesById}.
@@ -126,7 +126,7 @@ export function locateAddressFinding(finding: object, noteFiles: Map<string, str
  * known — and says so, rather than leaving the reader to wonder whether one was
  * looked for.
  *
- * **A declared rename says it is declared** (#278). The two claims are not
+ * **A declared rename says it is declared**. The two claims are not
  * equally checkable: an id match is a fact in the artefacts, while a
  * declaration is an author's word, and a reader deciding whether to trust the
  * successor needs to know which one they have. Saying "the same document" of a