@heroiclands/package-build 22.15.1 → 22.17.0

package/docs/commands.md

@@ -1,16 +1,22 @@
+---
+shortcode: commands
+name: { full: "Command reference" }
+type: doc
+subType: reference
+---
+
 # Command reference
 
-`@heroiclands/package-build` ships two build binaries. `package-build` is the
-packaging half — clean, stage, check, package, deploy, run a Foundry
-container, drive the end-to-end suite. `content-build` is the content half —
-compile a note tree into compendium packs, check it, publish it as a site or a
-book, and manage the caches a build resolves other packages through.
+`@heroiclands/package-build` ships the `package-build` command. It checks and
+compiles content, builds sites and books, stages packages, writes manifests,
+and manages release and deployment tasks.
 
-Both read `package-build.config.yaml` from the repository root — see
-[Configuration](configuration.md) for every key. Neither reads it for
-`--version` or `--help`: those two answer in a directory with no
-configuration at all, and every other invocation resolves the configuration
-and fails loudly when it is missing or wrong.
+The commands read `package-build.config.yaml` from the repository root — see
+[Configuration](configuration.md) for every key. `--version` and `--help`
+work in a directory with no configuration. Commands that need a package
+resolve its configuration and report missing or invalid values.
+`package-build --help` lists every command; `package-build <command> --help`
+shows its actions and options.
 
 Each command below reads like a manual page: **NAME**, **SYNOPSIS**,
 **DESCRIPTION**, **OPTIONS**, **EXIT STATUS**, **EXAMPLES**, **SEE ALSO**, in
@@ -21,7 +27,7 @@ says so under **OPTIONS** rather than omitting the section.
 
 **Every finding is `file:line:column: severity: message`**, the path starting
 the line — the diagnostic contract this package's own build tooling emits and
-that both build binaries' content-side commands use for anything found in a
+that content commands use for anything found in a
 specific file. A field that cannot be known is dropped rather than guessed:
 `file:line:` when the column means nothing, `file:` when only the file is
 known. See [Diagnostics](diagnostics.md) for the full contract.
@@ -32,34 +38,24 @@ do. 1 is failure: a configuration error, a missing prerequisite, or findings
 that the command treats as errors. Each command's own **EXIT STATUS** states
 exactly what makes its run a 1.
 
-**`package-build` has one failure path for everything **`.fail()`** does not
-handle specially: every thrown error, from any command, is caught, printed as
-one line — `package-build: <message>`, or the bare diagnostic when the error
-already carries its own `file:line:column:` — and turned into exit code 1. A
-command that additionally emits findings of its own (`lang coverage`, `yaml`,
-`bundle check`, …) is called out below.**
-
-**`content-build` has no such umbrella.** Each command catches its own errors,
-logs them (prefixed `[timestamp] [LEVEL]:` for ordinary failures, unprefixed
-for a located diagnostic) and sets `process.exitCode = 1`; a command-line
-parse error — an unknown flag, a missing required option, an action outside
-its `choices` — is reported by yargs' own default handler and also exits 1.
-
-**Both binaries are `strict()` and `demandCommand(1, …)`.** An unknown
-command or option is refused rather than ignored, and running either with no
-command prints usage and exits 1 rather than silently doing nothing — the
-failure mode that let a typo in a build script pass the step it was meant to
-run. The one exception is `package-build e2e <action>`, which relaxes to
+Packaging handlers report a thrown error as `package-build: <message>`, or as
+the bare diagnostic when it already has a location. Content handlers report
+their own failures, with ordinary failures prefixed by loglevel and located
+diagnostics unprefixed. Both forms exit 1. A parse error from an unknown flag,
+missing option, or invalid action also exits 1.
+
+The command uses `strict()` and `demandCommand(1, …)`. An unknown
+command or option is refused rather than ignored, and running it with no
+command prints usage and exits 1. `package-build e2e <action>` relaxes to
 `.strict(false)` for everything after the action, because that belongs to the
 suite or the fast loop and this command line must not judge it.
 
-**`--help` / `-h` and `--version` are global, not per-command.** Both
-binaries register them once on their own top-level parser
-(`.version(ownVersion())`, `.help()`, `.alias("help", "h")`); no command below
-lists them among its own options.
+**`--help` / `-h` and `--version` are global.** The parser registers them
+once, and `--help` can be used with any command for its own actions and options.
+The command entries below list only their own options.
 
 **`PACKAGE_BUILD_CONFIG`** names the configuration file explicitly instead of
-the walk up from the working directory both binaries otherwise do — the only
+the walk up from the working directory the CLI otherwise does — the only
 environment variable the toolchain itself reads for configuration
 resolution. `deploy`, `container` and `e2e` additionally read `FOUNDRYVTT_*`,
 documented where each applies.
@@ -70,7 +66,139 @@ behaviour where they appear below; read the command, not the name.
 
 ---
 
