@heroiclands/package-build 23.11.0 → 23.12.0

package/docs/api.md

@@ -744,23 +744,23 @@ The corpus registry anchors each calendar's year 1, day 1 to its canonical `data
 
 A calendar is a `lore` note with `subType: calendar`, declaring the months it keeps, the weekdays it names, the seasons it marks and the eras it counts years in. How long the year is, how the day divides and how the moon moves are facts about the **world**, written on its `place` note and its moon's, and no calendar may restate them — which is why the months summing to the world's year is the only arithmetic a calendar note is held to. One definition is emitted per calendar, in array shape: Foundry core prunes the keys outside its schema, and Calendaria converts the arrays to its own keyed collections.
 
-| Export                      | Signature                                             | Returns                                    | Use it when                                                                       |
-| --------------------------- | ----------------------------------------------------- | ------------------------------------------ | --------------------------------------------------------------------------------- |
-| `CALENDAR_SUBTYPE`          | `const CALENDAR_SUBTYPE`                              | —                                          | naming the `lore` subType whose notes are calendars                               |
-| `INVARIANT_SUBTYPES`        | `const INVARIANT_SUBTYPES`                            | —                                          | naming the `place` subTypes a world fact may be written on                        |
-| `CALENDAR_FIELDS`           | `const CALENDAR_FIELDS`                               | —                                          | reading the closed list of what a calendar note may declare                       |
-| `CALENDAR_ENTRY_FIELDS`     | `const CALENDAR_ENTRY_FIELDS`                         | —                                          | reading the keys one entry of each calendar list takes, as inner-key declarations |
-| `CALENDAR_DATE_FORMAT_KEYS` | `const CALENDAR_DATE_FORMAT_KEYS`                     | —                                          | reading the supported Calendaria display slots                                    |
-| `CALENDAR_FORMAT_TOKENS`    | `const CALENDAR_FORMAT_TOKENS`                        | —                                          | checking bare date tokens in a format string                                      |
-| `INVARIANT_FIELDS`          | `const INVARIANT_FIELDS`                              | —                                          | reading the closed list of what a body may declare about itself                   |
-| `checkCalendarNote`         | `checkCalendarNote(note, opts)`                       | `object[]` — findings                      | holding a `lore` note to the family and to the year the world keeps               |
-| `checkCalendarDateFormats`  | `checkCalendarDateFormats(note)`                      | `object[]` — findings                      | checking named patterns and the readable default                                  |
-| `checkWorldFacts`           | `checkWorldFacts(note, opts)`                         | `object[]` — findings                      | holding a `place` note's world facts to one body, one year and one moon           |
-| `worldInvariants`           | `worldInvariants(index)`                              | `{year, present, moon, body, moonName, …}` | reading the year, the present and the moon a package's own notes state            |
-| `quarterDays`               | `quarterDays(daysPerYear)`                            | `number[]` — four days of the year         | asking which days the year turns on                                               |
-| `compileCalendar`           | `compileCalendar({note, invariants, contentPackage})` | `object` — the definition                  | building the one object both a core consumer and Calendaria read                  |
-| `compileCalendars`          | `compileCalendars(index, opts)`                       | `{calendars, invariants}`                  | building every calendar a package declares, or none where it states no year       |
-| `calendariaEnvelope`        | `calendariaEnvelope(definition, opts)`                | `object` — the import envelope             | wrapping a definition for a hand import through Calendaria's settings             |
+| Export                      | Signature                                             | Returns                            | Use it when                                                                       |
+| --------------------------- | ----------------------------------------------------- | ---------------------------------- | --------------------------------------------------------------------------------- |
+| `CALENDAR_SUBTYPE`          | `const CALENDAR_SUBTYPE`                              | —                                  | naming the `lore` subType whose notes are calendars                               |
+| `INVARIANT_SUBTYPES`        | `const INVARIANT_SUBTYPES`                            | —                                  | naming the `place` subTypes a world fact may be written on                        |
+| `CALENDAR_FIELDS`           | `const CALENDAR_FIELDS`                               | —                                  | reading the closed list of what a calendar note may declare                       |
+| `CALENDAR_ENTRY_FIELDS`     | `const CALENDAR_ENTRY_FIELDS`                         | —                                  | reading the keys one entry of each calendar list takes, as inner-key declarations |
+| `CALENDAR_DATE_FORMAT_KEYS` | `const CALENDAR_DATE_FORMAT_KEYS`                     | —                                  | reading the supported Calendaria display slots                                    |
+| `CALENDAR_FORMAT_TOKENS`    | `const CALENDAR_FORMAT_TOKENS`                        | —                                  | checking bare date tokens in a format string                                      |
+| `INVARIANT_FIELDS`          | `const INVARIANT_FIELDS`                              | —                                  | reading the closed list of what a body may declare about itself                   |
+| `checkCalendarNote`         | `checkCalendarNote(note, opts)`                       | `object[]` — findings              | holding a `lore` note to the family and to the year the world keeps               |
+| `checkCalendarDateFormats`  | `checkCalendarDateFormats(note)`                      | `object[]` — findings              | checking named patterns and the readable default                                  |
+| `checkWorldFacts`           | `checkWorldFacts(note, opts)`                         | `object[]` — findings              | holding a `place` note's world facts to one body, one year and one moon           |
+| `worldInvariants`           | `worldInvariants(index)`                              | `{year, moon, body, moonName, …}`  | reading the year and moon a package's own notes state                             |
+| `quarterDays`               | `quarterDays(daysPerYear)`                            | `number[]` — four days of the year | asking which days the year turns on                                               |
+| `compileCalendar`           | `compileCalendar({note, invariants, contentPackage})` | `object` — the definition          | building the one object both a core consumer and Calendaria read                  |
+| `compileCalendars`          | `compileCalendars(index, opts)`                       | `{calendars, invariants}`          | building every calendar a package declares, or none where it states no year       |
+| `calendariaEnvelope`        | `calendariaEnvelope(definition, opts)`                | `object` — the import envelope     | wrapping a definition for a hand import through Calendaria's settings             |
 
 ### `engine.calendarArtifacts`
 
