@heroiclands/package-build 20.3.1 → 20.4.0

package/engine/note-schemas.mjs

@@ -13,7 +13,7 @@
 
 /**
  * The note types the **engine** declares — the ones whose vocabulary is a fact
- * about the note format rather than about any game system (#51).
+ * about the note format rather than about any game system.
  *
  * `sohl/note-schemas.mjs` is the other half, and the line between them is the
  * `engine/` ÷ `sohl/` line everywhere else in this package: note-format
@@ -55,7 +55,7 @@ import { HOMEPAGE_FIELDS, HOMEPAGE_TYPE } from "./homepage.mjs";
  * all three and nothing implemented them, so a note using one was reported as
  * having no schema and then *skipped entirely*: `lintNote` returns after that
  * finding, so the note's `data:`, `subType`, references and system block all
- * went unexamined (#231).
+ * went unexamined.
  *
  * @type {readonly import("./field-spec.mjs").FieldSpec[]}
  */
@@ -90,7 +90,7 @@ const BUNDLE_FIELDS = Object.freeze([]);
  * Empty for the same reason a bundle's is: a folder declares no system-block
  * fields, because a `Folder` is a core Foundry document rather than any
  * system's. Its two properties — `parent` and `color` — are `data:` keys, held
- * closed by `engine/note-vocabulary.mjs` (#256).
+ * closed by `engine/note-vocabulary.mjs`.
  *
  * @type {readonly import("./field-spec.mjs").FieldSpec[]}
  */

package/engine/note-vocabulary.mjs

@@ -13,7 +13,7 @@
 
 /**
  * The **closed** half of a note's frontmatter: the `data:` container, and the
- * `subType` each note type declares (#128).
+ * `subType` each note type declares.
  *
  * A note's frontmatter has three regions, and only one of them is open. The
  * **top level** describes the note as a published artefact, every key of it is
@@ -42,17 +42,17 @@
  * transmission — and is true of it whichever system is reading. What each
  * system makes of that value is declared elsewhere, in that system's own half.
  *
- * **The type names here are the specification's**, since #78 renamed `armor`,
+ * **The type names here are the specification's**, which renamed `armor`,
  * `projectile` and `concoction` off the `…gear` spellings that named a SoHL
  * document subtype rather than the thing the note is about. `weapon` is the one
  * the specification and this registry still spell differently: both systems
  * call that document a `weapongear`, so the name says nothing system-specific
- * and #78's table has no row for it. A note left on a renamed spelling still
+ * and the table has no row for it. A note left on a renamed spelling still
  * reaches its entry — every type-keyed lookup normalises through
  * `RENAMED_TYPES` — and is reported rather than refused until the content trees
  * have swept.
  *
- * **A type name and a subType value are held to the address charset** (#206), so
+ * **A type name and a subType value are held to the address charset**, so
  * both are `^[A-Za-z0-9]+$` — the charset `engine/address-charset.mjs` states
  * and the shortcode is already held to. For a type that is literal: it is a
  * segment of every address — the first of the short form an author writes
@@ -63,7 +63,7 @@
  * about why.
  *
  * A subType reaches no address of its own. It did when this rule was written —
- * a `doc`'s was its section, a path segment — and #204 retired sections from
+ * a `doc`'s was its section, a path segment — and sections are retired from
  * the note format one release later. It keeps the rule regardless, and the
  * reason is not inertia: a subType is a vocabulary term the whole toolchain
  * keys on, it is one closed set away from being an address again, and a charset
@@ -76,11 +76,11 @@
  */
 
 // The one charset, read rather than restated. A second spelling of the pattern
-// is how the three disagreements found in #202/#203 happened.
+// is how a disagreement between the three arises.
 import { ADDRESS_SEGMENT_PATTERN, isAddressSegment } from "./address-charset.mjs";
 // The retirement window for a renamed type, read rather than restated: a
 // vocabulary that answered only to the current spelling would report every key
-// of an unswept note as unknown (#78).
+// of an unswept note as unknown.
 import { currentType } from "./ids.mjs";
 
 /**
@@ -88,7 +88,7 @@ import { currentType } from "./ids.mjs";
  *
  * A deliberate subset of {@link import("./field-spec.mjs").FieldSpec}: no `to`,
  * because nothing here builds anything yet. Reading `data.*` through into a
- * document's `system` block is the passthrough slice (#126), and claiming an
+ * document's `system` block is the passthrough slice, and claiming an
  * emitted path this does not produce would be a lie in the one place a reader
  * would trust it.
  *
@@ -155,9 +155,9 @@ const LINKS = Object.freeze({ shape: "list of wikilinks", kind: "list" });
  * the scalar cannot, that the answer *differs by pack*. A folder's `parent` is
  * the case it exists for — a folder's identity is one thing and its hierarchy
  * another, and both large trees file the same folder under a different parent
- * in the items pack and the journals pack (#276).
+ * in the items pack and the journals pack.
  *
- * Typing it as a bare {@link LINK} is what #288 was: the compiler read both
+ * Typing it as a bare {@link LINK} makes the compiler read both
  * forms and the lint rejected one of them, so every note using the form the
  * specification prescribes was a finding and no note using it was not.
  */
@@ -235,7 +235,7 @@ const CHARGES = Object.freeze([
  * @type {Readonly<Record<string, TypeVocabulary>>}
  */
 /**
- * The tags that **classify** a note, grouped by what they classify (#172).
+ * The tags that **classify** a note, grouped by what they classify.
  *
  * `tags:` lives at the open top level and most tags belong there: a theme, a
  * region, a working state is the author's own and this build has no opinion
@@ -261,7 +261,7 @@ const CHARGES = Object.freeze([
  * this replaced had to spell it `Fishing Village` as a value of its own.
  */
 /**
- * The declared tag that marks a note as **unfinished** (#183).
+ * The declared tag that marks a note as **unfinished**.
  *
  * Named once and referenced from the declaration below, because a second
  * spelling is how the two come apart: rename the tag in `DECLARED_TAGS` and a
@@ -399,7 +399,7 @@ export function hasTag(fm, tag) {
 }
 
 /**
- * Whether a note is tagged as an unfinished **draft** (#183).
+ * Whether a note is tagged as an unfinished **draft**.
  *
  * The one reader of {@link DRAFT_TAG}, so both builds ask the same question of
  * the same field. Presentation only: a draft note is in the packs, in the
@@ -418,7 +418,7 @@ export const NOTE_VOCABULARY = Object.freeze({
 
     being: Object.freeze({
         // Derived from the note's `(type, subType)` by each system's map, which
-        // lands with #79. Declared open until it does, because inventing the
+        // lands with. Declared open until it does, because inventing the
         // values here would put a second, weaker answer beside the real one.
         subTypes: null,
         data: Object.freeze([
@@ -794,10 +794,10 @@ export const NOTE_VOCABULARY = Object.freeze({
 
     doc: Object.freeze({
         // `userguide`, not `user-guide`: a subType is held to the address
-        // charset, and a segment carries no hyphen (#206). The old spelling was
+        // charset, and a segment carries no hyphen. The old spelling was
         // accepted transitionally for one release so the consumer trees could
         // sweep; they have, so it is refused by the charset check now, with no
-        // retirement-specific code left over (#210).
+        // retirement-specific code left over.
         subTypes: Object.freeze(["rules", "userguide", "reference"]),
         data: Object.freeze([]),
     }),
@@ -805,12 +805,12 @@ export const NOTE_VOCABULARY = Object.freeze({
     macro: Object.freeze({ data: Object.freeze([]) }),
 
     // Foundry's `Folder`, and the last document this package compiled from
-    // bespoke configuration rather than from a note (#256). It declares no
+    // bespoke configuration rather than from a note. It declares no
     // system-block fields, like a bundle: a `Folder` is a core Foundry
     // document, so its address carries the `none` system segment and
     // everything it says is a `data` property.
     //
-    // It carries **no prose**, which is the decision #256 left open: a folder
+    // It carries **no prose**: a folder
     // is structure, not content, so it wants no documentation journal and takes
     // no part in `docEntryTypes`.
     folder: Object.freeze({
@@ -836,7 +836,7 @@ export const NOTE_VOCABULARY = Object.freeze({
     // calls it: a set of documents taken as a unit. The document is an
     // installer — it carries copies, and importing one creates or updates each
     // document in the world — which is what separates a bundle from a folder,
-    // a live grouping that persists in the pack (#259).
+    // a live grouping that persists in the pack.
     //
     // How many Adventures a bundle makes is decided by its system blocks, as
     // for every other type, and not by a property: an `Adventure` has no
@@ -940,12 +940,12 @@ export const NOTE_VOCABULARY = Object.freeze({
 
     map: Object.freeze({
         // One type, three subTypes: they differ only in the canvas defaults
-        // derived for them, which is precisely what a subType decides (#174).
+        // derived for them, which is precisely what a subType decides.
         subTypes: Object.freeze(["battlemap", "localmap", "regionalmap"]),
         data: Object.freeze([
             // `img`, as every other note type spells its artwork. A map alone
             // read `image` out of its `sohl:` block; that spelling is retired
-            // and gone (#149), so the two names are one again.
+            // and gone, so the two names are one again.
             {
                 name: "img",
                 ...TEXT,
@@ -1001,10 +1001,11 @@ export const NOTE_VOCABULARY = Object.freeze({
 /**
  * What a note carrying a subType outside the address charset is told.
  *
- * **Why the charset holds for a subType, which reaches no address.** #206 said
+ * **Why the charset holds for a subType, which reaches no address.** The rule
+ * said
  * "the hyphen separates the segments of an address", and that was true of a
  * subType when it shipped: `sectionOf` returned a `doc`'s subType, so the value
- * was a URL path segment. #204 retired sections and it is not one now. The rule
+ * was a URL path segment. Sections are retired and it is not one. The rule
  * stays, on its own footing: a subType is a vocabulary term the whole toolchain
  * keys on, and it is one closed set away from being an address segment again —
  * so the reason to spell it in the address charset is that a charset holding
@@ -1054,8 +1055,8 @@ export function typeCharsetMessage(type) {
  *
  * The message states the reason **per key**, as {@link typeCharsetMessage} and
  * {@link subTypeCharsetMessage} do: a type is an address segment, and a subType
- * has not been one since #204 retired sections, so a single claim covering both
- * would be half wrong (#210).
+ * is not one, since sections are retired, so a single claim covering both
+ * would be half wrong.
  *
  * @param {Readonly<Record<string, TypeVocabulary>>} vocabulary - The registry.
  * @param {string} [where] - What declares it, for the message.
@@ -1077,7 +1078,7 @@ export function assertVocabularyCharset(vocabulary, where = "the note vocabulary
         `${where} declares ${bad.join(", ")}, which ${bad.length === 1 ? "is" : "are"} ` +
             `not ${ADDRESS_SEGMENT_PATTERN.source}. A type is an address segment, ` +
             `and the hyphen separates segments rather than occurring inside one. ` +
-            `A subType reaches no address since #204 retired sections, and is ` +
+            `A subType reaches no address, and is ` +
             `held to the same charset anyway: it is a vocabulary term the whole ` +
             `toolchain keys on, one closed set away from being a segment again, ` +
             `and a charset holding for every term but that one would be a rule ` +

package/engine/pack-config.mjs

@@ -17,7 +17,7 @@
  * One module, one import: everything the compilers used to hard-code — the
  * content package, the Foundry package and its kind, every path, the `_stats`
  * identity, the item-type membership, and the pack list — arrives from the
- * consuming repository's `package-build.config.yaml` (#1508).
+ * consuming repository's `package-build.config.yaml`.
  *
  * **The configuration is data, and a repository writes it as data.** Every
  * value in it is a literal; the three consumers' configs held no logic between
@@ -58,7 +58,7 @@
  * resolution walks parent directories. `import.meta.dirname` is then inside the
  * parent, the walk lands on the parent's configuration, and the build compiles
  * the parent's content tree into the parent's `build/` and exits 0 — saying so
- * only in paths that are easy to read past (#364).
+ * only in paths that are easy to read past.
  *
  * That failure is undetectable on exactly the work most likely to provoke it.
  * The usual tell is a zero diff where a change was expected; an
@@ -75,7 +75,7 @@
  * `node_modules`. `PACKAGE_BUILD_CONFIG` names the file explicitly and skips
  * both walks, which is why it was the workaround.
  *
- * What #1508 removed stays removed. The property it bought was not "resolve
+ * What was removed stays removed. The property it bought was not "resolve
  * from the module"; it was that a build reads one tree however it was launched,
  * and an upward walk from the working directory keeps that — every directory
  * inside a repository resolves that repository's single configuration.
@@ -179,7 +179,7 @@ export function findConfigFile(from) {
  *
  * Kept separate from {@link loadPackConfig} because the *choice* is worth being
  * able to ask about without loading anything: the two walks disagreeing is the
- * observable form of #364, and a caller that wants to report it — or a test
+ * observable form of that, and a caller that wants to report it — or a test
  * that wants to describe it — should not have to reproduce the resolution and
  * risk disagreeing with the loader about it. It performs I/O, and is named for
  * it, like the {@link findConfigFile} it calls twice.
@@ -244,7 +244,7 @@ const ITEM_BUILDER_REGISTRIES = Object.freeze({
  *
  * `stats.systemVersion` is stamped into every compiled document, and a
  * transcribed copy of it froze at `0.6.0` for four releases before anyone
- * noticed (#1548). `package.json` is the file Changesets bumps, so reading it
+ * noticed. `package.json` is the file Changesets bumps, so reading it
  * is what keeps the stamp equal to the version that did the compiling.
  *
  * The read happens *here*, in the loader, rather than in `defineConfig`:
@@ -309,7 +309,7 @@ function foundryPackageId(rootDir) {
  * the whole point:
  *
  * - A **system** ships itself, so its own `package.json` version *is* the
- *   system version. That is the read #1548 introduced after a transcribed copy
+ *   system version. That is the read to make, because a transcribed copy
  *   froze at `0.6.0` for four releases.
  * - A **module** ships content *for* someone else's system. Its own version is
  *   the module's — `sohl-thalorna` sits at `0.0.1` — so deriving from it would
@@ -343,7 +343,7 @@ function shippedSystemVersion(rootDir, input) {
     const declaredSystems = /** @type {Record<string, unknown>} */ (input.relationships ?? {})
         .systems;
 
-    // The `systems:` block declares without requiring (#48), so it is consulted
+    // The `systems:` block declares without requiring, so it is consulted
     // first: a package that has adopted it needs no relationship, and one that
     // ships for two systems could not express itself through a relationship at
     // all. `requiresSystem` names the package-wide default when there is one;
@@ -373,7 +373,7 @@ function shippedSystemVersion(rootDir, input) {
     // system data, and it installs under any system. There is no version to
     // stamp, and inventing one would be the very thing the throw below guards
     // against. The two signals together are what separate this from a module
-    // that simply forgot to declare its system (#43).
+    // that simply forgot to declare its system.
     if (
         (systemId === undefined || systemId === null) &&
         !(Array.isArray(declaredSystems) && declaredSystems.length)
@@ -453,7 +453,7 @@ function positionInConfig(configPath, field) {
  * worse than locating none — a reader would learn that some configuration
  * errors carry a position and could not predict which — so the path rides on
  * the error and every one of them is located here, at the boundary that knows
- * which file was read (#95).
+ * which file was read.
  *
  * The message keeps its body and gains the `file:line:column: error: ` prefix
  * every other finding in this build already uses, so nothing a reader has today
@@ -500,7 +500,7 @@ export function locateConfigError(err, configPath) {
  *   cannot write `import.meta.dirname`, and any absolute path it wrote instead
  *   would be one machine's — so authoring it is rejected rather than honoured.
  * - **`itemBuilders`** is a *name* (`sohl`) — or a list of names, for a tree
- *   feeding more than one system (#58) — resolved against the built-in
+ *   feeding more than one system — resolved against the built-in
  *   registries. A registry's name is the system it belongs to. A registry of a
  *   consumer's own is code, and code goes in an `.mjs` configuration.
  * - **`stats.systemVersion`** is derived from the adjacent `package.json` when
@@ -539,7 +539,7 @@ export function configFromData(data, configPath) {
 
     // Transcribed from `package.json`, and therefore free to disagree with it.
     // Every consumer's copy matched exactly, which is what a transcription
-    // looks like right up until it does not (#1548 froze one at `0.6.0` for
+    // looks like right up until it does not (a transcribed one freezes
     // four releases while nothing said so).
     if (input.foundryPackage !== undefined) {
         throw new Error(
@@ -554,7 +554,7 @@ export function configFromData(data, configPath) {
         const declared = input.itemBuilders;
         const known = Object.keys(ITEM_BUILDER_REGISTRIES).join(", ");
         // One name or several. A repository feeding two systems needs both
-        // vocabularies, and one registry can only carry one (#58); the scalar
+        // vocabularies, and one registry can only carry one; the scalar
         // form every existing configuration uses is the one-element case and
         // means exactly what it always did.
         const names = Array.isArray(declared) ? declared : [declared];
@@ -691,7 +691,7 @@ export function loadPackConfig() {
     }
 
     // Two different files, one of which is about to be ignored. Said out loud
-    // because the alternative is what #364 was: a build that reads the parent
+    // because the alternative is a build that reads the parent
     // checkout's configuration, compiles the parent's tree, and reports it only
     // in absolute paths nobody rereads. A warning rather than an error — the
     // shape is legitimate, and the working directory's answer is the right one

package/engine/prose-config.mjs

@@ -14,14 +14,14 @@
 /**
  * The prose conventions every content repository writes to — one Prettier
  * configuration and one markdownlint rule set, declared here so a note
- * formatted in one repository is formatted the same way in the next (#69).
+ * formatted in one repository is formatted the same way in the next.
  *
- * These used to exist in exactly one consumer. The SoHL repository carried
+ * These belong in no single consumer. The SoHL repository carried
  * both; `sohl-thalorna` had Prettier but never ran it from `lint`; and
  * `sohl-kethira-basic` had neither, so the package least likely to have been
  * proofread was checked for addresses and nothing else. A rule set copied into
  * three repositories is one rule with three implementations, which is the drift
- * #20 exists to remove — so it is declared once, here, and every consumer
+ * this exists to remove — so it is declared once, here, and every consumer
  * invokes it.
  *
  * **Neither of these is an override.** A consumer that declares its own
@@ -89,7 +89,7 @@ export const PRETTIER_BASE = Object.freeze({
  * **Declared apart from the `overrides` block, not derived from it.** Prettier
  * applies `overrides` only while resolving a config *file*; options handed to
  * it directly keep the global values, so a consumer with no config of its own
- * silently got markdown at 4 (#76). The runner needs the adjustment as data it
+ * silently got markdown at 4. The runner needs the adjustment as data it
  * can apply itself, and {@link PRETTIER_CONFIG} composes the same values into
  * the shape a config file wants — one source, two presentations.
  *
@@ -128,7 +128,7 @@ export const PRETTIER_CONFIG = Object.freeze({
  *
  * @param {string} file - Path of the file about to be formatted.
  * @returns {object} Options to hand Prettier directly. Never carries
- *   `overrides`: passing that inline is what silently did nothing (#76).
+ *   `overrides`: passing that inline is what silently did nothing.
  */
 export function sharedPrettierOptionsFor(file) {
     return /\.md$/i.test(file) ? { ...PRETTIER_BASE, ...PRETTIER_MARKDOWN } : { ...PRETTIER_BASE };
@@ -140,11 +140,11 @@ export function sharedPrettierOptionsFor(file) {
  * The runner resolves each file's options as *either* the consumer's own config
  * or {@link sharedPrettierOptionsFor}, never a merge. That is what bare Prettier
  * does and it is the contract — but it means the conventions this package exists
- * to publish hold by convention alone, and they lapse in two opposite directions
- * (#133). A consumer that declares any config of its own gets whatever that
+ * to publish hold by convention alone, and they lapse in two opposite directions.
+ * A consumer that declares any config of its own gets whatever that
  * config says: spread {@link PRETTIER_BASE} without the markdown override and
- * every note reindents at 4, the reindentation the override was added to prevent
- * (#76); write a partial `.prettierrc` such as `{"tabWidth": 2}` and
+ * every note reindents at 4, the reindentation the override was added to prevent;
+ * write a partial `.prettierrc` such as `{"tabWidth": 2}` and
  * `printWidth`, `trailingComma`, `experimentalTernaries` and the rest fall back
  * to Prettier's own defaults. A consumer that declares *nothing* formats one way
  * under this command and another under a bare `npx prettier`.

package/engine/prose-lint.mjs

@@ -13,13 +13,13 @@
 
 /**
  * Running the shared prose conventions over a repository — Prettier for
- * formatting, markdownlint for the structure Prettier is indifferent to (#69).
+ * formatting, markdownlint for the structure Prettier is indifferent to.
  *
  * Both are thin: the rules live in `./prose-config.mjs` and the tools are
  * Prettier and markdownlint themselves. What this module adds is the two things
  * a consumer would otherwise have to get right on its own — supplying the
  * shared configuration *as a default a local one overrides*, and reporting
- * findings in the one parseable form every check in this package emits (#17).
+ * findings in the one parseable form every check in this package emits.
  *
  * **Neither tool's own file discovery is reimplemented.** Prettier decides what
  * it formats and what an ignore file excludes, through `getFileInfo`;
@@ -68,7 +68,7 @@ const IGNORE_FILES = Object.freeze([".gitignore", ".prettierignore"]);
  * `format` is *assumed* idempotent and is not guaranteed to be: a single pass
  * can leave text the next pass would still change, and a `--write` run that
  * takes one pass then reports success has called such a file formatted while
- * `prettier --check` still rejects it (#125). Formatting to a fixpoint removes
+ * `prettier --check` still rejects it. Formatting to a fixpoint removes
  * the assumption — the file lands on the value repeated formatting converges
  * to, whatever it took to get there.
  *
@@ -86,7 +86,7 @@ const MAX_FORMAT_PASSES = 3;
  * configured to do means asking about a file. These are the two answers that
  * differ: markdown carries the shared `tabWidth` override and everything else
  * does not, so a single probe would check half the conventions and miss the one
- * most worth checking (#133).
+ * most worth checking.
  *
  * Ordinary names at the repository root, and neither has to exist —
  * `resolveConfig` reads the path to walk up from it and to match `overrides`
@@ -147,8 +147,7 @@ function walkFiles(root) {
  * @param {boolean} [opts.write=false] - Rewrite unformatted files in place
  *   rather than reporting them. Each file is formatted to a fixpoint (up to
  *   {@link MAX_FORMAT_PASSES} passes), so a written tree is one a second run
- *   leaves alone; a file that will not converge is reported and left unchanged
- *   (#125).
+ *   leaves alone; a file that will not converge is reported and left unchanged.
  * @param {object} [opts.prettier] - The Prettier module, for tests.
  * @returns {Promise<{findings: Array<{file: string, severity: string,
  *   message: string}>, checked: number, written: string[]}>} The findings, how
@@ -185,7 +184,7 @@ export async function checkFormatting(root, opts = {}) {
         });
         // `resolveConfig` has already applied any `overrides` the consumer's
         // own config declares. The shared fallback has to apply its own, since
-        // Prettier ignores an `overrides` block passed inline (#76).
+        // Prettier ignores an `overrides` block passed inline.
         const options = {
             ...(local ?? sharedPrettierOptionsFor(file)),
             filepath: file,
@@ -199,7 +198,7 @@ export async function checkFormatting(root, opts = {}) {
         try {
             if (write) {
                 // Format to a fixpoint rather than once, so what lands on disk
-                // is what a second run would have produced (#125).
+                // is what a second run would have produced.
                 let formatted = source;
                 let converged = false;
                 for (let pass = 0; pass < MAX_FORMAT_PASSES; pass += 1) {
@@ -221,7 +220,7 @@ export async function checkFormatting(root, opts = {}) {
                         file,
                         severity: "error",
                         // No line or column: the verdict is about the whole
-                        // file, and #17's rule is to drop a field rather than
+                        // file, and the rule is to drop a field rather than
                         // invent one.
                         message:
                             `did not converge after ${MAX_FORMAT_PASSES} formatting passes; ` +
@@ -242,7 +241,7 @@ export async function checkFormatting(root, opts = {}) {
                     file,
                     severity: "error",
                     // No line or column: Prettier's answer is about the whole
-                    // file, and #17's rule is to drop a field rather than
+                    // file, and the rule is to drop a field rather than
                     // invent one.
                     message: "is not formatted; run `content-build format --write` to fix it",
                 });
@@ -272,7 +271,7 @@ export async function checkFormatting(root, opts = {}) {
  *
  * The two cases read differently on purpose. A key set to something else is a
  * choice someone made and can defend; a key that is simply absent is the
- * silent half of #133 — the consumer did not choose Prettier's default, it
+ * silent half — a consumer does not choose Prettier's default, it
  * arrived because declaring one option discards every option not restated.
  *
  * @param {{key: string, shared: unknown, local: unknown}} divergence - From
@@ -291,7 +290,7 @@ function divergenceMessage({ key, shared, local }, scope = "") {
 
 /**
  * Report where a repository's own Prettier configuration parts from the shared
- * one — or that it has none at all (#133).
+ * one — or that it has none at all.
  *
  * **Warnings, every one of them.** A consumer's config wins by design and this
  * does not change that; it only refuses to let the divergence be silent, which
@@ -312,7 +311,7 @@ function divergenceMessage({ key, shared, local }, scope = "") {
  * @returns {Promise<{findings: Array<{file?: string, severity: string,
  *   message: string}>, configFile: string|null}>} The findings and the config
  *   file they are about, which is `null` when the repository declares none. A
- *   finding about a missing file carries no `file`: #17's rule is to drop a
+ *   finding about a missing file carries no `file`: the rule is to drop a
  *   field rather than invent one.
  */
 export async function checkPrettierConventions(root, opts = {}) {

package/engine/region-events.mjs

@@ -22,10 +22,10 @@
  * runtime bridge from drifting apart.
  *
  * It sits in this package rather than in the system's `src/` tree because the
- * map-note compiler that reads it is installed as a dependency (#1501), and a
+ * map-note compiler that reads it is installed as a dependency, and a
  * relative path out of the package would resolve to garbage from
  * `node_modules`. The runtime reaches it back through the package's
- * `./engine/region-events` entry point (#1510). It is engine-side, not
+ * `./engine/region-events` entry point. It is engine-side, not
  * SoHL-side, because any content module that authors a scene region — an
  * adventure module included — needs this vocabulary.
  *