-## `package-build`
+## Package and release operations
+
+### `package-build ci`
+
+**NAME**
+
+Replay the commands from pull-request workflows.
+
+**SYNOPSIS**
+
+```text
+package-build ci [--native]
+```
+
+**DESCRIPTION**
+
+The default command runs in Docker on Linux against a clean export of the
+current commit. It reads the repository's pull-request workflows under
+`.github/workflows/` and runs their `run:` steps in workflow order. A failed
+step stops the replay. Uncommitted changes are absent from the clean export.
+
+`--native` runs the same steps on the host in the current working tree. It
+needs no Docker and includes uncommitted changes, but its operating system and
+existing files can differ from a clean GitHub runner. The steps themselves
+still come from the workflow files.
+
+The command lists `uses:` steps that it cannot run locally. A successful replay
+covers the listed `run:` steps; GitHub runs the published actions separately.
+Workflow steps may install dependencies, generate files, or perform other
+declared build actions.
+
+**OPTIONS**
+
+| Option     | Type    | Default | Description                                  |
+| ---------- | ------- | ------- | -------------------------------------------- |
+| `--native` | boolean | false   | Run on the host in the current working tree. |
+
+**EXIT STATUS**
+
+0 when every runnable step succeeds. 1 when a step fails, no pull-request
+workflow supplies runnable steps, Docker is unavailable for the default mode,
+or the replay cannot start.
+
+**EXAMPLES**
+
+```bash
+package-build ci
+package-build ci --native
+```
+
+**SEE ALSO**
+
+[End-to-end testing](guides/e2e.md), [Project setup](project-setup.md).
+
+### `package-build init [directory]`
+
+**NAME**
+
+Create a HeroicLands content package or check an existing one.
+
+**SYNOPSIS**
+
+```text
+package-build init [directory] [--kind <kind>] [--name <name>] [--title <title>] [--description <description>] [--author <author>] [--license <license>] [--core-minimum <version>] [--core-verified <version>]
+package-build init --check [directory]
+```
+
+**DESCRIPTION**
+
+The directory defaults to the current directory. If it does not exist, `init`
+creates it. The directory needs no Git repository, `package.json`, or local
+installation of package-build. It may contain unrelated files, but `init`
+refuses a package-build configuration or any file it would overwrite. It
+generates a homepage, introduction, package metadata, content configuration,
+book document tree, website and book scripts, formatting rules, changeset
+configuration, label registry, and build workflow. It does not install
+dependencies, initialize Git, or deploy a site.
+
+`--check` reads the named directory and reports missing or invalid project
+requirements without writing anything. It accepts existing files with valid
+custom content and scripts; they need not be identical to the scaffold.
+
+Without a terminal, the identity and license arguments must be supplied. At a
+terminal, missing values are prompted. The package name defaults to the target
+directory's basename and determines the content package id by removing hyphens.
+The package kind defaults to `modules`; the license template defaults to
+`original`. `systems` and `modules` receive a journal pack and Foundry
+manifest configuration. `documentation` receives no Foundry pack or manifest.
+Every kind includes site and book targets. Hugo Extended and Typst are needed
+to render them locally; deployment needs separate hosting configuration.
+
+**OPTIONS**
+
+| Option            | Type                                     | Default                   | Description                                               |
+| ----------------- | ---------------------------------------- | ------------------------- | --------------------------------------------------------- |
+| `directory`       | path                                     | current directory         | New or existing target directory.                         |
+| `--check`         | boolean                                  | `false`                   | Inspect an existing package without writing.              |
+| `--kind`          | `systems`, `modules`, or `documentation` | `modules`                 | Package kind.                                             |
+| `--name`          | string                                   | target directory basename | npm and Foundry package name.                             |
+| `--title`         | string                                   | words of the package name | Reader-facing title.                                      |
+| `--description`   | string                                   | —                         | Package and website description.                          |
+| `--author`        | string                                   | —                         | Author credited in the package.                           |
+| `--license`       | `original` or `fan`                      | `original`                | License template for original or unofficial fan material. |
+| `--core-minimum`  | string                                   | `14.359`                  | Minimum Foundry core version for a Foundry package.       |
+| `--core-verified` | string                                   | `14.364`                  | Verified Foundry core version for a Foundry package.      |
+
+**EXIT STATUS**
+
+0 when the package is created or passes `--check`. 1 when required answers are
+missing, the target conflicts with an existing project file, a generated file
+cannot be written, or `--check` finds an unmet requirement. A failed write
+removes the files created by that invocation.
+
+**EXAMPLES**
+
+```bash
+npm exec --package=@heroiclands/package-build -- package-build init acme-bestiary --kind modules --name acme-bestiary --title "Acme Bestiary" --description "Creatures of the reed flats." --author "Acme" --license original
+cd acme-bestiary
+npm install
+npm run lint
+npm run build:site
+npm run serve:site
+npm run build:book
+package-build init --check
+```
+
+For a global installation, run `npm install --global
+@heroiclands/package-build` once and then `package-build init [directory]`.
+
+**SEE ALSO**
+
+[Getting started](getting-started.md), [Project setup](project-setup.md),
+[Configuration](configuration.md).
 
 ### `package-build clean`
 
@@ -113,6 +241,43 @@ Nothing to clean.
 
 [Configuration](configuration.md).
 
+### `package-build stage reset`
+
+**NAME**
+
+Clear the assembled Foundry package stage before a complete build.
+
+**SYNOPSIS**
+
+```
+package-build stage reset
+```
+
+**DESCRIPTION**
+
+The `reset` action removes `packageBuild.stageDir` without removing the content index, PDF, site,
+or other build outputs. Run it once before the commands that write assets, packs,
+bundles, and the manifest. It succeeds when the stage is already empty.
+
+**OPTIONS**
+
+There are no options.
+
+**EXIT STATUS**
+
+1 on an invalid configuration or a stage directory outside the project. Otherwise 0.
+
+**EXAMPLES**
+
+```
+$ package-build stage reset
+Removed build/stage
+```
+
+**SEE ALSO**
+
+[Project setup](project-setup.md), [Configuration](configuration.md).
+
 ### `package-build assets`
 
 **NAME**
@@ -176,7 +341,7 @@ Reads the package's current JSONL content index and writes
 `build/calendars/<shortcode>.calendaria.json` for each calendar note. The
 import file contains the same definition and a fixed `exportedAt` sentinel,
 making both files reproducible. A package with no calendars gets an empty
-`build/calendars/` directory. Run `content-build content-index` after changing
+`build/calendars/` directory. Run `package-build content-index` after changing
 notes and before this command. Stage the generated directory with
 `packageBuild.assets` when the Foundry package should ship it.
 
@@ -199,7 +364,90 @@ $ package-build calendars --calendaria-version 1.4.2
 
 **SEE ALSO**
 
-`content-build content-index`, [Getting started](getting-started.md).
+`package-build content-index`, [Getting started](getting-started.md).
+
+### `package-build datefrom`
+
+**NAME**
+
+Convert a day in an authored calendar to a canonical date.
+
+**SYNOPSIS**
+
+```
+package-build datefrom <calendar> <date>
+```
+
+**DESCRIPTION**
+
+Reads the current content tree, resolves its world year and calendar eras, and
+prints `<year>.<day>[:HHMMSS]` to standard output. `<calendar>` is a calendar
+shortcode, full Address, or addressed era. The date follows the calendar's
+`data.formats.std` pattern, or its first named pattern when `std` is absent.
+For example, `MM/DD/Y GGG` reads `04/23/326 VR`. An era-relative year written
+with `[yearInEra]` must identify its era. A date must specify a day;
+year-only and month-only dates do not identify one canonical day.
+Prefix the date with `~` to preserve an approximate value.
+
+**OPTIONS**
+
+None.
+
+**EXIT STATUS**
+
+1 if the content tree or calendar is invalid, the era is missing or mismatched,
+or the date cannot be resolved to one day. Otherwise 0.
+
+**EXAMPLES**
+
+```
+$ package-build datefrom vrcal '23 Taranis 326 VR'
+326.114
+```
+
+**SEE ALSO**
+
+`package-build dateto`, [Content format](content-format.md).
+
+### `package-build dateto`
+
+**NAME**
+
+Express a canonical day in an authored calendar.
+
+**SYNOPSIS**
+
+```
+package-build dateto <calendar> <canonical-date> [--format <name>]
+```
+
+**DESCRIPTION**
+
+Reads the current content tree, selects the era covering the canonical day, and
+prints the date using `data.formats.std`, or the first named pattern if `std`
+is absent. The input is
+`<year>.<day>[:HHMMSS]`, optionally prefixed with `~`. A date in a gap between
+eras has no conversion.
+
+**OPTIONS**
+
+`--format` selects another named pattern from the calendar note; pass its name as the value.
+
+**EXIT STATUS**
+
+1 if the content tree or calendar is invalid, the canonical date is invalid,
+or no era covers that day. Otherwise 0.
+
+**EXAMPLES**
+
+```
+$ package-build dateto vrcal 326.114
+23 Taranis 326 VR
+```
+
+**SEE ALSO**
+
+`package-build datefrom`, [Content format](content-format.md).
 
 ### `package-build schema`
 