@@ -776,18 +776,45 @@ identical bytes.
 | ----------------------- | ---------------------------------------------------- | ------------------------------- | ---------------------------------------------------- |
 | `emitCalendarArtifacts` | `emitCalendarArtifacts({config, calendariaVersion})` | `{directory, calendars, files}` | writing calendar files for a package's Foundry stage |
 
+### `engine.definitionList`
+
+HTML definition lists use semantic dictionary rows. The plugin groups each term
+and all its definitions inside one `div` under `dl.dictionary`, preserving
+nested blocks, inline formatting and document footnotes. Register it after
+`markdown-it-deflist`.
+
+| Export                 | Signature                  | Returns | Use it when                                                     |
+| ---------------------- | -------------------------- | ------- | --------------------------------------------------------------- |
+| `dictionaryListPlugin` | `dictionaryListPlugin(md)` | `void`  | Giving an HTML Markdown parser the shared dictionary structure. |
+
+The website groups Goldmark's final HTML through the `dictionary-lists.html`
+partial, retaining its headings, TOC and footnotes. Shared content styles use a
+150px hanging indent, a `.75em` term gap and `.5em` space between entries. At
+viewport widths of 600px or less the indent is 100px. Terms are bold and stay on
+one line. A long term pushes the first definition farther right; continuation
+lines return to the common indent. Profile infobox grids keep their own layout.
+
+### `engine.currentDate`
+
+The shared current-date setting is a neutral string and requires no calendar or
+configuration loading. Undefined selects the default; invalid explicit values
+throw `TypeError`. Day digits remain exactly as authored.
+
+| Export                 | Signature                      | Returns   | Use it when                                     |
+| ---------------------- | ------------------------------ | --------- | ----------------------------------------------- |
+| `DEFAULT_CURRENT_DATE` | Constant                       | `"720.1"` | Selecting the setting-wide default.             |
+| `normalizeCurrentDate` | `normalizeCurrentDate(value?)` | `string`  | Validating a configuration or adapter override. |
+
 ### `engine.beingAge`
 
-The middle state of a being's `age`: absent beside a dated `born`, it is computed against the package's declared present — the two dates compared, not the two years subtracted, so a birthday later in the year than the present counts one less. `applyComputedBeingAge` fills it in on the frontmatter object a pass already holds, never on the note; `checkBeingAge` is `being`'s `NOTE_VOCABULARY` check, raising a warning where an authored `age` disagrees with what a dated `born` computes to. An estimate's `~` is read the way a date's is: the authored string stays verbatim, and `ageYears` carries the magnitude beside it.
+The middle state of a being's `age`: absent beside a dated `born`, it is computed against the configured `currentDate` (default `"720.1"`) — the two dates compared, not the two years subtracted, so a birthday later in the year than the present counts one less. `applyComputedBeingAge` fills it in on the frontmatter object a pass already holds, never on the note; `checkBeingAge` is `being`'s `NOTE_VOCABULARY` check, raising a warning where an authored `age` disagrees with what a dated `born` computes to. An estimate's `~` is read the way a date's is: the authored string stays verbatim, and `ageYears` carries the magnitude beside it.
 
