@heroiclands/package-build 23.12.3 → 23.12.5

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @heroiclands/package-build
 
+## 23.12.5
+
+### Patch Changes
+
+In PDF books, the page number and section name at the foot of each page are set at the size of the body text.
+
+In PDF books, list items sit apart from one another and carry a bullet large enough to see at book size.
+
+In PDF books, a reference to another book that already sits in brackets joins them, reading (The Crossing, Thal. p524) rather than nesting a second pair.
+
+Chronology sections, and the other event sections, list each event's date first, written in the setting's calendar. A chronology shows its Felt here column only when some event is felt in the place, and prints across the full page in PDF books. A captioned table can ask to span the page in a PDF book with `.full-width`. A wide table floats to where it fits, and the text runs on past its heading rather than leaving an empty page.
+
+In PDF books, a profile box too long for the rest of a page continues on the next one between its rows, instead of running off the page over the footer.
+
+A note's name may give a `sort` form, the way an index would write it: `sort: Black Flame, The` for _The Black Flame_, or `sort: Hilvan, Doran`. It files the note in the book index, page lists and other name-ordered lists, and it is the note's entry text in the book index; every other list still shows the full name. Authored `sql` fences can order by the new `nameSort` column of `entries`, which is the `sort` form or, without one, the full name.
+
+Profile figures read as numbers do: 12,500 under a million, and 11 million or 1.2 million above it, on the website, in Foundry and in PDF books.
+
+## 23.12.4
+
+### Patch Changes
+
+A PDF book may declare a short `abbreviation`, so references into it read `(Aelw. p307)` instead of naming the full title, and the other books' indexes list its notes the same way.
+
+In PDF books, a definition list sets its term in bold at the start of the line with the description running on after it, indented on later lines, and no space appears between a linked name and the punctuation that follows it.
+
+`project init` scaffolds the build workflow at `.gitea/workflows/build.yml`, and `project check` and `package-build ci` read it from there.
+
 ## 23.12.3
 
 ### Patch Changes

package/ci/ci-steps.mjs

@@ -18,7 +18,7 @@
  * of the command list is a second statement of one thing, and the copy is the
  * one that goes stale — silently, because a pre-push check that runs four of
  * five steps still exits 0. So the steps are parsed out of
- * `.github/workflows/build.yml` at run time and there is nothing to keep in
+ * `.gitea/workflows/build.yml` at run time and there is nothing to keep in
  * step.
  *
  * **It refuses rather than assumes.** If the workflow's shape changes so that
@@ -28,7 +28,7 @@
  *
  * **What it cannot run**, and says so: a `uses:` step is a published action, not
  * a command — the forbidden-marker check, the coverage upload. Those stay
- * GitHub's to run, and the summary names them so the gap is visible rather than
+ * CI's to run, and the summary names them so the gap is visible rather than
  * assumed away.
  *
  * **It parses the workflow itself rather than importing a YAML library**, for a
@@ -64,7 +64,7 @@ const ROOT = process.cwd();
  * failed*. Mirrors the same constant in `ci-docker.mjs`.
  */
 export const UNAVAILABLE = 2;
-const WORKFLOW_DIR = path.join(ROOT, ".github/workflows");
+const WORKFLOW_DIR = path.join(ROOT, ".gitea/workflows");
 
 /**
  * The workflow's steps, split into what can be run here and what cannot.
@@ -77,7 +77,7 @@ export function ciSteps() {
     const files = prTriggeredWorkflows();
     if (!files.length) {
         throw new NoWorkflow(
-            `no workflow under .github/workflows is triggered by \`pull_request\`, ` +
+            `no workflow under .gitea/workflows is triggered by \`pull_request\`, ` +
                 `so there is nothing here that a pull request would run.`,
         );
     }
@@ -236,7 +236,7 @@ function main() {
         });
         if (result.status !== 0) {
             console.error(
-                `\nci-steps: FAILED at "${step.name}" — this is what GitHub would report.\n` +
+                `\nci-steps: FAILED at "${step.name}" — this is what CI would report.\n` +
                     `  Fix it, or push with --no-verify if you mean to.`,
             );
             return result.status ?? 1;

package/content-config.mjs

@@ -787,6 +787,7 @@ const PDF_KEYS = [
 const PDF_BOOK_KEYS = [
     "id",
     "title",
+    "abbreviation",
     "subtitle",
     "coverImage",
     "front",
@@ -1813,6 +1814,8 @@ function normalizeSite(value) {
  * @typedef {object} ResolvedPdfBook
  * @property {string} id          Its name on the command line, `--book <id>`.
  * @property {string} title
+ * @property {string} abbreviation  Names the book in another book's
+ *                                references; `""` when none is declared.
  * @property {string} subtitle    `""` when none is declared.
  * @property {string} coverImage  Absolute; `""` when none is declared.
  *                                Whether the file exists is checked when the
@@ -1984,6 +1987,8 @@ function normalizePdfBooks(value, rootDir, contentPackage) {
     const ids = new Set();
     /** @type {Map<string, number>} Stem → the book that took it. */
     const stems = new Map();