@@ -216,13 +464,13 @@ package-build schema
 **DESCRIPTION**
 
 Publishes the registries named in `packageBuild.schema` as `schema.json`, read
-by `content-build content-format schema` and, in a consuming package, by
-`content-build lint`'s emitted-versus-declared check. A repository that
+by `package-build content-format schema` and, in a consuming package, by
+`package-build lint`'s emitted-versus-declared check. A repository that
 declares no registries has nothing to publish. Reads the registries
 `packageBuild.schema` names; writes `build/schema.json`. A release publishes
 it beside the archive and the manifest when `packageBuild.assets` names
 `build/schema.json` (see `package-build release`); a module's
-`content-build deps fetch` keeps the copy from the archive it downloads.
+`package-build deps fetch` keeps the copy from the archive it downloads.
 
 **OPTIONS**
 
@@ -242,7 +490,7 @@ package-build: no `packageBuild.schema` declared; nothing to publish.
 
 **SEE ALSO**
 
-`content-build content-format schema`, `content-build lint [root]`,
+`package-build content-format schema`, `package-build lint [root]`,
 `package-build release`, [Configuration](configuration.md).
 
 ### `package-build manifest`
@@ -268,12 +516,14 @@ in `packageBuild.manifestFlags` for a flag the repository has to compute
 itself — the compendium address of a document that exists only once the
 content tree has been walked. Reads the shared pack configuration and
 `package.json`; writes the manifest into `packageBuild.stageDir`.
+`packageBuild.manifest.title` must be a non-empty string, so the staged
+manifest carries the title Foundry requires for installation.
 
 **Refused for `packageKind: documentation`.** A manifest is the file Foundry
 reads to install a package, and a documentation package is not one —
 emitting `module.json` for it would advertise an installable package with no
 packs, no compatibility range and no id. Its site is built by
-`content-build site`, and its book by `content-build pdf`.
+`package-build site`, and its book by `package-build pdf`.
 
 **OPTIONS**
 
@@ -284,7 +534,8 @@ None.
 1 for `packageKind: documentation`. 1 if `packageBuild.manifestFlags` is
 declared but cannot be loaded, or exports no `flags` function. 1 on any other
 thrown error (a manifest key the configuration cannot supply —
-`package.json` naming no `repository.url`, for instance). Otherwise 0.
+`package.json` naming no `repository.url`, or a missing or blank
+`packageBuild.manifest.title`, for instance). Otherwise 0.
 
 **EXAMPLES**
 
@@ -293,12 +544,12 @@ $ package-build manifest
 ✅ Wrote build/stage/module.json (10 keys, 2 packs).
 
 $ package-build manifest   # packageKind: documentation
-package-build: `packageKind: documentation` ships no Foundry package, so there is no manifest to generate. The site and the book are built by `content-build`.
+package-build: `packageKind: documentation` ships no Foundry package, so there is no manifest to generate. The site and the book are built by `package-build`.
 ```
 
 **SEE ALSO**
 
-`content-build site`, `content-build pdf`, `package-build bundle check`,
+`package-build site`, `package-build pdf`, `package-build bundle check`,
 [Configuration](configuration.md).
 
 ### `package-build site-root`
@@ -388,7 +639,7 @@ Search is off (`site.search: false`), so no index was written.
 
 **SEE ALSO**
 
-`content-build site`, [Configuration](configuration.md).
+`package-build site`, [Configuration](configuration.md).
 
 `package-build lang <action>` asks three independent questions about this
 repository's localization, each blind to what the others see: `check`,
@@ -721,7 +972,9 @@ from the heading rule, since neither is authored.
 A token that reads as code — `camelCase()`, a `path/with/slashes.ext`,
 `SCREAMING_SNAKE` — outside any code span is a warning, not a failure: a
 user-facing note sometimes needs one (`Compendium.hm3.items.Item.<id>`), but
-rarely. A block's bold label absent from a declared `changelog.labels` is
+rarely. Accented letters keep proper names such as HârnMaster whole, so a
+fragment of one does not trigger a code-token warning. A block's bold label
+absent from a declared `changelog.labels` is
 also a warning — the drift `**Character data**` beside `**Characters**`
 produces — and checks nothing when the repository declares no
 `changelog.labels`. Every other finding is an error. Reads the files given,
@@ -885,8 +1138,8 @@ states it a second time. It also publishes the content index the manifest
 advertises (`flags.metadataUrl`) and, when the stage carries one,
 `schema.json` — a repository that names `build/schema.json` in
 `packageBuild.assets` gets it released beside the archive; one that does not
-gets none. When the package publishes content (`publish.site: content`), it
-also builds the content-tree book (see `content-build pdf`) and reports it
+gets none. When the content tree holds notes beyond its homepage, it
+also builds the content-tree book (see `package-build pdf`) and reports it
 alongside the archive; `--no-pdf` skips that step for a release that has a
 tree but does not want the book this time. A book that fails to build is
 reported, never fatal — the archive above is the release regardless. Reads
@@ -910,12 +1163,12 @@ are reported on stderr but do not fail the release.
 ```
 $ package-build release
 ✅ Packaged 1.0.0 for release: build/dist/module.zip (0.0 MB)
-   No book: `publish.site` is `homepage`, which fences the content surfaces off — the tree is not walked and no book is built. Publish content to build one.
+   No book: The content tree contains only a homepage, so there is no book to build.
 ```
 
 **SEE ALSO**
 
-`content-build pdf`, `package-build schema`, [Configuration](configuration.md).
+`package-build pdf`, `package-build schema`, [Configuration](configuration.md).
 
 ### `package-build deploy <stage>`
 
@@ -1107,9 +1360,9 @@ package-build: This repository declares no end-to-end suite to `run`. Name one u
 
 ---
 
-## `content-build`
+## Content operations
 
-### `content-build package <action> [pack] [entry]`
+### `package-build package <action> [pack] [entry]`
 
 **NAME**
 
@@ -1119,9 +1372,9 @@ process.
 **SYNOPSIS**
 
 ```
