@heroiclands/package-build 20.3.0 → 20.4.0

package/types/engine/metadata-index.d.mts

@@ -22,7 +22,7 @@ export function metadataFileName(pkg: string): string;
  * `itemCatalog: true` says a dependency supplies *items*; citing its
  * *addresses* is a separate edge, and a package may have either without the
  * other. `harn-ensemble` cites no foreign address and carries 324,016 embedded
- * item references (`HeroicLands/harn-ensemble#42`); a package citing addresses
+ * item references; a package citing addresses
  * and needing no items is the mirror of it. Gating the index on the catalogue
  * flag would serve neither.
  *
@@ -84,7 +84,7 @@ export function cachedMetadataFiles(config: object): string[];
  * The same fetched indexes, each paired with the package that published it.
  *
  * The id is what a SQL content table addresses a dependency's notes by
- * (`FROM sohl.notes`, #246), so the pairing has to survive the lookup —
+ * (`FROM sohl.notes`), so the pairing has to survive the lookup —
  * {@link cachedMetadataFiles} drops it, and a caller reconstructing the id from
  * the file name would be parsing a path to recover something the declaration
  * already stated.
@@ -113,7 +113,7 @@ export function cachedMetadataIndexes(config: object): Array<{
  * rather than being written once per cache. Two copies would be two chances to
  * get it wrong, and the wrong answer is invisible: every cached version is a
  * complete, stamped, perfectly valid artifact, so picking the older one reports
- * nothing and simply resolves against stale data (#272).
+ * nothing and simply resolves against stale data.
  *
  * @param {string[]} dirs - Complete cache directories, named `<id>@<version>`.
  * @returns {string} The newest one.
@@ -179,7 +179,7 @@ export function cachedIndexPath(config: object, pkg: string): string;
  * therefore reported against the index, once, instead of once per citing note.
  *
  * The realistic cause is a version skew: a dependency released before the
- * address grammar gained its `<system>` segment (#59) ships three-segment keys.
+ * address grammar gained its `<system>` segment ships three-segment keys.
  * Re-fetching after that dependency releases is the fix.
  *
  * @param {Map<string, object>} foreignIndex - The resolved foreign index.

package/types/engine/note-claims.d.mts

@@ -10,19 +10,19 @@
  * @param {ClaimSources} [sources] - What to answer from.
  * @param {object} [opts] - Options.
  * @param {readonly object[]} [opts.records] - The corpus, derived once by the
- *   compile and handed in — required, for the reason above (#243). Defaults to the
+ *   compile and handed in — required, for the reason above. Defaults to the
  *   configured registries and the systems this toolchain ships.
  * @returns {ReadonlySet<string>} The note types such a pass would claim.
  */
 export function noteTypesClaimedBy(docType: string, sources?: ClaimSources): ReadonlySet<string>;
 /**
- * Every document class a note of one type compiles into (#152).
+ * Every document class a note of one type compiles into.
  *
  * **A note produces more than one document, and that is the ordinary case.** An
  * item note compiles an Item *and* the JournalEntry its prose becomes; a map
- * note a Scene and a JournalEntry; since #337 an actor note an Actor and a
+ * note a Scene and a JournalEntry; an actor note an Actor and a
  * JournalEntry too. {@link claimedNoteTypes} unions over the configured packs
- * and so answers "is this note compiled *at all*", which is #146's question and
+ * and so answers "is this note compiled *at all*", and
  * cannot see a note that compiles one of its two documents and loses the other.
  *
  * Asked of the **claim table** rather than of a list of its own, so the set of
@@ -33,7 +33,7 @@ export function noteTypesClaimedBy(docType: string, sources?: ClaimSources): Rea
  * **Union across systems, never per system.** A type one system maps and
  * another does not appears once, because the `Item` and `Actor` rows already
  * fold the maps together — so this cannot report a document class a system
- * deliberately declines to produce, which is the silence #79 requires.
+ * deliberately declines to produce, which is the silence the rule requires.
  *
  * ## The JournalEntry row is the one that is per *note*
  *
@@ -73,13 +73,14 @@ export function documentClassesFor(type: string, sources?: ClaimSources, { hasPr
  *
  * The union across the configured pack list, so a type claimed by any one pack
  * is claimed — which is what keeps a type deliberately unmapped for one system,
- * and claimed for another, silent (#79).
+ * and claimed for another, silent.
  *
  * **A prebuilt pack claims nothing.** Its per-document JSON is checked in
  * rather than compiled, so it has no pass and no note is routed into one —
  * which `content-config.mjs` already states by refusing `default: true`
  * alongside `prebuilt`. Counting it would tell an author their note is claimed
- * by a pack that will never look at it. Before #259 the point could not arise:
+ * by a pack that will never look at it. With no unimplemented type declared,
+ * the point cannot arise:
  * the only prebuilt pack in the wild is `harn-adventures`'s Adventure pack, and
  * no compiler was registered for that document type, so the row answered for
  * nothing whatever it was asked. Now one is.
@@ -89,7 +90,7 @@ export function documentClassesFor(type: string, sources?: ClaimSources, { hasPr
  * @param {ClaimSources} [sources] - What to answer from.
  * @param {object} [opts] - Options.
  * @param {readonly object[]} [opts.records] - The corpus, derived once by the
- *   compile and handed in — required, for the reason above (#243).
+ *   compile and handed in — required, for the reason above.
  * @returns {ReadonlySet<string>} The claimed note types.
  */
 export function claimedNoteTypes(config?: object, sources?: ClaimSources): ReadonlySet<string>;
@@ -105,7 +106,7 @@ export function claimedNoteTypes(config?: object, sources?: ClaimSources): Reado
  * @param {ClaimSources} [sources] - What to answer from.
  * @param {object} [opts] - Options.
  * @param {readonly object[]} [opts.records] - The corpus, derived once by the
- *   compile and handed in — required, for the reason above (#243).
+ *   compile and handed in — required, for the reason above.
  * @returns {ReadonlySet<string>} The vocabulary.
  */
 export function noteTypeVocabulary(sources?: ClaimSources): ReadonlySet<string>;
@@ -124,7 +125,7 @@ export function noteTypeVocabulary(sources?: ClaimSources): ReadonlySet<string>;
  * @param {ClaimSources} [sources] - What to answer from.
  * @param {object} [opts] - Options.
  * @param {readonly object[]} [opts.records] - The corpus, derived once by the
- *   compile and handed in — required, for the reason above (#243).
+ *   compile and handed in — required, for the reason above.
  * @returns {Array<{file: string, line?: number, column?: number,
  *   severity: "error", message: string, type: string}>} One finding per note.
  */
@@ -162,11 +163,11 @@ export const NEVER_PACKED_TYPES: ReadonlySet<string>;
  * correctly and is worthless, because the configured vocabulary is *derived
  * from the routing*. Take a type's route away and it leaves the vocabulary too,
  * so the inference excuses precisely the mistake it was meant to catch. That is
- * not hypothetical: it is #241, where `place`, `lore` and `scenario` were
- * declared, validated and unrouted, and every gate reported success until a
- * downstream repository failed on 450 notes.
+ * not hypothetical: `place`, `lore` and `scenario` were declared, validated
+ * and unrouted, and every gate reported success until a downstream repository
+ * failed on the notes carrying them.
  *
- * A type leaves this set when it is implemented, the way `bundle` did in #259.
+ * A type leaves this set when it is implemented.
  * The membership is asserted, so it cannot be forgotten in either direction.
  *
  * @type {ReadonlySet<string>}
@@ -178,7 +179,7 @@ export const UNIMPLEMENTED_TYPES: ReadonlySet<string>;
  * A folder is the only one, and it is not unclaimed: it compiles to a real
  * `Folder` document. What it has no answer to is *which* pack claims it, because
  * that is not a property of the note — a folder materialises in every pack
- * holding a document that references it, and its ancestors with it (#257). So
+ * holding a document that references it, and its ancestors with it. So
  * it is exempt from the claim check for the opposite reason a homepage is:
  * a homepage is in no pack, and a folder may be in several.
  *

package/types/engine/note-ids.d.mts

@@ -5,15 +5,15 @@
  * the rule but an application of it.** A `Folder` is a document of its own
  * class, and its id is hashed under the `folder` namespace so that a folder and
  * an item sharing a shortcode cannot derive one id — a collision Foundry would
- * not report, since it keys folders and documents in separate collections
- * (#258). So the answer for a folder comes from
+ * not report, since it keys folders and documents in separate collections.
+ * So the answer for a folder comes from
  * {@link module:engine/folder-notes.folderDocId}, the pass that emits those
  * documents, rather than from a second derivation here.
  *
  * That this function ever answered differently was invisible from inside a
  * build — no pass reads a folder's id from here — and surfaced only in the
  * content index, which is read from outside and had no way to be checked
- * against what shipped (#310).
+ * against what shipped.
  *
  * Returns `undefined` for a file with **no address** — no `type`, or no
  * `shortcode`. Such a file is not an addressable note, so it has no document
@@ -26,7 +26,7 @@
  * @param {object|null|undefined} fm - Parsed frontmatter.
  * @param {object} [opts]
  * @param {string} [opts.pkg] - The owning content package. Defaults to the
- *   configured one, which is the only package a tree's notes belong to (#56).
+ *   configured one, which is the only package a tree's notes belong to.
  * @param {readonly object[]} [opts.maps] - The document-subtype maps, which
  *   decide the address's `<system>` segment.
  * @returns {string|undefined} The document's `_id`, or `undefined` when the

package/types/engine/note-package.d.mts

@@ -6,7 +6,7 @@
  * 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/types/engine/note-renames.d.mts

@@ -1,10 +1,10 @@
 /**
- * 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.
@@ -39,7 +39,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/types/engine/note-vocabulary.d.mts

@@ -24,7 +24,7 @@ export function declaredTags(type: string, groups?: object): readonly string[];
  */
 export function hasTag(fm: object | null | undefined, tag: string): boolean;
 /**
- * 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
@@ -38,10 +38,11 @@ export function isDraftNote(fm: object | null | undefined): boolean;
 /**
  * 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
@@ -72,8 +73,8 @@ export function typeCharsetMessage(type: string): string;
  *
  * 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.
@@ -116,7 +117,7 @@ export function subTypes(type: string, vocabulary?: Readonly<Record<string, Type
  * @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
@@ -142,7 +143,7 @@ export function subTypes(type: string, vocabulary?: Readonly<Record<string, Type
  * 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
@@ -361,7 +362,7 @@ export const NOTE_VOCABULARY: Readonly<{
  *
  * 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.
  */

package/types/engine/pack-config.d.mts

@@ -20,7 +20,7 @@ export function findConfigFile(from: string): string | undefined;
  *
  * 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.
@@ -58,7 +58,7 @@ export function resolveConfigFile({ cwd, moduleDir }?: {
  * 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
@@ -82,7 +82,7 @@ export function locateConfigError(err: unknown, configPath?: string): unknown;
  *   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

package/types/engine/pack-router.d.mts

@@ -48,7 +48,7 @@ export class PackRoutingError extends Error {
  *
  * Deliberately close to the retired `package:` and deliberately not the same
  * word: `package:` said which *distribution* owned a note — now the
- * repository's `contentPackage`, and no longer authorable (#56) — while `pack:`
+ * repository's `contentPackage`, and no longer authorable — while `pack:`
  * says which *compendium* receives its document.
  */
 export const PACK_FIELD: "pack";

package/types/engine/prose-config.d.mts

@@ -6,7 +6,7 @@
  *
  * @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: string): object;
 /**
@@ -15,11 +15,11 @@ export function sharedPrettierOptionsFor(file: string): object;
  * 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`.
@@ -53,14 +53,14 @@ export function sharedPrettierDivergence(resolved: object | null | undefined, fi
 /**
  * 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
@@ -95,7 +95,7 @@ export const PRETTIER_BASE: Readonly<object>;
  * **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.
  *

package/types/engine/prose-lint.d.mts

@@ -14,8 +14,7 @@
  * @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
@@ -37,7 +36,7 @@ export function checkFormatting(root: string, opts?: {
 }>;
 /**
  * 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
@@ -58,7 +57,7 @@ export function checkFormatting(root: string, opts?: {
  * @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 function checkPrettierConventions(root: string, opts?: {

package/types/engine/region-events.d.mts

@@ -9,10 +9,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.
  *

package/types/engine/retired-fields.d.mts

@@ -43,11 +43,11 @@ export function assertNoDraftField(fm: object | null | undefined, { file, absPat
  * It says what the field fed and what to write instead, rather than which value
  * to correct: no value makes declaring it right.
  *
- * **What it did (#180).** It was the authored half of the alias index — the
+ * **What it did.** It was the authored half of the alias index — the
  * namespace a bare `[[Alias]]` was looked up in. Across the three content trees
  * not one bare link resolved through it, while the collision rule that kept it
  * unambiguous folded in every note's `name.full` and so dictated what a note
- * could be named (#179). The form is retired, so the list has no reader.
+ * could be named. The form is retired, so the list has no reader.
  *
  * **`name.aliases` is a different field and is not retired.** It fed the same
  * index, but unlike the top-level list it is being kept — reserved, unread,
@@ -114,10 +114,10 @@ export function declaresRetiredAliasesField(fm: object | null | undefined): bool
  * It names what lands a section now rather than a value to correct: no value
  * makes declaring the field right.
  *
- * **What it did (#202).** It named the section a `collection` note headed,
+ * **What it did.** It named the section a `collection` note headed,
  * under the `collection` landing rule — the only reader it ever had, in the
  * second branch of `landingOf` (`engine/content-address.mjs`). That rule went
- * first, and the whole mechanism went with it (#204): a section is a Hugo
+ * first, and the whole mechanism went with it: a section is a Hugo
  * directory the note format does not carry, so no note lands one and a page
  * that introduces a type is an ordinary note addressed `doc-<type>`. Nothing
  * else read the field, and no schema or vocabulary declared it, so left in
@@ -237,7 +237,7 @@ export function retiredAliasMessage(retired: string, current: string, file?: str
  * What a note writing a field at its **legacy in-block position** is told.
  *
  * The same three-step retirement `retiredAliasMessage` announces, applied to a
- * *position* rather than a spelling (#305). A field whose shared source moved
+ * *position* rather than a spelling. A field whose shared source moved
  * under `data:` keeps reading the key its block still carries, that read wins,
  * and it is reported here so a sweep has something to count down — without it,
  * moving a field into `data:` would be a flag day across every repository that
@@ -260,9 +260,10 @@ export function legacyKeyMessage(block: string, field: {
 }, file?: string): string;
 /**
  * What a note writing a field at the **top-level key `data:` gathered it off**
- * is told (#332).
+ * is told.
  *
- * {@link legacyKeyMessage}'s counterpart for the other retiring position. #128
+ * {@link legacyKeyMessage}'s counterpart for the other retiring position. The
+ * sweep
  * did not invent the facts `data:` holds — it collected them out of the note's
  * open top level — so `portrait:` beside `img:` is the *pre-`data:`* spelling
  * of `data.portrait`, and both are read for the same reason both in-block
@@ -322,14 +323,14 @@ export function readAliasedField(fm: object | null | undefined, current: string)
  * `relation` is retired on an affiliation — which declares `relations` — and
  * remains an unknown key anywhere else.
  *
- * **`templatePriority` (#266).** The number that decides which of several
+ * **`templatePriority`.** The number that decides which of several
  * competing templates the Create dialog offers was called `archetype`, and
  * `archetypes` — one letter apart — is a list of what *sort* a character is.
  * A priority and a taxonomy cannot be told apart by a plural `s`, so the
  * priority takes the name that says what it is. The specification already
  * called it `templatePriority` on two of its three sides.
  *
- * **`relations` (SoHL#1781).** The field holds a *map* of standings, one per
+ * **`relations`.** The field holds a *map* of standings, one per
  * affiliation — its own description says so, and `resolveRelation` has always
  * read it that way. `relation` named the many as one, which every author had to
  * read past. Only `affiliation` declares the field, so the alias is reported

package/types/engine/schema-check.d.mts

@@ -46,7 +46,7 @@ export function declaredFields(artifact: SchemaArtifact, documentType: string, s
  * the path beneath it separately, so a comparison that knew only the leaf would
  * report the container as unemitted and the leaf as undeclared.
  *
- * **A runtime-only field is not in it** (#330). It declares a `to` in order to
+ * **A runtime-only field is not in it**. It declares a `to` in order to
  * *claim* the path — so the verbatim passthrough leaves it alone and the
  * refusal has something to name — and `buildFromFields` deliberately skips it,
  * because the document writes that field in play. Counting it here would make
@@ -76,7 +76,7 @@ export function emittedFields(fields: readonly {
  *   compile into.
  * @param {(type: string) => string} [opts.subtypeOf] - Maps a builder's type to
  *   the document subtype it emits. Defaults to identity, which is what the
- *   coincidence of names amounts to today (#79) — stated as a seam so that the
+ *   coincidence of names amounts to today — stated as a seam so that the
  *   explicit map replaces a default rather than a hard-coded assumption.
  * @returns {{undeclared: object[], unemitted: object[], skipped: string[]}}
  *   `undeclared` fails a build; `unemitted` is reported; `skipped` names the
@@ -96,7 +96,7 @@ export function compareFields({ builders, artifact, documentType, subtypeOf, }:
 };
 /**
  * What a **compiled document** carries in `system`, against what the receiving
- * subtype declares (#155).
+ * subtype declares.
  *
  * The third of the three checks, and the only one whose emitted set is
  * *observed*. {@link compareFields} reads the `itemBuilders` declarations and
@@ -148,7 +148,7 @@ export function compareEmittedSystem({ system, artifact, documentType, subtype,
  * The published schema this build should check itself against, or `null`.
  *
  * **Which system, and which version, are already settled.** `stats.systemId`
- * and `stats.systemVersion` are derived rather than authored (#48) — a system
+ * and `stats.systemVersion` are derived rather than authored — a system
  * package is its own system, and a module takes the one it requires — and the
  * version is the `compatibility.verified` it pins. So the question "whose
  * schema, at what version" has one answer here rather than a second set of
@@ -168,12 +168,12 @@ export function compareEmittedSystem({ system, artifact, documentType, subtype,
  * stamps no system at all, and a system that has not adopted the artifact yet
  * is simply unchecked. Neither is an error, and the caller says which it was.
  *
- * **A build may have more than one system, and then the caller names it (#139).**
+ * **A build may have more than one system, and then the caller names it.**
  * `stats.systemId` is the package-wide answer, and a repository shipping content
  * for two systems has no package-wide answer — it is deliberately `null` there,
  * because a module feeding both `sohl` and `hm3` targets neither. Left at that,
  * every schema check in such a build would be skipped in silence, which is the
- * state #60 exists to remove: the five type names the two systems *share* are
+ * state this exists to remove: the five type names the two systems *share* are
  * exactly the ones a wrong-system emission hides in. So a pass supplies the
  * system its pack declares, and the version comes from that system's own
  * `systems:` entry rather than from a package-wide stamp.
@@ -236,7 +236,7 @@ export function unemittedMessage(finding: object): string;
 export function emittedUndeclaredMessage(finding: EmissionFinding): string;
 /**
  * What a note authors under `<system>.system`, against what the receiving
- * subtype declares (#58).
+ * subtype declares.
  *
  * The **note-side** half of the check `compareFields` performs on the
  * declarations. A field list is checked once for the whole build because it is
@@ -261,7 +261,7 @@ export function emittedUndeclaredMessage(finding: EmissionFinding): string;
  * @param {string} opts.documentType - `Item`, `Actor`, …
  * @param {string} opts.subType - The document subtype the note compiles into.
  * @param {string} [opts.system] - The system whose published schema to read,
- *   where a build has more than one (#139). Defaults to the package-wide
+ *   where a build has more than one. Defaults to the package-wide
  *   `stats.systemId`.
  * @param {object} [opts.config] - The resolved build configuration.
  * @returns {{path: string, message: string}[]} One finding per undeclared path,
@@ -279,7 +279,7 @@ export function checkAuthoredSystemData(fm: object, { block, documentType, subTy
 }[];
 /**
  * The `system` block a compiler just assembled, against what the receiving
- * subtype declares (#155).
+ * subtype declares.
  *
  * The build-time face of {@link compareEmittedSystem}: it resolves the schema
  * the way every other check here does — the system's own committed artifact, or
@@ -302,7 +302,7 @@ export function checkAuthoredSystemData(fm: object, { block, documentType, subTy
  * @param {readonly {to?: string}[]} [opts.fields] - The type's field
  *   declaration, which decides each finding's origin.
  * @param {string} [opts.system] - The system whose published schema to read,
- *   where a build has more than one (#139). Defaults to the package-wide
+ *   where a build has more than one. Defaults to the package-wide
  *   `stats.systemId`.
  * @param {object} [opts.config] - The resolved build configuration.
  * @returns {(EmissionFinding & {message: string})[]} One per undeclared path.
@@ -326,7 +326,7 @@ export function checkEmittedSystemData(emitted: any, { fm, block, documentType,
  *
  * A mismatch stops the check rather than resolving anyway: a schema read under
  * the wrong shape would report confident nonsense in both directions, and a
- * silently skipped check is the state #60 exists to leave.
+ * silently skipped check is the state this exists to leave.
  *
  * @type {number}
  */