@heroiclands/package-build 22.21.0 → 22.23.0

package/CHANGELOG.md

@@ -1,5 +1,228 @@
 # @heroiclands/package-build
 
+## 22.23.0
+
+### Minor Changes
+
+**Figures**
+
+- A picture and the words about it are written as one block: the caption is optional, several pictures can share one, and a border is available.
+- Prose refers to a figure by name, in its own note or in another, and reads back its number, its number and caption, or the caption alone.
+- A figure drawn from a map counts as a Map, numbered the same way on every surface.
+- A figure holding one picture opens as an illustrated page in Foundry, with that viewer's own pop-out and zoom.
+
+**Pictures**
+
+- A picture carrying no caption draws no line beneath it, on a page, in a journal or in print.
+- A picture states what it is for, and is drawn at the size that choice gives it — never larger than it was made.
+- A page's hero image is 1792×768, and one of any other size is refused, naming the size to cut it to.
+
+**Art provenance**
+
+- A record saying a file is not machine-generated is published saying so.
+- A package may refuse generated art in its own tree.
+- A package may declare that a dependency's art answers its own addresses, and the book draws the replacement.
+
+**Notes**
+
+- A lore note states the occasions it records, each with a date and an optional recurrence, and publishes the next one due.
+- A note may write a shared field at the position it is being retired from, and the build accepts it with a warning rather than refusing the note.
+
+### Patch Changes
+
+**Item-frontmatter reference**: regenerating the page no longer renders a broken sentence for `affiliation`'s `title`, which now says plainly that a top-level key is refused outright.
+
+## 22.22.0
+
+### Minor Changes
+
+**Diagnostics**
+
+- A dead `#anchor` now fails the website build, matching the compendium build
+  and the link checker — a link that used to publish a dead section quietly now
+  reports it.
+- A note with more than one problem in its body now reports every one of them
+  in a single build, instead of only the first.
+
+**The book**
+
+- A page link in a book now goes where it says, and one into a package the book
+  depends on reaches that package's pages; the address they are built from is
+  `package.json`'s `homepage`, which a book now needs.
+- A note written for the next author — a `markdownlint` pragma, an aside about a
+  quoted notice — no longer appears on the page.
+- A box written inside a GM-only section prints as a box.
+- A box's title prints as written, emphasis included, and one carrying a bracket,
+  a `#` or a `$` no longer stops the book being made.
+- Two captions sharing one id each print their own block once, under their own
+  number.
+- A link that resolves nowhere now fails the book build, as it already fails the
+  compendium and website builds, and the book is still written so the page
+  carrying the link can be found.
+- Markup the book cannot set is reported at the file and line it is written on
+  rather than printed on the page, in a title page and a prose file as well as in
+  a note.
+- A table query that selects no rows now says so, and names the line, where it
+  read `[object Object]`.
+- A link the book cannot resolve names the line and column it is written on.
+
+**Affiliations**
+
+- A rank with no title or no description is now reported instead of shipping, so
+  a member's standing can no longer resolve to a blank on a sheet or a page.
+- A rank level that is not a whole number, and a key a rank does not take, are
+  reported too, each naming the line the rank is written on.
+- Every problem on one rank is reported at once, so a ladder is fixed in a single
+  pass.
+- A rank needs only its level, title and description; the lore note is for a
+  standing that needs more said about it than a description can hold.
+- An affiliation's rank ladder now appears on its page, alongside its offices,
+  ordered by level.
+- A note's `lore`, `parents`, `domains` and `economy` lists now reach the page
+  wherever they are authored, instead of vanishing silently.
+- A being's entry in a body states the rung it stands on — an ordinary member is
+  1, someone cast out is 0 — and an entry that states none is reported.
+- An office is not a rung, so an entry naming a post and no standing is reported
+  with the rest of them.
+- A body that gives two rungs one level is reported on the second, so what a
+  standing is called does not depend on which rung is written first.
+
+**Authoring**
+
+- A note's frontmatter accepts only the documented keys; an unrecognised one is an error at its own line, naming every accepted key and the one it was probably meant to be.
+- A page takes its heading from the note's name, so a homepage stating a title any other way publishes the name its package manifest carries.
+- Active Effects and document flags are read from the game-system block that carries them, so a note stating either outside one ships a document without them.
+- Info boxes, warning boxes and captions can be written again: any note using
+  one failed its build with an error about a secret block it did not contain.
+- A note may now mix boxes, captions and GM-only sections freely, and a box
+  inside a GM-only section stays inside it.
+- A `:::` line that closes nothing says so plainly instead of naming the wrong
+  construct.
+- An image may be sized `full-width`, and a float takes a named corner — both
+  always worked and neither was written down.
+
+**Beings**
+
+- A being's complexion can now hold several values, because a face is weathered
+  and ruddy at once rather than only one of them.
+- Several of them read as one phrase on a sheet or a page — "weathered, ruddy and
+  scarred complexion" — rather than saying the word once per value.
+- A being may be recorded as `nonbinary`, or as having no gender at all, where
+  before only `male`, `female` and `other` were named.
+- A frame is `scant`, `light`, `medium`, `heavy` or `massive`. The reference named
+  a `heavy` frame `large`, which nothing wrote.
+- A being's body and movement are authored under `sohl.system`, and its
+  attributes and skills as `sohl.items` entries; a note writing either
+  elsewhere in the block is reported.
+
+**Actors**
+
+- An `{#appearance}` or `{#dossier}` anchor written on a heading below the top
+  level now fails the build naming the file and the line, instead of compiling
+  a blank appearance or biography with nothing to say why.
+
+**Dates**
+
+- A birth or death date written without quotes is reported where a day's
+  trailing zero could have been lost, naming both days the value could mean. A
+  calendar's epoch and a moon's new day read the same way.
+
+**Definition lists**
+
+- Every package now ships a definition-list style, so a term and its definition
+  line up in two columns with the terms sharing one right edge.
+- A narrow journal window stacks each term above its own definition instead of
+  cramping both into columns, and widening the window restores them.
+- A term is bold wherever it appears, so writing one needs no `**` around it.
+- Infobox rows in the book sit against the same right edge, with space between
+  rows rather than run together.
+
+**Packages**
+
+- `packageBuild.baseStyles: false` declines the shared style for a package that
+  wants the surface entirely to itself.
+
+**Named blocks**
+
+- A `:::secret`, `:::info` or `:::warn` block now takes a title of its own, so a
+  GM passage can say "For the GM" or "If they ask about the harbour" instead of
+  one fixed word.
+- A block also takes an id, classes and other attributes, so a note can link to
+  one and a package can style a particular kind its own way.
+- Without a title a block heads itself **Secret**, **Info** or **Warn**. A
+  warning that used to head "Warning" now heads "Warn", and a secret that used to
+  head "GM note" now heads "Secret"; writing `title="GM note"` keeps the old
+  wording.
+- A secret on a web page now opens with its own title rather than the word
+  "Spoiler", and carries its kind so a site can style it.
+- A block's colours come from a stylesheet rather than from the block itself,
+  so a light panel no longer keeps a light background against dark page text.
+- A misspelled block name is now reported instead of being left in the page as
+  the literal `:::name` an author typed.
+- One malformed block no longer stops every other block in the same note from
+  rendering.
+- A box written inside a GM-only section stays inside it, and a box inside
+  another box says so rather than rendering as a muddle.
+
+**Configuration**
+
+- A `compatibility.verified` build below the package's own `compatibility.minimum`
+  is now reported instead of shipping a manifest that claims a build was verified
+  against a floor it cannot install on.
+- The same check applies to a declared system's and a related package's own
+  `compatibility`, naming the file and line of the offending `verified`.
+
+### Patch Changes
+
+**Lists**
+
+- A list item opened with `- [ ]` or `- [x]` reads as its own words everywhere
+  — on the website, in the compendium, and in the book — never as a checkbox.
+- Writing one that way is reported at its own line, naming the ordinary list
+  it belongs in.
+
+**Footnotes**
+
+- A footnote referenced inside a box or a caption now prints and numbers with
+  the rest of the note instead of showing as literal text.
+- A definition written below the top level of a note is reported, as is a
+  reference nothing defines.
+- A definition no reference uses is reported rather than dropped from the page.
+
+**Named blocks and captions**
+
+- A heading that would open a page of its own is reported when it is written
+  inside a box or a caption.
+
+**Headings**
+
+- A heading carrying classes or attributes beside its anchor now anchors on the
+  anchor alone, so a link written to it resolves on every surface.
+- A Foundry journal and a web page carry a heading's classes and attributes onto
+  the heading, and no surface prints the braces.
+- A heading whose braces hold something other than an attribute block is
+  reported at its own line instead of being typeset.
+- `.secret` on the heading that opens a section makes its Foundry page the
+  GM's alone.
+- A withheld section reads as a spoiler on the web and a labelled block in the
+  book, which conceal it rather than withhold it.
+- A heading refuses `id=`, `class=` and any key beginning `on`, as a named block
+  does, so no note writes an event handler onto a page.
+
+**Page lists**
+
+- A note can now write a page list: name a tag, and the pages carrying it come out as a list of links.
+- The list reaches a reader in Foundry, on the website and in the book alike, from the one directive.
+- A page joins the list by carrying its tag and leaves by losing it, so a landing page stays true as notes are written.
+- A list can print each page's description beside its link, and can be restricted to one note type.
+- A tag that no page carries is reported with the tag it looked for, rather than printing nothing.
+
+**Beings**
+
+- A being's `socialTies` map now builds without the two findings it always
+  produced, so a patron, friend, dependent, acquaintance, rival or nemesis
+  can be written.
+
 ## 22.21.0
 
 ### Minor Changes