-content-build package compile [pack]
-content-build package unpack [pack] [entry]
-content-build package clean [pack] [entry]
+package-build package compile [pack]
+package-build package unpack [pack] [entry]
+package-build package clean [pack] [entry]
 ```
 
 **DESCRIPTION**
@@ -1141,8 +1394,8 @@ the staged LevelDB packs.
 `unpack` and `clean` alike. A package of that kind declares no packs by
 rule, so there is nothing to compile, unpack or clean; a run that exited 0
 having done nothing would be the quiet failure this toolchain refuses
-everywhere else. Its site is built by `content-build site`, and its book by
-`content-build pdf`.
+everywhere else. Its site is built by `package-build site`, and its book by
+`package-build pdf`.
 
 **OPTIONS**
 
@@ -1163,10 +1416,10 @@ step to report against. 1 on any other thrown error. Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build package compile   # packageKind: documentation
-[…] ERROR: `packageKind: documentation` compiles no compendium, so there is nothing to compile. Build its site with `content-build site` and its book with `content-build pdf`.
+$ package-build package compile   # packageKind: documentation
+[…] ERROR: `packageKind: documentation` compiles no compendium, so there is nothing to compile. Build its site with `package-build site` and its book with `package-build pdf`.
 
-$ content-build package compile
+$ package-build package compile
 […] Content tree: 4 note(s) at /private/tmp/pb-docs-demo-410/assets/content
 […] Pack items: /private/tmp/pb-docs-demo-410/assets/content → …/build/packs-json/items
 […] Compiled 0 items:
@@ -1176,7 +1429,7 @@ $ content-build package compile
 […] Pack journals: compiling to LevelDB at …/build/stage/packs/journals
 […] Pack compilation complete.
 
-$ content-build package unpack
+$ package-build package unpack
 […] Extracting pack items
 […] Extracting pack journals
 Wrote welcome.json
@@ -1184,10 +1437,10 @@ Wrote welcome.json
 
 **SEE ALSO**
 
-`content-build site`, `content-build pdf`, `content-build addresses diff`,
+`package-build site`, `package-build pdf`, `package-build addresses diff`,
 [Diagnostics](diagnostics.md), [Configuration](configuration.md).
 
-### `content-build deps fetch`
+### `package-build deps fetch`
 
 **NAME**
 
@@ -1196,7 +1449,7 @@ Fill the caches a build resolves other packages through.
 **SYNOPSIS**
 
 ```
-content-build deps fetch [--from <zip|dir>] [--id <id>]
+package-build deps fetch [--from <zip|dir>] [--id <id>]
 ```
 
 **DESCRIPTION**
@@ -1212,6 +1465,12 @@ is not reproducible and hides a dependency's version change behind a
 passing run. Each cache is stamped complete only once its fetch finishes,
 so a half-finished one reads as cold.
 
+`lint`, `links`, `site`, `pdf`, `map`, `reachability`, and `package compile`
+check the declared dependencies' content-index cache before reading notes or
+writing output. A cold cache produces a diagnostic at the package configuration
+file naming `deps fetch`. These checks only read local files; `deps fetch` is
+the separate step that reaches the network.
+
 The navigation is fetched first, because every package needs it and it
 depends on nothing a repository declares — so a dependency whose release
 cannot be read stops the run with the navigation already cached.
@@ -1240,20 +1499,140 @@ including when the repository declares no dependencies at all.
 **EXAMPLES**
 
 ```
-$ content-build deps fetch
+$ package-build deps fetch
 […] Fetched the site navigation to build/cache/navigation/nav.json.
 […] No relationship declares `itemCatalog: true`; nothing to fetch.
 […] This package declares no dependencies.
 
-$ content-build deps fetch --from build/dist/module.zip
+$ package-build deps fetch --from build/dist/module.zip
 […] ERROR: --from needs --id when a package declares several dependencies (declared: none)
 ```
 
 **SEE ALSO**
 
-`content-build site`, `content-build addresses diff`, [Configuration](configuration.md).
+`package-build site`, `package-build addresses diff`, [Configuration](configuration.md).
+
+### `package-build types check`
+
+**NAME**
+
+Check project declarations.
+
+**SYNOPSIS**
+
+```sh
+package-build types check [--project <tsconfig>] [--exports]
+```
+
+**DESCRIPTION**
+
+Check a TypeScript project's declarations with library checking enabled. The
+default `--project` is `tsconfig.json`. Diagnostics in `node_modules` are
+excluded; diagnostics in project files name the file, line, and column.
+`--exports` also checks every declaration entry point advertised by
+`package.json` `exports`, including wildcard subpaths. Run it after generating
+declarations.
+
+**OPTIONS**
+
+| Option      | Default         | Meaning                                     |
+| ----------- | --------------- | ------------------------------------------- |
+| `--project` | `tsconfig.json` | TypeScript project file.                    |
+| `--exports` | off             | Include published declaration entry points. |
+
+**EXIT STATUS**
+
+1 when a project declaration fails to type-check or an exported entry point is
+missing; otherwise 0.
+
+**EXAMPLES**
+
+```sh
+package-build types check --project tsconfig.json
+```
+
+**SEE ALSO**
+
+`package-build docs links`.
+
+### `package-build docs links`
+
+**NAME**
+
+Check documentation links.
+
+**SYNOPSIS**
+
+```sh
+package-build docs links [--root <dir>]
+```
+
+**DESCRIPTION**
+
+Check relative Markdown links and heading anchors in a documentation tree.
+Code fences and code spans are ignored. The default root is `docs`; use
+`--root <dir>` for another tree. Missing targets and anchors are reported at
+the link's file, line, and column.
+
+**OPTIONS**
+
+| Option   | Default | Meaning             |
+| -------- | ------- | ------------------- |
+| `--root` | `docs`  | Documentation root. |
+
+**EXIT STATUS**
+
+1 when a link or anchor fails to resolve; otherwise 0.
+
+**EXAMPLES**
+
+```sh
+package-build docs links --root docs
+```
+
+**SEE ALSO**
+
+`package-build docs index`.
 
-### `content-build docs item-fields`
+### `package-build docs index`
+
+**NAME**
+
+Check documentation index coverage.
+
+**SYNOPSIS**
+
+```sh
+package-build docs index [--root <dir>]
+```
+
+**DESCRIPTION**
+
+Check that every Markdown page immediately inside each section directory is
+linked from the documentation root's `README.md`. The default root is `docs`;
+use `--root <dir>` for another tree. Each unlinked page is reported by path.
+
+**OPTIONS**
+
+| Option   | Default | Meaning             |
+| -------- | ------- | ------------------- |
+| `--root` | `docs`  | Documentation root. |
+
+**EXIT STATUS**
+
+1 when a page is not indexed; otherwise 0.
+
+**EXAMPLES**
+
+```sh
+package-build docs index --root docs
+```
+
+**SEE ALSO**
+
+`package-build docs links`.
+
+### `package-build docs item-fields`
 
 **NAME**
 
@@ -1262,7 +1641,7 @@ Render this repository's item-frontmatter reference.
 **SYNOPSIS**
 
 ```