-| Export                     | Signature                                | Returns                        | Use it when                                                               |
-| -------------------------- | ---------------------------------------- | ------------------------------ | ------------------------------------------------------------------------- |
-| `computeAge`               | `computeAge(bornRaw, presentRaw)`        | `number \| null`               | reading the age two dates imply, in whole years                           |
-| `parseAgeMagnitude`        | `parseAgeMagnitude(raw)`                 | `{approximate, value} \| null` | reading an authored `age`'s `~` mark and its magnitude                    |
-| `applyComputedBeingAge`    | `applyComputedBeingAge(fm, presentRaw)`  | `void` — mutates `fm.data`     | filling in a being's computed `age`, or the `ageYears` beside an estimate |
-| `presentAmongRecords`      | `presentAmongRecords(records)`           | the present, or `null`         | reading the declared present from a batch of flat index records           |
-| `presentAmongFrontmatters` | `presentAmongFrontmatters(frontmatters)` | the present, or `null`         | reading the declared present from a batch of raw frontmatter objects      |
-| `checkBeingAge`            | `checkBeingAge(note, opts)`              | `object[]` — findings          | holding a being's authored `age` to what `born` and the present compute   |
+| Export                  | Signature                                     | Returns                        | Use it when                                                               |
+| ----------------------- | --------------------------------------------- | ------------------------------ | ------------------------------------------------------------------------- |
+| `computeAge`            | `computeAge(bornRaw, presentRaw)`             | `number \| null`               | reading the age two dates imply, in whole years                           |
+| `parseAgeMagnitude`     | `parseAgeMagnitude(raw)`                      | `{approximate, value} \| null` | reading an authored `age`'s `~` mark and its magnitude                    |
+| `applyComputedBeingAge` | `applyComputedBeingAge(fm, presentRaw)`       | `void` — mutates `fm.data`     | filling in a being's computed `age`, or the `ageYears` beside an estimate |
+| `checkBeingAge`         | `checkBeingAge(note, { index, currentDate })` | `object[]` — findings          | holding a being's authored `age` to what `born` and the present compute   |
 
 ### `engine.contentAddress`
 
@@ -1290,30 +1317,33 @@ index for checking page links.
 
 ### `engine.sitePreview`
 
-`prepareSitePreview({ config })` reads the saved content tree and declared dependency indexes, prepares its SQL corpus, and returns a private preview context. Pass the active note's absolute path and complete buffer text to `render(file, text)`. A successful result has `{ ok: true, markdown, frontmatter, findings: [] }`; a failed result has `{ ok: false, findings }` and no replacement content. Findings identify the source file and carry a line and column when the offending text can be located.
+`renderPreview(text, { dark = false, infobox = true, file = "", currentDate = "720.1" })` renders the current Markdown buffer directly to HTML. Frontmatter is optional. It needs no package configuration, saved note, content tree, dependency cache, database or Pandoc installation. The result is `{ ok, html, frontmatter, findings }`; `file` only labels diagnostics. Malformed frontmatter produces a warning and remains visible without preventing a preview update.
 
-| Export               | Signature                        | Returns                                    | Use it when                                        |
-| -------------------- | -------------------------------- | ------------------------------------------ | -------------------------------------------------- |
-| `prepareSitePreview` | `prepareSitePreview({ config })` | `{render(file, text), refresh(), close()}` | An editor needs a private, reusable page renderer. |
+| Export                   | Signature                       | Returns                               | Use it when                                                            |
+| ------------------------ | ------------------------------- | ------------------------------------- | ---------------------------------------------------------------------- |
+| `renderPreview`          | `renderPreview(text, options?)` | `{ ok, html, frontmatter, findings }` | An editor or external renderer needs a preview from one buffer.        |
+| `previewStyles`          | `previewStyles()`               | CSS string                            | A host needs the shared, scoped light and dark palettes.               |
+| `readPreviewCurrentDate` | `readPreviewCurrentDate(root)`  | `Promise<string>`                     | Opting into the nearest project's validated root current-date setting. |
+| `PREVIEW_HELPERS`        | Constant                        | Helper dependency policy              | Checking preview coverage when adding an expression helper.            |
 
-The context keeps other notes and foreign packages at their saved state. Call `refresh()` after a save to read them again, and `close()` when the editor releases the project. Rendering and refreshing never write the authored notes or the site's `build/hugo/content` mount. The editor owns any private HTML artifact and keeps its last complete artifact when a render fails.
+The returned HTML includes an `.hl-preview` wrapper with exactly one explicit mode class, `.hl-preview-light` or `.hl-preview-dark`. Include `previewStyles()` once in the host document. The stylesheet colors only the preview container, including its backgrounds, source tokens, alerts and optional local infobox. Set `dark` from the host's selected theme; browser preference does not override it.
 
 ```js
-import { sitePreview } from "@heroiclands/package-build/engine";
+import { renderPreview, previewStyles } from "@heroiclands/package-build/engine/site-preview";
 
-const preview = await sitePreview.prepareSitePreview({ config });
-try {
-  const result = await preview.render(absoluteFile, currentBufferText);
-  if (result.ok) {
-    // Convert result.markdown and result.frontmatter to the editor's HTML preview.
-  } else {
-    showDiagnostics(result.findings);
-  }
-} finally {
-  await preview.close();
-}
+const result = renderPreview(currentBufferText, { dark: true });
+// Include previewStyles() in a stylesheet and result.html in the preview document.
+showDiagnostics(result.findings);
 ```
 
