@heroiclands/package-build 20.3.1 → 20.5.0

package/sohl/item-fields.mjs

@@ -17,8 +17,8 @@
  * This is the authority for what an item note may write, and — because
  * {@link buildFromFields} turns each list into the builder that runs — it is
  * the same authority the compiler obeys. A field that is not here is not
- * emitted; a description here is a description of the thing that executes
- * (#22). The per-type authoring reference on the knowledgebase is generated
+ * emitted; a description here is a description of the thing that executes.
+ * The per-type authoring reference on the knowledgebase is generated
  * from this file.
  *
  * **SoHL type vocabulary, so it lives in `sohl/`.** `engine/` holds the
@@ -197,7 +197,7 @@ const STRIKE_MODES = Object.freeze({
  * depends on it.
  *
  * Authored `impact.die`, stored `impactBase.die` — the one re-reading field
- * whose two positions are spelled differently, so both are named (#126).
+ * whose two positions are spelled differently, so both are named.
  *
  * @param {object} fm - The note's frontmatter.
  * @returns {number} The die size, `0` when the projectile declares none.
@@ -340,8 +340,7 @@ export const ITEM_FIELDS = Object.freeze({
         },
         {
             // Plural because the field holds a map of many standings, one per
-            // affiliation — the singular was a misnomer every author read past
-            // (SoHL#1781).
+            // affiliation — the singular reads as a misnomer.
             name: "relations",
             to: "relations",
             ...RELATION,
@@ -448,7 +447,7 @@ export const ITEM_FIELDS = Object.freeze({
             describe:
                 "What running the course to the end does to the host: `death`, or the benign default `cured`.",
         },
-        // The two **authored** thirds of each timed-phase triplet (#329). Every
+        // The two **authored** thirds of each timed-phase triplet. Every
         // one omits its key when the note does not carry it, because the value
         // that stands otherwise is the DataModel's `initial: null` — writing a
         // compile-time `null` over it would say "this phase takes no time",
@@ -513,7 +512,7 @@ export const ITEM_FIELDS = Object.freeze({
                 "The resolution interval in seconds, standing in for a roll of the formula. Omitted when unset.",
         },
         // The `…Date` third of every timed-phase triplet, declared as **runtime
-        // state** (#330). A phase is authored as its `…DurationFormula`; the
+        // state**. A phase is authored as its `…DurationFormula`; the
         // `…DurationBase` records what that rolled to; the date records *when
         // it happened*, and only play can know that. All four are
         // `worldTimeDateField()`s in SoHL's schema — nullable rather than
@@ -949,7 +948,7 @@ export const ITEM_FIELDS = Object.freeze({
             default: null,
             describe: "Shortcode of the body location injured. Unset on a descriptive condition.",
         },
-        // A trauma's three timed phases (#329). Its healing check and course
+        // A trauma's three timed phases. Its healing check and course
         // both fall back to a **world setting** when the trauma sets neither
         // half, which is the sharper reason these omit rather than default: a
         // compile-time `null` written here is still a value, and the seeding in
@@ -1007,7 +1006,7 @@ export const ITEM_FIELDS = Object.freeze({
             describe:
                 "The course-test interval in seconds, standing in for a roll of the formula. Omitted when unset.",
         },
-        // Runtime state, for the reason `affliction`'s four are (#330): a
+        // Runtime state, for the reason `affliction`'s four are: a
         // trauma's dates are crystallized when the phase fires, and world time
         // does not exist while content is compiled.
         {

package/sohl/items.mjs

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

package/sohl/kb-passes.mjs

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

package/sohl/note-schemas.mjs

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

package/sohl/skill-base.mjs

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

package/types/content-config.d.mts

@@ -1,3 +1,16 @@
+/**
+ * Whether this package compiles Foundry documents at all.
+ *
+ * The one question every Foundry-side reader asks — the manifest writer, to
+ * decide whether there is a package for Foundry to install, and the pack
+ * compilers, to decide whether there is anything to compile.
+ *
+ * @param {{packageKind: string}} config - A resolved configuration.
+ * @returns {boolean} Whether the package compiles Foundry documents.
+ */
+export function compilesFoundryDocuments(config: {
+    packageKind: string;
+}): boolean;
 /**
  * Whether this package publishes the pages its content tree compiles to.
  *
@@ -30,13 +43,27 @@ export function publishesContentPages(config: {
  */
 export function defineConfig(config: ContentBuildConfigInput): ContentBuildConfig;
 /**
- * The two kinds of Foundry package a content module can be built into. The
- * value is also the directory Foundry installs the package under, which is why
- * it is plural.
+ * What kind of package this is.
+ *
+ * `systems` and `modules` are the two Foundry answers, and the value is also
+ * the directory Foundry installs the package under, which is why they are
+ * plural. `documentation` is the answer "not a Foundry package at all": it
+ * publishes a site and a book from its notes, installs into no Foundry data
+ * directory and compiles no compendium.
  *
  * @satisfies {readonly PackageKind[]}
  */
-export const PACKAGE_KINDS: readonly ["systems", "modules"];
+export const PACKAGE_KINDS: readonly ["systems", "modules", "documentation"];
+/**
+ * The kind that compiles no Foundry documents.
+ *
+ * Spelled once and read wherever a pass asks whether it applies, so the
+ * validator, the CLI and the compile passes cannot come to disagree about what
+ * the value means.
+ *
+ * @type {string}
+ */
+export const DOCUMENTATION_KIND: string;
 export namespace DEFAULT_PATHS {
     let content: "assets/content";
     let contentIndex: "build/content-index";
@@ -49,7 +76,7 @@ export namespace DEFAULT_PATHS {
 /**
  * The Foundry document types a compendium pack may hold. This is the set the
  * toolchain is able to compile a pack of; a document type Foundry supports but
- * this toolchain does not compile is deliberately absent (see #1501 — playlists
+ * this toolchain does not compile is deliberately absent (playlists
  * and roll tables are out of scope).
  *
  * @satisfies {readonly PackDocumentType[]}
@@ -68,15 +95,11 @@ export const PACK_DOCUMENT_TYPES: readonly ["Actor", "Adventure", "Item", "Journ
  * key is **refused**, at the line it was written on, with a message that says
  * the mechanism is gone rather than naming a value to correct.
  *
- * **What `landing` did (#204).** It named which note addressed a whole section
+ * **`landing` is one such key.** It named which note addressed a whole section
  * rather than a page within one — a *landing page*, which therefore had no slug
- * of its own. #203 retired the second of its two rules and #204 retired the
- * concept both rules chose between: a section is a Hugo content directory that
- * the note format does not carry, a page's address names no directory, and so
- * no note lands anything. The key outlived its mechanism by one release only
- * because both publishing consumers still declared the then-true
- * `landing: readme`, and neither breaking them over a correct statement nor
- * accepting the key in silence was acceptable. Neither declares it now.
+ * of its own. There are no sections to address: a section is a Hugo content
+ * directory the note format does not carry, a page's address names no
+ * directory, and so no note lands anything.
  *
  * @type {Readonly<Record<string, string>>}
  */
@@ -89,7 +112,7 @@ export const RETIRED_ADDRESS_KEYS: Readonly<Record<string, string>>;
  * `thalorna`, whose site is nothing but its content. It is not the package's
  * own mount point: where the package itself is served is the consuming build's
  * knowledge, held in `PACKAGE_BASE` (`engine/content-address.mjs`) and prefixed at
- * resolve time, so it is never recorded here (#1465).
+ * resolve time, so it is never recorded here.
  *
  * It is the whole scheme: `landing`, the key that named which note addressed a
  * whole section, is retired with the sections themselves — see
@@ -103,7 +126,7 @@ export const DEFAULT_ADDRESS_SCHEME: Readonly<{
  *
  * Every HeroicLands package publishes something: a top-level, human-authored
  * homepage at `https://www.heroiclands.org/<contentPackage>/` saying what the
- * module is, which system it needs and how to install it (#50). So there is no
+ * module is, which system it needs and how to install it. So there is no
  * value here meaning *no web presence at all* — homepage-only is the **floor**,
  * and the default.
  *
@@ -141,7 +164,7 @@ export const SITE_MODES: readonly ["homepage", "content"];
  * How the loader hands {@link defineConfig} the system version it resolved.
  *
  * A **Symbol**, deliberately. `stats.systemVersion` is refused from an authored
- * configuration (#48), but the value still has to reach here from the loader —
+ * configuration, but the value still has to reach here from the loader —
  * which is the half that may do I/O, and which reads a system package's version
  * out of the adjacent `package.json`. A string key would be a second spelling of
  * the refused one, forgeable from YAML and reachable by `rejectUnknownKeys`; a
@@ -156,7 +179,7 @@ export const DERIVED_SYSTEM_VERSION: symbol;
  *
  * Every HeroicLands package publishes something: a top-level, human-authored
  * homepage at `https://www.heroiclands.org/<contentPackage>/` saying what the
- * module is, which system it needs and how to install it (#50). So there is no
+ * module is, which system it needs and how to install it. So there is no
  * value here meaning *no web presence at all* — homepage-only is the **floor**,
  * and the default.
  *
@@ -183,7 +206,7 @@ export const DERIVED_SYSTEM_VERSION: symbol;
  * means what it said.
  */
 export type SiteMode = "homepage" | "content";
-export type PackageKind = "systems" | "modules";
+export type PackageKind = "systems" | "modules" | "documentation";
 export type PackDocumentType = "Actor" | "Adventure" | "Item" | "JournalEntry" | "Macro" | "Scene";
 /**
  * One compendium pack the build compiles, named exactly as it is declared in
@@ -194,7 +217,7 @@ export type PackDocumentType = "Actor" | "Adventure" | "Item" | "JournalEntry" |
  * type** receives its document. The two are orthogonal, and both are needed
  * once a repository groups same-type documents editorially — which it may have
  * to, since a compendium UUID carries its pack name and collapsing such a
- * layout breaks every stored reference (#1566).
+ * layout breaks every stored reference.
  */
 export type PackSpec = {
     /**
@@ -304,7 +327,7 @@ export type PathsInput = {
     foreignCache?: string | undefined;
     /**
      * Where a dependency's published content
-     *     index is fetched to (#239). Inbound,
+     *     index is fetched to. Inbound,
      *     for *every* declared dependency, not
      *     only those supplying a catalogue.
      */
@@ -503,7 +526,7 @@ export type AddressSchemeInput = {
  * `fields` is what makes the type documentable: a builder function says
  * nothing about the vocabulary it consumes, so a consumer that declares its
  * fields can generate its own authoring reference and check its own notes,
- * while one that does not is simply undocumented rather than broken (#22).
+ * while one that does not is simply undocumented rather than broken.
  */
 export type ItemBuilderEntry = ((fm: object) => object) | {
     system: (fm: object) => object;
@@ -511,7 +534,7 @@ export type ItemBuilderEntry = ((fm: object) => object) | {
     fields?: readonly object[];
 };
 /**
- * One **registry** of a declared set, and the system it belongs to (#58).
+ * One **registry** of a declared set, and the system it belongs to.
  *
  * A repository shipping content for two systems declares one of these per
  * system: the accepted type vocabulary is their union, and a type both declare
@@ -546,17 +569,27 @@ export type ContentBuildConfigInput = {
     contentPackage: string;
     /**
      * Foundry package id, as it appears in
-     * `system.json` / `module.json`.
+     *       `system.json` / `module.json`.
+     *       Refused by a `documentation`
+     *       package, which ships no Foundry
+     *       package.
      */
-    foundryPackage: string;
+    foundryPackage?: string | undefined;
     /**
-     * Whether the package is a system or a module.
+     * Whether the package is a system, a
+     * module, or documentation — the kind
+     * that publishes a site and a book
+     * while compiling nothing.
      */
     packageKind: PackageKind;
     /**
-     * Identity stamped into every document's `_stats`.
+     * Identity stamped into every
+     *             document's `_stats`. Required of a
+     *             package that compiles documents, and
+     *             refused by a `documentation` one,
+     *             which compiles none.
      */
-    stats: StatsSpec;
+    stats?: StatsSpec | undefined;
     /**
      * The consumer's
      * item-type registry: each content `type`
@@ -570,7 +603,7 @@ export type ContentBuildConfigInput = {
      * two systems declares a **list** of
      * `{ system, builders }` registries
      * instead, and the accepted type
-     * vocabulary is their union (#58).
+     * vocabulary is their union.
      */
     itemBuilders?: Record<string, ItemBuilderEntry> | readonly ItemRegistrySpec[] | undefined;
     /**
@@ -579,8 +612,7 @@ export type ContentBuildConfigInput = {
      * the pack it belongs in with its
      * `pack:` frontmatter, and one pack of
      * the type is marked `default: true` to
-     * receive the notes that name none
-     * (#1566).
+     * receive the notes that name none.
      */
     packs: PackSpec[];
     /**
@@ -631,15 +663,29 @@ export type ContentBuildConfigInput = {
 export type ContentBuildConfig = {
     rootDir: string;
     contentPackage: string;
-    foundryPackage: string;
+    /**
+     * `null` for a `documentation`
+     * package, which ships no Foundry package.
+     */
+    foundryPackage: string | null;
     packageKind: PackageKind;
     /**
-     * Derived: the served Foundry asset root,
-     * `<packageKind>/<foundryPackage>/assets`.
+     * Derived, and **conditional**: the served
+     * Foundry asset root,
+     * `<packageKind>/<foundryPackage>/assets`,
+     * for a package Foundry installs — and
+     * `null` for a `documentation` package,
+     * which Foundry serves no files for. See
+     * {@link module :engine/helpers.resolveImg},
+     * the one reader of it.
      */
-    assetRoot: string;
+    assetRoot: string | null;
     paths: Readonly<ResolvedPaths>;
-    stats: Readonly<StatsSpec>;
+    /**
+     * `null` for a `documentation`
+     * package, which stamps no `_stats`.
+     */
+    stats: Readonly<StatsSpec> | null;
     /**
      * Derived: the
      * `system` builder of each entry, whichever
@@ -658,14 +704,13 @@ export type ContentBuildConfig = {
      * the frontmatter fields each entry
      * declared. Sparse, like `itemArt` — a type
      * absent here compiles normally and is
-     * simply undocumented (#22).
+     * simply undocumented.
      */
     itemFields: Readonly<Record<string, readonly object[]>>;
     /**
      *                                     Derived: the same builders, kept per
      *                                     declaring system. `{}` for the single
-     *                                     registry form, which names no system
-     *                                     (#58).
+     *                                     registry form, which names no system.
      */
     itemBuildersBySystem: Readonly<Record<string, Readonly<Record<string, Function>>>>;
     /**
@@ -688,7 +733,7 @@ export type ContentBuildConfig = {
      * {@link ContentBuildConfigInput.itemBuilders},
      * unioned across every declared registry, so
      * the accepted item types and the builder
-     * tables are one list (#1504).
+     * tables are one list.
      */
     itemTypes: ReadonlySet<string>;
     /**
@@ -700,6 +745,13 @@ export type ContentBuildConfig = {
      */
     docEntryTypes: ReadonlySet<string>;
     skipDirectories: readonly string[];
+    /**
+     * The
+     * fonts this package ships and the names it
+     * draws from them; empty when it declares
+     * none.
+     */
+    icons: import("./engine/content-icons.mjs").IconRegistry;
     packs: readonly Readonly<ResolvedPackSpec>[];
     /**
      * Derived: every pack directory

package/types/e2e.d.mts

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