-content-build docs item-fields [--out <path>] [--check] [--title <title>]
+package-build docs item-fields [--out <path>] [--check] [--title <title>]
 ```
 
 **DESCRIPTION**
@@ -1303,15 +1682,16 @@ body alone, with no frontmatter, exactly as before.
 
 **OPTIONS**
 
-| Positional | Type                         | Default | Description             |
-| ---------- | ---------------------------- | ------- | ----------------------- |
-| `action`   | string, one of `item-fields` | —       | The document to render. |
+| Positional | Type                                           | Default | Description               |
+| ---------- | ---------------------------------------------- | ------- | ------------------------- |
+| `action`   | string, one of `item-fields`, `links`, `index` | —       | The documentation action. |
 
 | Option    | Type    | Default                 | Description                                            |
 | --------- | ------- | ----------------------- | ------------------------------------------------------ |
 | `--out`   | string  | `docs.itemFields.out`   | Write to this file instead of the configured location. |
 | `--check` | boolean | `false`                 | Compare against the file already there; write nothing. |
 | `--title` | string  | `docs.itemFields.title` | The page's H1.                                         |
+| `--root`  | string  | `docs`                  | Documentation root for `links` and `index`.            |
 
 **EXIT STATUS**
 
@@ -1321,10 +1701,10 @@ body alone, with no frontmatter, exactly as before.
 **EXAMPLES**
 
 ```
-$ content-build docs item-fields --out docs/item-fields.md --title "Demo Item Fields"
+$ package-build docs item-fields --out docs/item-fields.md --title "Demo Item Fields"
 […] Wrote docs/item-fields.md
 
-$ content-build docs item-fields --out docs/item-fields.md --title "Demo Item Fields" --check
+$ package-build docs item-fields --out docs/item-fields.md --title "Demo Item Fields" --check
 […] docs/item-fields.md is up to date.
 ```
 
@@ -1332,7 +1712,96 @@ $ content-build docs item-fields --out docs/item-fields.md --title "Demo Item Fi
 
 [Configuration](configuration.md).
 
-### `content-build lint [root]`
+### `package-build prose lint [path]`
+
+**NAME**
+
+Analyze note prose for readability and simpler wording.
+
+**SYNOPSIS**
+
+```text
+package-build prose lint [path] [--age <years>] [--threshold <count>] [--min-words <count>]
+```
+
+**DESCRIPTION**
+
+Run this command from the package root to review the readable prose in one
+Markdown note or a content tree. Pass a note path while editing that note;
+omit it to review the configured `paths.content` tree. A directory path scans
+its Markdown files recursively and honors `skipDirectories`. A file path
+analyzes that file alone, even if it sits in an excluded directory. The command
+reads source files and writes nothing. It is an optional editorial check:
+`package-build lint` and the normal lint scripts do not run it.
+
+Set defaults in `package-build.config.yaml` under `packageBuild.proseLint`:
+
+```yaml
+packageBuild:
+  proseLint: { age: 21, threshold: 5, minWords: 8 }
+```
+
+No configuration is required; the values above are the defaults. `age` is the
+intended reader's age in years. `threshold` is the number of seven readability
+algorithms that must classify a sentence as difficult before it is reported.
+For example, a threshold of 5 reports a sentence if five or more algorithms
+flag it; a threshold of 7 reports only unanimous findings. `minWords` excludes
+shorter sentences from readability analysis. Each setting is a positive integer,
+and `threshold` must be at most 7. CLI options override individual settings:
+`--min-words` overrides `minWords`, while `--age` and `--threshold` override
+their matching keys.
+
+The command analyzes Markdown prose with `retext-english`,
+`retext-readability`, and `retext-simplify`; `retext-stringify` completes the
+text pipeline. YAML frontmatter, code blocks, wikilink addresses, and inline
+expressions are excluded. Each suggestion is a warning with a file, line,
+column, rule ID, confidence, offending sentence, and `expected` replacement
+list. The source location marks the difficult sentence or the specific phrase
+that could be simplified. Readability confidence is the number of algorithms
+that found the sentence difficult, out of seven. Simplify suggestions have no
+numeric confidence score, so they say `unscored`. `expected` lists suggested
+replacements; `[]` means the rule offers no replacement and may recommend
+deleting a word or rewriting a sentence. Suggestions are advisory, are never
+applied automatically, and do not make the command fail. Unreadable paths and
+invalid options do.
+
+**OPTIONS**
+
+| Input         | Default                    | Meaning                                  |
+| ------------- | -------------------------- | ---------------------------------------- |
+| `path`        | configured `paths.content` | Markdown file or content tree            |
+| `--age`       | 21                         | Reader age in years                      |
+| `--threshold` | 5                          | Number of readability algorithms (1–7)   |
+| `--min-words` | 8                          | Minimum words for readability assessment |
+
+**EXIT STATUS**
+
+0 after reporting suggestions; 1 for invalid options or unreadable paths.
+
+**EXAMPLES**
+
+```bash
+package-build prose lint assets/content/Lore/Harbor.md
+package-build prose lint
+package-build prose lint assets/content --age 18 --threshold 6 --min-words 10
+```
+
+For a note whose fifth line says `The utilization is very high.`, the command
+can report:
+
+```text
+assets/content/Lore/Harbor.md:5:5: warning: retext-simplify/utilization: confidence=unscored; sentence="The utilization is very high."; expected=["use"]; Unexpected `utilization`, use `use` instead
+```
+
+Open the file at line 5, column 5, and decide whether `use` suits the context.
+The rule ID identifies the suggestion if you need to search or group results.
+
+**SEE ALSO**
+
+[`package-build lint`](#package-build-lint-root),
+[Configuration](configuration.md#packagebuildproselint).
+
+### `package-build lint [root]`
 
 **NAME**
 
@@ -1341,7 +1810,7 @@ Check a content tree's addresses and frontmatter without compiling it.
 **SYNOPSIS**
 
 ```
