@heroiclands/package-build 20.3.0 → 20.4.0

package/types/engine/site-build.d.mts

@@ -5,7 +5,7 @@
  * tree in reverse. Order was load-bearing here when the address index carried
  * first-writer-wins fallbacks for a page's name, filename and slug — reversing
  * the walk silently changed which page an ambiguous name resolved to. Those
- * fallbacks are gone with the bare `[[Name]]` form (#180), so this is now
+ * fallbacks are gone with the bare `[[Name]]` form, so this is now
  * ordinary reading order rather than a dependency; it is kept because a site's
  * emitted pages should not reorder for no reason.
  *
@@ -51,13 +51,13 @@ export function collectTreePages(tree: object, ctx: object): {
  * it, because in homepage-only mode it is the **whole** of the site build: the
  * content tree is never read for pages at all, so the licensing constraint two
  * packages ship under is a property of the code path rather than of a
- * configuration that happens to be empty (#55).
+ * configuration that happens to be empty.
  *
  * Returned as a list rather than as the one note there should be, because the
- * count is what {@link checkHomepageCount} judges (#52) — this walk reports
+ * count is what {@link checkHomepageCount} judges — this walk reports
  * what it found, and {@link buildSite} decides whether that is one.
  *
- * A homepage that declares no `shortcode` has no address (#182), and is
+ * A homepage that declares no `shortcode` has no address, and is
  * reported rather than written: it is the same finding a content page's missing
  * shortcode produces, and it has to be available in homepage-only mode, where
  * no other gate runs.
@@ -85,13 +85,13 @@ export function collectHomepages(contentBase: string, ctx: object): {
  * for, and would make homepage-only mode depend on the index, the foreign
  * manifests and the table universe that mode exists to not build.
  *
- * **Verbatim is the answer to #54, not a gap left by it.** A landing's links
+ * **Verbatim is the answer, not a gap.** A landing's links
  * could not be *resolved* here without giving `homepage` mode the index its
  * licensing fence exists to not build, so they are **checked** instead:
  * {@link auditHomepageLinks} reads the `landing:` addresses and the body's
  * markdown links, and reports a wikilink on the page rather than resolving one.
  *
- * **Its destination is no longer fixed** (#182). The file is written at the
+ * **Its destination is no longer fixed**. The file is written at the
  * note's address, flat at the package's site root, and the page states that
  * address as its `url` — the same separation of file from URL every other page
  * has. Nothing is written at `/<package>/` itself: that becomes a redirect the
@@ -117,8 +117,7 @@ export function writeHomepages(outRoot: string, pages: readonly object[], config
  * - **Addresses** next: a note that has no address — no shortcode to be
  *   addressed by, or no section to be filed under — would silently drop a page.
  *   There is no collision gate beside it: an address is `(type, shortcode)`,
- *   which is unique within a package by rule, so two pages cannot claim one URL
- *   (#181).
+ *   which is unique within a package by rule, so two pages cannot claim one URL.
  * - **Foreign manifests** last, in two steps. *Unusable* is a file this build
  *   cannot read; *unaddressable* is one it can read but cannot look anything up
  *   in — a distinction worth keeping, because the second surfaces as a pile of
@@ -167,7 +166,7 @@ export function tableUniverse(pages: object[]): Map<string, object[]>;
  *   a value YAML can carry, and would abort the serializer.
  *
  * Everything else the section declared is passed through. That is the point of
- * the function: before #91 both writers transcribed `title` and `banner` by
+ * the function: two writers transcribing `title` and `banner` by
  * name, so the vocabulary lived in three places — the schema that admits a key
  * and the two writers that copy it — and a key added to the schema alone
  * validated cleanly and then reached no page. The *schema* is the bound worth
@@ -182,7 +181,7 @@ export function sectionFrontmatter(meta: object): object;
 /**
  * The frontmatter a page publishes with.
  *
- * An authored `aliases` is retired (#180) and refused before a build reaches
+ * An authored `aliases` is retired and refused before a build reaches
  * here, which makes this a guard rather than a working path. It was Obsidian's
  * — a list of *names* a reader might call
  * the note, which is vault addressing and stays in the vault. Hugo reads
@@ -191,13 +190,13 @@ export function sectionFrontmatter(meta: object): object;
  * redirects of its own.
  *
  * A content page states its own **`url`**, which is its address rather than its
- * path (#181). It is written flat under the content mount (#204), so Hugo would
+ * path. It is written flat under the content mount, so Hugo would
  * otherwise publish it at `<mount><type>-<shortcode>/` rather than at the
  * package-wide address the link manifest records — the same address, one
  * segment too deep. So the address is stated and the mount does not reach it.
  *
- * **It is stated relative to the site root, and so carries no package base**
- * (#217). Hugo resolves a `url` against `baseURL`, whose path is already where
+ * **It is stated relative to the site root, and so carries no package base**.
+ * Hugo resolves a `url` against `baseURL`, whose path is already where
  * the package is served — a consumer's Hugo site *is* its package — so writing
  * `page.url`, which carries the base for every href this build renders, wrote
  * that base a second time and published every content page a segment too deep
@@ -206,8 +205,8 @@ export function sectionFrontmatter(meta: object): object;
  * index a wikilink resolves through, and the link manifest — composes
  * `<base><slug>/`.
  *
- * A content page carries the package the build **derived** (#65). No note
- * declares one — `package:` is retired (#56) — so the note's frontmatter alone
+ * A content page carries the package the build **derived**. No note
+ * declares one — `package:` is retired — so the note's frontmatter alone
  * would publish a page that does not say which package it belongs to. The
  * emitted page is what a
  * theme reads: `breadcrumbs.html` builds its middle crumb from
@@ -228,9 +227,9 @@ export function pageFrontmatter(page: object, { readmeSections, decorate }: obje
 /**
  * Where a page is written, relative to the output root.
  *
- * **Flat, under the mount, named by its address** (#204). A content page's URL
+ * **Flat, under the mount, named by its address**. A content page's URL
  * is its address — `/<package>/<type>-<shortcode>/` — and the file is now named
- * the same way, so the two agree. It used to be filed into `<section>/` so that
+ * the same way, so the two agree. Filing it into `<section>/` so that
  * Hugo would read a section off its path; a section appears in no address, and
  * a directory chosen only to satisfy a rendering engine's idea of what a
  * section is has no business in the note format.
@@ -238,7 +237,7 @@ export function pageFrontmatter(page: object, { readmeSections, decorate }: obje
  * The name is the *whole* address rather than a section-relative half of it, so
  * two types cannot fight over one file: a `doc` note's `subType` may be spelled
  * the same as another note's `type`, and `doc-gear.md` and `weapongear-gear.md`
- * are distinct whatever the sections used to be.
+ * are distinct whatever the sections.
  *
  * **A `trees` entry is the exception, and always was.** Those pages preserve
  * their source layout below a named section — they are a book with chapters,
@@ -274,7 +273,7 @@ export function renderPages(pages: object[], options: object): {
 /**
  * Writes the Hugo sections a published tree declares.
  *
- * **This is where a section lives now, and the only place** (#204). A content
+ * **This is where a section lives now, and the only place**. A content
  * note carries none: it is addressed by `(type, shortcode)` and emitted flat
  * under the mount, so nothing a page does creates a directory. A site that wants
  * `/<package>/<prefix><section>/` to answer — with a title, a hero, and whatever

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

@@ -38,7 +38,7 @@ export function buildSiteIndex(entries: readonly SiteEntry[], { foreignIndex }?:
  *
  * There is deliberately **no `manifestsComplete`**. It used to let a resolver
  * soften an unresolved cross-package address while any package's manifest was
- * missing; #184 retired the softening, since the pack compilers and the link
+ * missing; the softening is retired, since the pack compilers and the link
  * checker never had it and one authored link must not get two verdicts. A
  * caller still passing it is ignored rather than obeyed.
  */
@@ -76,8 +76,7 @@ export type SiteEntry = {
      * The Hugo section a **tree** page is filed under, and
      *   the first segment of the `<sec>/<slug>` address it
      *   is reachable by. A content page has none: it is
-     *   addressed by `(type, shortcode)` and emitted flat
-     *   (#204).
+     *   addressed by `(type, shortcode)` and emitted flat.
      */
     sec?: string | undefined;
     /**
@@ -101,7 +100,7 @@ export type SiteIndex = {
     /**
      *                                       Address → page. `draft` says the page
      *                                       carries the `draft` tag, which marks a
-     *                                       link *into* it (#183).
+     *                                       link *into* it.
      */
     index: Map<string, {
         url: string;

package/types/engine/sql-tables.d.mts

@@ -2,7 +2,7 @@
  * Every `sql` fence in a markdown body, with the position each occupies.
  *
  * Positions are 0-based lines into the body as given, which is what a diagnostic
- * about a directive needs (#17) and what the expander uses to splice results
+ * about a directive needs and what the expander uses to splice results
  * back in.
  *
  * @param {string} markdown - The note body, frontmatter already stripped.
@@ -47,7 +47,7 @@ export function findSqlBlocks(markdown: string): Array<{
  * It is `FROM` rather than a fence property naming a file, for two reasons. A
  * path in authored content is a build artifact's name written into the corpus,
  * so renaming the artifact means sweeping every note that cites it — the
- * coupling #126 exists to undo. And *which dataset a query reads* is what
+ * coupling the corpus move exists to undo. And *which dataset a query reads* is what
  * `FROM` is for: the same rule that keeps `_ref` and `_section` ordinary SQL,
  * visible where an author is already looking, rather than fence options.
  *
@@ -95,6 +95,11 @@ export function runSqlQuery(db: object, sql: string): Promise<{
  * authored `ORDER BY` decides the section order too, and one query replaces the
  * forty near-identical blocks the language used to require.
  *
+ * **A result selecting nothing still renders its header and rule.** The finding
+ * is the point, not withholding the output: an authored heading with an empty
+ * table under it says the query ran and matched nothing, where a heading with
+ * *nothing* under it reads as a page that failed to build.
+ *
  * @param {{columns: string[], rows: object[]}} result - From
  *   {@link runSqlQuery}.
  * @param {object} [opts]
@@ -117,7 +122,7 @@ export function renderSqlTable(result: {
  * {@link module:engine/content-tables.expandContentTables} is not — nor should
  * it become so: two of its three callers are synchronous, and one of those,
  * `renderPages`, is exported. Preparing the results first keeps every one of
- * those signatures intact, and it is the shape #243 is heading for anyway —
+ * those signatures intact, and it is the shape the index is heading for anyway —
  * the corpus enumerated once, each pass reading the answer rather than
  * deriving it again.
  *
@@ -149,7 +154,8 @@ export function prepareSqlTables(db: object, sources: Array<{
  * Answer every `sql` directive in a content tree.
  *
  * The one entry point each pass uses, so the compiler, the link checker and the
- * site build cannot disagree about what a table selects — the failure mode #243
+ * site build cannot disagree about what a table selects — the failure mode the
+ * shared index
  * describes, where N passes each derive the corpus their own way.
  *
  * **Nothing is opened for a tree with no `sql` directive.** The corpus is still
@@ -163,7 +169,7 @@ export function prepareSqlTables(db: object, sources: Array<{
  * @param {readonly string[]} [opts.skipDirectories] - The walk's scope.
  * @param {object[]} [opts.records] - Index records the caller already derived.
  *   A command that also builds a link index holds them already, and deriving
- *   them twice is the duplicated-corpus failure #243 is closing.
+ *   them twice is the duplicated-corpus failure this closes.
  * @returns {Promise<Map<string, object[]>|undefined>} Results by note path, or
  *   nothing when the tree has no such directive.
  */

package/types/engine/subtype-registry.d.mts

@@ -11,7 +11,7 @@ export function subtypeMapFor(system: string | undefined): import("./document-su
  * translation the *schema* check needs, and the reason it needs one.
  *
  * A schema artifact is keyed by document subtype; a field declaration is keyed
- * by note type. Those were the same string until #78 renamed three of them, and
+ * by note type. Those would be the same string but for three renames, and
  * a check that went on joining them by name simply stopped reporting on
  * `armorgear` — a warning that vanishes is worse than one that fires, because
  * nothing says it went.
@@ -29,7 +29,7 @@ export function schemaSubtypeOf(system: string | undefined, type: string): strin
 /**
  * The note-type → document-subtype maps this toolchain ships.
  *
- * Two, since `hm3/` landed (#139) — and it joined this list rather than the
+ * Two, since `hm3/` landed — and it joined this list rather than the
  * claim table growing a second copy of the same fact, which is what the list
  * was for.
  *
@@ -55,7 +55,7 @@ export const KNOWN_DOCUMENT_SUBTYPE_MAPS: readonly import("./document-subtypes.m
  * {@link KNOWN_DOCUMENT_SUBTYPE_MAPS} exists rather than a hand-kept table.
  *
  * It exists because an actor note publishes documentation like every other
- * system-bearing note (#337). `docEntryTypes` was `itemTypes` plus `macro` and
+ * system-bearing note. `docEntryTypes` was `itemTypes` plus `macro` and
  * the map types, which left a being as the one system-bearing note with no
  * `none` address — nothing a prose link could land on, since its only address
  * named the Actor. Composing that set needs to know which types are actors, and

package/types/engine/system-block.d.mts

@@ -117,7 +117,7 @@ export function legacyKeyOf(field: {
 /**
  * The bare top-level key a `data:`-sourced field is being swept off — step 3b.
  *
- * `data:` (#128) did not invent the facts it holds; it *gathered* them, out of
+ * `data:` did not invent the facts it holds; it *gathered* them, out of
  * the note's open top level where each was a sibling of `img` and `shortcode`.
  * So the retiring spelling of `data.portrait` is not a second declaration
  * anyone has to write — it is `portrait`, mechanically, and the same holds for
@@ -208,7 +208,7 @@ export function systemDataPaths(data: Record<string, unknown>, prefix?: string):
  *
  * It stayed invisible while those maps were authored *outside* `<system>.system`
  * and so were never walked. The moment the corpus moves them to the destination
- * (#126) every one of them lights up — 62 findings on `sohl-thalorna` alone,
+ * every one of them lights up — 62 findings on `sohl-thalorna` alone,
  * none of them a defect.
  *
  * So descent is conditional on the schema declaring something *beneath* the
@@ -237,7 +237,7 @@ export function undeclaredPaths(data: Record<string, unknown>, declared: Readonl
  * @param {object} options - Options.
  * @param {Iterable<string>} options.known - The keys this system declares on
  *   top of the shared vocabulary: its generators, its toolchain keys, and —
- *   until #126 moves them — the field names its notes still author in the
+ *   until the corpus moves them — the field names its notes still author in the
  *   block.
  * @returns {string[]} The unrecognized keys, in authored order.
  */

package/types/engine/web-wikilinks.d.mts

@@ -1,5 +1,5 @@
 /**
- * Every wikilink authored inside a frontmatter value (#1428).
+ * Every wikilink authored inside a frontmatter value.
  *
  * Wikilinks are resolved in a note's **body** — by {@link resolveWebWikilinks}
  * here, and by the pack compilers' `convertWikilinks` for Foundry. Frontmatter
@@ -36,19 +36,19 @@ export function frontmatterWikilinks(fm: unknown): Array<{
  * `section/slug`), then in the vendored `ctx.foreign` manifests. A target is a
  * *partial* address: an omitted package means this package, an omitted system
  * is a wildcard, and exactly one match resolves — two are `ambiguous`. A link written
- * without a label addresses nothing at all and is reported as such (#180) —
+ * without a label addresses nothing at all and is reported as such —
  * there is no second namespace left for it to name.
  *
  * Only a slash-qualified target reaches the raw key, which is what keeps
  * `section/slug` addressable without a page's own slug answering for it.
  *
- * **Every target that resolves nowhere fails the build** (#184), and is
+ * **Every target that resolves nowhere fails the build**, and is
  * classified into the vocabulary all three resolvers share — `unlabelled`,
  * `not-an-address`, `unknown-type`, `ambiguous`, `unresolved`. Failures are
  * collected in `ctx.errors`, each carrying the authored `link` and its
  * `occurrence` so a caller can report the line and column it sits on.
  *
- * There used to be one exception: a hyphen-form address was let through while
+ * There is deliberately no exception letting a hyphen-form address through while
  * any linkable package had no vendored manifest, since a real cross-package
  * reference and a typo look identical from here. The pack compilers and the
  * link checker never made that allowance, so its only surviving effect was to
@@ -56,13 +56,13 @@ export function frontmatterWikilinks(fm: unknown): Array<{
  * instead.
  *
  * A target that resolves nowhere still renders through {@link unresolvedLink}
- * rather than as bare prose (#1665): the author's text is kept, marked so a
+ * rather than as bare prose: the author's text is kept, marked so a
  * reader can see a link was intended. The marking and the failure are separate
  * jobs and always were — the mark is for whoever reads the page a *previous*
  * build emitted, the failure is for the author of this one.
  *
  * A target that **resolved** to an entry with no page is not this case and is
- * not marked: a pack-only package (#1516) publishes Foundry addresses and no
+ * not marked: a pack-only package publishes Foundry addresses and no
  * web pages, so the author wrote a real address and there is simply nothing to
  * link to.
  *
@@ -71,7 +71,7 @@ export function frontmatterWikilinks(fm: unknown): Array<{
  *   foreign, type, errors, src, file }`.
  *   `packages` is every package an address may name, without which the leading
  *   package segment of a canonical address reads as an unknown type; `foreign`
- *   is the cross-package manifest index (#1446). `src` is the page's display
+ *   is the cross-package manifest index. `src` is the page's display
  *   path and `file` the source file a diagnostic should name — absent, `src`
  *   stands in.
  * @returns {string} The body with wikilinks rewritten.

package/types/engine/wikilink-syntax.d.mts

@@ -10,7 +10,7 @@
  * @property {string|null} display - The text after `|`, or `null` when the link
  *   is unlabelled. `null` and `""` differ: an author may write `[[x|]]`.
  * @property {boolean} labelled - Whether a `|` was present at all. A link
- *   without one addresses nothing and is a finding (#180) — see
+ *   without one addresses nothing and is a finding — see
  *   {@link unlabelledLinkMessage} — so every reader has to be able to ask.
  */
 /**
@@ -32,12 +32,12 @@ export function parseWikilink(rawInner: string): ParsedWikilink;
  * `display: null` does. The two are still distinguishable through
  * {@link ParsedWikilink.labelled}, which is the thing that genuinely differs:
  * `[[x|]]` is labelled and `[[x]]` is not, and only the first addresses
- * anything (#180).
+ * anything.
  *
  * Stated here because the two resolvers had already drawn the line in two
  * places and drawn it differently: the packs tested falsiness and were right,
  * the web tested `??` — which falls through on `null` only — and emitted
- * `[](/url/)`, a link with no clickable text, through every build (#113). That
+ * `[](/url/)`, a link with no clickable text, through every build. That
  * is the same drift this module exists to prevent, in the case its own
  * {@link ParsedWikilink} docstring calls out. One reading, one place.
  *
@@ -56,12 +56,12 @@ export function authoredLabel({ display }: {
  * the form to write rather than a value to correct: there is no value that
  * makes an unlabelled link resolve.
  *
- * **Why there is nothing left for a bare link to mean** (#180). The pipe used
+ * **Why there is nothing left for a bare link to mean**. The pipe used
  * to select between two namespaces — address and alias — and the alias one was
  * empty in practice: across 8,305 wikilinks in three content trees, not one
  * bare `[[Alias]]` resolved to a note. What the index it looked up in *did* do
  * was fold every note's `name.full` into itself, which forbade two notes of a
- * type from sharing a display name (#179). So the namespace is gone, every
+ * type from sharing a display name. So the namespace is gone, every
  * link is an address, and an address needs the pipe that says so.
  *
  * The **link part may still be an anchor**: `[[#slug|Text]]` addresses a
@@ -80,12 +80,12 @@ export function unlabelledLinkMessage(target: string): string;
  * package publishing it is not a declared dependency — or is one whose index
  * has not been fetched — and the link itself looks identical in every case.
  *
- * This used to be a **warning** in the checker and, in the site build, nothing
+ * As a **warning** in the checker and, in the site build, nothing
  * at all until every linkable package's manifest was accounted for — on the
  * reasoning that a bare `[[Name]]` might be a placeholder for a note nobody had
- * written yet. That reasoning was a property of the bare form, which is retired
- * (#180); the intent behind it now has a real spelling, a `draft`-tagged note
- * that exists and resolves and renders marked (#183). So an address naming no
+ * written yet. That reasoning was a property of the bare form, which is retired;
+ * the intent behind it now has a real spelling, a `draft`-tagged note
+ * that exists and resolves and renders marked. So an address naming no
  * note is a typo or an omission, both want fixing, and all three builds say so.
  *
  * @param {string} target - The address as authored, named in the message.
@@ -101,9 +101,9 @@ export function unresolvedAddressMessage(target: string): string;
  * message names the claimants so the author can choose between them without
  * going looking.
  *
- * **The correction is the canonical form**, all four segments (#59). Omission
+ * **The correction is the canonical form**, all four segments. Omission
  * runs strictly left to right, so there is no `package-type-shortcode` to offer
- * — naming a package means naming the system before the type. That used to be
+ * — naming a package means naming the system before the type. That would be
  * the correction here, back when a written target could state three segments at
  * most; the grammar is positional now, and a three-segment target names a
  * *system*, not a package.
@@ -166,7 +166,7 @@ export function isSamePage({ target, anchor }: ParsedWikilink): boolean;
  * The web side's pattern omitted `\n` from the excluded set, so an unclosed
  * bracket consumed everything up to the next `]]` anywhere in the document —
  * the same shape of corruption a hand-rolled code-fence regex caused on the one
- * page whose subject is link syntax (SoHL#1665). It was also internally
+ * page whose subject is link syntax. It was also internally
  * inconsistent: its *frontmatter* scan excluded newlines while its body scan did
  * not.
  *
@@ -182,7 +182,7 @@ export function isSamePage({ target, anchor }: ParsedWikilink): boolean;
  * ({@link LINK_FINDING_REASONS}) and the message each one reports through
  * ({@link linkFindingMessage}). Three builds read one authored link; an author
  * meets whichever ran first, and a consumer switching on a `reason` should not
- * be switching on which build produced it (#184).
+ * be switching on which build produced it.
  *
  * @module
  */
@@ -196,16 +196,16 @@ export function isSamePage({ target, anchor }: ParsedWikilink): boolean;
  */
 export const WIKILINK: RegExp;
 /**
- * Every way a link can fail, named once for all three resolvers (#184).
+ * Every way a link can fail, named once for all three resolvers.
  *
  * A link is read in three places — the checker (`content-links.mjs`), the pack
  * compilers (`wikilinks.mjs`) and the web resolver (`web-wikilinks.mjs`) — and
- * each used to name the failures in its own words. `unknown` in one was
+ * each would otherwise name the failures in its own words. `unknown` in one is
  * `unresolved` in another and `broken type/shortcode` in the third, so a
  * consumer switching on a `reason` was switching on which build had produced
  * it. The set is closed and lives here, beside the syntax the three share.
  *
- * - `unlabelled` — no `|`, so the link addresses nothing (#180).
+ * - `unlabelled` — no `|`, so the link addresses nothing.
  * - `not-an-address` — labelled, but the target does not parse as an address.
  * - `unknown-type` — definitely qualified, but names no type this build knows.
  * - `unresolved` — parses as an address, and nothing publishes it.
@@ -240,7 +240,7 @@ export type ParsedWikilink = {
     display: string | null;
     /**
      * - Whether a `|` was present at all. A link
-     * without one addresses nothing and is a finding (#180) — see
+     * without one addresses nothing and is a finding — see
      * {@link unlabelledLinkMessage} — so every reader has to be able to ask.
      */
     labelled: boolean;

package/types/engine/wikilinks.d.mts

@@ -3,15 +3,15 @@
  * not one.
  *
  * A document and its documentation are two documents in two packs, so they
- * need two addresses (#1362). `skill/wpnc` is the item; `docskill/wpnc` is the
+ * need two addresses. `skill/wpnc` is the item; `docskill/wpnc` is the
  * JournalEntry its prose compiled into, and `docmacro/autoattack` is the same
- * arrangement for a macro (#1514).
+ * arrangement for a macro.
  *
  * The virtual form exists for a type that carries separate documentation
  * ({@link sohl.utils.packs.docEntryTypes} — the set the journals compiler and
  * the link manifest read too), **or** for one that routes to the items pack.
  * The second clause is the older rule and stays: types that compile into items
- * are the open, unenumerated set (#1276), and a foreign package may publish an
+ * are the open, unenumerated set, and a foreign package may publish an
  * item type this build has never heard of. Dropping it would silently unlink
  * every `doc<type>` address into such a package.
  *
@@ -31,8 +31,8 @@ export function resolveItemDocType(qualifier: string, types: Set<string>): strin
  * Two separators are accepted, and they are **not** interchangeable in how
  * confidently they mark a target as qualified:
  *
- * - **`type-shortcode`** and its qualified forms — the canonical spelling
- *   (#1398). Obsidian reads `/` inside a wikilink as a *path* and resolves it
+ * - **`type-shortcode`** and its qualified forms — the canonical spelling.
+ * Obsidian reads `/` inside a wikilink as a *path* and resolves it
  *   against the vault's folders, so a slash-qualified link is a broken link in
  *   the editor where the content is now authored.
  * - **`type/shortcode`** — the legacy form, still resolved so that a link
@@ -41,7 +41,7 @@ export function resolveItemDocType(qualifier: string, types: Set<string>): strin
  *   before it is reported rather than guessed at. The split is at the **last**
  *   slash, as it always was.
  *
- * **The grammar is strict, and omission runs left to right** (#59):
+ * **The grammar is strict, and omission runs left to right**:
  *
  * ```text
  * [[[[<package>-]<system>-]<type>-]<shortcode>]
@@ -56,12 +56,13 @@ export function resolveItemDocType(qualifier: string, types: Set<string>): strin
  * **Parsing is plain positional counting**, the same rule
  * {@link readCanonicalKey} follows, and it is sound for the same reason: every
  * segment is `^[A-Za-z0-9]+$` (`ADDRESS_SEGMENT_PATTERN`, enforced on
- * shortcodes by `content-lint.mjs` since #1397), so the hyphen is purely a
+ * shortcodes by `content-lint.mjs`), so the hyphen is purely a
  * separator and the count alone determines every field. Verified across the
  * four content trees: 138,204 authored shortcodes, none carrying a separator.
  *
  * That replaced a first-hyphen split which let a shortcode contain a hyphen
- * (`trauma-self-pro` → `trauma` + `self-pro`). The tolerance predates #1397 and
+ * (`trauma-self-pro` → `trauma` + `self-pro`). The tolerance predates the
+ * charset rule and
  * outlived it; no tree has used it, and keeping it would make a three-segment
  * target ambiguous between a system and a hyphenated shortcode.
  *
@@ -120,7 +121,7 @@ export function anchorPageId(noteId: string, anchorSlug: string): string;
  *   One entry per content note. `pack` / `docPack` name the packs the note's
  *   document and its documentation entry landed in; omitted, the conventional
  *   one-pack-per-type names stand in. `draft` says the note carries the `draft`
- *   tag, which marks links *into* it and changes nothing else (#183).
+ *   tag, which marks links *into* it and changes nothing else.
  * @param {string} packageId - The Foundry package shipping the packs; the first
  *   segment of every emitted UUID.
  * @param {Map<string, object>} [foreign] - Canonically keyed entries from
@@ -153,7 +154,7 @@ export function buildWikilinkIndex(docs: Array<{
  *
  * **Code is verbatim.** A `[[…]]` inside a fenced or indented code block, or
  * inside an inline code span, is source text an author wrote to be read as
- * written, so it is left alone and not reported (#1505). Without that, a
+ * written, so it is left alone and not reported. Without that, a
  * script sample containing `grid[[0]]` became a link — and only for some
  * array shapes, `[[1,2],[3,4]]` having an inner `]` the pattern cannot cross,
  * so the corruption looked arbitrary. It reaches the reader through the
@@ -174,10 +175,10 @@ export function buildWikilinkIndex(docs: Array<{
  * @returns {{markdown: string, unresolved: Array<{link: string, target: string,
  *   offset: number, reason: string, packages?: string[], anchor?: string}>}}
  *   Each `reason` is one of {@link LINK_FINDING_REASONS}, the vocabulary all
- *   three resolvers share (#184) — `ambiguous` carries the claiming `packages`
+ *   three resolvers share — `ambiguous` carries the claiming `packages`
  *   and `unknown-anchor` the section it named. `offset` is the link's 0-based
  *   position in `markdown`, which is what lets a caller report the line and
- *   column it sits on (#17).
+ *   column it sits on.
  */
 export function convertWikilinks(markdown: string, { type, id, pack, docPack, index }: {
     type: string;

package/types/hm3/actors.d.mts

@@ -35,7 +35,7 @@ export class Hm3Actors extends SystemActorCompiler {
      * template priority.
      *
      * The rule itself is {@link module:hm3/template-priority.templateFlags},
-     * because the Item pass writes the same flag from the same statement (#283)
+     * because the Item pass writes the same flag from the same statement
      * and two copies of it were one copy too many — this pass had the only one,
      * and the Item pass had none.
      *

package/types/hm3/document-subtypes.d.mts

@@ -17,7 +17,7 @@ export const HM3_TYPE_KEY: string;
  * map does not name — `affiliation`, `affliction`, `attribute`,
  * `concoction`, `mystery`, and every core type — compile into no HM3
  * document at all, silently and correctly: HM3 has no form of them, and a
- * finding on every such note would be the noise #79's rule exists to prevent.
+ * finding on every such note would be the noise the rule exists to prevent.
  *
  * @type {import("../engine/document-subtypes.mjs").DocumentSubtypeMap}
  */

package/types/hm3/items.d.mts

@@ -1,8 +1,7 @@
 export class Hm3Items extends SystemItemCompiler {
     /**
      * HM3's note-type → document-subtype map — the one declaration that says
-     * which block this pass reads, which notes it claims, and what each becomes
-     * (#58/#79).
+     * which block this pass reads, which notes it claims, and what each becomes.
      *
      * @type {import("../engine/document-subtypes.mjs").DocumentSubtypeMap}
      */

package/types/hm3/template-priority.d.mts

@@ -5,7 +5,7 @@
  * A note that is not a template — or states nothing — writes nothing, rather
  * than a `null` nothing reads.
  *
- * **Read through the shared resolver, not a field declaration** (#266). A
+ * **Read through the shared resolver, not a field declaration**. A
  * `FieldSpec`'s shared source is a single position, and this value has five:
  * `data:`, this block, the top level, and the retiring `archetype` spelling in
  * the latter two. The resolver is the single implementation of what a note said,

package/types/manifest.d.mts

@@ -43,7 +43,7 @@ export function releaseUrls({ repoUrl, version, artifact }: {
     download: string;
 };
 /**
- * Where this release publishes its content index (#239).
+ * Where this release publishes its content index.
  *
  * **Pinned to this version, like `download` and unlike `manifest`.** A
  * consumer reaches this URL by reading the dependency's manifest, so the
@@ -66,7 +66,7 @@ export function metadataUrl({ repoUrl, version, contentPackage }: {
 /**
  * The manifest's `packs`, derived from the one pack list the build already has.
  *
- * The two used to be written separately — `package-build.config.yaml` declared
+ * The two are not written separately, with `package-build.config.yaml` declaring
  * a pack's name and type, and the manifest template declared them again beside
  * a label, a path and a system id, with nothing checking that the pairs agreed.
  * They are one list now.
@@ -89,12 +89,12 @@ export function manifestPacks(config: object): object[];
  * `styles`, `languages`), and a staged file is a different relation, checked
  * against the stage rather than against configuration. So this is the one place
  * a declaration can go stale against a value the build already computed — and
- * until now nothing compared them (#81).
+ * until now nothing compared them.
  *
  * `HarnMaster-3-FoundryVTT` shipped the consequence: its folder named four
  * packs, three of which had not existed since the compendium was consolidated,
  * and omitted `items` — 1,577 of 1,597 documents, loose in Foundry's compendium
- * browser, with the build reporting nothing (HM3#420).
+ * browser, with the build reporting nothing.
  *
  * **The two findings are not the same finding**, and giving them one severity
  * gets one of them wrong:
@@ -187,7 +187,7 @@ export function buildManifest({ config, packageJson, artifact, flags }: {
  * The declared `packFolders` is checked against the derived `packs[]` first,
  * and an unresolvable name **stops the write**: a manifest already known to
  * describe packs the package does not ship should not reach the stage, where
- * the next command would deploy it (#81). See {@link packFolderFindings} for
+ * the next command would deploy it. See {@link packFolderFindings} for
  * the rule and why its two findings carry different severities.
  *
  * @param {object} options - As {@link buildManifest}, plus where to write.
@@ -229,14 +229,14 @@ export const ARTIFACTS: readonly string[];
  *
  * `relationships` is the one manifest block with a second reader.
  * `@heroiclands/content-build` consumes it too, and v1.8.0 added
- * `itemCatalog: true` as an opt-in on a declared dependency
- * (content-build#82): it selects that package's Item packs as a resolution
+ * `itemCatalog: true` as an opt-in on a declared dependency: it selects that
+ * package's Item packs as a resolution
  * source for the actors pass. That is an instruction to the build, not a fact
  * about the shipped package — Foundry's relationship schema does not define
  * it, and someone reading a published manifest cannot tell a build directive
  * from a declaration about what the package needs.
  *
- * So the block is filtered rather than copied whole (#29). The rule is the
+ * So the block is filtered rather than copied whole. The rule is the
  * distinction, not the name: a key listed here answers *how is this built?*,
  * and every key that survives answers *what does this package depend on?*.
  * `itemCatalog` is the first build-time key to land on a relationship and is

package/types/sohl/actors.d.mts

@@ -2,7 +2,7 @@ export class Actors extends SystemActorCompiler {
     /**
      * SoHL's note-type → document-subtype map — the one declaration that says
      * which block this pass reads, which notes it claims, and what each
-     * becomes (#79). It is also what every embedded reference is translated
+     * becomes. It is also what every embedded reference is translated
      * through, which is why a subclass replaces one thing and not two.
      *
      * @type {import("../engine/document-subtypes.mjs").DocumentSubtypeMap}
@@ -14,7 +14,7 @@ export class Actors extends SystemActorCompiler {
      */
     buildEmbeddedItems(itemsMap: any, actorId: any, fm: any, ctx: any): any[];
     /**
-     * Bake each unopened skill's opening mastery level into the document (#46).
+     * Bake each unopened skill's opening mastery level into the document.
      *
      * A skill whose `masteryLevelBase` is still null once the note's frontmatter
      * has been merged onto the catalogue entry is *not yet opened*, and the