gutterpress 0.10.11 → 0.11.1

package/dist/index.js

@@ -143,15 +143,15 @@ import {
   syncProject,
   testRemoteAccess,
   validateProjectExtensions
-} from "./index-03cqyyyk.js";
+} from "./index-qmvmvetj.js";
 import {
   BUILD_DIAGNOSTIC_CODES
-} from "./index-a0e2253t.js";
+} from "./index-12pvhbyz.js";
 import {
   BuildError,
   DEFAULT_PRINT_OPTS,
   readyProbeExpr
-} from "./index-5dgxeevv.js";
+} from "./index-6n15e1ze.js";
 import {
   AUTO_SNAPSHOT_MESSAGE,
   HISTORY_PAGE_LIMIT,

package/dist/lib/markdown/index.d.ts

@@ -1,6 +1,6 @@
 import { type LayoutWarning } from "./assemble";
 import { type AssetCopy } from "../asset-inline";
-import type { LoadedPlugin } from "./renderer";
+import type { LoadedPlugin, PluginStyleGroup } from "./renderer";
 export type { LayoutWarning } from "./assemble";
 /**
  * THE canonical "which markdown files make up this book, and in what order?"
@@ -36,21 +36,14 @@ export declare function renderChapters(inputDir: string, opts?: {
     styles?: string[];
     files?: string[] | null;
     plugins?: LoadedPlugin[];
-    pluginCss?: string;
     /**
-     * #238 — absolute paths of plugin-declared `styles` files, in plugin load
-     * order (`loadPluginsWithCss`'s `pluginStylePaths`). Inlined through the
-     * SAME pipeline the project's own stylesheets get (`inlineStyles`: fonts/
+     * Each extension's CSS (`loadPluginsWithCss`'s `pluginStyles`), in
+     * `extensions:` list order. Every group is inlined through the SAME
+     * pipeline as the project's own stylesheets (`inlineStyles`: fonts and
      * images embedded, local `@import` followed, print-safety lintable) and
-     * placed in the SAME cascade position the legacy `pluginCss` string
-     * already holds — after core, before the project's own stylesheets.
-     * Absolute paths pass through `inlineStyles` unchanged (`path.resolve` is
-     * a no-op on an already-absolute input), so a plugin's stylesheet
-     * location is independent of `inputDir`. Omitting this (existing
-     * string-only-`css` plugins, or none at all) is a zero-cost, byte-
-     * identical no-op — see the test asserting exactly that.
+     * wrapped in its own cascade layer — see the block below.
      */
-    pluginStylePaths?: string[];
+    pluginStyles?: PluginStyleGroup[];
     /** Wrap each source file for incremental preview pagination. */
     wrapChapters?: boolean;
     /** Add source-file ids to source-mapped preview blocks without wrappers. */
@@ -83,9 +76,8 @@ export declare function renderChaptersToFile(inputDir: string, outDir: string, o
     styles?: string[];
     files?: string[] | null;
     plugins?: LoadedPlugin[];
-    pluginCss?: string;
-    /** #238 — see {@link renderChapters}'s option of the same name. */
-    pluginStylePaths?: string[];
+    /** See {@link renderChapters}'s option of the same name. */
+    pluginStyles?: PluginStyleGroup[];
     /** ARCH finding #4 — see {@link renderChapters}'s option of the same name. */
     onChapterWarnings?: (file: string, warnings: LayoutWarning[]) => void;
     /** See {@link renderChapters}'s options of the same names. */

package/dist/lib/markdown/plugins.d.ts

@@ -1,7 +1,9 @@
 import type { ResolvedExtensionConfig } from "../../schema/manifest.types";
 import type { LoadedPlugin } from "./renderer";
 export type { GutterpressMarkerDeclaration, GutterpressMarkerLabel, GutterpressMarkerTable, GutterpressPlugin, GutterpressPluginMetadata, GutterpressPluginExport, LoadedPlugin, } from "./renderer";
-export { applyPlugins, collectPluginCss, collectPluginStylePaths } from "./renderer";
+export { applyPlugins, collectPluginCss, collectPluginStylePaths, collectPluginStyleGroups } from "./renderer";
+export type { PluginStyleGroup } from "./renderer";
+import { type PluginStyleGroup } from "./renderer";
 /** Test-only mutation seam between snapshot completion and snapshot verification. */
 export declare function __setVendorSnapshotHookForTests(hook?: (sourceRoot: string, snapshotRoot: string) => void | Promise<void>): void;
 export declare function clearVendoredPluginResolver(baseDir: string, packageName: string, version: string): void;
@@ -32,13 +34,16 @@ export declare function loadPlugin(config: ResolvedExtensionConfig, baseDir: str
  */
 export declare function loadPlugins(configs: ResolvedExtensionConfig[], baseDir: string, onError?: (pluginRef: string, error: Error) => void): Promise<LoadedPlugin[]>;
 /** Result of {@link loadPluginsWithCss}: loaded plugins ready for `applyPlugins`
- * plus their concatenated CSS ready for injection into the rendered document. */
+ * plus their CSS, grouped per extension for the renderer. */
 export interface LoadedPluginsWithCss {
     /** `undefined` (not `[]`) when there were no configs to load — matches the
      * `plugins?:` field the renderer options expect, so callers can pass this
      * straight through without an `?? []` at every call site. */
     plugins: LoadedPlugin[] | undefined;
-    pluginCss: string;
+    /** Each extension's CSS — its stylesheet files and `css` export — in load
+     * order, each destined for its own cascade layer (`renderChapters`). `[]`
+     * when no loaded plugin has any. */
+    pluginStyles: PluginStyleGroup[];
     /**
      * #238 — absolute paths of every plugin-declared `styles` file, flattened
      * in plugin load order. `[]` when no loaded plugin declares any (including
@@ -58,7 +63,7 @@ export interface LoadedPluginsWithCss {
  * wiring around it.
  *
  * A `configs` of `undefined`/empty short-circuits WITHOUT calling
- * `loadPlugins` at all (`plugins: undefined`, `pluginCss: ""`) — matching
+ * `loadPlugins` at all (`plugins: undefined`, `pluginStyles: []`) — matching
  * both call sites' prior behavior of never plugin-loading when the manifest
  * declares no plugins.
  */

package/dist/lib/markdown/renderer.d.ts

@@ -260,3 +260,21 @@ export declare function collectPluginCss(plugins: LoadedPlugin[]): string;
  * files are actually read.
  */
 export declare function collectPluginStylePaths(plugins: LoadedPlugin[]): string[];
+/** One extension's CSS, ready for its own cascade layer in the built document. */
+export interface PluginStyleGroup {
+    /** The extension's name, for the comment above its block. */
+    name: string;
+    /** Its cascade layer, `ext.<slug>`, unique within the book. */
+    layer: string;
+    /** Absolute paths of its stylesheet files, in declared order. */
+    paths: string[];
+    /** Its `css` string export, placed after the files. */
+    css?: string;
+}
+/**
+ * Group every plugin's CSS by plugin, in load order, and name each group's
+ * cascade layer after the plugin. The renderer wraps each group in that
+ * layer, so `extensions:` list order IS the cascade order whatever an
+ * extension's own CSS does. Plugins with no CSS are left out.
+ */
+export declare function collectPluginStyleGroups(plugins: LoadedPlugin[]): PluginStyleGroup[];

package/dist/lib/project-scaffold.d.ts

@@ -134,7 +134,7 @@ export interface AdoptFolderOptions {
     title?: string;
     /** Author display name. Optional. */
     author?: string;
-    /** Template whose starter theme/chapter is used. Defaults to `"book"`. */
+    /** Template whose starter chapter is used. Defaults to `"book"`. */
     template?: ProjectTemplateId;
     /** Version-history mode. Defaults to `"local-git"`. */
     versionHistory?: ProjectVersionHistoryMode;

package/dist/{lint-va95zh6j.js → lint-cwb6h2n5.js}

@@ -1,16 +1,16 @@
 import {
   MANIFEST_FILENAMES,
   runLint
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   EXIT_CODES

package/dist/{new-3ex11eyq.js → new-sja9wn5c.js}

@@ -7,16 +7,16 @@ import {
   TARGET_IDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   resolveGhostscript
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import {
   isToolAvailable
 } from "./cli-c41yr7he.js";

package/dist/plugin-spbcem4j.css

@@ -0,0 +1,103 @@
+/* ===========================================================================
+ * {{NAME}} — component stylesheet
+ *
+ * OWNS
+ *   The look of everything `plugin.js` emits: the `@term-box` container, its
+ *   variants and label, and the `[[key term]]` inline span. Every one of
+ *   those looks is driven by a PUBLIC custom property declared at `:root`
+ *   below, so a book can retune this component without touching this file.
+ *
+ * MUST NOT CONTAIN
+ *   - `@page` rules or page geometry. A plugin styles its own components; the
+ *     book's theme owns the page.
+ *   - Bare element selectors (`p`, `table`, `h2`). They would leak this
+ *     plugin's opinions into every book that installs it. Scope every rule
+ *     under a `{{PREFIX}}` class.
+ *   - Any `gp-` class. That prefix is Gutterpress core's.
+ *   - Per-book values. Ship sane defaults; let the book override the tokens.
+ *
+ * THE CASCADE
+ *   Gutterpress wraps this whole extension's CSS in a cascade layer of its
+ *   own (`@layer ext.<name>`), in `extensions:` list order, before the book's
+ *   own stylesheets — so there is nothing to do here. The book's unlayered
+ *   rules beat every rule below at any specificity, which is right: a plugin
+ *   should always be the easiest thing in the book to override. Against a
+ *   look, the manifest's list order decides.
+ * ======================================================================== */
+
+/* -----------------------------------------------------------------------
+ * PUBLIC TOKENS — this component's entire theming surface.
+ *
+ * Declared at `:root` with real defaults so the component looks right in
+ * any book with no setup at all. A book retunes it by resetting these in
+ * its own CSS — either globally, or scoped to one chapter/page/section:
+ *
+ *     #ch-appendix { --{{PREFIX}}term-box-accent: #7a1f1f; }
+ *
+ * Rules below consume them as BARE `var(--x)`, never `var(--x, fallback)`:
+ * the default lives at `:root` exactly once, so there is one place to look
+ * and no second copy to drift.
+ * -------------------------------------------------------------------- */
+:root {
+  --{{PREFIX}}term-box-accent: #2f5d8a;
+  --{{PREFIX}}term-box-bg: #f2f6fa;
+  --{{PREFIX}}term-box-ink: inherit;
+  --{{PREFIX}}term-box-pad: 0.6em 0.9em;
+  --{{PREFIX}}term-box-rule: 3px;
+  --{{PREFIX}}term-box-label-size: 0.78em;
+  --{{PREFIX}}term-box-label-tracking: 0.08em;
+  --{{PREFIX}}term-ink: #2f5d8a;
+  --{{PREFIX}}term-weight: 600;
+}
+
+/* -----------------------------------------------------------------------
+ * The container emitted by `@term-box` (plugin.js's `markers` table).
+ * -------------------------------------------------------------------- */
+.{{PREFIX}}term-box {
+  background: var(--{{PREFIX}}term-box-bg);
+  border-left: var(--{{PREFIX}}term-box-rule) solid var(--{{PREFIX}}term-box-accent);
+  color: var(--{{PREFIX}}term-box-ink);
+  padding: var(--{{PREFIX}}term-box-pad);
+  /* Print hygiene: a callout that splits across a page break reads badly,
+     and a two-line orphan reads worse. Both are the component's business,
+     not the book's. */
+  break-inside: avoid;
+  margin-block: 1em;
+}
+
+.{{PREFIX}}term-box > :first-child { margin-block-start: 0; }
+.{{PREFIX}}term-box > :last-child { margin-block-end: 0; }
+
+/* The label element, present only when the author wrote `label="…"`. */
+.{{PREFIX}}term-box-label {
+  color: var(--{{PREFIX}}term-box-accent);
+  font-size: var(--{{PREFIX}}term-box-label-size);
+  letter-spacing: var(--{{PREFIX}}term-box-label-tracking);
+  text-transform: uppercase;
+  font-weight: 700;
+  margin-block: 0 0.35em;
+}
+
+/* -----------------------------------------------------------------------
+ * Variants. Each one only ever RESETS a public token — it never writes a
+ * second copy of the component's rules. That is what keeps a variant three
+ * lines long instead of thirty, and what lets a book add its own variant
+ * without this file changing.
+ * -------------------------------------------------------------------- */
+.{{PREFIX}}term-box-note {
+  --{{PREFIX}}term-box-accent: #2f5d8a;
+  --{{PREFIX}}term-box-bg: #f2f6fa;
+}
+
+.{{PREFIX}}term-box-warning {
+  --{{PREFIX}}term-box-accent: #9a5b12;
+  --{{PREFIX}}term-box-bg: #fdf6ec;
+}
+
+/* -----------------------------------------------------------------------
+ * The inline span emitted by `[[key term]]` (plugin.js's bespoke rule).
+ * -------------------------------------------------------------------- */
+.{{PREFIX}}term {
+  color: var(--{{PREFIX}}term-ink);
+  font-weight: var(--{{PREFIX}}term-weight);
+}

package/dist/{plugin.test.js-k2r87k04.tpl → plugin.test.js-nw7c84s6.tpl}

@@ -222,11 +222,10 @@ describe("conventions", () => {
     }
   });
 
-  test("the stylesheet keeps all of its rules inside its own cascade layer", () => {
-    // An unlayered rule beats every layered one, including this package's
-    // own — see the header comment in styles/plugin.css.
-    expect(css).toContain("@layer {{SLUG}} {");
-    const outside = css.replace(/@layer\s+[\w-]+\s*\{[\s\S]*\}/m, "");
-    expect(outside).not.toMatch(/^[^*\/\s][^{}]*\{/m);
+  test("the stylesheet declares no cascade layer of its own", () => {
+    // Gutterpress wraps this extension's CSS in `@layer ext.<name>` itself,
+    // in `extensions:` list order — see the header comment in
+    // styles/plugin.css. A layer declared here would only nest inside it.
+    expect(css).not.toMatch(/@layer/);
   });
 });

package/dist/{preflight-q8w6dnjh.js → preflight-maw8h45k.js}

@@ -2,16 +2,16 @@ import {
   executeValidation,
   publishTargetFor,
   reportMissingTools
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   EXIT_CODES

package/dist/{preview-azatsrtp.js → preview-vjwpj4tf.js}

@@ -6,10 +6,10 @@ import {
   runBuild,
   splitOutPath,
   startPreviewServer
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   parseFormat,
@@ -17,8 +17,8 @@ import {
   rejectExtraPositionals,
   rejectUnknownFlags,
   resolvePort
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   BuildError

package/dist/{publish-5tqzepkb.js → publish-spej40gd.js}

@@ -11,17 +11,17 @@ import {
   publishProviderFor,
   resolvePublishFormat,
   runPublish
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   FileTokenStore,
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   EXIT_CODES

package/dist/render.js

@@ -1892,7 +1892,7 @@ ${MARKER_CSS.trim()}
 @layer gp.vocab {
 ${GUTTERPRESS_CSS.trim()}
 }`,
-    pluginCss ? `/* user plugin css */
+    pluginCss ? `/* extension css */
 ${pluginCss.trim()}` : null,
     projectCss ? `/* project css */
 ${projectCss.trim()}` : null

package/dist/{tokens-2sracx1w.css → tokens-7984461t.css}

@@ -30,15 +30,15 @@
  *
  * Two things worth knowing before you edit this:
  *
- *   - These layers are unlayered RELATIVE TO Gutterpress core (which puts its
- *     own CSS in `gp.marker` and `gp.vocab`). So every rule here still beats
- *     core, exactly as it did before layers existed. Declaring an order only
- *     changes how YOUR OWN files settle ties with each other.
+ *   - Gutterpress wraps this whole extension in a cascade layer of its own
+ *     (`ext.<name>`), after core's `gp.marker`/`gp.vocab` and before the
+ *     book's own stylesheets. These layers nest inside it, so declaring an
+ *     order only changes how YOUR OWN files settle ties with each other; the
+ *     book's rules still beat every one of them.
  *
- *   - A rule left OUTSIDE all of these layers is fully unlayered and beats
- *     every layered rule here, at any specificity. That is the one real trap:
- *     adopt the convention per whole sheet, never for a few rules inside an
- *     otherwise plain file.
+ *   - A rule left OUTSIDE all of these layers beats every layered rule here,
+ *     at any specificity. That is the one real trap: adopt the convention
+ *     per whole sheet, never for a few rules inside an otherwise plain file.
  * ------------------------------------------------------------------------ */
 @layer tokens, base, components, templates, pages, book;
 

package/dist/{validate-rp613ejg.js → validate-3ppsdngq.js}

@@ -1,15 +1,15 @@
 import {
   executeAndReport
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   EXIT_CODES

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gutterpress",
-  "version": "0.10.11",
+  "version": "0.11.1",
   "description": "Markdown-to-PDF converter for professional print layout using a native Chromium print engine and Ghostscript.",
   "author": "itlackey",
   "license": "MPL-2.0",

package/dist/plugin-m2w7g47v.css

@@ -1,114 +0,0 @@
-/* ===========================================================================
- * {{NAME}} — component stylesheet
- *
- * OWNS
- *   The look of everything `plugin.js` emits: the `@term-box` container, its
- *   variants and label, and the `[[key term]]` inline span. Every one of
- *   those looks is driven by a PUBLIC custom property declared at `:root`
- *   below, so a book can retune this component without touching this file.
- *
- * MUST NOT CONTAIN
- *   - `@page` rules or page geometry. A plugin styles its own components; the
- *     book's theme owns the page.
- *   - Bare element selectors (`p`, `table`, `h2`). They would leak this
- *     plugin's opinions into every book that installs it. Scope every rule
- *     under a `{{PREFIX}}` class.
- *   - Any `gp-` class. That prefix is Gutterpress core's.
- *   - Per-book values. Ship sane defaults; let the book override the tokens.
- *
- * WHY THE @layer
- *   Gutterpress injects plugin CSS before the book's own stylesheets, and in
- *   CSS an UNLAYERED rule beats a layered one no matter how specific the
- *   layered one is. So an unlayered plugin sheet would quietly outrank every
- *   rule in a book that had adopted the recommended
- *   `@layer tokens, base, components, templates, pages, book;` convention —
- *   the author would edit their own CSS and nothing would happen.
- *
- *   Declaring our own layer fixes that by construction. This sheet loads
- *   first, so `{{SLUG}}` becomes the FIRST (weakest) layer; every layer the
- *   book declares afterwards is appended after it and therefore wins, and the
- *   book's unlayered rules win too. A plugin should always be the easiest
- *   thing in the book to override.
- *
- *   Adopt it for the WHOLE sheet: a rule left outside the layer here is
- *   unlayered, and would beat every rule inside it — including our own.
- * ======================================================================== */
-
-@layer {{SLUG}} {
-  /* -----------------------------------------------------------------------
-   * PUBLIC TOKENS — this component's entire theming surface.
-   *
-   * Declared at `:root` with real defaults so the component looks right in
-   * any book with no setup at all. A book retunes it by resetting these in
-   * its own CSS — either globally, or scoped to one chapter/page/section:
-   *
-   *     #ch-appendix { --{{PREFIX}}term-box-accent: #7a1f1f; }
-   *
-   * Rules below consume them as BARE `var(--x)`, never `var(--x, fallback)`:
-   * the default lives at `:root` exactly once, so there is one place to look
-   * and no second copy to drift.
-   * -------------------------------------------------------------------- */
-  :root {
-    --{{PREFIX}}term-box-accent: #2f5d8a;
-    --{{PREFIX}}term-box-bg: #f2f6fa;
-    --{{PREFIX}}term-box-ink: inherit;
-    --{{PREFIX}}term-box-pad: 0.6em 0.9em;
-    --{{PREFIX}}term-box-rule: 3px;
-    --{{PREFIX}}term-box-label-size: 0.78em;
-    --{{PREFIX}}term-box-label-tracking: 0.08em;
-    --{{PREFIX}}term-ink: #2f5d8a;
-    --{{PREFIX}}term-weight: 600;
-  }
-
-  /* -----------------------------------------------------------------------
-   * The container emitted by `@term-box` (plugin.js's `markers` table).
-   * -------------------------------------------------------------------- */
-  .{{PREFIX}}term-box {
-    background: var(--{{PREFIX}}term-box-bg);
-    border-left: var(--{{PREFIX}}term-box-rule) solid var(--{{PREFIX}}term-box-accent);
-    color: var(--{{PREFIX}}term-box-ink);
-    padding: var(--{{PREFIX}}term-box-pad);
-    /* Print hygiene: a callout that splits across a page break reads badly,
-       and a two-line orphan reads worse. Both are the component's business,
-       not the book's. */
-    break-inside: avoid;
-    margin-block: 1em;
-  }
-
-  .{{PREFIX}}term-box > :first-child { margin-block-start: 0; }
-  .{{PREFIX}}term-box > :last-child { margin-block-end: 0; }
-
-  /* The label element, present only when the author wrote `label="…"`. */
-  .{{PREFIX}}term-box-label {
-    color: var(--{{PREFIX}}term-box-accent);
-    font-size: var(--{{PREFIX}}term-box-label-size);
-    letter-spacing: var(--{{PREFIX}}term-box-label-tracking);
-    text-transform: uppercase;
-    font-weight: 700;
-    margin-block: 0 0.35em;
-  }
-
-  /* -----------------------------------------------------------------------
-   * Variants. Each one only ever RESETS a public token — it never writes a
-   * second copy of the component's rules. That is what keeps a variant three
-   * lines long instead of thirty, and what lets a book add its own variant
-   * without this file changing.
-   * -------------------------------------------------------------------- */
-  .{{PREFIX}}term-box-note {
-    --{{PREFIX}}term-box-accent: #2f5d8a;
-    --{{PREFIX}}term-box-bg: #f2f6fa;
-  }
-
-  .{{PREFIX}}term-box-warning {
-    --{{PREFIX}}term-box-accent: #9a5b12;
-    --{{PREFIX}}term-box-bg: #fdf6ec;
-  }
-
-  /* -----------------------------------------------------------------------
-   * The inline span emitted by `[[key term]]` (plugin.js's bespoke rule).
-   * -------------------------------------------------------------------- */
-  .{{PREFIX}}term {
-    color: var(--{{PREFIX}}term-ink);
-    font-weight: var(--{{PREFIX}}term-weight);
-  }
-}