-content-build lint [root] [--no-references]
+package-build lint [root] [--no-references]
 ```
 
 **DESCRIPTION**
@@ -1377,27 +1846,27 @@ itself could not be built for any note. Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build lint
+$ package-build lint
 […] No `itemBuilders` registry declares the vocabulary of `demo`, so that system's block is unchecked — a key inside one is discarded at compile with no warning. Declare `itemBuilders: [demo]`.
-[…] No published schema for demo@1.0.0, so emitted `system` fields are unchecked. A system generates its own; a module gets one from `content-build deps fetch`.
+[…] No published schema for demo@1.0.0, so emitted `system` fields are unchecked. A system generates its own; a module gets one from `package-build deps fetch`.
 […] Addresses and frontmatter are well-formed (4 address(es) across 4 note(s)).
 ```
 
 **SEE ALSO**
 
-`content-build links [root]`, `content-build reachability <dir> [file]`,
-`content-build content-format schema`, `content-build content-format fields`,
-`content-build content-format notes`, [Diagnostics](diagnostics.md),
+`package-build links [root]`, `package-build reachability <dir> [file]`,
+`package-build content-format schema`, `package-build content-format fields`,
+`package-build content-format notes`, [Diagnostics](diagnostics.md),
 [Configuration](configuration.md).
 
-`content-build content-format <action>` checks `docs/content-format.md` —
+`package-build content-format <action>` checks `docs/content-format.md` —
 the content-format specification this package ships — against reality, in
 three ways that fail for different reasons at different times: `schema`,
 `fields` and `notes`, one section below per action. All three read the
 specification named by `--spec`, defaulting to the one this package ships,
 and write nothing.
 
-### `content-build content-format schema`
+### `package-build content-format schema`
 
 **NAME**
 
@@ -1406,7 +1875,7 @@ Compare the content-format specification against a published schema.
 **SYNOPSIS**
 
 ```
-content-build content-format schema --schema <system>=<path> [--schema <system>=<path> ...] [--spec <path>]
+package-build content-format schema --schema <system>=<path> [--schema <system>=<path> ...] [--spec <path>]
 ```
 
 **DESCRIPTION**
@@ -1419,10 +1888,10 @@ like one that passed.
 
 **OPTIONS**
 
-| Option     | Type                         | Default                              | Description                               |
-| ---------- | ---------------------------- | ------------------------------------ | ----------------------------------------- |
-| `--spec`   | string                       | the shipped `docs/content-format.md` | The specification to read.                |
-| `--schema` | string, repeatable, required | —                                    | A published schema, as `<system>=<path>`. |
+| Option     | Type                         | Default                                  | Description                               |
+| ---------- | ---------------------------- | ---------------------------------------- | ----------------------------------------- |
+| `--spec`   | string                       | the shipped `engine/content-format.yaml` | The specification to read.                |
+| `--schema` | string, repeatable, required | —                                        | A published schema, as `<system>=<path>`. |
 
 **EXIT STATUS**
 
@@ -1432,17 +1901,17 @@ like one that passed.
 **EXAMPLES**
 
 ```
-$ content-build content-format schema --schema sohl=schema.json
+$ package-build content-format schema --schema sohl=schema.json
 […] 19 claim(s) about hm3 are unchecked — no schema was supplied for it, so nothing here confirms them.
 […] 76 mapping claim(s) confirmed against the supplied schemas.
 ```
 
 **SEE ALSO**
 
-`content-build content-format fields`, `content-build content-format notes`,
+`package-build content-format fields`, `package-build content-format notes`,
 `package-build schema`, [Configuration](configuration.md).
 
-### `content-build content-format fields`
+### `package-build content-format fields`
 
 **NAME**
 
@@ -1452,7 +1921,7 @@ declarations.
 **SYNOPSIS**
 
 ```
-content-build content-format fields [--fields <system>] [--coverage] [--spec <path>]
+package-build content-format fields [--fields <system>] [--coverage] [--spec <path>]
 ```
 
 **DESCRIPTION**
@@ -1474,7 +1943,7 @@ vocabularies differ by design until a note's data fully moves under `data:`.
 
 | Option       | Type                         | Default                                       | Description                                         |
 | ------------ | ---------------------------- | --------------------------------------------- | --------------------------------------------------- |
-| `--spec`     | string                       | the shipped `docs/content-format.md`          | The specification to read.                          |
+| `--spec`     | string                       | the shipped `engine/content-format.yaml`      | The specification to read.                          |
 | `--fields`   | string, one of `sohl`, `hm3` | the consuming repository's own `itemBuilders` | A declaration set this package ships, by system id. |
 | `--coverage` | boolean                      | `false`                                       | List, per type, the fields only one side names.     |
 
@@ -1486,7 +1955,7 @@ declaration that compiles it. Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build content-format fields --fields sohl --coverage
+$ package-build content-format fields --fields sohl --coverage
 […] 13 type(s) compared against sohl's declarations (56 field pair(s)).
 […] 12 type(s) the format declares are out of reach — no `itemBuilders` entry covers them: being, homepage, vehicle, armorlocation, lore, map, place, scenario, doc, macro, bundle, folder.
 […] affiliation: format only [demonym, economy, epithet, governance, lore, population, symbol, templatePriority], declaration only [commonSkills, level, office, society, subType, title]
@@ -1494,10 +1963,10 @@ $ content-build content-format fields --fields sohl --coverage
 
 **SEE ALSO**
 
-`content-build content-format schema`, `content-build content-format notes`,
+`package-build content-format schema`, `package-build content-format notes`,
 [Configuration](configuration.md).
 
-### `content-build content-format notes`
+### `package-build content-format notes`
 
 **NAME**
 
@@ -1506,7 +1975,7 @@ Measure a content tree against the specification's vocabulary.
 **SYNOPSIS**
 
 ```
-content-build content-format notes [root] [--strict] [--spec <path>]
+package-build content-format notes [root] [--strict] [--spec <path>]
 ```
 
 **DESCRIPTION**
@@ -1524,10 +1993,10 @@ class of finding reaches zero.
 | ---------- | ------ | ------------------------------ | ------------------------ |
 | `root`     | string | the configured `paths.content` | Content tree to measure. |
 
-| Option     | Type    | Default                              | Description                                          |
-| ---------- | ------- | ------------------------------------ | ---------------------------------------------------- |
-| `--spec`   | string  | the shipped `docs/content-format.md` | The specification to read.                           |
-| `--strict` | boolean | `false`                              | Fail on the findings instead of only reporting them. |
+| Option     | Type    | Default                                  | Description                                          |
+| ---------- | ------- | ---------------------------------------- | ---------------------------------------------------- |
+| `--spec`   | string  | the shipped `engine/content-format.yaml` | The specification to read.                           |
+| `--strict` | boolean | `false`                                  | Fail on the findings instead of only reporting them. |
 
 **EXIT STATUS**
 
