@heroiclands/package-build 11.0.0 → 13.0.0

package/engine/note-vocabulary.mjs

@@ -53,9 +53,31 @@
  * one is already reported as a type no schema declares, which is the finding it
  * deserves until the type exists.
  *
+ * **A type name and a subType value are held to the address charset** (#206), so
+ * both are `^[A-Za-z0-9]+$` — the charset `engine/address-charset.mjs` states
+ * and the shortcode is already held to. For a type that is literal: it is the
+ * first segment of every address (`type-shortcode`), the hyphen is the
+ * separator between segments and can therefore never occur inside one, and a
+ * hyphenated name would be read back as two segments and resolve to nothing,
+ * reporting nothing about why.
+ *
+ * A subType reaches no address of its own. It did when this rule was written —
+ * a `doc`'s was its section, a path segment — and #204 retired sections from
+ * the note format one release later. It keeps the rule regardless, and the
+ * reason is not inertia: a subType is a vocabulary term the whole toolchain
+ * keys on, it is one closed set away from being an address again, and a charset
+ * that held for a type, a shortcode and a package but not for a subType would
+ * be a rule nobody could state in one sentence. The registry below is checked
+ * against it as this module loads, so a declaration that breaks it cannot be
+ * imported, let alone shipped.
+ *
  * @module
  */
 
+// The one charset, read rather than restated. A second spelling of the pattern
+// is how the three disagreements found in #202/#203 happened.
+import { ADDRESS_SEGMENT_PATTERN, isAddressSegment } from "./address-charset.mjs";
+
 /**
  * One `data:` key a note type may carry.
  *
@@ -641,7 +663,12 @@ export const NOTE_VOCABULARY = Object.freeze({
     /* ----- core documents ------------------------------------------- */
 
     doc: Object.freeze({
-        subTypes: Object.freeze(["rules", "user-guide", "reference"]),
+        // `userguide`, not `user-guide`: a `doc` routes by its subType, so the
+        // value is a path segment, and a segment carries no hyphen (#206). The
+        // old spelling is accepted transitionally — see {@link RETIRED_SUBTYPES}
+        // — but it is not declared here, because this list is what the format
+        // says a note *should* write.
+        subTypes: Object.freeze(["rules", "userguide", "reference"]),
         data: Object.freeze([]),
     }),
 
@@ -704,6 +731,137 @@ export const NOTE_VOCABULARY = Object.freeze({
     }),
 });
 