package/assets/styles/content-base.css

@@ -0,0 +1,162 @@
+/*
+ * This file is part of the Song of Heroic Lands (SoHL) system for Foundry VTT.
+ * Copyright (c) 2024-2026 Tom Rodriguez ("Toasty") — <toasty@heroiclands.org>
+ *
+ * This work is licensed under the GNU General Public License v3.0 (GPLv3).
+ * You may copy, modify, and distribute it under the terms of that license.
+ *
+ * For full terms, see the LICENSE.md file in the project root or visit:
+ * https://www.gnu.org/licenses/gpl-3.0.html
+ *
+ * SPDX-License-Identifier: GPL-3.0-or-later
+ */
+
+/*
+ * The base stylesheet every package ships, staged into the package root and
+ * named first in the manifest's `styles`.
+ *
+ * It carries only what every package needs for its compiled content to be
+ * legible, which today is the definition list: an infobox emits one, and so
+ * does the ordinary markdown `Term` / `: definition` syntax. A package keeps
+ * its own stylesheet for its own needs and overrides anything here from it.
+ *
+ * `packageBuild.baseStyles: false` declines it.
+ *
+ * **The scope is the content, not the interface.** Foundry styles `dl dt` and
+ * `dl dd` itself, application-wide, and a package stylesheet loads into a later
+ * cascade layer than those rules sit in — so an unscoped `dl` here would
+ * restyle every definition list in Foundry's own chrome and in every other
+ * package's sheets. The four roots are where compiled content renders: a
+ * journal page, a journal entry, an enriched field, and the editor.
+ */
+
+/*
+ * Definition lists, in two states of one style.
+ *
+ * **Wide.** Two columns, the term right-aligned against a fixed gutter so every
+ * term in the list shares one right edge, the definition in the remaining
+ * space. The fixed track is what produces the shared edge; a `max-content`
+ * track cannot, because each row then sizes itself.
+ *
+ * **Narrow.** Stacked, the term above its own definition, with space between
+ * pairs and none between a term and the definition it belongs to.
+ *
+ * **The measurement is the list, not the screen.** A Foundry journal is a
+ * resizable window, usually far narrower than the viewport, so a viewport media
+ * query would hold a journal stacked while the screen said otherwise — or cramp
+ * it into two columns at 300px. `container-type: inline-size` on the `dl` and a
+ * `@container` query on its children measure the list itself, and give the same
+ * two states on a page, in a window and in a sidebar.
+ *
+ * The narrow state is reached by spanning both tracks rather than by changing
+ * the template, because an element cannot query the container it establishes:
+ * the `dl` holds the grid and the container, so only `dt` and `dd` can respond.
+ * Row spacing is the definition's bottom margin rather than the grid's
+ * `row-gap` for the same reason — `row-gap` sits on the `dl`, and the two
+ * states need different values.
+ *
+ * The three tunable values are custom properties, so a package adjusts the term
+ * column, the gutter or the stacking point without copying the rule.
+ */
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) dl {
+    display: grid;
+    /* `minmax(0, …)` keeps the track at its full width wherever there is room
+     * and lets it shrink rather than overflow where there is not. */
+    grid-template-columns: minmax(0, var(--pb-deflist-term-width, 11rem)) 1fr;
+    column-gap: var(--pb-deflist-gutter, 2rem);
+    container-type: inline-size;
+    container-name: pb-deflist;
+}
+
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) dl > dt {
+    grid-column: 1;
+    /* The one rule that holds on every surface, so an author writes the term
+     * and nothing else rather than bolding it by hand. */
+    font-weight: 600;
+    text-align: right;
+    line-height: 1.6;
+    margin: 0;
+}
+
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) dl > dd {
+    grid-column: 2;
+    margin: 0 0 var(--pb-deflist-row-gap, 1.5rem);
+    line-height: 1.6;
+}
+
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) dl > dd:last-child {
+    margin-bottom: 0;
+}
+
+/*
+ * Stacked, below the width two columns need: the term column, the gutter, and
+ * enough left for a definition to read as prose rather than as a word per line.
+ *
+ * Named, so the query resolves against a list this sheet set up rather than
+ * against whichever ancestor container happens to be nearest.
+ */
+@container pb-deflist (max-width: 32rem) {
+    dt {
+        grid-column: 1 / -1;
+        text-align: left;
+    }
+
+    dd {
+        grid-column: 1 / -1;
+    }
+}
+
+/*
+ * Named body blocks. `:::info` and `:::warn` emit a `<section>` carrying the
+ * block's name as its class, so the appearance belongs here rather than in an
+ * inline `style` a consumer cannot override.
+ *
+ * `secret` is deliberately absent: Foundry styles `section.secret` itself and
+ * owns the reveal control on it, and a rule here would fight both.
+ *
+ * Every colour is a custom property, so a package overrides one from its own
+ * sheet without restating the layout.
+ */
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror)
+    :is(section.info, section.warn) {
+    border-left: 3px solid var(--pb-block-edge);
+    background: var(--pb-block-fill);
+    color: var(--pb-block-text, inherit);
+    padding: 0.5em 0.8em;
+    margin: 0.75em 0;
+}
+
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror)
+    :is(section.info, section.warn)
+    > strong:first-child {
+    color: var(--pb-block-edge);
+}
+
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) section.info {
+    --pb-block-edge: #2f6f9f;
+    --pb-block-fill: #eef6fb;
+}
+
+:is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) section.warn {
+    --pb-block-edge: #9a6700;
+    --pb-block-fill: #fff5db;
+}
+
+/*
+ * A light panel keeps a dark foreground whatever the surrounding theme does to
+ * the inherited colour, because the fill does not follow it.
+ */
+@media (prefers-color-scheme: dark) {
+    :is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror)
+        :is(section.info, section.warn) {
+        --pb-block-text: #1b1b1b;
+    }
+
+    :is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) section.info {
+        --pb-block-edge: #1d4f75;
+    }
+
+    :is(.journal-entry-page, .journal-entry-content, .editor-content, .prosemirror) section.warn {
+        --pb-block-edge: #7a5100;
+    }
+}