@@ -1538,17 +2007,17 @@ Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build content-format notes
+$ package-build content-format notes
 […] 0 finding(s) across 4 note(s) measured against docs/content-format.md.
 ```
 
 **SEE ALSO**
 
-`content-build content-format schema`, `content-build content-format fields`,
-`content-build lint [root]`, [Diagnostics](diagnostics.md),
+`package-build content-format schema`, `package-build content-format fields`,
+`package-build lint [root]`, [Diagnostics](diagnostics.md),
 [Configuration](configuration.md).
 
-### `content-build links [root]`
+### `package-build links [root]`
 
 **NAME**
 
@@ -1557,7 +2026,7 @@ Check that every link in a content tree lands.
 **SYNOPSIS**
 
 ```
-content-build links [root]
+package-build links [root]
 ```
 
 **DESCRIPTION**
@@ -1568,7 +2037,7 @@ retired — every link is an address), a wikilink authored in frontmatter
 (which is data and is never resolved), and a package homepage's markdown
 links and `landing:` addresses, which are published verbatim and use no
 wikilink at all. Also reports a vendored foreign-package content index that
-has drifted out of reach, naming `content-build deps fetch` as the fix.
+has drifted out of reach, naming `package-build deps fetch` as the fix.
 Reads the content tree named by `root`, defaulting to `paths.content`, and
 the cached content indexes of any declared dependency; writes nothing.
 
@@ -1587,17 +2056,17 @@ found. Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build links
+$ package-build links
 […] 2 notes: every link is a labelled address, every anchor link lands and every address resolves (0 cross-package reference(s) via manifest), no wikilink in frontmatter, every homepage address resolvable.
 ```
 
 **SEE ALSO**
 
-`content-build lint [root]`, `content-build reachability <dir> [file]`,
-`content-build deps fetch`, [Diagnostics](diagnostics.md),
+`package-build lint [root]`, `package-build reachability <dir> [file]`,
+`package-build deps fetch`, [Diagnostics](diagnostics.md),
 [Configuration](configuration.md).
 
-### `content-build format [paths..]`
+### `package-build format [paths..]`
 
 **NAME**
 
@@ -1606,7 +2075,7 @@ Check formatting with the shared Prettier configuration.
 **SYNOPSIS**
 
 ```
-content-build format [paths..] [--write]
+package-build format [paths..] [--write]
 ```
 
 **DESCRIPTION**
@@ -1644,24 +2113,24 @@ Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build format
-warning: this repository declares no Prettier configuration, so `content-build format` applies the shared conventions while an editor and a bare `npx prettier` apply Prettier's own to the same tree; declare them in a prettier.config.mjs — export { default } from "@heroiclands/package-build/prettier";
-build/dist/module.json: error: is not formatted; run `content-build format --write` to fix it
+$ package-build format
+warning: this repository declares no Prettier configuration, so `package-build format` applies the shared conventions while an editor and a bare `npx prettier` apply Prettier's own to the same tree; declare them in a prettier.config.mjs — export { default } from "@heroiclands/package-build/prettier";
+build/dist/module.json: error: is not formatted; run `package-build format --write` to fix it
 […]
 […] ERROR: 10 of 15 file(s) are not formatted.
 
-$ content-build format --write
+$ package-build format --write
 […] Formatted 10 of 15 file(s).
 
-$ content-build format
+$ package-build format
 […] Formatting is clean (15 file(s)).
 ```
 
 **SEE ALSO**
 
-`content-build markdown [paths..]`, [Diagnostics](diagnostics.md).
+`package-build markdown [paths..]`, [Diagnostics](diagnostics.md).
 
-### `content-build markdown [paths..]`
+### `package-build markdown [paths..]`
 
 **NAME**
 
@@ -1670,7 +2139,7 @@ Lint markdown with the shared markdownlint rule set.
 **SYNOPSIS**
 
 ```
-content-build markdown [paths..] [--fix]
+package-build markdown [paths..] [--fix]
 ```
 
 **DESCRIPTION**
@@ -1682,6 +2151,8 @@ the one these repositories write. Runs over the repository rather than the
 content tree, taking its rules from this package unless the consumer
 declares its own. `--fix` applies the fixes markdownlint can make. Reads
 every matched file; `--fix` rewrites them.
+Installed dependencies under `node_modules` are excluded even when the
+repository has no `.gitignore` or supplies its own markdownlint ignore list.
 
 **OPTIONS**
 
@@ -1701,15 +2172,15 @@ exists at all). Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build markdown
+$ package-build markdown
 […] Markdown is clean.
 ```
 
 **SEE ALSO**
 
-`content-build format [paths..]`, [Diagnostics](diagnostics.md).
+`package-build format [paths..]`, [Diagnostics](diagnostics.md).
 
-### `content-build content-index [root]`
+### `package-build content-index [root]`
 
 **NAME**
 
@@ -1718,7 +2189,7 @@ Emit this package's note index as JSON Lines.
 **SYNOPSIS**
 
 ```
-content-build content-index [root] [--out <dir>]
+package-build content-index [root] [--out <dir>]
 ```
 
 **DESCRIPTION**
@@ -1751,16 +2222,16 @@ into `--out`, defaulting to the configured `paths.contentIndex`.
 **EXAMPLES**
 
 ```
-$ content-build content-index
+$ package-build content-index
 […] demo → build/content-index/demo-metadata.jsonl (4 notes, 2 KiB)
 ```
 
 **SEE ALSO**
 
-`content-build site`, `content-build pdf`, `content-build deps fetch`,
+`package-build site`, `package-build pdf`, `package-build deps fetch`,
 [Configuration](configuration.md).
 
-### `content-build site`
+### `package-build site`
 
 **NAME**
 
@@ -1769,7 +2240,7 @@ Build the Hugo source tree from the content tree.
 **SYNOPSIS**
 
 ```
-content-build site
+package-build site
 ```
 
 **DESCRIPTION**
@@ -1823,7 +2294,7 @@ None.
 
 1 if `package.json` declares no `homepage`, or one that does not end
 `/<contentPackage>/`; if `packageBuild.manifest.title` is undeclared; if the