+Ordinary Markdown, definition lists, footnotes, alert boxes, poetry, captions, local figures and container blocks render locally. Alerts reuse the four shared icons and titles, accept custom titles and nested alerts, and have opaque tinted backgrounds in both modes. Definition terms are bold; definitions retain ordinary Markdown styling. Wikilinks and image embeds retain their entire authored source: blue opening markers (including all of `![[`), brackets and pipes, purple addresses and anchors, bold foreground labels, and grey attributes. Spans retain their entire source in bold, with blue brackets and grey attributes. Code examples stay literal. Incomplete syntax remains visible while editing.
+
+SQL and pagelist fences remain grey source, including delimiters. Calendar/date expressions, cross-note references and maps remain green source. A dependent call nested inside a pure helper preserves the entire outer expression. Pure helpers and scalar frontmatter expressions evaluate locally; same-note figure references and non-date event facts can resolve from this buffer. Infobox fields show authored values and green reference source; image and portrait wikilinks use the image syntax colors. Missing ages are calculated locally from neutral birth dates and `currentDate`, defaulting to `"720.1"`; authored ages, including `0`, take precedence. Unavailable ages remain `null` internally, have no infobox row, and render as empty text in `{{data.age}}`. Named-calendar birth dates remain unavailable without calendar context. Set `infobox: false` to omit the profile.
+
+`readPreviewCurrentDate(root)` is an explicit configuration adapter. It discovers the nearest `package-build.config.yaml`, `.yml` or `.mjs` using the shared resolver. YAML reads only top-level `currentDate`, without loading the build pipeline or validating unrelated fields; MJS executes the trusted configuration module. Missing config or an absent setting returns the shared default. Invalid explicit values reject with a configuration-file diagnostic. Repeated calls reread YAML and refresh a changed MJS file. `renderPreview` never calls this adapter or reads configuration itself.
+
+Generated sections, Related pages and authored See also sections are absent. Preview performs no publication eligibility or link checks and never resolves other notes. It does not write notes or generated site files. Callers render each buffer directly without preparing or maintaining a snapshot.
+
 ### `engine.contentLint`
 
 Linting a content tree's **addresses** — the rules every package's notes are authored against, wherever those notes live. These rules do not live in a consumer's `utils/`, which has two consequences and no upside. `thalorna` and `kethira` notes were checked by nothing at all, so the packages most likely to carry authoring mistakes were the ones nothing inspected. And one rule with two implementations can disagree without anything detecting it, which the canonical-separator handling already did once on each side.