package/bin/content-commands.mjs

@@ -64,12 +64,14 @@ import {
 import { fetchNavigation, generateHugoConfig, writeHugoConfig } from "../engine/site-config.mjs";
 import { renderItemFieldReference, renderItemFieldsPage } from "../engine/field-reference.mjs";
 import { checkDocLinks, checkDocIndex } from "../engine/docs-checks.mjs";
+import { checkArtSlotSizes } from "../engine/art-fields.mjs";
 import { lintContentTree } from "../engine/content-lint.mjs";
 import { lintNoteStates } from "../engine/stub-lint.mjs";
 import { lintContentCharset } from "../engine/content-charset.mjs";
 import { lintContentHtml } from "../engine/content-html.mjs";
 import { lintContentIcons } from "../engine/content-icons.mjs";
 import { lintContentImages } from "../engine/content-images.mjs";
+import { lintContentTaskLists } from "../engine/content-tasklists.mjs";
 import {
     declaredSystems,
     lintFrontmatter,
@@ -108,6 +110,7 @@ import {
     authoredFrontmatter,
     emitContentIndex,
     indexRecordsFor,
+    isAssetRecord,
     isNoteRecord,
     noteFile,
 } from "../engine/content-index.mjs";
@@ -138,6 +141,7 @@ import { buildMaps, FROM_ALL, MAP_DIR } from "../engine/map-build.mjs";
 import { CHART_HORIZON_DAYS } from "../engine/map-layout.mjs";
 import { GRAPHVIZ_ENGINES } from "../engine/map-graphviz.mjs";
 import { loadMapWorld } from "../engine/map-places.mjs";
+import { encodeAddresses } from "../engine/address-values.mjs";
 
 /**
  * The packs `unpack` extracts.
@@ -1156,6 +1160,13 @@ function lintCommand() {
                     config,
                 });
 
+                // A list item opened with `[ ]` or `[x]` — nothing here is
+                // miscompiled, since every surface sets the marker as the
+                // item's own text and all three agree, so this is advisory.
+                const taskLists = lintContentTaskLists(root, {
+                    skipDirectories: config.skipDirectories,
+                });
+
                 // Whether every empty body is a stub on purpose, and how
                 // finished the tree is. The counts and the oldest drafts are
                 // prose rather than findings: a note nobody has finished is not
@@ -1167,6 +1178,32 @@ function lintCommand() {
                 });
                 for (const line of states.summary) log.info(line);
 
+                // Generated art, when this package declares it carries none.
+                // `records` already holds every asset of this build, so the
+                // check is a filter over the corpus already in hand rather
+                // than a second enumeration of the asset trees.
+                const generatedArt =
+                    config.forbidGeneratedArt ?
+                        records
+                            .filter(isAssetRecord)
+                            .filter((record) => record.asset.ai === true)
+                            .map((record) => ({
+                                file: path.join(config.paths.assets, record.asset.path),
+                                severity: "error",
+                                message:
+                                    `\`${encodeAddresses(record.address.canonical)}\` is ` +
+                                    "machine-generated art (`ai: true`), and " +
+                                    "`forbidGeneratedArt` refuses it in this package",
+                            }))
+                    :   [];
+
+                // A hero image against the size its slot is cut to, read
+                // from the records already in hand.
+                const artSizes = checkArtSlotSizes(records, {
+                    config,
+                    assetsBase: config.paths.assets,
+                });
+
                 const findings = [
                     ...addresses.findings,
                     ...frontmatter.findings,
@@ -1175,7 +1212,10 @@ function lintCommand() {
                     ...icons.findings,
                     ...html.findings,
                     ...images.findings,
+                    ...taskLists.findings,
                     ...states.findings,
+                    ...generatedArt,
+                    ...artSizes,
                 ];
                 // Only an **error** fails the run. Every finding was an error
                 // by then, so this changes nothing on its own —
@@ -1461,14 +1501,20 @@ function linksCommand() {
                     }),
                 );
 
+                // Worded by the shared table, like every finding below it: a
+                // sentence written here is free to describe the same defect
+                // differently from the build that also refuses it, which is the
+                // drift the table exists to prevent.
                 for (const d of deadAnchors) {
                     emitDiagnostic({
                         file: d.note.file,
                         ...positionOfLiteral(d.note.raw, d.text, d.occurrence),
                         severity: "error",
-                        message:
-                            `link [[${d.link}]] points at an anchor no ` +
-                            `heading in ${d.dest.rel} declares`,
+                        message: linkFindingMessage({
+                            reason: "unknown-anchor",
+                            target: d.target,
+                            anchor: d.anchor,
+                        }),
                     });
                 }
                 // Every link is an address and every address must
@@ -1799,6 +1845,15 @@ function siteCommand() {
                 for (const e of result.captionErrors) {
                     emitDiagnostic({ ...e, severity: "error" });
                 }
+                for (const e of result.headingErrors) {
+                    emitDiagnostic({ ...e, severity: "error" });
+                }
+                for (const e of result.footnoteErrors) {
+                    emitDiagnostic({ ...e, severity: "error" });
+                }
+                for (const e of result.embedErrors) {
+                    emitDiagnostic({ ...e, severity: "error" });
+                }
                 // Reported the way the pack build reports the very same
                 // finding: `file:line:column: error: message`, path first, and
                 // the message from the shared table, not a
@@ -1838,8 +1893,11 @@ function siteCommand() {
                     result.expressionErrors.length ||
                     result.secretErrors.length ||
                     result.captionErrors.length ||
+                    result.headingErrors.length ||
+                    result.footnoteErrors.length ||
                     result.wikiErrors.length ||
-                    result.imageErrors.length
+                    result.imageErrors.length ||
+                    result.embedErrors.length
                 ) {
                     process.exitCode = 1;
                     return;
@@ -2172,16 +2230,18 @@ async function fetchFromLocalArtifact(config, argv) {
 
 /**
  * `deps fetch` — fill the caches this build resolves other packages through:
- * the **content index** of every declared dependency, the **item catalogue**
- * of those additionally declaring `itemCatalog: true`, and the **site
- * navigation** heroiclands.org publishes, which the site build writes its
- * menu from.
- *
- * The two dependency sets differ deliberately. Citing another package's
- * *addresses* and embedding its *items* are separate edges, and a package may
- * have either without the other — `harn-ensemble` cites no foreign address and
- * embeds 324,016 item references. The navigation is fetched for every package,
- * because every package publishes a site.
+ * the **content index** of every declared dependency, the **item catalogue
+ * or asset archive** of those additionally declaring `itemCatalog: true` or
+ * `assetArchive: true`, and the **site navigation** heroiclands.org
+ * publishes, which the site build writes its menu from.
+ *
+ * The dependency sets differ deliberately. Citing another package's
+ * *addresses*, embedding its *items*, and staging its *asset bytes* are
+ * separate edges, and a package may declare any of them without the others —
+ * `harn-ensemble` cites no foreign address and embeds 324,016 item
+ * references. The navigation is fetched for every package, because every
+ * package publishes a site. A relationship declaring both `itemCatalog: true`
+ * and `assetArchive: true` is fetched once.
  *
  * Its own command rather than a step of `package compile` or `site`, so that
  * neither reaches the network. A build that downloads silently is not
@@ -2242,7 +2302,7 @@ function depsCommand() {
                 const indexes = await fetchAllMetadata(config);
                 if (indexes) log.info(`Fetched ${indexes} dependency content index(es).`);
                 const count = await fetchAllCatalogs(config);
-                if (count) log.info(`Fetched ${count} dependency catalogue(s).`);
+                if (count) log.info(`Fetched ${count} dependency catalogue(s) or archive(s).`);
                 if (!indexes && !count) {
                     // Distinguished from a package declaring nothing at all: a
                     // relationship may still be declared, just narrowed to the
@@ -2254,8 +2314,8 @@ function depsCommand() {
                     );
                     log.info(
                         declared ?
-                            "No declared dependency needs a fetched content index or item " +
-                                "catalogue."
+                            "No declared dependency needs a fetched content index, item " +
+                                "catalogue, or asset archive."
                         :   "This package declares no dependencies.",
                     );
                 }

package/bin/package-build.mjs

@@ -93,6 +93,7 @@ import { DEPLOY_ROOT } from "../engine/site-config.mjs";
 import { compilesFoundryDocuments } from "../content-config.mjs";
 import { loadPackConfig, packConfigPath, resolveConfigFile } from "../engine/pack-config.mjs";
 import { cleanBuildArtifacts, resetStage, stageAssets } from "../stage.mjs";
+import { baseStyleStageEntry } from "../engine/base-styles.mjs";
 import { buildSchemaArtifact } from "../engine/schema-extract.mjs";
 import { emitCalendarArtifacts } from "../engine/calendar-artifacts.mjs";
 import { dateFromCalendar, dateToCalendar } from "../engine/date-conversion.mjs";
@@ -424,7 +425,7 @@ function assetsCommand() {
         builder: (y) => y,
         handler: handler(async () => {
             const config = loadPackageBuildConfig();
-            if (!config.assets.length) {
+            if (!config.assets.length && !config.baseStyles) {
                 console.log("package-build: no `packageBuild.assets` declared; nothing to stage.");
                 return;
             }
@@ -462,10 +463,22 @@ function assetsCommand() {
                 from,
                 path.join(config.stageDir, to),
             ]);
-            const { entries: count, files } = stageAssets(entries, {
+            let { entries: count, files } = stageAssets(entries, {
                 cwd: config.rootDir,
                 transform,
             });
+
+            // Staged in its own pass, without the repository's transform: the
+            // sheet is this toolchain's file rather than one of the
+            // repository's assets, and a `transform` written to retheme a
+            // package's own SVGs has no business being handed it.
+            if (config.baseStyles) {
+                const staged = stageAssets([baseStyleStageEntry(config.stageDir)], {
+                    cwd: config.rootDir,
+                });
+                count += staged.entries;
+                files += staged.files;
+            }
             console.log(`✅ Static assets staged (${count} entries, ${files} files).`);
         }),
     };