@heroiclands/package-build 20.3.1 → 20.5.0

package/engine/note-package.mjs

@@ -19,10 +19,10 @@
  * single-sourced in the repository that ships it — so the package is a property
  * of the *repository*, not of the note, and no note declares it.
  *
- * It used to be a property of the note, and a **selector**: the compile loop
+ * It is not a property of the note, and not a **selector**: as one, the compile loop
  * read `package:` out of frontmatter and skipped anything that did not match
- * the configured value. That is the defect this module exists to remove
- * (#56). The skip was silent and it was bucketed as "belongs to another pass",
+ * the configured value. That is the defect this module exists to remove.
+ * The skip was silent and it was bucketed as "belongs to another pass",
  * so a tree whose notes named a package no configuration answered to compiled
  * **zero notes and exited 0** — which is exactly the state the un-migrated
  * `hm-loc-*` / `hm-adv-*` repositories are in today.
@@ -64,7 +64,7 @@ import { locateFrontmatterKey } from "./retired-fields.mjs";
  * field, so a collection note that scopes itself with `WHERE … and package =
  * "sohl"` would match nothing now that the field is gone, and would render an
  * **empty table** in silence. Supplying the derived value here is what kept the
- * sweep mechanical rather than a trap (#56) — and a query that never mentions
+ * sweep mechanical rather than a trap — and a query that never mentions
  * `package` is unaffected either way.
  *
  * The frontmatter is copied rather than written into: it is the note's own

package/engine/note-renames.mjs

@@ -12,12 +12,12 @@
  */
 
 /**
- * The shortcodes a note declares it used to be published under (#278).
+ * The shortcodes a note declares it used to be published under.
  *
  * A package's `(type, shortcode)` addresses are a published interface, and
  * `addresses diff` reports what a build stopped publishing — telling a
  * **rename** from a **withdrawal** by matching document ids across two
- * releases. #270 removed the property that rested on. An id is now derived from
+ * releases. The property that rested on is gone: an id is derived from
  * the canonical address, which carries the shortcode, so renaming a shortcode
  * moves the id too: both sides of the join move together, the match finds
  * nothing, and a rename is reported as a withdrawal with no successor named.
@@ -52,7 +52,7 @@
  * **It is transient.** Once every baseline a build is compared against post-dates
  * the rename, the declaration has nothing left to say and may be deleted. That
  * is the difference from an `id:` pin, which is permanent, opaque, and a second
- * identity for a thing that already has one (#270).
+ * identity for a thing that already has one.
  *
  * **It is one key per note, at the top level, however many systems the note
  * compiles into.** A shortcode is the note's, not a system block's: a note

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
@@ -34,11 +34,6 @@
 
 import { HOMEPAGE_FIELDS, HOMEPAGE_TYPE } from "./homepage.mjs";
 
-/**
- * Every engine-level content type, and what a note of that type may write.
- *
- * @type {Readonly<Record<string, readonly import("./field-spec.mjs").FieldSpec[]>>}
- */
 /**
  * A note that compiles to a JournalEntry and nothing else.
  *
@@ -55,7 +50,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 +85,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,19 +42,19 @@
  * 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
- * 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
+ * **A type name and a subType value are held to the address charset**, so
+ * both match `ADDRESS_SEGMENT_PATTERN` — 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
  * (`type-shortcode`), the third of the canonical
  * `package-system-type-shortcode` — the hyphen is the separator between
@@ -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.
  */
@@ -223,19 +223,22 @@ const CHARGES = Object.freeze([
 /* --------------------------------------------------------------------- */
 
 /**
- * Every note type this toolchain compiles, and the closed vocabulary it
- * declares.
+ * The declared tag that marks a note as **unfinished**.
  *
- * Taken from the content-format specification, one `### type:` section per
- * entry. Where the specification and the shape notes are authored in today
- * disagree, the specification wins on the **name** — that is what a `data:`
- * key will be called — and the disagreement is recorded on the field rather
- * than resolved silently.
+ * 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
+ * private copy elsewhere keeps matching the old word, silently.
  *
- * @type {Readonly<Record<string, TypeVocabulary>>}
+ * It is a **presentation** fact and nothing more. A draft note compiles,
+ * validates, publishes and resolves like any other; only a link *into* it
+ * renders marked. What it emphatically is not is the retired `draft:` field,
+ * whose entire effect was to move a note from published to unresolvable — see
+ * {@link draftRetiredMessage}.
  */
+export const DRAFT_TAG = "draft";
+
 /**
- * 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
@@ -260,21 +263,6 @@ const CHARGES = Object.freeze([
  * fishing village is a `village` that is `fishing`, and the single-valued field
  * this replaced had to spell it `Fishing Village` as a value of its own.
  */
-/**
- * The declared tag that marks a note as **unfinished** (#183).
- *
- * 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
- * private copy elsewhere keeps matching the old word, silently.
- *
- * It is a **presentation** fact and nothing more. A draft note compiles,
- * validates, publishes and resolves like any other; only a link *into* it
- * renders marked. What it emphatically is not is the retired `draft:` field,
- * whose entire effect was to move a note from published to unresolvable — see
- * {@link draftRetiredMessage}.
- */
-export const DRAFT_TAG = "draft";
-
 export const DECLARED_TAGS = Object.freeze({
     /** What a place *is*. */
     placeKind: Object.freeze({
@@ -399,7 +387,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
@@ -413,12 +401,24 @@ export function isDraftNote(fm) {
     return hasTag(fm, DRAFT_TAG);
 }
 
+/**
+ * Every note type this toolchain compiles, and the closed vocabulary it
+ * declares.
+ *
+ * Taken from the content-format specification, one `### type:` section per
+ * entry. Where the specification and the shape notes are authored in today
+ * disagree, the specification wins on the **name** — that is what a `data:`
+ * key will be called — and the disagreement is recorded on the field rather
+ * than resolved silently.
+ *
+ * @type {Readonly<Record<string, TypeVocabulary>>}
+ */
 export const NOTE_VOCABULARY = Object.freeze({
     /* ----- actors --------------------------------------------------- */
 
     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([
@@ -793,24 +793,25 @@ export const NOTE_VOCABULARY = Object.freeze({
     /* ----- core documents ------------------------------------------- */
 
     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
-        // 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).
-        subTypes: Object.freeze(["rules", "userguide", "reference"]),
+        // Five genres, and a genre is all this field carries: what kind of page
+        // it is, never who reads it. An audience term alongside them would give
+        // a developer how-to two valid values and no rule for choosing.
+        //
+        // `userguide` and `howto`, not `user-guide` and `how-to`: a subType is
+        // held to the address charset, and a segment carries no hyphen.
+        subTypes: Object.freeze(["rules", "userguide", "reference", "howto", "concept"]),
         data: 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 +837,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 +941,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 +1002,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 +1056,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 +1079,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.
@@ -104,7 +104,7 @@ import path from "node:path";
 import { createRequire } from "node:module";
 import YAML from "yaml";
 
-import { defineConfig, DERIVED_SYSTEM_VERSION } from "../content-config.mjs";
+import { defineConfig, DERIVED_SYSTEM_VERSION, DOCUMENTATION_KIND } from "../content-config.mjs";
 import {
     emitDiagnostic,
     formatDiagnostic,
@@ -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
@@ -513,7 +513,7 @@ export function locateConfigError(err, configPath) {
  *
  * @param {unknown} data - The parsed configuration document.
  * @param {string} configPath - Absolute path of the file it was parsed from.
- * @returns {import("../config.mjs").ContentBuildConfig} The frozen configuration.
+ * @returns {import("../content-config.mjs").ContentBuildConfig} The frozen configuration.
  * @throws {Error} When the document is not a mapping, declares `rootDir`, or
  *   names an item-builder registry this package does not ship.
  */
@@ -539,22 +539,27 @@ 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(
-            `package-build: ${configPath} declares \`foundryPackage\`, which ` +
-                `a data configuration may not: it is the \`name\` of the ` +
-                `\`package.json\` beside it. Remove the key.`,
-        );
+    // A documentation package has no Foundry package, so there is no id to
+    // derive: the validator refuses the key by name, with a locator, and
+    // deriving one here would hand it the very key it is about to refuse.
+    if (input.packageKind !== DOCUMENTATION_KIND) {
+        if (input.foundryPackage !== undefined) {
+            throw new Error(
+                `package-build: ${configPath} declares \`foundryPackage\`, which ` +
+                    `a data configuration may not: it is the \`name\` of the ` +
+                    `\`package.json\` beside it. Remove the key.`,
+            );
+        }
+        input.foundryPackage = foundryPackageId(rootDir);
     }
-    input.foundryPackage = foundryPackageId(rootDir);
 
     if (input.itemBuilders !== undefined) {
         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];
@@ -590,7 +595,16 @@ export function configFromData(data, configPath) {
     }
 
     const stats = input.stats;
-    if (stats !== null && typeof stats === "object" && !Array.isArray(stats)) {
+    // Skipped for a documentation package, which stamps no `_stats` and
+    // declares no system to take a version from: the derivation would throw a
+    // bare error about a missing system relationship, burying the located
+    // refusal of the `stats:` key that is the finding an author needs.
+    if (
+        input.packageKind !== DOCUMENTATION_KIND &&
+        stats !== null &&
+        typeof stats === "object" &&
+        !Array.isArray(stats)
+    ) {
         const declared = /** @type {Record<string, unknown>} */ (stats);
         // `stats.systemId` and `stats.systemVersion` are both refused by
         // `defineConfig`, which reports them with a locator — so nothing is
@@ -620,7 +634,7 @@ export function configFromData(data, configPath) {
  * Load an `.mjs` configuration — one that called `defineConfig` itself.
  *
  * @param {string} configPath - Absolute path of the file.
- * @returns {import("../config.mjs").ContentBuildConfig} What it exported.
+ * @returns {import("../content-config.mjs").ContentBuildConfig} What it exported.
  * @throws {Error} When its module graph uses top-level `await`, which a
  *   synchronously-read configuration cannot.
  */
@@ -662,7 +676,7 @@ let loadedFrom;
  * configuration (#2). The result is memoised, so calling it in a default
  * parameter — the usual spelling here — costs one property read per call.
  *
- * @returns {import("../config.mjs").ContentBuildConfig} The frozen configuration.
+ * @returns {import("../content-config.mjs").ContentBuildConfig} The frozen configuration.
  * @throws {Error} When no configuration file can be found, or the one named
  *   cannot be loaded. Absence is a defect, not a fallback: without it the
  *   compilers know neither what to compile nor where to put it.
@@ -691,7 +705,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