@heroiclands/package-build 22.14.0 → 22.14.2

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @heroiclands/package-build
 
+## 22.14.2
+
+### Patch Changes
+
+Lore notes can carry structured event metadata for chronologies.
+
+## 22.14.1
+
+### Patch Changes
+
+Item-field reference pages generated inside content packages pass note validation and formatting checks.
+
 ## 22.14.0
 
 ### Minor Changes

package/docs/content-format.md

@@ -3453,6 +3453,13 @@ In-world information about people, places, or concepts.
 | `weekdays`      | `{ name, abbreviation? }[]`                                             | The days of the week it names, in order; a calendar with no week writes none      |
 | `seasons`       | `{ name, abbreviation?, monthStart?, monthEnd?, dayStart?, dayEnd? }[]` | The seasons it marks, bounded by month or by day of year                          |
 | `eras`          | `{ shortcode, name, abbreviation?, proclaimedBy?, start, end? }[]`      | The year-counts kept in it, each addressed `<calendar shortcode>.<era shortcode>` |
+| `event`         | `Map<field, value>`                                                     | A dated occurrence, with its sources, locations, reach, and relationships         |
+
+`data.event` is available on every `lore` subType. It holds structured
+chronology metadata, including the event's kind, date, sources, and the places
+it affects. The shared format checks that it is a map; a content package may
+check the details and relationships within that map. It is metadata for
+chronology tools and does not appear as an infobox row.
 
 #### What a calendar note declares
 

package/engine/field-reference.mjs

@@ -36,6 +36,7 @@
 
 import path from "node:path";
 import matter from "gray-matter";
+import { formatNoteFrontmatter } from "./note-format.mjs";
 
 import { authoredFields, runtimeOnlyFields } from "./field-spec.mjs";
 import { loadPackConfig } from "./pack-config.mjs";
@@ -389,7 +390,7 @@ export function shortcodeFromBasename(destination) {
  * The universal keys every note in the format carries: `type: doc`,
  * `subType: reference` — this page is out-of-world lookup material, the same
  * genre as every other generated reference — a `shortcode`, `name.full` from
- * the page's title, and `pack: none`, since the page publishes to the website
+ * the page's title, and `data.pack: none`, since the page publishes to the website
  * and compiles into no compendium document. A consumer's own
  * `docs.itemFields.frontmatter` is deep-merged over it, so it may add keys or
  * override any of the derived ones, `shortcode` included.
@@ -409,7 +410,7 @@ export function itemFieldsEnvelope({ title, shortcode, frontmatter }) {
             subType: "reference",
             shortcode,
             name: { full: title },
-            pack: "none",
+            data: { pack: "none" },
         },
         frontmatter,
     );
@@ -448,5 +449,5 @@ export function renderItemFieldsPage(body, { title, destination, contentRoot, fr
     // between them, so a page written without one fails a consumer's
     // `lint:format` the moment it is committed. Insert it here rather than
     // let the generator and the formatter rewrite the file back and forth.
-    return page.replace(/^(---\n[\s\S]*?\n---\n)/, "$1\n");
+    return formatNoteFrontmatter(page.replace(/^(---\n[\s\S]*?\n---\n)/, "$1\n"));
 }

package/engine/infobox.mjs

@@ -274,6 +274,7 @@ export const NOTE_FIELD_PRESENTATION = Object.freeze({
     bgImage: Object.freeze({ withheld: "an image, which the box never carries" }),
     banner: Object.freeze({ withheld: "an image, which the box never carries" }),
     overlay: Object.freeze({ withheld: "an image, which the box never carries" }),
+    "lore.event": Object.freeze({ withheld: "chronology machinery, not a summary row" }),
 
     assocSkill: Object.freeze({ label: "Skill" }),
     assocAffiliation: Object.freeze({ label: "Affiliation" }),

package/engine/note-vocabulary.mjs

@@ -1189,7 +1189,15 @@ export const NOTE_VOCABULARY = Object.freeze({
         // because `DataFieldSpec` declares the keys a type accepts and not the
         // subType that may write them.
         check: checkCalendarNote,
-        data: CALENDAR_FIELDS,
+        data: Object.freeze([
+            ...CALENDAR_FIELDS,
+            {
+                name: "event",
+                kind: "map",
+                shape: "event metadata map",
+                describe: "A dated occurrence and its relationships to other events and places.",
+            },
+        ]),
     }),
 
     place: Object.freeze({

package/package.json

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

package/types/engine/field-reference.d.mts

@@ -52,7 +52,7 @@ export function shortcodeFromBasename(destination: string): string;
  * The universal keys every note in the format carries: `type: doc`,
  * `subType: reference` — this page is out-of-world lookup material, the same
  * genre as every other generated reference — a `shortcode`, `name.full` from
- * the page's title, and `pack: none`, since the page publishes to the website
+ * the page's title, and `data.pack: none`, since the page publishes to the website
  * and compiles into no compendium document. A consumer's own
  * `docs.itemFields.frontmatter` is deep-merged over it, so it may add keys or
  * override any of the derived ones, `shortcode` included.