@@ -1999,6 +2029,29 @@ Where HM3 records the template priority — one statement (`data.templatePriorit
 | `HM3_DEFAULT_ITEM_ART` | `const HM3_DEFAULT_ITEM_ART` | —                                 | reading the full map of default item artwork keyed by **note** type (not document subtype) for HM3 items |
 | `hm3DefaultItemArt`    | `hm3DefaultItemArt(type)`    | `string` — the default image path | getting the default art path for an HM3 item's note type, throwing when the type is unknown              |
 
+## `./preview`
+
+Import the buffer-only renderer directly without loading the build pipeline:
+
+```js
+import { renderPreview, previewStyles } from "@heroiclands/package-build/preview";
+
+const { html, findings } = renderPreview(currentBufferText, { dark: true });
+const css = previewStyles();
+```
+
+| Export                   | Signature                       | Returns                               | Use it when                                                            |
+| ------------------------ | ------------------------------- | ------------------------------------- | ---------------------------------------------------------------------- |
+| `renderPreview`          | `renderPreview(text, options?)` | `{ ok, html, frontmatter, findings }` | Rendering one Markdown buffer without configuration or an index.       |
+| `previewStyles`          | `previewStyles()`               | CSS string                            | Installing both scoped palettes in an editor or external host.         |
+| `readPreviewCurrentDate` | `readPreviewCurrentDate(root)`  | `Promise<string>`                     | Opting into the nearest project's validated root current-date setting. |
+| `PREVIEW_HELPERS`        | Constant                        | Helper dependency policy              | Checking coverage for every registered expression helper.              |
+
+These are the same exports as [`engine.sitePreview`](#enginesitepreview), with
+the same explicit palette, local infobox, source-preservation and diagnostics
+contract. See [Source preview](source-preview.md) for the standalone command and
+Gitea installation.
+
 ## `./content-config`
 
 The per-repository configuration contract: what `package-build.config.yaml` (or an `.mjs` config calling `defineConfig` directly) must satisfy. `defineConfig` validates and normalizes the whole thing, returning a deeply frozen copy, and performs no I/O — `engine.packConfig` is what locates and reads a repository's file, deriving the three fields absent from authored YAML (`rootDir`, `stats.systemVersion`, the resolved `itemBuilders` table). See `docs/configuration.md` for the full key-by-key reference; this section covers the module's own exported shape.
@@ -2391,9 +2444,15 @@ The engine wildcard subpath also exposes the body parsers below. Their figure ex
 
 Inline `.secret` spans preserve their inline content, name classes and
 attributes. Site rendering uses a separate show/hide button and content span,
-so a link inside the content does not become a nested control. Foundry renders
-visible inline text with a **Secret:** label, without native secret-section
-concealment; book rendering uses static secret styling and the same label.
+so a link inside the content does not become a nested control. Foundry emits a
+focusable inline spoiler: scoped content CSS redacts its text and descendants
+until pointer hover or keyboard focus reveals them. Its focus outline and
+accessible cue identify the reveal interaction. Native Foundry secret sections
+keep their separate controls. Book rendering discards inline `.secret` classes
+and prints their content normally, retaining emphasis, links, anchors and `.name`
+bold styling. Book secret sections and fences retain their visible labelled
+boxes. The span parser's opaque source tokens retain a `secret` boolean from
+their parsed classes for preview presentation.
 `collectAnchors` includes `secret: true` on secret anchors for destination
 presentation. Block and heading secrecy retain their separate scope and
 Foundry permission handling.

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

@@ -40,11 +40,12 @@ Linking to the public note as a whole does not inherit a section's secrecy.
 | Surface | Reference to a secret destination                                                                                                                                      |
 | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Website | An inline show/hide spoiler conceals its label. An omitted GM-only destination produces text without an unusable link. A published secret heading can still be linked. |
-| Foundry | A visible inline spoiler labelled **Secret:** contains the reference. Private pack and page permissions govern whether its destination can be opened.                  |
-| Book    | The reference prints with secret styling and a **Secret:** label. An omitted GM-only destination produces text without a link.                                         |
+| Foundry | A CSS-redacted inline spoiler reveals the reference on hover or keyboard focus. Private pack and page permissions govern whether its destination can be opened.        |
+| Book    | The reference prints normally, preserving emphasis and name styling. An omitted GM-only destination produces text without a link.                                      |
 
-`.show` removes that automatic spoiler presentation on every surface. Where
-the target is unavailable it still produces text without a link.
+`.show` removes automatic spoiler presentation on the website and in Foundry.
+Book references already print normally. Where the target is unavailable the
+reference still produces text without a link.
 
 To intentionally reveal this reference, add `.show` immediately after the link:
 
@@ -251,11 +252,13 @@ reference concealment; an enclosing authored `.secret` still marks its text.
 
 On the website an inline spoiler has a button to show or hide its content.
 It stays within the surrounding sentence, and links inside it can be followed
-after revealing it. Foundry prints a visible inline `secret` span labelled
-**Secret:**; this span does not withhold its text from players. The book prints
-the text with secret styling and a **Secret:** label; printed text cannot be
-interactively concealed.
-These presentations preserve inline emphasis and the `.name` classification.
+after revealing it. Foundry redacts inline `secret` spans with a solid cover;
+hover the span or focus it with the keyboard to reveal its text, links and
+images. A visible focus outline and a spoiler cue identify the interaction.
+This does not change native Foundry secret-section controls. The book ignores
+`.secret` on inline spans and prints their text normally, preserving emphasis,
+links, anchors and `.name` bold styling. Secret sections and `:::secret` fences
+retain their visible labelled boxes.
 
 Published web HTML contains the spoiler's text. Revealing the spoiler or reading
 the page source exposes it; this is presentation, not access control. GM-only
@@ -432,8 +435,40 @@ Janapada
 : Also the land associated with that community.
 ```
 
-The web and Foundry render a definition list with HTML `<dl>`, `<dt>`, and
-`<dd>` elements. The book renders it as a term list.
+To continue the same definition, leave a blank line and indent the next
+paragraph or block by four spaces. For a fenced code block, indent both fences
+and its contents:
+
+````markdown
+Harbour due
+: A toll on every hull that ties up.
+
+    The harbourmaster collects it before unloading begins.
+
+    ```text
+    One hull: two silver pieces.
+    ```
+
+Anchorage
+: A sheltered place where a ship can lie at anchor.
+````
+
+The continuation paragraph and code block belong to the same definition.
+Repeat `:` only when starting a separate definition for the same term, as in
+the first example. The next unindented term starts a new entry.
+
+Definition lists use a dictionary hanging indent in the website, Foundry,
+preview and book. A bold term begins the row, followed by its normally styled
+definition. Short terms share a definition column 150px from the row's left
+edge; browser viewports of 600px or less use 100px. The gap after a term is
+`.75em`, with `.5em` between entries. A long term stays on one line and pushes
+the first definition farther right; wrapped lines return to the common column.
+The book uses the equivalent print dimensions.
+
+HTML surfaces preserve the semantic `<dl class="dictionary">`, `<dt>` and `<dd>`
+elements, with one grouping `<div>` for each term and all its definitions.
+Multiple definitions, continuation paragraphs, nested lists and footnotes keep
+their normal Markdown meaning. Infobox profiles retain their own layout.
 
 ## Lists
 

package/docs/commands.md

@@ -66,6 +66,50 @@ behaviour where they appear below; read the command, not the name.
 
 ---
 
+## Standalone source preview
+
+### `package-build-preview`
+
+**NAME**
+
+Render a Markdown buffer without a content index.
+
+**SYNOPSIS**
+
+`package-build-preview [--dark] [--current-date DATE] [--css] < note.md`
+
+**DESCRIPTION**
+
+Reads Markdown from stdin and writes an HTML fragment. Requires no package
+configuration. Local Markdown and extensions render; constructs needing other
+notes remain highlighted source. Shared CSS is supplied separately.
+
+**OPTIONS**
+
+- `--dark` — select dark mode; light is the default.
+- `--current-date DATE` — override the setting-wide neutral current date; otherwise
+  read the nearest root configuration setting, defaulting to `"720.1"`.
+- `--css` — emit the shared scoped stylesheet without reading stdin.
+- `--help`, `-h` — show usage.
+
+**EXIT STATUS**
+
+0 on success, 1 for an invalid argument or rendering error. Findings go to
+stderr; stdout contains only HTML (or CSS with `--css`).
+
+**EXAMPLES**
+
+```sh
+package-build-preview --dark < note.md > preview.html
+package-build-preview --css > preview.css
+```
+
+**SEE ALSO**
+
+[Source preview and Gitea renderer](source-preview.md), [API](api.md).
+
+---
+
 ## Package and release operations
 
 ### `package-build ci`
@@ -3017,7 +3061,7 @@ exactly as given, at every depth, and every field it leaves out is generated:
 | `data.templatePriority`, `data.occupation`, `data.died` | `null`.                                                                                                                                   |
 | `data.lore`, `data.homes`                               | `[]`.                                                                                                                                     |
 | `data.affiliations`                                     | `{}`.                                                                                                                                     |
-| `data.born`                                             | An adult age of 18 to 60 years before the package's present, as a `<year>.<day>` date; `unknown` where the package states no present.     |
+| `data.born`                                             | An adult age of 18 to 60 years before the configured `currentDate` (default `"720.1"`), as a `<year>.<day>` date.                         |
 | `data.frame`, `data.appearance.*`                       | Weighted draws from the culture's appearance profile; `extra_features` is `[]`.                                                           |
 | `data.height`                                           | From the profile's range for the gender, in feet and inches.                                                                              |
 | `data.weight`                                           | From the height and the frame's body-mass band, in pounds. A spec giving height and weight but no frame gets the frame they imply.        |
@@ -3105,7 +3149,7 @@ dossier: |
   record rather than of reputation.
 ```
 
-Run against a package whose world states `present: "720.300"`, whose
+Run against a package configured with `currentDate: "720.300"`, whose
 `khelathi` culture carries the profile in
 [appearance profiles](reference/format-details.md#appearance-profiles) and
 names `language: skill-khelathilng`, and whose language carries the lists in

package/docs/configuration.md

@@ -54,7 +54,7 @@ around its own evaluation.
 
 ### Quick reference
 
-23 top-level keys. `rootDir` is not one of them — a data configuration never
+24 top-level keys. `rootDir` is not one of them — a data configuration never
 writes it — and is documented under [Derived values](#derived-values) instead,
 alongside `foundryPackage`, `homepage`, `author` and `itemBuilders`, whose
 data-configuration behaviour is also derivation rather than ordinary
@@ -62,6 +62,7 @@ authoring.
 
 | Key                                         | Type                                                                       | Required                                                                                           | Default                   |
 | ------------------------------------------- | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------- |
+| [`currentDate`](#currentdate)               | quoted neutral date string                                                 | no                                                                                                 | `"720.1"`                 |
 | [`contentPackage`](#contentpackage)         | string                                                                     | yes                                                                                                | —                         |
 | [`foundryPackage`](#foundrypackage)         | string                                                                     | yes (`.mjs` only — derived in YAML); refused in a `documentation` package                          | —                         |
 | [`homepage`](#homepage)                     | string                                                                     | no (`.mjs` only — derived in YAML)                                                                 | `null`                    |
@@ -87,7 +88,7 @@ authoring.
 
 Any key outside this list is refused:
 
-> `` `<key>` is not a recognized option (expected one of: rootDir, contentPackage, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog). ``
+> `` `<key>` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog). ``
 
 (`rootDir` appears in that list because it is a key `defineConfig` itself
 accepts — an `.mjs` configuration authors it directly. A YAML configuration
@@ -194,7 +195,7 @@ build writes its `name` as `params.author`. `null` when `authors` is empty.
 as an unknown key, at the key's own line, because `authors` is the one list a
 package names its people in:
 
-> ``package-build config: `author` is not a recognized option (expected one of: rootDir, contentPackage, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog).``
+> ``package-build config: `author` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog).``
 
 `package.json`'s own `author` is npm's and is not read.
 
@@ -294,7 +295,23 @@ Unlike the first three, authoring `itemBuilders` is not an error — it is
 
 ---
 
-## The 22 keys
+## Configuration keys
+
+### `currentDate`
+
+The setting-wide date used for computed ages, age lint, content-index dates,
+Foundry and website output, NPC generation and editor preview. It defaults to
+`"720.1"`. Quote the value so YAML preserves the exact ordinal day digits:
+
+```yaml
+contentPackage: thalorna
+currentDate: "720.130"
+```
+
+Use a neutral `<year>[.<day>[:HHMMSS]]` string. A bare quoted year means its first
+day. Named calendars, `unknown`, numeric YAML values and malformed dates are
+configuration errors located at `currentDate`. Birth dates can still use named
+calendars when the output has the relevant calendar context.
 
 ### `contentPackage`
 

package/docs/design.md

@@ -33,9 +33,10 @@ Concealment and access remain separate decisions. Public site and book builds
 omit GM-only notes; a reference to an omitted destination carries no unusable
 link. Foundry's private packs and page permissions govern destination access.
 Web inline spoilers use a separate show/hide control beside their content, so
-a revealed link is independently usable. Foundry and book inline spoilers are
-visible labelled text; an inline Foundry span has no native secret-section
-permission behavior. A spoiler in published HTML remains readable in the source. See the
+a revealed link is independently usable. Foundry inline spoilers use a CSS
+redaction revealed on hover or keyboard focus; they have no native secret-section
+permission behavior. Books ignore inline `.secret` and preserve normal text
+formatting. A spoiler in published HTML remains readable in the source. See the
 [authoring contract](authoring/links-and-markup.md#references-to-secret-subjects)
 for syntax and surface presentation.
 

package/docs/guides/book.md

@@ -522,12 +522,16 @@ Anchors on headings are scoped to their entries, so two entries can use the
 same heading anchor. The build reports an unresolved destination while
 keeping the source available for inspection.
 
-A reference to a GM-only note or secret heading prints with secret styling
-and a **Secret:** label. GM-only notes remain omitted, and references to them
-print as text without a link. `.show` removes the automatic spoiler presentation
-of that reference, without adding the destination to the book. An authored
-`[text]{.secret}` uses the same static inline styling. Printed text remains
-visible; see [secret references](../authoring/links-and-markup.md#references-to-secret-subjects).
+A reference to a GM-only note or secret heading prints normally. GM-only notes
+remain omitted, and references to them print as text without a link. `.show`
+does not add an omitted destination to the book. Inline `[text]{.secret}` spans
+print as ordinary text, preserving emphasis, links, anchors and `.name` bold
+styling; the book ignores their `.secret` class.
+
+Secret sections and `:::secret` fences keep their visible contents in pale
+lavender boxes (`#f2eefb`) with a purple left border and title (`#5c4b8a`). The
+default title is **! Secret**; a fence can supply its own title. See
+[secret references](../authoring/links-and-markup.md#references-to-secret-subjects).
 
 The [generated sections](../reference/format-details.md#generated-sections)
 an entry carries — **Within**, **Governed by**, **In song and story**, the

package/docs/reference/format-details.md

@@ -1822,11 +1822,12 @@ link to the whole public note does not inherit a section's secrecy.
 
 The website renders an inline show/hide spoiler; an omitted GM-only target
 retains its reference as text without a dead link. A published secret section
-retains its link. Foundry renders a visible inline spoiler with a **Secret:**
-label, with access to its destination controlled by private packs and page
-permissions. Books print secret styling and a **Secret:** label, retaining text
-without a link when the GM-only destination is omitted. `.show` bypasses the
-automatic spoiler presentation on each surface; an unavailable destination
+retains its link. Foundry renders a CSS-redacted inline spoiler, revealed on
+hover or keyboard focus, with destination access controlled by private packs
+and page permissions. Books ignore inline `.secret` presentation and print
+references normally, retaining text without a link when the GM-only destination
+is omitted. `.show` bypasses automatic spoiler presentation on the website and
+in Foundry; book references already print normally. An unavailable destination
 still has no link.
 
 An immediately following `.show` attribute explicitly reveals the reference:
@@ -2667,7 +2668,13 @@ local to a note; rendered markers are sequential numbers. A Foundry page
 collects its referenced footnotes in a Footnotes section at the bottom of that
 JournalEntryPage, while a book places them at the bottom of the page of
 reference. A term followed by `: definition` lines creates a definition list.
-See the [authoring examples](../authoring/links-and-markup.md#footnotes-and-definition-lists).
+After a blank line, indent continuation paragraphs and blocks by four spaces
+to keep them in the same definition; indent a code block's opening fence,
+contents and closing fence. Another `:` starts a separate definition for the
+same term. See the [authoring examples](../authoring/links-and-markup.md#footnotes-and-definition-lists). Definition lists use dictionary hanging indents: bold, nonwrapping terms,
+normal definitions, a 150px shared column (100px at browser widths up to 600px),
+a `.75em` term gap and `.5em` entry spacing. A long term pushes only the first
+definition line beyond the shared column; continuation lines return to it.
 
 ```
 # Heading {#id .class1 .class2 attr="value"}
@@ -3528,11 +3535,13 @@ The exact `.secret` class marks the enclosed text as an inline spoiler:
 ```
 
 The website provides an inline show/hide button and preserves interactive links
-inside the revealed content. Foundry prints a visible inline `secret` span
-with a **Secret:** label; the span does not withhold its text from players.
-The book prints the text with secret styling and a **Secret:** label.
-Inline emphasis and combined `.name` classification survive rendering. Published HTML retains the text, so opening
-the spoiler or inspecting the source reveals it.
+inside the revealed content. Foundry renders a focusable, CSS-redacted inline
+span that reveals its text and nested content on hover or keyboard focus.
+Native Foundry secret sections retain their own controls. Books ignore `.secret`
+on inline spans, preserving their text, emphasis, links, anchors and `.name`
+bold styling. Secret sections and `:::secret` fences keep their visible labelled
+boxes. Published HTML retains the text, so opening the spoiler or inspecting the
+source reveals it.
 
 This span has no effect on a destination's audience. Ordinary wikilinks derive
 spoilers from their resolved destinations; `.show` bypasses that automatic
@@ -4555,7 +4564,7 @@ three fields are built around.
   unrecorded. Both spellings of `died` mean dead.
 - **`age` is optional and is an override.** Written, it wins over anything the
   dates say. Unwritten beside a dated `born`, it is the age that follows from
-  the date and the package's declared present — see below. Unwritten beside
+  the date and the configured current date — see below. Unwritten beside
   `born: unknown` or an absent `born`, the age is unknown.
 
 Most people in a setting do not know their own birth date, so an age beside
@@ -4568,22 +4577,15 @@ read it.
 
 #### The age a dated `born` computes to
 
-A package states the day its setting stops on `data.present`, on its own
-`world` or `celestial` `place` note — see _What a body states about itself_
-under `type: place`. Against that date, a being with a dated `born` and no
-authored `age` compiles the age it implies: the two dates compared, not the
-two years subtracted, so a birthday that falls later in the year than the
-present counts one less than the years alone would say. A package that
-declares no present computes no age and says nothing about it — the same
-silence a package with no calendar mechanism meets.
-
-**An authored `age` beside a dated `born` is expected to agree with what the
-date computes.** Where it does not, `package-build lint` raises a warning
-naming both values, so a stale age left behind after a `born` was corrected
-does not go unnoticed. The warning is silent beside `born: unknown` or an
-absent `born` — there is nothing there to disagree with — and silent wherever
-the package declares no present, for the same reason no age is computed at
-all.
+The root configuration's `currentDate` states the setting's neutral current
+date, defaulting to `"720.1"`. A being with a dated `born` and no authored `age`
+compiles the age implied by those dates. A birthday later in the year counts one
+less than the difference between the years. A year-only birth date uses day one.
+Unknown and absent birth dates supply no computed age.
+
+An authored `age` beside a dated `born` is expected to agree with the configured
+current date. `package-build lint` warns when the values disagree. Authored ages,
+including zero and estimates such as `~34`, remain unchanged in built output.
 
 Use `born:` for a being's birth date.
 
@@ -6989,7 +6991,6 @@ level with no background prints nothing.
 | `year.hoursPerDay`                | `number`                                                                         | How many hours the day divides into                                                                       |
 | `year.minutesPerHour`             | `number`                                                                         | How many minutes the hour divides into                                                                    |
 | `year.secondsPerMinute`           | `number`                                                                         | How many seconds the minute divides into                                                                  |
-| `present`                         | `date`                                                                           | The day the setting stops and play begins                                                                 |
 | `body.diameterKm`                 | `number`                                                                         | The body's diameter, in kilometres                                                                        |
 | `body.orbitalRadiusKm`            | `number`                                                                         | How far it orbits from the body it circles, in kilometres                                                 |
 | `body.orbit`                      | `string`                                                                         | The orbit's shape — `circular` means the cycle never varies                                               |
@@ -7021,7 +7022,6 @@ about the world's year.
 data:
   world: { equatorialCircumferenceKm: 40000, surfaceGravityG: 1.0, axialTiltDegrees: 23.5 }
   year: { days: 365, hoursPerDay: 24, minutesPerHour: 60, secondsPerMinute: 60 }
-  present: 720
 
 # its moon — a note of its own, because a moon is a body and not a property
 data:
@@ -7039,14 +7039,13 @@ else wrote down.
 can say which one a calendar divides; a `moon` with no `year` anywhere is
 refused, because a cycle counted in days has no year to be measured against.
 
-**`present` is the day an age is computed against**, written in the grammar a
-note's dates are written in, so a setting whose present is best said in an era
-says it that way.
+The root configuration's `currentDate` supplies the neutral date used for age
+calculations throughout the setting. Its default is `"720.1"`.
 
 **`world.axialTiltDegrees`, the circumference, the gravity, the moon's diameter
 and its orbital radius are read by nobody.** They are there so a reader knows
 what kind of world this is. What the build consumes is the year, the day's
-divisions, the present, the moon's cycle and epoch, and whether its orbit is
+divisions, the moon's cycle and epoch, and whether its orbit is
 circular and inclined.
 
 #### What a settlement's market supports

package/docs/reference/note-types.md

@@ -885,7 +885,6 @@ Lore records in-world knowledge. A `culture` describes a people; a `custom` desc
 | `data.year.hoursPerDay`                | number                                                            | How many hours the day divides into.                                                                                                                                                |
 | `data.year.minutesPerHour`             | number                                                            | How many minutes the hour divides into.                                                                                                                                             |
 | `data.year.secondsPerMinute`           | number                                                            | How many seconds the minute divides into.                                                                                                                                           |
-| `data.present`                         | a date                                                            | The day the setting stops and play begins — what an age is computed against.                                                                                                        |
 | `data.body.diameterKm`                 | number                                                            | The body's diameter, in kilometres.                                                                                                                                                 |
 | `data.body.orbitalRadiusKm`            | number                                                            | How far the body orbits from the one it circles, in kilometres.                                                                                                                     |
 | `data.body.orbit`                      | string                                                            | The orbit's shape — `circular` means the cycle never varies.                                                                                                                        |