+    /** @type {Map<string, string>} Abbreviation → the id of the book that took it. */
+    const abbreviations = new Map();
     return Object.freeze(
         value.map((entry, i) => {
             const where = `pdf.books[${i}]`;
@@ -2003,6 +2008,19 @@ function normalizePdfBooks(value, rootDir, contentPackage) {
             if (ids.has(id)) fail(`${where}.id`, `is \`${id}\`, which names a book more than once`);
             ids.add(id);
             const title = requireNonEmptyString(book.title, `${where}.title`);
+            let abbreviation = "";
+            if (book.abbreviation !== undefined) {
+                abbreviation = requireNonEmptyString(book.abbreviation, `${where}.abbreviation`);
+                const holder = abbreviations.get(abbreviation);
+                if (holder !== undefined) {
+                    fail(
+                        `${where}.abbreviation`,
+                        `is \`${abbreviation}\`, which books \`${holder}\` and \`${id}\` both ` +
+                            "declare — a reader could not tell which book to open",
+                    );
+                }
+                abbreviations.set(abbreviation, id);
+            }
 
             // One tree, from exactly one place: two would leave the reader to
             // guess which is printed, and none prints nothing.
@@ -2059,6 +2077,7 @@ function normalizePdfBooks(value, rootDir, contentPackage) {
             return Object.freeze({
                 id,
                 title,
+                abbreviation,
                 subtitle:
                     book.subtitle === undefined ?
                         ""

package/docs/api.md

@@ -384,6 +384,7 @@ The declared infobox: what a note's summary panel holds, decided once and render
 | `assertInfoboxSet`        | `assertInfoboxSet(boxes, fm, options)` | `readonly object[]`, throws | refusing a page that carries anything but the boxes its type maps to                   |
 | `buildInfoboxes`          | `buildInfoboxes(fm, options)`          | `object[]`                  | building every box a note carries, against a given set of maps and declarations        |
 | `defineInfobox`           | `defineInfobox(declaration)`           | `object`                    | declaring one system's half of the infobox                                             |
+| `formatQuantity`          | `formatQuantity(value)`                | `string`                    | writing a number as a profile shows it: `12,500` under a million, `11 million` above   |
 | `hasRenderableValue`      | `hasRenderableValue(kind, value)`      | `boolean`                   | deciding whether a built value is worth a row                                          |
 | `hasValue`                | `hasValue(value)`                      | `boolean`                   | deciding whether an authored value is worth a row                                      |
 | `humanizeFieldName`       | `humanizeFieldName(name)`              | `string`                    | turning a declared key into the label a reader sees                                    |

package/docs/authoring/frontmatter.md

@@ -21,7 +21,7 @@ data: {}
 ---
 ```
 
-`name` is a map with a required, nonempty `full` display name. Every note may also use `aliases` for an ordered list of other names. The note infobox lists aliases directly beneath the full name. For a `being` with `subType: character`, `given` and `clan` are optional name components. The first alias of a character or NPC is its nickname. Omit optional keys when they do not apply; `given`, `clan`, and alias entries must be nonempty strings when present. No other keys are accepted under `name`.
+`name` is a map with a required, nonempty `full` display name. Every note may also use `aliases` for an ordered list of other names, and `sort` for the form the name takes in an index, such as `Black Flame, The` or `Hilvan, Doran`. The note infobox lists aliases directly beneath the full name. `sort` files the note wherever notes are ordered by name — the book index, page lists, generated lists of related notes, and the `nameSort` column of the `entries` relation — and is the note's entry text in the book index. Every other list still displays the `full` name. A note with no `sort` files and indexes by its `full` name. For `name: {full: The Black Flame, sort: "Black Flame, The"}`, the book index prints _Black Flame, The_ under **B**, and a page list prints _The Black Flame_ at the same place.
 
 `description` is the short page summary. `tags` hold draft state and descriptive labels. The note type's classification belongs in `subType` where it is declared. `data` holds facts about the subject shared by systems. A YAML comment is the place for an author-only note: commented values remain valid YAML but do not enter the content index or generated documents.
 

package/docs/authoring/links-and-markup.md

@@ -197,7 +197,7 @@ The caption attaches to exactly the next supported block:
 
 The optional `type` attribute overrides inference and accepts `figure`, `table`, `poetry`, `code`, `prose`, and `example`. `type=example` uses **Example 1**, **Example 2**, and so on. It does not allow an unsupported target. A heading, list, thematic break, another caption or end of document after a caption is an error. Caption markers without separating spaces or caption text are errors too.
 
-Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
+Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. On a captioned table or SQL fence, `.full-width` sets the table across the page in a PDF book instead of in one column (`: Regional trade routes {.full-width}`); the other surfaces ignore it. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
 
 Each numbered type has its own counter. Websites and Foundry number within a note; books number across their reading order. Unnumbered captions neither display nor consume a number. A map image can retain its asset-derived **Map** classification when no type is specified.
 
@@ -543,7 +543,7 @@ A column's heading is its SQL alias, so `AS "Name"` is what a reader sees. A cel
 | `market`           | The market scale as three columns — `value`, `name`, `trade` — so a table can print `village` beside the number a note wrote.                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
 | `<package>.notes`  | The same relations — `notes`, `entries`, `events`, `names`, `words`, `affixes`, `fields`, `glossary`, `language_lineage`, `dictionary`, `terms`, `register`, `tongues`, `retired`, `scope`, `letters`, `edges`, `clusters`, `stress`, `finals`, `syllables`, `joining`, `joins`, `marks`, `skeleton`, `frames`, `read_past`, `mutations`, `cluster_groups`, `sound_changes`, `elements`, `roots`, `cognates`, `calling_names`, `older`, `negation`, `name_shapes`, `name_edges`, `name_draws`, `held_from` and `near_names` — for each package this one declares a dependency on, in a schema named for it. |
 
-Nested frontmatter is addressed exactly as a note writes it: `name.full`, `sohl.weight`, `data.born`. Every Address is a string — the full canonical Address, as in `list_contains(data.parents, 'thalorna-note-place-xerathia')` — whichever package published it. Every note carries a computed `state` column of `full`, `draft` or `stub`. Notes tagged `gm` are absent from the relations on public surfaces.
+Nested frontmatter is addressed exactly as a note writes it: `name.full`, `sohl.weight`, `data.born`. Every Address is a string — the full canonical Address, as in `list_contains(data.parents, 'thalorna-note-place-xerathia')` — whichever package published it. Every note carries a computed `state` column of `full`, `draft` or `stub`, and a `nameSort` column holding its `name.sort` or, without one, its `name.full`, to `ORDER BY`. Notes tagged `gm` are absent from the relations on public surfaces.
 
 ### Sections the build adds
 
@@ -567,7 +567,7 @@ The vale holds three villages, of which only [[place-ford|Ford]] is walled.
 
 ### Sections the build adds about events
 
-A note's events are listed for you on the notes they concern: a place gets a **Chronology** of what happened there and below it, with every `depth: world` event as context, a being, affiliation or people the **Events** it took part in, an affiliation, place or people the **Accounts** it gives, and a note holding events **What followed** them. Each is a section appended after everything you wrote, with a fixed anchor — `chronology`, `events`, `accounts`, `followed` — and it appears only where it has something to list.
+A note's events are listed for you on the notes they concern: a place gets a **Chronology** of what happened there and below it, with every `depth: world` event as context, a being, affiliation or people the **Events** it took part in, an affiliation, place or people the **Accounts** it gives, and a note holding events **What followed** them. Each is a section appended after everything you wrote, with a fixed anchor — `chronology`, `events`, `accounts`, `followed` — and it appears only where it has something to list. Each lists the date first, written in the setting's calendar, followed by what happened; a Chronology adds a **Felt here** column only where some event is felt in the place, and a PDF book prints it across the full page width.
 
 To replace one, write the section yourself with the same anchor. The build then adds nothing for it and leaves yours exactly as written:
 
@@ -577,7 +577,7 @@ To replace one, write the section yourself with the same anchor. The build then
 The fells keep no reckoning before the raising.
 
 ```sql
-SELECT summary AS "What happened", "when" AS "When"
+SELECT summary AS "What happened", whenText AS "When"
 FROM events
 WHERE list_contains("where".locus, 'thalorna-note-place-ironfells')
 ORDER BY whenSort

package/docs/commands.md

@@ -128,16 +128,16 @@ package-build ci [--native]
 
 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
+`.gitea/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
+existing files can differ from a clean CI 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.
+covers the listed `run:` steps; the forge runs the published actions separately.
 Workflow steps may install dependencies, generate files, or perform other
 declared build actions.
 
@@ -2632,7 +2632,8 @@ Typst compiler; `--no-compile` emits the Typst source and stops there,
 which is what lets the source be inspected or compiled by hand.
 
 A reference to a note that another book is home to prints that book and page,
-`Name (_Book title_, p. 12)`. A compile renders and lays out every book, writes
+`Name (_Book title_, p. 12)`, or `Name (Aelw. p12)` when that book declares an
+`abbreviation`. A compile renders and lays out every book, writes
 `pages.json` (each note's home book and the page its entry starts on) into the
 output directory, and renders again with those pages; `--no-compile` runs
 neither pass and prints `p. ?`. See the

package/docs/configuration.md

@@ -1156,6 +1156,7 @@ pdf:
   books:
     - id: core
       title: The World of Thalorna
+      abbreviation: Thal.
       subtitle: A Song of Heroic Lands Sourcebook
       coverImage: assets/images/covers/core.webp
       document: book.yaml
@@ -1209,7 +1210,8 @@ The keys of `pdf` itself are shared by every book:
 
 - `pdf.indexSeeAlso` adds a line to a book's index for each note that another
   book prints and this book mentions in authored prose, written
-  `Name: _Book title_, p. N` with the page the note's entry starts on in its
+  `Name: _Book title_, p. N` (or `Name: Aelw. p307` when that book declares an
+  `abbreviation`) with the page the note's entry starts on in its
   home book. It is `false` by default, and the index then lists only the notes
   the book is home to. See [The index](guides/book.md#the-index).
 - `pdf.indexHeads` lists leading words that open many names, such as
@@ -1236,20 +1238,31 @@ Targud` is also listed as `Targud, Kingdom of`, with the same pages as the
 
 Each entry of `pdf.books` is one PDF:
 
-| Key                      | Type                      | Required       | Default                 |
-| ------------------------ | ------------------------- | -------------- | ----------------------- |
-| `pdf.books[].id`         | string                    | yes            | —                       |
-| `pdf.books[].title`      | string                    | yes            | —                       |
-| `pdf.books[].subtitle`   | string                    | no             | `""`                    |
-| `pdf.books[].coverImage` | string (path)             | no             | `""` — no cover         |
-| `pdf.books[].front`      | string[] (markdown files) | no             | `[]`                    |
-| `pdf.books[].out`        | string (file stem)        | no             | `<contentPackage>-<id>` |
-| `pdf.books[].contents`   | list (the tree, inline)   | one of the two | —                       |
-| `pdf.books[].document`   | string (path to the tree) | one of the two | —                       |
+| Key                        | Type                      | Required       | Default                   |
+| -------------------------- | ------------------------- | -------------- | ------------------------- |
+| `pdf.books[].id`           | string                    | yes            | —                         |
+| `pdf.books[].title`        | string                    | yes            | —                         |
+| `pdf.books[].abbreviation` | string                    | no             | `""` — the title names it |
+| `pdf.books[].subtitle`     | string                    | no             | `""`                      |
+| `pdf.books[].coverImage`   | string (path)             | no             | `""` — no cover           |
+| `pdf.books[].front`        | string[] (markdown files) | no             | `[]`                      |
+| `pdf.books[].out`          | string (file stem)        | no             | `<contentPackage>-<id>`   |
+| `pdf.books[].contents`     | list (the tree, inline)   | one of the two | —                         |
+| `pdf.books[].document`     | string (path to the tree) | one of the two | —                         |
 
 - `id` is lowercase letters, digits and hyphens, starting with a letter or
   digit. It is what `--book <id>` names and the tail of the default file stem.
   Each `id` is used once.
+- `abbreviation` is a short name for the book, such as `Aelw.`. It is used only
+  where another book refers to this one: a reference to a note this book
+  prints reads `Name (Aelw. p307)`, with a non-breaking space between the
+  abbreviation and the page, and the other book's index, when
+  `pdf.indexSeeAlso` is on, lists the note as `Name: Aelw. p307`. A book
+  with no abbreviation is named by its full title in italics, `Name (_Book
+title_, p. 307)`. A link the text closes a bracket on takes the reference
+  inside that bracket after a comma, so `(see The Crossing)` prints
+  `(see The Crossing, Thal. p524)` rather than nesting brackets. Each abbreviation is used once, since a reader could not
+  tell which book to open from one shared by two.
 - `contents` is the tree written inline — the same `sectionName` /
   `contents` / `filter` / `file` shape a tree file holds under its own
   `contents:` key — and `document` names the file holding it. A book declares
@@ -1296,6 +1309,10 @@ file, line and column the key is written at:
 
 > ``package-build config: `pdf.books[0].title` must be a non-empty string.``
 
+> ``package-build config: `pdf.books[0].abbreviation` must be a non-empty string.``
+
+> ``package-build config: `pdf.books[1].abbreviation` is `Thal.`, which books `core` and `vedyara` both declare — a reader could not tell which book to open.``
+
 > ``package-build config: `pdf.books[0]` must declare exactly one of `contents` and `document` — the tree written inline, or the file holding it.``
 
 > ``package-build config: `pdf.books[0].out` is `dist/core`, which is not a file stem — letters, digits, `.`, `_` and `-`, with no directory; the directory is `pdf.out`.``
@@ -1304,7 +1321,7 @@ file, line and column the key is written at:
 
 > ``package-build config: `pdf.books[0].front` must be a list of markdown files.``
 
-> ``package-build config: `pdf.books[0].<key>` is not a recognized option (expected one of: id, title, subtitle, coverImage, front, out, contents, document).``
+> ``package-build config: `pdf.books[0].<key>` is not a recognized option (expected one of: id, title, abbreviation, subtitle, coverImage, front, out, contents, document).``
 
 > ``package-build config: `pdf.coverage` must be one of: warning, error, off.``
 

package/docs/guides/book.md

@@ -174,11 +174,11 @@ the Lyrebird Inn (The Tenebrae Volume, p. 214)
 
 Which form a wikilink takes depends on where its target is printed:
 
-| The target is                                                 | The link prints                           |
-| ------------------------------------------------------------- | ----------------------------------------- |
-| An entry of the same book, including a note the book reprints | An internal destination                   |
-| An entry of another book, and not of this one                 | `Name (_Book title_, p. N)`, with no link |
-| A note in no book                                             | The web address of the note's page        |
+| The target is                                                 | The link prints                                                                                                                            |
+| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| An entry of the same book, including a note the book reprints | An internal destination                                                                                                                    |
+| An entry of another book, and not of this one                 | `Name (_Book title_, p. N)`, or `Name (Aelw. pN)` with an abbreviation, with no link; inside a bracket the text closes, `(Name, Aelw. pN)` |
+| A note in no book                                             | The web address of the note's page                                                                                                         |
 
 The page is the page the PDF itself numbers, which is the number printed in the
 footer and used by the contents and the index, so the printed `p. N` is the
@@ -406,12 +406,12 @@ A book that prints at least one note ends with an **Index** chapter, grouped
 under letter headings. Nothing configures it: the build derives it from the
 notes the book prints.
 
-| Term                     | Source                | Shown as                                                                           |
-| ------------------------ | --------------------- | ---------------------------------------------------------------------------------- |
-| A note's name            | `name.full`           | the page of the note's entry in **bold**, then the pages of every authored mention |
-| A name without its head  | `name.full`           | the same pages as the note's entry, filed as `Targud, Kingdom of`                  |
-| An alias                 | `name.aliases`        | _see_ the note's name                                                              |
-| An event's in-world name | `data.events[].names` | _see_ the name of the note that holds the event                                    |
+| Term                     | Source                        | Shown as                                                                           |
+| ------------------------ | ----------------------------- | ---------------------------------------------------------------------------------- |
+| A note's name            | `name.sort`, else `name.full` | the page of the note's entry in **bold**, then the pages of every authored mention |
+| A name without its head  | `name.full`                   | the same pages as the note's entry, filed as `Targud, Kingdom of`                  |
+| An alias                 | `name.aliases`                | _see_ the note's name                                                              |
+| An event's in-world name | `data.events[].names`         | _see_ the name of the note that holds the event                                    |
 
 A name that opens with a generic word a reader would not look under, such as
 `Kingdom of Targud` or `Ritual: Blessing`, is also filed under the rest of the
@@ -438,7 +438,7 @@ first book in `pdf.books` that selects it. In a package of several books:
   as the cross-book references (`pages.json`), so the page a reference prints
   for a note is the page its home book's index lists for the note's own entry.
 - A mention of a note another book prints is not a term of the mentioning
-  book. The mention reads `Name (_Book title_, p. N)` in the text, and the note's
+  book. The mention reads `Name (_Book title_, p. N)` in the text (`Name (Aelw. pN)` when the home book declares an `abbreviation`), and the note's
   entry and its page are in the other book's index.
 
 Set [`pdf.indexSeeAlso`](../configuration.md) to `true` to list those mentions
@@ -447,6 +447,8 @@ then has a line, filed under its name:
 
 > Sword: _Book A_, p. 12
 
+A home book with an `abbreviation` files the line as `Sword: BkA. p12`.
+
 Two kinds of link add nothing:
 
 - **Links in generated sections** such as "Within" or "Governed by". They name
@@ -458,7 +460,7 @@ Two kinds of link add nothing:
 
 Terms sort on the ASCII fold the content index derives for names (`nameAscii`),
 ignoring case, so an accented name files under its base letter and the order
-matches the table of contents. A term that does not begin with a letter files
+matches the table of contents. A note's own entry reads as its `name.sort` when it declares one, in index form such as `Black Flame, The` or `Hilvan, Doran`, and as its `name.full` otherwise; it files, and takes its letter heading, from that form. A note that declares a `sort` is not also filed under `pdf.indexHeads`. A term that does not begin with a letter files
 first, under `#`. An alias or event name that folds to the same text as the
 note's own name is not listed again.
 

package/docs/guides/release-and-deploy.md

@@ -182,17 +182,14 @@ release runs in two halves, one on each:
    pushes the tag `v<version>` at the merged version commit. Releasing from
    Gitea is switched on by the repository variable `HL_RELEASE_ENABLED`.
 2. **Publish, on GitHub.** The push mirror carries the tag to GitHub, where it
-   starts the **Publish to npm** workflow, `.github/workflows/release.yml`. It
-   refuses a tag that names a commit outside `main` or that is not
-   `v<version>` of the tagged `package.json`. When npm does not have the
-   version yet, it runs the tests and publishes through npm Trusted Publishing
-   with provenance. It then creates the GitHub Release from the version's
-   changelog section, unless one exists.
+   starts the **Publish to npm** workflow, `.github/workflows/release.yml`, the
+   only workflow GitHub runs. Every check has already run on Gitea before the
+   tag exists, so the workflow installs, publishes through npm Trusted
+   Publishing with provenance, and creates the GitHub Release from the
+   version's changelog section.
 
 Nothing on Gitea publishes to npm, and nothing on GitHub runs for a branch
-push. Every step of the GitHub half is safe to repeat: re-running it, or
-dispatching it with the tag as its ref, finishes a release whose publish or
-Release step failed and changes nothing for one that completed. The
+push. The
 [npm package page](https://www.npmjs.com/package/@heroiclands/package-build)
 shows the published version and README.
 

package/docs/project-setup.md

@@ -513,7 +513,7 @@ tool:
 organisation-level and defined in `HeroicLands/.github`, so the repository
 carries no label registry of its own.
 
-`.github/workflows/` then carries the repository's own CI. The org-wide
+`.gitea/workflows/` carries the repository's own CI. The org-wide
 `HeroicLands/.github` repository supplies the shared composite actions those
 workflows `uses:` — `labels`, `no-attribution` and `todos` — plus the reusable
 site-deploy workflow, so a fix to any of them reaches every repository at once.
@@ -522,16 +522,16 @@ site-deploy workflow, so a fix to any of them reaches every repository at once.
 
 A summary, because "where does this come from" is the question that recurs.
 
-| Read                          | By                                                                                                        |
-| ----------------------------- | --------------------------------------------------------------------------------------------------------- |
-| `package.json`                | The Foundry package id, the version, the release addresses; the site's `baseURL`, description and author. |
-| `package-build.config.yaml`   | Everything else about the build.                                                                          |
-| `assets/content/**/*.md`      | Every content command.                                                                                    |
-| `.gitignore`                  | `package-build format`, `package-build markdown`.                                                         |
-| `.prettierignore`             | `package-build format`.                                                                                   |
-| `lang/*.json`                 | `package-build lang`.                                                                                     |
-| `.env.local`                  | `package-build deploy`.                                                                                   |
-| `.github/workflows/build.yml` | The `pre-push` hook, for its step list.                                                                   |
+| Read                         | By                                                                                                        |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------- |
+| `package.json`               | The Foundry package id, the version, the release addresses; the site's `baseURL`, description and author. |
+| `package-build.config.yaml`  | Everything else about the build.                                                                          |
+| `assets/content/**/*.md`     | Every content command.                                                                                    |
+| `.gitignore`                 | `package-build format`, `package-build markdown`.                                                         |
+| `.prettierignore`            | `package-build format`.                                                                                   |
+| `lang/*.json`                | `package-build lang`.                                                                                     |
+| `.env.local`                 | `package-build deploy`.                                                                                   |
+| `.gitea/workflows/build.yml` | The `pre-push` hook, for its step list.                                                                   |
 
 Everything written goes under `build/`. Nothing the toolchain generates is
 committed.

package/docs/reference/format-details.md

@@ -379,7 +379,13 @@ content, comment out its YAML lines with `#`. Comments remain valid YAML text
 and do not become data in the JSONL index, generated pages, or Foundry documents.
 
 `name` is a map with a required nonempty `full` string when present. It may
-also contain `aliases`, an ordered list of nonempty strings. A being with
+also contain `aliases`, an ordered list of nonempty strings, and `sort`, a nonempty
+string giving the form the name takes in an index, such as `Black Flame, The` or
+`Hilvan, Doran`. `sort` files the note wherever notes are ordered by name (page
+lists, generated lists of related notes, the book index, the `nameSort` column)
+and is the note's entry text in the book index; every other list still displays
+`full`. Without `sort`, the note files and indexes by `full`. Ordering compares
+the ASCII fold of the key (`Árdavon` files beside `Ardavon`). A being with
 `subType: character` may additionally contain nonempty `given` and `clan`
 strings. Other keys under `name` are errors. For a character or NPC, the first
 alias is its nickname. A being's homes belong in `data.homes`.
@@ -2916,7 +2922,9 @@ reads `NULL` rather than failing. `data.culture` is the one field that reads as
 a derived value: the note's own culture, or the one it inherits. See
 [Culture in the index](#culture-in-the-index).
 
-**`notes` leaves out stubs; `entries` does not.** Both carry a derived `state`
+**`notes` leaves out stubs; `entries` does not.** Both carry a derived `nameSort`
+column — the note's `name.sort` when it declares one, otherwise its `name.full`,
+unfolded — for `ORDER BY`, and a derived `state`
 column — `stub`, `draft` or `full` — and `notes` is exactly
 `SELECT * FROM entries WHERE state <> 'stub'`. So every table already written
 selects what it always selected, and gains `state` for free; a table that should
@@ -2957,20 +2965,21 @@ query rather than a list kept by hand:
 
 ````markdown
 ```sql
-SELECT note AS _ref, "when" AS "When", summary AS "What happened"
+SELECT note AS _ref, whenText AS "When", summary AS "What happened"
 FROM events
 WHERE kind IN ('war', 'siege', 'battle')
 ORDER BY whenSort
 ```
 ````
 
-| Column                   | What it holds                                                                                                                                                                                                               |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                  |
-| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                 |
-| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`. |
-| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                       |
-| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                              |
+| Column                   | What it holds                                                                                                                                                                                                                                                                                  |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                                                                                     |
+| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                                                                                    |
+| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`.                                                                    |
+| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                                                                                          |
+| `whenText`, `untilText`  | The date as a reader sees it, printed as `dateformat` prints it in the calendar the owning note names in `data.calendar`, else the one the world note names, else in the era the date itself names; `~` marks an approximate date. A date that does not resolve keeps the text its note wrote. |
+| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                                                                                                 |
 
 `when` and `until` read as the text the note wrote, `~` included. The sort
 keys and years are positions on the canonical axis, which counts a year `0`
@@ -3498,7 +3507,7 @@ The caption attaches to exactly the next supported block:
 
 The optional `type` attribute overrides inference and accepts `figure`, `table`, `poetry`, `code`, `prose`, and `example`. `type=example` uses **Example 1**, **Example 2**, and so on. It does not allow an unsupported target. A heading, list, thematic break, another caption or end of document after a caption is an error. Caption markers without separating spaces or caption text are errors too.
 
-Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
+Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. On a captioned table or SQL fence, `.full-width` sets the table across the page in a PDF book instead of in one column (`: Regional trade routes {.full-width}`); the other surfaces ignore it. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
 
 Each numbered type has its own counter. Websites and Foundry number within a note; books number across their reading order. Unnumbered captions neither display nor consume a number. A map image can retain its asset-derived **Map** classification when no type is specified.
 
@@ -3763,11 +3772,14 @@ The build appends sections to the end of a note's body that list the events conc
 
 | View          | Anchor       | On                                                               | Rows                                                                                                                                                                              | Columns                            |
 | ------------- | ------------ | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
-| Chronology    | `chronology` | a `place`                                                        | events whose `where.locus` names the place or a place below it in `parents`; events whose `where.reach` names one, with that entry's `how`; every `depth: world` event as context | What happened, When, Felt here     |
-| Events        | `events`     | a `being`, an `affiliation`, a `lore` note of `subType: culture` | events whose `who[].ref` names the note, with the role it played                                                                                                                  | What happened, When, Role          |
-| Accounts      | `accounts`   | an `affiliation`, a `place`, a `lore` note of `subType: culture` | each `accounts[]` entry the note gives, with the event it concerns                                                                                                                | Event, When, What they say, Agrees |
-| What followed | `followed`   | a note holding events                                            | events whose `follows[].event` names one of this note's events, with how                                                                                                          | What followed, When, How           |
-
+| Chronology    | `chronology` | a `place`                                                        | events whose `where.locus` names the place or a place below it in `parents`; events whose `where.reach` names one, with that entry's `how`; every `depth: world` event as context | When, What happened, Felt here     |
+| Events        | `events`     | a `being`, an `affiliation`, a `lore` note of `subType: culture` | events whose `who[].ref` names the note, with the role it played                                                                                                                  | When, What happened, Role          |
+| Accounts      | `accounts`   | an `affiliation`, a `place`, a `lore` note of `subType: culture` | each `accounts[]` entry the note gives, with the event it concerns                                                                                                                | When, Event, What they say, Agrees |
+| What followed | `followed`   | a note holding events                                            | events whose `follows[].event` names one of this note's events, with how                                                                                                          | When, What followed, How           |
+
+- **Every view's first column is When**, the event's date written in the setting's calendar — the `events` relation's `whenText` column. An event whose date does not resolve shows the text its note wrote.
+- **A chronology's Felt here column appears only where some row is felt in the place.** A place whose rows are all events that happened there, or world events, has the When and What happened columns alone.
+- **A chronology is always set across the full page width in a PDF book**, whatever its columns.
 - **The views follow everything the author wrote**, in the order of the [generated sections](#generated-sections).
 - **A view with no rows is not generated.** A chronology is generated only where the place has rows of its own; the world events beside them are context and make no chronology by themselves.
 - **An author's own section replaces a view.** A note whose body declares a prose anchor with the view's slug — `# Chronology {#chronology}`, or a block or span with that `id` — gets no generated section for it, and its own section is left exactly as written. This is the one way to turn a view off, and the way to choose a different table: write the section and its own `sql` fence.

package/docs/reference/note-types.md

@@ -18,7 +18,7 @@ These are the only keys a note writes at its top level, in the order the formatt
 | Key           | Meaning                                                                                   |
 | ------------- | ----------------------------------------------------------------------------------------- |
 | `shortcode`   | The note's own address segment, unique within its type.                                   |
-| `name`        | The display names — a required `full`, and any `aliases`.                                 |
+| `name`        | The display names — a required `full`, and any `aliases` and `sort`.                      |
 | `type`        | What the note is about, which decides its vocabulary and its document.                    |
 | `subType`     | The type's own genre, where it declares one.                                              |
 | `description` | The short page summary.                                                                   |

package/engine/content-index.mjs

@@ -108,8 +108,9 @@ import { analyzeNameSpans } from "./names.mjs";
 import fs from "node:fs";
 import path from "node:path";
 
-import unidecode from "unidecode";
+import { asciiName } from "./name-sort.mjs";
 
+export { asciiName };
 import { loadForeignIndexes, metadataFileName } from "./metadata-index.mjs";
 import { collectAssetRecords } from "./asset-index.mjs";
 import { checkForeignAssetBindings } from "./asset-bindings.mjs";
@@ -245,44 +246,6 @@ export function noteAddress(frontmatter, contentPackage) {
     };
 }
 
-/**
- * A note's display name reduced to printable 7-bit ASCII.
- *
- * Content names carry the setting's orthography — `Kûrbúl Helm`, `Hârn`,
- * `Kèthîra` — and nobody types them. A reader searching the index, or an editor
- * completing a wikilink, needs a form that matches what a keyboard produces, so
- * the record states one rather than leaving every consumer to invent it (and to
- * invent a *different* one, which is how two searches over the same data come
- * to disagree).
- *
- * **Transliterated, not stripped.** `unidecode` — the same table
- * {@link slugify} already runs, so an ASCII name and a slug can never disagree
- * about a character — carries a letter across rather than deleting it:
- * diacritics fold (`â`→`a`, `è`→`e`), ligatures expand (`æ`→`ae`, `Œ`→`OE`,
- * `ß`→`ss`), the runic letters spell out (`þ`→`th`, `Þ`→`Th`, `ð`→`d`), and
- * even a vulgar fraction becomes readable (`¾`→`3/4`). Deleting them instead
- * would collapse `Kûrbúl` to `Krbl`, which is worse than the original.
- *
- * Anything still outside printable ASCII after that becomes a space, and runs
- * of whitespace collapse — a space rather than nothing, so a character that
- * transliterates away cannot silently weld two words together.
- *
- * The value is emitted even when it equals the name, so a consumer matching on
- * it never has to branch on whether the name happened to be ASCII already.
- *
- * @param {unknown} name - The note's `name.full`.
- * @returns {string|null} The ASCII form, or `null` when there is no name, or
- *   nothing printable survives.
- */
-export function asciiName(name) {
-    if (typeof name !== "string") return null;
-    const folded = unidecode(name)
-        .replace(/[^\x20-\x7E]/g, " ")
-        .replace(/\s+/g, " ")
-        .trim();
-    return folded === "" ? null : folded;
-}
-
 /**
  * A note's `name.aliases` reduced to printable 7-bit ASCII, in order.
  *