+/**
+ * The retired spelling of a subType a type declares → what to write now (#206).
+ *
+ * Keyed by type, because a retirement is a statement about *that type's*
+ * vocabulary: `user-guide` on a `doc` is the old spelling of `userguide`, while
+ * the same string on any other type is nothing but a charset violation, and
+ * saying "did you mean userguide" there would be a guess dressed as a fact.
+ *
+ * **Recorded here rather than left in `subTypes`** so the declared list stays
+ * the list of values a note *should* write. A retired value is accepted, not
+ * declared — the difference is exactly what makes the finding possible.
+ *
+ * **Deliberately not the shape of a type rename** ({@link
+ * import("./ids.mjs").RETIRED_TYPES}), which is an error: a retired type routes
+ * a note to the wrong pack, whereas a retired subType still compiles to the
+ * correct page. The sweep is the consumer's, and the ordering is the reverse of
+ * the usual — the acceptance ships *first*, because declaring only the new
+ * spelling while 43 `sohl` notes still author the old one would invalidate all
+ * 43 with a release they had no chance to sweep ahead of. A later change
+ * removes this map, and the old spelling then falls through to the ordinary
+ * undeclared-value error with no code left to remove.
+ *
+ * @type {Readonly<Record<string, Readonly<Record<string, string>>>>}
+ */
+export const RETIRED_SUBTYPES = Object.freeze({
+    doc: Object.freeze({ "user-guide": "userguide" }),
+});
+
+/**
+ * What to write in place of a retired subType value, if it is one.
+ *
+ * @param {string} type - The note's `type`.
+ * @param {string} value - The authored `subType`.
+ * @param {Readonly<Record<string, Readonly<Record<string, string>>>>} [retired]
+ *   The map to read, defaulting to {@link RETIRED_SUBTYPES}.
+ * @returns {string|undefined} The current spelling, or `undefined` when the
+ *   value is not a retired one — which is not the same as it being valid.
+ */
+export function retiredSubType(type, value, retired = RETIRED_SUBTYPES) {
+    const forType = retired?.[type];
+    if (!forType || !Object.hasOwn(forType, value)) return undefined;
+    return forType[value];
+}
+
+/**
+ * What a note carrying a retired subType is told.
+ *
+ * One message, so the lint and any later refusal cannot describe the same
+ * retirement differently.
+ *
+ * @param {string} type - The note's `type`.
+ * @param {string} value - The retired spelling the note carries.
+ * @param {string} replacement - What to write instead.
+ * @returns {string} The message.
+ */
+export function retiredSubTypeMessage(type, value, replacement) {
+    return (
+        `\`subType\` "${value}" is a retired spelling of "${replacement}" on a ` +
+        `${type}; write "${replacement}". A subType is an address segment, and ` +
+        `a segment is ${ADDRESS_SEGMENT_PATTERN.source} — the hyphen separates ` +
+        `segments, so it can never occur inside one. The old spelling is still ` +
+        `accepted, and will stop being accepted once the trees have swept`
+    );
+}
+
+/**
+ * What a note carrying a subType outside the address charset is told.
+ *
+ * @param {string} value - The authored `subType`.
+ * @returns {string} The message.
+ */
+export function subTypeCharsetMessage(value) {
+    return (
+        `\`subType\` "${value}" is not an address segment — a subType is ` +
+        `letters and digits only (${ADDRESS_SEGMENT_PATTERN.source}), the same ` +
+        `charset a shortcode is held to. The hyphen separates the segments of ` +
+        `an address, so a value containing one is read back as two segments ` +
+        `and resolves to nothing`
+    );
+}
+
+/**
+ * What a note carrying a type outside the address charset is told.
+ *
+ * @param {string} type - The authored `type`.
+ * @returns {string} The message.
+ */
+export function typeCharsetMessage(type) {
+    return (
+        `content type "${type}" is not an address segment — a type is letters ` +
+        `and digits only (${ADDRESS_SEGMENT_PATTERN.source}), the same charset ` +
+        `a shortcode is held to. A type is the first segment of every address ` +
+        `("type-shortcode"), so a hyphenated one is read back as two segments ` +
+        `and resolves to nothing`
+    );
+}
+
+/**
+ * Refuse a vocabulary that declares a type or subType outside the charset.
+ *
+ * Run over {@link NOTE_VOCABULARY} as this module loads, so a declaration that
+ * breaks the rule cannot be imported. That is stricter than a lint on purpose:
+ * a note's bad value is one author's mistake and belongs in a report, while a
+ * bad *declaration* would tell every author to write something unaddressable.
+ *
+ * @param {Readonly<Record<string, TypeVocabulary>>} vocabulary - The registry.
+ * @param {string} [where] - What declares it, for the message.
+ * @throws {Error} Naming every offending type and subType at once, rather than
+ *   stopping at the first — a reader fixing a list wants the whole list.
+ */
+export function assertVocabularyCharset(vocabulary, where = "the note vocabulary") {
+    const bad = [];
+    for (const [type, entry] of Object.entries(vocabulary ?? {})) {
+        if (!isAddressSegment(type)) bad.push(`type "${type}"`);
+        const values = entry?.subTypes;
+        if (!Array.isArray(values)) continue;
+        for (const value of values) {
+            if (!isAddressSegment(value)) bad.push(`subType "${value}" on ${type}`);
+        }
+    }
+    if (!bad.length) return;
+    throw new Error(
+        `${where} declares ${bad.join(", ")}, which ${bad.length === 1 ? "is" : "are"} ` +
+            `not ${ADDRESS_SEGMENT_PATTERN.source}. A type and a subType are both ` +
+            `address segments, and the hyphen separates segments rather than ` +
+            `occurring inside one.`,
+    );
+}
+
+assertVocabularyCharset(NOTE_VOCABULARY);
+
 /**
  * The `data:` keys a note type may carry.
  *

package/engine/retired-fields.mjs

@@ -22,9 +22,9 @@
  * says what to write instead rather than which value to correct.
  *
  * `package:` is retired the same way and is refused from `note-package.mjs`,
- * where the concept it belonged to still lives. `draft:` and the top-level
- * `aliases:` have no such home — there is no surviving concept either was part
- * of — so they are refused here.
+ * where the concept it belonged to still lives. `draft:`, the top-level
+ * `aliases:` and `section:` have no such home — there is no surviving concept
+ * any of them was part of — so they are refused here.
  *
  * **What `draft:` did (#69).** It excluded a note from the compiled packs, from
  * the link manifest and from a consuming site build. Nothing reported the
@@ -41,6 +41,13 @@
  * `name.full` and so decided what a note could be named (#179). The form and
  * the index are retired together, leaving the field with no reader at all.
  *
+ * **What `section:` did (#202).** It named the section a `collection` note
+ * headed, under the `collection` landing rule — its only reader anywhere. That
+ * rule is retired, a section being landed by the `README.md` in its directory,
+ * so the field has none. No schema or vocabulary ever declared it either, and
+ * nothing checks unrecognized top-level keys, so left in place it would be
+ * silently ignored rather than reported.
+ *
  * **`name.aliases` fed the same index and is nonetheless kept.** It is
  * **reserved** — held for a use that does not exist yet — so it is the one
  * field here that is neither retired nor read. Nothing consults it: no index,
@@ -216,6 +223,72 @@ export function declaresRetiredAliasesField(fm) {
     return Boolean(fm) && typeof fm === "object" && Object.hasOwn(fm, "aliases");
 }
 
+/**
+ * What a note declaring `section:` is told, in one place.
+ *
+ * Shared by the compile-time refusal and the frontmatter lint, because an
+ * author meets whichever of the two runs first and they should read the same.
+ * 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,
+ * 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
+ * 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
+ * place it would be ignored in silence — the note saying one thing and the
+ * build doing another.
+ *
+ * @param {string} [file] - The note's path, named in the message. Omit it where
+ *   the caller emits through a diagnostic, whose locator already starts the
+ *   line — repeating it prints the path twice.
+ * @returns {string} The message, unpunctuated at the end as a finding is.
+ */
+export function sectionRetiredMessage(file) {
+    return (
+        "`section:` is a retired frontmatter field — delete it" +
+        (file ? ` — ${file}` : "") +
+        ". It named the section a `collection` note headed, and both the rule " +
+        "and the sections it routed to are retired: a page that introduces " +
+        "the notes of a type is an ordinary note — `type: doc`, " +
+        "`subType: reference`, `shortcode: <type>` — addressed `doc-<type>`. " +
+        "Nothing else ever read the field"
+    );
+}
+
+/**
+ * Refuse a note that declares `section:` at all.
+ *
+ * Presence is the whole test, as it is for `draft:` and `aliases:`: an empty
+ * value reads as "this note heads a section and names none", a statement about
+ * a rule that no longer exists.
+ *
+ * @param {object|null|undefined} fm - Parsed frontmatter, or nothing when it
+ *   could not be parsed.
+ * @param {object} [options] - Options.
+ * @param {string} [options.file] - The note's path, named in the message. Omit
+ *   it where the caller emits through a diagnostic, which puts the locator at
+ *   the start of the line already — repeating it prints the path twice.
+ * @param {string} [options.absPath] - The note's file on disk, read only on the
+ *   failing path to locate the offending line and column. The position rides on
+ *   the thrown error as `position`, for a caller that emits a diagnostic.
+ * @returns {void}
+ * @throws {Error} When the note declares the field.
+ */
+export function assertNoSectionField(fm, { file, absPath } = {}) {
+    if (!fm || typeof fm !== "object" || !Object.hasOwn(fm, "section")) return;
+
+    const err = new Error(`${sectionRetiredMessage(file)}.`);
+    // Anchored at column 1: `site.trees[].section` is a *configuration* key of
+    // the same name, and a nested `section:` inside some other block is not
+    // this field — a finding about the top-level one must not open on it.
+    const position = locateFrontmatterKey(absPath, "section", undefined, { topLevel: true });
+    if (position) err.position = position;
+    throw err;
+}
+
 /**
  * A frontmatter key's position in a note's file, or nothing.
  *

package/engine/site-build.mjs

@@ -50,7 +50,7 @@ import { createRequire } from "node:module";
 import matter from "gray-matter";
 
 import { slugify } from "./content-slug.mjs";
-import { addressSlug, sectionOf } from "./content-address.mjs";
+import { addressSlug } from "./content-address.mjs";
 import { protectCode } from "./code-fences.mjs";
 import { expandContentTables } from "./content-tables.mjs";
 import { buildSiteIndex, wikiContext } from "./site-index.mjs";
@@ -132,11 +132,10 @@ function readNote(file) {
  * @returns {{pages: object[], addressFindings: object[], fmLinkFindings: object[]}}
  */
 export function collectContentPages(contentBase, ctx) {
-    // Where an addressed page publishes. The section below is guarded so a note
-    // is never "written to `undefined/`"; the same reasoning applies here, and a
-    // missing `base` would put *every* page there rather than one. It is the
-    // caller's contract rather than a note's defect, so it throws instead of
-    // being collected as a finding (#195).
+    // Where an addressed page publishes. A missing `base` would put *every*
+    // page at `undefined/` rather than one, and it is the caller's contract
+    // rather than a note's defect, so it throws instead of being collected as a
+    // finding (#195).
     if (typeof ctx.base !== "string" || !ctx.base) {
         throw new TypeError(
             "collectContentPages: `ctx.base` must be a non-empty string — it is the package address every page's URL is built on",
@@ -178,20 +177,6 @@ export function collectContentPages(contentBase, ctx) {
         }
 
         const base = path.basename(file);
-        const isReadme = base.toLowerCase() === "readme.md";
-        const sec = sectionOf(fm);
-        // A page's URL no longer contains its section, but the section is still
-        // what decides the directory the file is written to — and Hugo derives
-        // a page's section from that directory, not from its URL. So a note
-        // with none is still a note with nowhere to be published, and is
-        // reported rather than written to `undefined/`.
-        if (typeof sec !== "string" || !sec) {
-            addressFindings.push({
-                file,
-                reason: `type "${fm.type}" has no section, so there is nowhere to file the page`,
-            });
-            continue;
-        }
         const rel = path.relative(contentBase, file);
         pages.push({
             kind: "content",
@@ -218,15 +203,12 @@ export function collectContentPages(contentBase, ctx) {
             // The immediate source subfolder, the only surviving record of the
             // authoring folder, for grouped landings.
             folder: path.basename(path.dirname(file)),
-            sec,
-            // A landing page **is** its section, so it is addressed by the
-            // mount the section lives at; every other page is addressed by
-            // `(type, shortcode)` at the package root, which takes no mount
-            // (#181). The file is still written into `<sec>/` either way — see
-            // {@link pageDestination} — and the front matter carries this `url`
-            // so Hugo publishes it at its address rather than at its path.
-            url: isReadme ? `${ctx.mount}${sec}/` : `${ctx.base}${slug}/`,
-            isReadme,
+            // Every page is addressed by `(type, shortcode)` at the package
+            // root, which takes no content mount (#181). The file is written
+            // flat under the mount — see {@link pageDestination} — and the
+            // front matter carries this `url` so Hugo publishes it at its
+            // address rather than at its path.
+            url: `${ctx.base}${slug}/`,
         });
     }
     return { pages, addressFindings, fmLinkFindings };
@@ -557,12 +539,10 @@ export function sectionFrontmatter(meta) {
  * redirects of its own.
  *
  * A content page states its own **`url`**, which is its address rather than its
- * path (#181). Hugo would otherwise publish it where the file sits — under the
- * mount, inside its section directory — and the file sits there for a reason:
- * Hugo derives a page's section from its directory, which is what gives the
- * section its landing page, `.CurrentSection` and its per-section layout
- * lookup. So the directory stays and the address is stated, and the two are
- * free to differ.
+ * path (#181). It is written flat under the content mount (#204), 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.
  *
  * A content page carries the package the build **derived** (#65). No note
  * declares one — `package:` is retired (#56) — so the note's frontmatter alone
@@ -574,8 +554,12 @@ export function sectionFrontmatter(meta) {
  * self-describing and makes sweeping the field out of a content tree
  * output-preserving for a site as it already is for the packs.
  *
+ * A **tree** page is the one that still reads `readmeSections`: a `trees` entry
+ * keeps its source layout below a named section, so its own `README` is that
+ * section's landing and takes the title and hero the section declares.
+ *
  * @param {object} page - The page.
- * @param {object} options - `{ sections, readmeSections, decorate }`.
+ * @param {object} options - `{ readmeSections, decorate }`.
  * @returns {object} The frontmatter to write.
  */
 export function pageFrontmatter(page, { readmeSections = {}, decorate }) {
@@ -598,14 +582,6 @@ export function pageFrontmatter(page, { readmeSections = {}, decorate }) {
             kbfolder: page.folder,
         };
         if (decorate) decorate(data, page);
-        if (isReadme) {
-            const meta = readmeSections[sec];
-            // What the section says about itself wins over what its README
-            // happens to carry — the landing has to match the card linking to
-            // it. Assigned rather than transcribed key by key, so a section's
-            // vocabulary is decided in one place (#91).
-            if (meta) Object.assign(data, sectionFrontmatter(meta));
-        }
     } else {
         // A tree's own landing describes the *mount*, and nothing beneath it. A
         // nested README is a sub-section's landing, and reading the section's
@@ -623,23 +599,25 @@ export function pageFrontmatter(page, { readmeSections = {}, decorate }) {
 /**
  * Where a page is written, relative to the output root.
  *
- * **Into its section directory, which is not where it publishes** (#181). A
- * content page's URL is its address — `/<package>/<type>-<shortcode>/` — and it
- * is stated in the front matter; the file still goes to `<section>/`, because
- * Hugo reads a page's section from its path and nothing else. Flattening the
- * tree to match the URL would take the section landings, `.CurrentSection` and
- * every per-section layout with it.
+ * **Flat, under the mount, named by its address** (#204). 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
+ * 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.
+ *
+ * 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.
  *
- * The filename is the address rather than the section-relative half of it, so
- * two sections cannot fight over one file: a `doc` note routes by its `subType`,
- * which may be spelled the same as another note's `type`.
+ * **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,
+ * addressed by their path — so a `README` there is still its directory's
+ * `_index.md`.
  */
 export function pageDestination(page) {
-    if (page.kind === "content") {
-        return page.isReadme ?
-                path.join(page.sec, "_index.md")
-            :   path.join(page.sec, `${page.slug}.md`);
-    }
+    if (page.kind === "content") return `${page.slug}.md`;
     const rel =
         page.isReadme ? path.posix.join(path.posix.dirname(page.rel), "_index.md") : page.rel;
     return path.join(page.sec, rel);
@@ -681,7 +659,11 @@ export function renderPages(pages, options) {
     const byKind = {};
 
     for (const page of pages) {
-        const src = page.rel ?? `${page.sec}/${page.base}`;
+        // The page's path in the tree an author edits: below the content root
+        // for a content note, below the tree's own root for a `trees` page. It
+        // used to be composed as `<section>/<basename>` for a content note,
+        // which named a directory that was never the note's (#204).
+        const src = page.relPath ?? page.rel ?? page.base;
         const ctx = wikiContext(index, {
             src,
             file: page.file,
@@ -724,26 +706,43 @@ export function renderPages(pages, options) {
 }
 
 /**
- * Writes the section landings a published tree needs but no note supplies.
+ * Writes the Hugo sections a published tree declares.
+ *
+ * **This is where a section lives now, and the only place** (#204). 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
+ * listing its layout builds — says so here, in configuration, and this writes
+ * the `_index.md` that makes Hugo agree it is a section.
  *
- * Two separate jobs, and both exist because of how Hugo decides what a section
- * is:
+ * Three jobs, all of them Hugo's directory semantics rather than the note
+ * format's:
  *
+ * - **The mount's own landing**, so `/<package>/<prefix>` is a page rather than
+ *   a directory listing. It carries a `type` of its own: Hugo's template lookup
+ *   walks up a page's path, so an untyped landing template at the mount would
+ *   also serve every section below it that has none.
  * - **Declared sections** get a titled `_index.md` with their hero, so a landing
  *   matches the card that links to it instead of showing Hugo's auto-humanised
- *   directory name. The body is empty, which lets the theme list the section's
- *   children — or say it is empty, for a section whose content has not shipped.
- * - **Every other section directly under the mount** gets a bare `_index.md`,
+ *   directory name. The body is empty, which lets the theme decide what to list.
+ * - **Every other directory directly under the mount** gets a bare `_index.md`,
  *   or its own address publishes nothing. Hugo generates a section page
  *   automatically only for a *top-level* content directory; below that, a
- *   directory without an `_index.md` is not a section, so its URL 404s while
- *   its children publish normally. Mounting a tree one level down demotes every
- *   section it holds, and the ones with no landing of their own quietly stop
- *   existing while every page inside them keeps working.
+ *   directory without an `_index.md` is not a section, so its URL 404s while its
+ *   children publish normally. With content pages flat, what that reaches is a
+ *   `trees` entry's directory — the one thing left below the mount that a note
+ *   creates.
+ *
+ * **A section listing is not a page listing any more.** A layout that reads
+ * `.Pages` off a section it declares here will find nothing, because no file is
+ * filed into it; one that queries `site.RegularPages` by `Params.type` — which
+ * is how `sohl`'s eleven catalog layouts already work — is unaffected. That is a
+ * consumer's layout to choose, and it is stated here because the choice is no
+ * longer free.
  *
  * Scoped to one level on purpose. A directory further down was not a section
- * before the move either, and giving it one here would silently re-scope the
- * prev/next navigation of every page inside it.
+ * before either, and giving it one here would silently re-scope the prev/next
+ * navigation of every page inside it.
  *
  * @param {string} outRoot - The mount directory.
  * @param {object} options - `{ sections, landing, sectionTitle }`.
@@ -752,11 +751,6 @@ export function renderPages(pages, options) {
 export function writeSectionLandings(outRoot, { sections = {}, landing, sectionTitle }) {
     let written = 0;
 
-    // The mount's own landing carries a `type` of its own. Hugo's template
-    // lookup walks up a page's path, so a landing template at the mount would
-    // also serve every section below it that has no template of its own —
-    // each would render the mount's front page. Typing the landing moves its
-    // template out of the path where it could be inherited.
     if (landing) {
         fs.mkdirSync(outRoot, { recursive: true });
         fs.writeFileSync(path.join(outRoot, "_index.md"), matter.stringify("", landing));
@@ -1024,9 +1018,7 @@ export function buildSite({ config, outRoot } = {}) {
         name: page.fm.name?.full ?? homepageTitle(page.fm, resolved),
         slug: addressSlug(page.fm),
         base: path.basename(page.file),
-        sec: sectionOf(page.fm),
         url: `${base}${addressSlug(page.fm)}/`,
-        isReadme: false,
     }));
 
     const trees = site.trees.map((t) => ({

package/engine/site-index.mjs

@@ -65,10 +65,15 @@ import { isDraftNote } from "./note-vocabulary.mjs";
  * @property {object} fm     The note's frontmatter.
  * @property {string} name   Display name.
  * @property {string} slug   URL segment.
- * @property {string} sec    Section the page is filed under.
+ * @property {string} [sec]  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).
  * @property {string} base   Source file's basename, e.g. `Climbing.md`.
  * @property {string} url    The page's published address.
- * @property {boolean} isReadme  Whether the page is its section's landing.
+ * @property {boolean} [isReadme]  Whether a tree page is its directory's
+ *                           landing.
  */
 
 /**
@@ -169,13 +174,20 @@ export function buildSiteIndex(entries, { foreignIndex = new Map() } = {}) {
     const ownPackage = contentPackage();
     const packages = new Set(ownPackage ? [ownPackage] : []);
 
-    // `section/slug` is unique by construction. A page's name, filename and
-    // bare slug were indexed here too, as collision-aware fallbacks the bare
-    // `[[Name]]` form looked up; that form is retired and nothing consults
-    // them, so they are gone and with them the rule that two pages of a type
-    // may not share a name (#179, #180).
+    // `section/slug` is unique by construction, and is now a **tree** page's
+    // address: a `trees` entry keeps its source layout below a named section,
+    // so `dev-docs/testing` is how one is cited. A content page carries no
+    // section at all (#204) and is addressed by `(type, shortcode)` below —
+    // indexing it here as well would have written `weapongear/weapongear-dagger`,
+    // a key no author could reasonably write.
+    //
+    // A page's name, filename and bare slug were indexed here too, as
+    // collision-aware fallbacks the bare `[[Name]]` form looked up; that form is
+    // retired and nothing consults them, so they are gone and with them the rule
+    // that two pages of a type may not share a name (#179, #180).
     for (const e of entries) {
-        sections.add(String(e.sec).toLowerCase());
+        if (typeof e.sec !== "string" || !e.sec) continue;
+        sections.add(e.sec.toLowerCase());
         // `draft` rides on every key a page is addressable by, because a link
         // into a draft note renders marked whichever of them the author wrote
         // (#183). It decides nothing about resolution: the page is indexed and

package/engine/web-wikilinks.mjs

@@ -28,7 +28,7 @@
  * pack build together.
  *
  * The KB *section* is not always the type: prose pages (`type: doc`) route by
- * their `category`, so `doc/quickstart` lands on `/user-guide/sohl-quickstart/`.
+ * their `category`, so `doc/quickstart` lands on `/userguide/sohl-quickstart/`.
  * The caller supplies that mapping already resolved, in the index it builds.
  *
  * Lives here rather than in a consumer so every package resolves a link the

package/engine/wikilinks.mjs

@@ -36,7 +36,7 @@
  * Nothing narrower than `(type, shortcode)` is consulted — a note's directory
  * and its `category` play no part in resolution — and nothing wider: a note's
  * *name* is not an address, so two notes of a type may share a display name
- * ("Gear" as a rules page and as a user-guide page) with nothing to disambiguate
+ * ("Gear" as a rules page and as a user guide page) with nothing to disambiguate
  * (#179, #180).
  *
  * At compile time each becomes a Foundry UUID enricher, routed to the pack that

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@heroiclands/package-build",
-    "version": "11.0.0",
+    "version": "13.0.0",
     "description": "Shared toolchain for building and shipping a HeroicLands Foundry VTT package — content compilation, manifest, localization, staging, bundle, release and deployment.",
     "license": "GPL-3.0-or-later",
     "type": "module",