-navigation has not been fetched (`content-build deps fetch` fills the cache
+navigation has not been fetched (`package-build deps fetch` fills the cache
 and is named in the message); or if `@heroiclands/hugo-theme` is not
 installed. 1 if any gate fires — no homepage or two competing for it, a
 frontmatter wikilink, an address that cannot be derived, a stale or
@@ -1833,20 +2304,20 @@ failed to expand, or a dead wikilink. Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build site
+$ package-build site
 […] wrote 1 homepage(s) + 1 content page(s) to build/hugo/content
 […] wrote build/hugo/hugo.toml
 
-$ content-build site
-[…] ERROR: the site navigation has not been fetched. Run `content-build deps fetch` first.
+$ package-build site
+[…] ERROR: the site navigation has not been fetched. Run `package-build deps fetch` first.
 ```
 
 **SEE ALSO**
 
-`content-build deps fetch`, `package-build site-root`, `content-build package <action> [pack] [entry]`, `content-build pdf`, `content-build content-index [root]`,
+`package-build deps fetch`, `package-build site-root`, `package-build package <action> [pack] [entry]`, `package-build pdf`, `package-build content-index [root]`,
 [Diagnostics](diagnostics.md), [Configuration](configuration.md).
 
-### `content-build pdf`
+### `package-build pdf`
 
 **NAME**
 
@@ -1855,7 +2326,7 @@ Build the book the content tree publishes as.
 **SYNOPSIS**
 
 ```
-content-build pdf [--out <path>] [--book-version <version>] [--compile]
+package-build pdf [--out <path>] [--book-version <version>] [--compile]
 ```
 
 **DESCRIPTION**
@@ -1883,8 +2354,8 @@ configured `pdf.out`.
 
 **EXIT STATUS**
 
-0 when there is a stated reason not to build (`publish.site` is
-`homepage`, no `pdf:` block, no content tree). 1 if the document tree
+0 when there is a stated reason not to build (only a homepage note, no `pdf:`
+block, no content tree). 1 if the document tree
 `pdf.document` names cannot be read or parsed, or on any other thrown
 error. Otherwise 0 — findings inside a book that did build (a filter that
 matched nothing, for instance) are reported but never fail the command.
@@ -1892,19 +2363,19 @@ matched nothing, for instance) are reported but never fail the command.
 **EXAMPLES**
 
 ```
-$ content-build pdf
+$ package-build pdf
 […] No book built: no `pdf:` block is configured, so this package publishes no book
 
-$ content-build pdf --no-compile
+$ package-build pdf --no-compile
 demo-book: error: the document tree named by `pdf.document` cannot be read
 ```
 
 **SEE ALSO**
 
-`content-build site`, `content-build package <action> [pack] [entry]`,
+`package-build site`, `package-build package <action> [pack] [entry]`,
 [Diagnostics](diagnostics.md), [Configuration](configuration.md).
 
-### `content-build map`
+### `package-build map`
 
 **NAME**
 
@@ -1914,12 +2385,12 @@ route graph.
 **SYNOPSIS**
 
 ```
-content-build map --tree [--root <shortcode>] [--engine dot|twopi|neato] [--rankdir TB|LR|BT|RL]
+package-build map --tree [--root <shortcode>] [--engine dot|twopi|neato] [--rankdir TB|LR|BT|RL]
                   [--nodesep <inches>] [--ranksep <inches>] [--no-polities]
-content-build map --from <shortcode>.. | --from all
-content-build map --chart <shortcode>.. | --chart all [--horizon <days>]
-content-build map --travel
-content-build map [...] [--scale <factor>] [--base <url>] [--out <dir>]
+package-build map --from <shortcode>.. | --from all
+package-build map --chart <shortcode>.. | --chart all [--horizon <days>]
+package-build map --travel
+package-build map [...] [--scale <factor>] [--base <url>] [--out <dir>]
 ```
 
 **DESCRIPTION**
@@ -2084,28 +2555,28 @@ that does not resolve, a cycle), or on any other thrown error. Otherwise 0
 **EXAMPLES**
 
 ```
-$ content-build map --tree
+$ package-build map --tree
 assets/content/Regions/Sea.md:16:5: warning: place "innersea" has more than one parent (northc, southc), which is legal for a sea between continents or a region split between two, and worth a look otherwise
 assets/content/Regions/Marches/Lost_Fort.md:9:14: error: place "lostfort" names parent "marchs", which does not resolve to any place in this package or a fetched index
 […] 394 place(s) → 7 drawing(s) under build/map
 
-$ content-build map --from dunharargn --base /thalorna/
+$ package-build map --from dunharargn --base /thalorna/
 […] 394 place(s) → 1 drawing(s) under build/map
 
-$ content-build map --chart takheperurgn --horizon 90
+$ package-build map --chart takheperurgn --horizon 90
 […] 394 place(s) → 1 drawing(s) under build/map
 
-$ content-build map --travel
+$ package-build map --travel
 […] 394 place(s) → 1 drawing(s) under build/map
 ```
 
 **SEE ALSO**
 
-`content-build lint [root]` (which checks `borders` and `routes` from both
-ends), `content-build deps fetch`, `content-build content-index [root]`,
+`package-build lint [root]` (which checks `borders` and `routes` from both
+ends), `package-build deps fetch`, `package-build content-index [root]`,
 [Content format](content-format.md), [Diagnostics](diagnostics.md).
 
-### `content-build reachability <dir> [file]`
+### `package-build reachability <dir> [file]`
 
 **NAME**
 
@@ -2114,7 +2585,7 @@ Check that every document in a corpus is reachable by reading.
 **SYNOPSIS**
 
 ```
-content-build reachability <dir> [file] [--index <shortcode> ...] [--root <path>]
+package-build reachability <dir> [file] [--index <shortcode> ...] [--root <path>]
 ```
 
 **DESCRIPTION**
@@ -2149,19 +2620,19 @@ in the corpus is unreachable from the entry page. Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build reachability Guide
+$ package-build reachability Guide
 […] All 2 document(s) in Guide are reachable from README.md.
 
-$ content-build reachability assets/content
+$ package-build reachability assets/content
 […] ERROR: no note at assets/content/README.md, so the corpus has no page to be read from
 ```
 
 **SEE ALSO**
 
-`content-build links [root]`, `content-build lint [root]`, [Diagnostics](diagnostics.md),
+`package-build links [root]`, `package-build lint [root]`, [Diagnostics](diagnostics.md),
 [Configuration](configuration.md).
 
-### `content-build addresses diff`
+### `package-build addresses diff`
 
 **NAME**
 
@@ -2170,7 +2641,7 @@ Report every published address a build no longer publishes.
 **SYNOPSIS**
 
 ```
-content-build addresses diff --from <zip|dir> [--strict]
+package-build addresses diff --from <zip|dir> [--strict]
 ```
 
 **DESCRIPTION**
@@ -2212,11 +2683,11 @@ this repository declaring no Item pack at all to diff). Otherwise 0.
 **EXAMPLES**
 
 ```
-$ content-build addresses diff --from build/dist/module.zip
+$ package-build addresses diff --from build/dist/module.zip
 […] ERROR: demo-package@1.0.0: pack "items" is declared at packs/items, which the package does not contain
 ```
 
 **SEE ALSO**
 
-`content-build package <action> [pack] [entry]`, `content-build deps fetch`,
+`package-build package <action> [pack] [entry]`, `package-build deps fetch`,
 [Diagnostics](diagnostics.md).