gutterpress 0.11.22 → 0.11.23-alpha.2

package/dist/lib/markdown/gutterpress-css.d.ts

@@ -151,7 +151,7 @@
  * carrying gp-left could start shifting; that is standards-tracking per
  * CLAUDE.md ("Chrome wins once it ships"), not a bug in the author's book.
  */
-export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary. One vocabulary, gp-* only \u2014 the\n   pre-vocabulary utility names (.center/.float-left/.float-right/\n   .full-width/.full-bleed) were REMOVED when gp-* shipped; books rename\n   the classes in their markdown (see the migration note). Source ORDER is\n   the contract \u2014 see the doctrine comment above. */\n\n/* flow positions */\n.gp-left {\n  float: left;\n  margin: 0 var(--gp-gap, 1em) var(--gp-gap, 1em) 0;\n  max-width: 50%;\n}\n.gp-right {\n  float: right;\n  margin: 0 0 var(--gp-gap, 1em) var(--gp-gap, 1em);\n  max-width: 50%;\n}\n.gp-center {\n  display: block;\n  float: none;\n  margin-left: auto;\n  margin-right: auto;\n  max-width: 100%;\n}\n.gp-full {\n  display: block;\n  float: none;\n  width: 100%;\n  max-width: 100%;\n}\n@page gp-full-bleed { margin-left: 0; margin-right: 0; }\n.gp-bleed {\n  display: block;\n  float: none;\n  break-before: page;\n  page: gp-full-bleed;\n  max-width: none;\n  width: 100%;\n  margin-left: 0;\n  margin-right: 0;\n}\n\n/* sizes \u2014 AFTER the flow positions so max-width:100% lifts the floats' 50%\n   cap at equal specificity */\n.gp-size-10 { width: 10%; max-width: 100%; }\n.gp-size-20 { width: 20%; max-width: 100%; }\n.gp-size-30 { width: 30%; max-width: 100%; }\n.gp-size-40 { width: 40%; max-width: 100%; }\n.gp-size-50 { width: 50%; max-width: 100%; }\n.gp-size-60 { width: 60%; max-width: 100%; }\n.gp-size-70 { width: 70%; max-width: 100%; }\n.gp-size-80 { width: 80%; max-width: 100%; }\n.gp-size-90 { width: 90%; max-width: 100%; }\n\n/* float clearance presets \u2014 consumed by var(--gp-gap) in the float rules\n   above and by .gp-shape's shape-margin below; --gp-gap itself is\n   author-settable CSS */\n.gp-tight { --gp-gap: 0.5em; }\n.gp-loose { --gp-gap: 2em; }\n\n/* column runs \u2014 plain CSS Multi-column, emitted by the core @columns marker\n   (markers.js): @columns [1-5] ... @end-columns is the ONE way to lay\n   content out in columns, and @column-break moves to the next column.\n   The classes below are the CSS that marker emits, not author vocabulary.\n\n   Permanent vocabulary, not a shim: Chromium implements multicol natively\n   and these rules are the standard properties verbatim, so there is no\n   spec gap here to remove later. Deliberately minimal \u2014 column-fill is\n   NOT set (the CSS initial balance applies).\n   Themes style a run through two tokens instead of writing column rules:\n     --gp-column-gap   default 1.5em\n     --gp-column-rule  default none (any column-rule shorthand value)\n   Both hooks sit at zero specificity (:where), so any author rule wins.\n   .gp-columns is two columns on its own; a count class (bare @columns\n   emits gp-columns-2) wins because it comes later at the same specificity. */\n:where(.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5) {\n  column-gap: var(--gp-column-gap, 1.5em);\n  column-rule: var(--gp-column-rule, none);\n}\n.gp-columns { columns: 2; }\n.gp-columns-1 { columns: 1; }\n.gp-columns-2 { columns: 2; }\n.gp-columns-3 { columns: 3; }\n.gp-columns-4 { columns: 4; }\n.gp-columns-5 { columns: 5; }\n\n/* fragmentation controls \u2014 generic pagination utilities for any element,\n   independent of the column vocabulary above (a book reached for\n   these just as often outside a multicol run: keeping a card whole,\n   forcing a section to start a fresh page). Standard properties only \u2014\n   this project is Chromium-only (CLAUDE.md), so there are no legacy\n   page-break-* twins to also emit. One name each. */\n.gp-no-break { break-inside: avoid; }\n.gp-break-before { break-before: page; }\n\n/* shape wrap \u2014 text follows the image's alpha silhouette instead of its\n   rectangular box. shape-outside only applies to floats, so this is inert\n   without .gp-left/.gp-right (and under .gp-pin, which un-floats). The\n   shape URL cannot be written in CSS (url() contexts can't read attr()),\n   so the image renderer rule (images.ts) mirrors the src into an inline\n   --gp-shape:url(...) custom property whenever it sees this class --\n   authors only ever type the class. threshold 0.2 ignores near-transparent\n   anti-aliasing halos; shape-margin shares the float-gap vocabulary. */\nimg.gp-shape {\n  shape-outside: var(--gp-shape);\n  shape-image-threshold: 0.2;\n  shape-margin: var(--gp-gap, 1em);\n}\n\n/* pin \u2014 within the nearest positioned ancestor (.page/.spread, rule above).\n   The four insets are the pin box: 0 (the text block's edge) unless an\n   engine set --gp-pin-<edge> on the page root for an edge a pin uses (the\n   art-safe line). Non-auto insets and the explicit centers are\n   load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  top: var(--gp-pin-top, 0px);\n  right: var(--gp-pin-right, 0px);\n  bottom: var(--gp-pin-bottom, 0px);\n  left: var(--gp-pin-left, 0px);\n  align-self: center;\n  justify-self: center;\n  margin: 0;\n  max-width: 100%;\n}\n\n/* pin edge modifiers \u2014 AFTER .gp-pin to beat its center defaults;\n   justify-self is inert on in-flow floats, so gp-left/gp-right safely do\n   double duty as flow float + pin edge */\n.gp-top { align-self: start; }\n.gp-bottom { align-self: end; }\n.gp-left { justify-self: start; }\n.gp-right { justify-self: end; }\n\n/* the escape hatch \u2014 the paper's edge, past the printer's safe area: the\n   pin box loses its art-safe insets. Set on the pin itself, so it beats the\n   values the page root hands down. */\n.gp-pin.gp-flush {\n  --gp-pin-top: 0px;\n  --gp-pin-right: 0px;\n  --gp-pin-bottom: 0px;\n  --gp-pin-left: 0px;\n}\n\n/* wrapper-margin neutralization (same pattern and rationale as the\n   .gp-bleed paragraph-margin note in the doctrine comment; for pin, the\n   emptied paragraph would otherwise leave a phantom margin gap in flow) */\n:where(p:has(> img.gp-bleed:only-child)) { margin: 0; }\n:where(p:has(> img.gp-pin:only-child)) { margin: 0; }\n\n/* depth \u2014 a named ladder for z-index, so books stop hand-tuning bare\n   integers. A real book measured 21 z-index declarations using only four\n   distinct values (-1, 0, 1, 2), each written literally at its use site.\n   The custom properties are the author-settable surface (a book needing a\n   deeper stack raises them once); the classes are the shorthand.\n\n   NOT named \"layer\": CSS Paged Media 3 \u00A73.1 already defines \"page layers\"\n   (page background, canvas, borders, contents, margin boxes) and those are\n   parts of the PAGE BOX, not a z-ladder for content. Reusing the word for a\n   different concept would collide with the spec vocabulary this project\n   tracks. The pin EDGE modifiers already own .gp-top/.gp-bottom, so the\n   ladder avoids those words too.\n\n   .gp-behind is the one that earns its place: it puts a pinned image UNDER\n   the page's text, which is otherwise impossible to express without a bare\n   negative z-index. \"Above\" needs no class \u2014 an out-of-flow pin already\n   paints above in-flow content.\n\n   Two things silently defeat .gp-behind, neither visible at the use site:\n     - a stacking context on the .page/.spread ancestor (z-index, isolation,\n       opacity, filter, transform on it traps the negative layer inside).\n       Core keeps .page/.spread at 'position: relative; z-index: auto'\n       precisely so they are not stacking contexts.\n     - a clipping ancestor (overflow other than visible) \u2014 but only where\n       the art actually overhangs that ancestor's clip box on a clipped\n       axis: the overhang is cut off, the same mechanism that clips a\n       .gp-bleed plate back to the wrapper's width. Clipping never reorders\n       layers \u2014 within-bounds art under a clipping .page prints whole and\n       still behind (measured; see the build audit's comment in\n       engine/compiler/build.ts), and a static wrapper's overflow never\n       binds an abspos .gp-pin at all.\n   The build-time engine.layer.trapped audit reports both against the live\n   ancestor chain. printsafe/page-containment is only an early source hint for\n   declarations written directly on .page/.spread. */\n:root {\n  --gp-z-behind: -1;\n  --gp-z-base: 0;\n  --gp-z-raised: 1;\n  --gp-z-front: 2;\n}\n.gp-behind { z-index: var(--gp-z-behind); }\n.gp-base   { z-index: var(--gp-z-base); }\n.gp-raised { z-index: var(--gp-z-raised); }\n.gp-front  { z-index: var(--gp-z-front); }\n\n/* GFM-style alert/callout boxes (#237) \u2014 the DOM gfm-alerts.ts emits from\n   \"> [!TYPE]\" blockquote syntax when a project opts into the bundled\n   gutterpress-gfm-alerts feature (BUILTIN_OPTIONAL_PLUGINS, renderer.ts).\n   The plugin is optional and inert by default; these rules are equally\n   inert wherever the classes never appear, exactly like every other\n   utility above, so shipping them costs nothing to a book that has not\n   turned the feature on.\n\n   This is authored-COMPONENT vocabulary, not the @marker structural family\n   (markers.js/MARKER_CSS) \u2014 CLAUDE.md \u00A76 splits the two core CSS blocks by\n   ROLE, and an author-facing box an author invokes via inline syntax is the\n   same role as every other gp-* utility here, not page/chapter/section DOM.\n\n   Deliberately minimal (CLAUDE.md \"thin over capable\" / the issue's own\n   \"a rule and a label\"): a left border plus a bold label, :where()'d to\n   zero specificity so a theme's own (unlayered) rule for any of these\n   classes wins outright regardless of selector weight \u2014 see the\n   cascade-layers note atop this file. Five semantic accent colors (the same\n   NOTE/TIP/IMPORTANT/WARNING/CAUTION hues GitHub's own alerts use \u2014 a\n   long-established, non-proprietary convention, not DC branding) are\n   exposed as :root custom properties, the same author-settable-surface\n   pattern as the --gp-z-* ladder above: a book retints every alert of one\n   type by overriding a single property, no specificity fight required.\n   --gp-alert-color cascades from the type modifier down to .gp-alert-title\n   through ordinary CSS inheritance (the title is always a DOM descendant of\n   the box), so it is set in exactly five places, not ten. */\n:root {\n  --gp-alert-note-color: #0969da;\n  --gp-alert-tip-color: #1a7f37;\n  --gp-alert-important-color: #8250df;\n  --gp-alert-warning-color: #9a6700;\n  --gp-alert-caution-color: #cf222e;\n}\n:where(.gp-alert) {\n  margin: 1em 0;\n  padding: 0.5em 1em;\n  border-left: 0.25em solid var(--gp-alert-color, currentColor);\n}\n:where(.gp-alert-title) {\n  margin: 0 0 0.5em;\n  font-weight: bold;\n  color: var(--gp-alert-color, inherit);\n}\n:where(.gp-alert-note)      { --gp-alert-color: var(--gp-alert-note-color); }\n:where(.gp-alert-tip)       { --gp-alert-color: var(--gp-alert-tip-color); }\n:where(.gp-alert-important) { --gp-alert-color: var(--gp-alert-important-color); }\n:where(.gp-alert-warning)   { --gp-alert-color: var(--gp-alert-warning-color); }\n:where(.gp-alert-caution)   { --gp-alert-color: var(--gp-alert-caution-color); }\n";
+export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary. One vocabulary, gp-* only \u2014 the\n   pre-vocabulary utility names (.center/.float-left/.float-right/\n   .full-width/.full-bleed) were REMOVED when gp-* shipped; books rename\n   the classes in their markdown (see the migration note). Source ORDER is\n   the contract \u2014 see the doctrine comment above. */\n\n/* flow positions */\n.gp-left {\n  float: left;\n  margin: 0 var(--gp-gap, 1em) var(--gp-gap, 1em) 0;\n  max-width: 50%;\n}\n.gp-right {\n  float: right;\n  margin: 0 0 var(--gp-gap, 1em) var(--gp-gap, 1em);\n  max-width: 50%;\n}\n.gp-center {\n  display: block;\n  float: none;\n  margin-left: auto;\n  margin-right: auto;\n  max-width: 100%;\n}\n.gp-full {\n  display: block;\n  float: none;\n  width: 100%;\n  max-width: 100%;\n}\n@page gp-full-bleed { margin-left: 0; margin-right: 0; }\n.gp-bleed {\n  display: block;\n  float: none;\n  break-before: page;\n  page: gp-full-bleed;\n  max-width: none;\n  width: 100%;\n  margin-left: 0;\n  margin-right: 0;\n}\n\n/* sizes \u2014 AFTER the flow positions so max-width:100% lifts the floats' 50%\n   cap at equal specificity */\n.gp-size-10 { width: 10%; max-width: 100%; }\n.gp-size-20 { width: 20%; max-width: 100%; }\n.gp-size-30 { width: 30%; max-width: 100%; }\n.gp-size-40 { width: 40%; max-width: 100%; }\n.gp-size-50 { width: 50%; max-width: 100%; }\n.gp-size-60 { width: 60%; max-width: 100%; }\n.gp-size-70 { width: 70%; max-width: 100%; }\n.gp-size-80 { width: 80%; max-width: 100%; }\n.gp-size-90 { width: 90%; max-width: 100%; }\n\n/* float clearance presets \u2014 consumed by var(--gp-gap) in the float rules\n   above and by .gp-shape's shape-margin below; --gp-gap itself is\n   author-settable CSS */\n.gp-tight { --gp-gap: 0.5em; }\n.gp-loose { --gp-gap: 2em; }\n\n/* column runs \u2014 plain CSS Multi-column, emitted by the core @columns marker\n   (markers.js): @columns [1-5] ... @end-columns is the ONE way to lay\n   content out in columns, and @column-break moves to the next column.\n   The classes below are the CSS that marker emits, not author vocabulary.\n\n   Permanent vocabulary, not a shim: Chromium implements multicol natively\n   and these rules are the standard properties verbatim, so there is no\n   spec gap here to remove later. Deliberately minimal \u2014 column-fill is\n   NOT set (the CSS initial balance applies).\n   Themes style a run through two tokens instead of writing column rules:\n     --gp-column-gap   default 1.5em\n     --gp-column-rule  default none (any column-rule shorthand value)\n   Both hooks sit at zero specificity (:where), so any author rule wins.\n   .gp-columns is two columns on its own; a count class (bare @columns\n   emits gp-columns-2) wins because it comes later at the same specificity. */\n:where(.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5) {\n  column-gap: var(--gp-column-gap, 1.5em);\n  column-rule: var(--gp-column-rule, none);\n}\n.gp-columns { columns: 2; }\n.gp-columns-1 { columns: 1; }\n.gp-columns-2 { columns: 2; }\n.gp-columns-3 { columns: 3; }\n.gp-columns-4 { columns: 4; }\n.gp-columns-5 { columns: 5; }\n\n/* fragmentation controls \u2014 generic pagination utilities for any element,\n   independent of the column vocabulary above (a book reached for\n   these just as often outside a multicol run: keeping a card whole,\n   forcing a section to start a fresh page). Standard properties only \u2014\n   this project is Chromium-only (CLAUDE.md), so there are no legacy\n   page-break-* twins to also emit. One name each. */\n.gp-no-break { break-inside: avoid; }\n.gp-break-before { break-before: page; }\n\n/* shape wrap \u2014 text follows the image's alpha silhouette instead of its\n   rectangular box. shape-outside only applies to floats, so this is inert\n   without .gp-left/.gp-right (and under .gp-pin, which un-floats). The\n   shape URL cannot be written in CSS (url() contexts can't read attr()),\n   so the image renderer rule (images.ts) mirrors the src into an inline\n   --gp-shape:url(...) custom property whenever it sees this class --\n   authors only ever type the class. threshold 0.2 ignores near-transparent\n   anti-aliasing halos; shape-margin shares the float-gap vocabulary. */\nimg.gp-shape {\n  shape-outside: var(--gp-shape);\n  shape-image-threshold: 0.2;\n  shape-margin: var(--gp-gap, 1em);\n}\n\n/* pin \u2014 within the nearest positioned ancestor (.page/.spread, rule above).\n   The four insets are the pin box: 0 (the text block's edge) unless an\n   engine set --gp-pin-<edge> on the page root for an edge a pin uses (the\n   art-safe line). Non-auto insets and the explicit centers are\n   load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  top: var(--gp-pin-top, 0px);\n  right: var(--gp-pin-right, 0px);\n  bottom: var(--gp-pin-bottom, 0px);\n  left: var(--gp-pin-left, 0px);\n  align-self: center;\n  justify-self: center;\n  margin: 0;\n  max-width: 100%;\n}\n\n/* pin edge modifiers \u2014 AFTER .gp-pin to beat its center defaults;\n   justify-self is inert on in-flow floats, so gp-left/gp-right safely do\n   double duty as flow float + pin edge */\n.gp-top { align-self: start; }\n.gp-bottom { align-self: end; }\n.gp-left { justify-self: start; }\n.gp-right { justify-self: end; }\n\n/* the escape hatch \u2014 the paper's edge, past the printer's safe area: the\n   pin box loses its art-safe insets. Set on the pin itself, so it beats the\n   values the page root hands down. */\n.gp-pin.gp-flush {\n  --gp-pin-top: 0px;\n  --gp-pin-right: 0px;\n  --gp-pin-bottom: 0px;\n  --gp-pin-left: 0px;\n}\n\n/* wrapper-margin neutralization (same pattern and rationale as the\n   .gp-bleed paragraph-margin note in the doctrine comment; for pin, the\n   emptied paragraph would otherwise leave a phantom margin gap in flow) */\n:where(p:has(> img.gp-bleed:only-child)) { margin: 0; }\n:where(p:has(> img.gp-pin:only-child)) { margin: 0; }\n\n/* depth \u2014 a named ladder for z-index, so books stop hand-tuning bare\n   integers. A real book measured 21 z-index declarations using only four\n   distinct values (-1, 0, 1, 2), each written literally at its use site.\n   The custom properties are the author-settable surface (a book needing a\n   deeper stack raises them once); the classes are the shorthand.\n\n   NOT named \"layer\": CSS Paged Media 3 \u00A73.1 already defines \"page layers\"\n   (page background, canvas, borders, contents, margin boxes) and those are\n   parts of the PAGE BOX, not a z-ladder for content. Reusing the word for a\n   different concept would collide with the spec vocabulary this project\n   tracks. The pin EDGE modifiers already own .gp-top/.gp-bottom, so the\n   ladder avoids those words too.\n\n   .gp-behind is the one that earns its place: it puts a pinned image UNDER\n   the page's text, which is otherwise impossible to express without a bare\n   negative z-index. \"Above\" needs no class \u2014 an out-of-flow pin already\n   paints above in-flow content.\n\n   Two things silently defeat .gp-behind, neither visible at the use site:\n     - a stacking context on the .page/.spread ancestor (z-index, isolation,\n       opacity, filter, transform on it traps the negative layer inside).\n       Core keeps .page/.spread at 'position: relative; z-index: auto'\n       precisely so they are not stacking contexts.\n     - a clipping ancestor (overflow other than visible) \u2014 but only where\n       the art actually overhangs that ancestor's clip box on a clipped\n       axis: the overhang is cut off, the same mechanism that clips a\n       .gp-bleed plate back to the wrapper's width. Clipping never reorders\n       layers \u2014 within-bounds art under a clipping .page prints whole and\n       still behind (measured; see the build audit's comment in\n       engine/compiler/build.ts), and a static wrapper's overflow never\n       binds an abspos .gp-pin at all.\n   The build-time engine.layer.trapped audit reports both against the live\n   ancestor chain. printsafe/page-containment is only an early source hint for\n   declarations written directly on .page/.spread. */\n:root {\n  --gp-z-behind: -1;\n  --gp-z-base: 0;\n  --gp-z-raised: 1;\n  --gp-z-front: 2;\n}\n.gp-behind { z-index: var(--gp-z-behind); }\n.gp-base   { z-index: var(--gp-z-base); }\n.gp-raised { z-index: var(--gp-z-raised); }\n.gp-front  { z-index: var(--gp-z-front); }\n\n/* GFM-style alert/callout boxes (#237) \u2014 the DOM gfm-alerts.ts emits from\n   \"> [!TYPE]\" blockquote syntax when a project opts into the bundled\n   gutterpress-gfm-alerts feature (BUILTIN_OPTIONAL_PLUGINS, renderer.ts).\n   The plugin is optional and inert by default; these rules are equally\n   inert wherever the classes never appear, exactly like every other\n   utility above, so shipping them costs nothing to a book that has not\n   turned the feature on.\n\n   This is authored-COMPONENT vocabulary, not the @marker structural family\n   (markers.js/MARKER_CSS) \u2014 CLAUDE.md \u00A76 splits the two core CSS blocks by\n   ROLE, and an author-facing box an author invokes via inline syntax is the\n   same role as every other gp-* utility here, not page/chapter/section DOM.\n\n   Deliberately minimal (CLAUDE.md \"thin over capable\" / the issue's own\n   \"a rule and a label\"): a left border plus a bold label, :where()'d to\n   zero specificity so a theme's own (unlayered) rule for any of these\n   classes wins outright regardless of selector weight \u2014 see the\n   cascade-layers note atop this file. Five semantic accent colors (the same\n   NOTE/TIP/IMPORTANT/WARNING/CAUTION hues GitHub's own alerts use \u2014 a\n   long-established, non-proprietary convention, not DC branding) are\n   exposed as :root custom properties, the same author-settable-surface\n   pattern as the --gp-z-* ladder above: a book retints every alert of one\n   type by overriding a single property, no specificity fight required.\n   --gp-alert-color cascades from the type modifier down to .gp-alert-title\n   through ordinary CSS inheritance (the title is always a DOM descendant of\n   the box), so it is set in exactly five places, not ten. */\n:root {\n  --gp-alert-note-color: #0969da;\n  --gp-alert-tip-color: #1a7f37;\n  --gp-alert-important-color: #8250df;\n  --gp-alert-warning-color: #9a6700;\n  --gp-alert-caution-color: #cf222e;\n}\n:where(.gp-alert) {\n  margin: 1em 0;\n  padding: 0.5em 1em;\n  border-left: 0.25em solid var(--gp-alert-color, currentColor);\n}\n:where(.gp-alert-title) {\n  margin: 0 0 0.5em;\n  font-weight: bold;\n  color: var(--gp-alert-color, inherit);\n}\n:where(.gp-alert-note)      { --gp-alert-color: var(--gp-alert-note-color); }\n:where(.gp-alert-tip)       { --gp-alert-color: var(--gp-alert-tip-color); }\n:where(.gp-alert-important) { --gp-alert-color: var(--gp-alert-important-color); }\n:where(.gp-alert-warning)   { --gp-alert-color: var(--gp-alert-warning-color); }\n:where(.gp-alert-caution)   { --gp-alert-color: var(--gp-alert-caution-color); }\n\n/* Math (the bundled gutterpress-math feature, math.ts): MathJax's own rules\n   for the <mjx-container> SVG output it emits, from its SVG output jax's\n   stylesheet, less the ones for its interactive menu and tooltips. Inert in\n   a book without formulas. */\nmjx-container[jax=\"SVG\"] { direction: ltr; }\nmjx-container[jax=\"SVG\"] > svg { overflow: visible; min-height: 1px; min-width: 1px; }\nmjx-container[jax=\"SVG\"] > svg a { fill: blue; stroke: blue; }\nmjx-container[jax=\"SVG\"][display=\"true\"] { display: block; text-align: center; margin: 1em 0; }\nmjx-container[jax=\"SVG\"][display=\"true\"][width=\"full\"] { display: flex; }\nmjx-container[jax=\"SVG\"][justify=\"left\"] { text-align: left; }\nmjx-container[jax=\"SVG\"][justify=\"right\"] { text-align: right; }\nmjx-container[jax=\"SVG\"] path[data-c], mjx-container[jax=\"SVG\"] use[data-c] { stroke-width: 3; }\nmjx-assistive-mml {\n  position: absolute !important;\n  top: 0px; left: 0px;\n  clip: rect(1px, 1px, 1px, 1px);\n  padding: 1px 0px 0px 0px !important;\n  border: 0px !important;\n  display: block !important;\n  width: auto !important;\n  overflow: hidden !important;\n  user-select: none;\n}\nmjx-assistive-mml[display=\"block\"] { width: 100% !important; }\ng[data-mml-node=\"merror\"] > g { fill: red; stroke: red; }\ng[data-mml-node=\"merror\"] > rect[data-background] { fill: yellow; stroke: none; }\ng[data-mml-node=\"mtable\"] > line[data-line], svg[data-table] > g > line[data-line] { stroke-width: 70px; fill: none; }\ng[data-mml-node=\"mtable\"] > rect[data-frame], svg[data-table] > g > rect[data-frame] { stroke-width: 70px; fill: none; }\ng[data-mml-node=\"mtable\"] > .mjx-dashed, svg[data-table] > g > .mjx-dashed { stroke-dasharray: 140; }\ng[data-mml-node=\"mtable\"] > .mjx-dotted, svg[data-table] > g > .mjx-dotted { stroke-linecap: round; stroke-dasharray: 0,140; }\ng[data-mml-node=\"mtable\"] > g > svg { overflow: visible; }\n";
 /**
  * GP_CLASSES — every class an author may legitimately write with a `gp-`
  * prefix: the `.gp-*` selectors in `GUTTERPRESS_CSS` above, the two

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

@@ -32,6 +32,8 @@ export declare function resolveActiveMarkdownFiles(inputDir: string, configuredF
  */
 export declare function renderChapters(inputDir: string, opts?: {
     title?: string;
+    /** See {@link AssembleBookHtmlOptions.language}. */
+    language?: string;
     /** See {@link AssembleBookHtmlOptions.print}. */
     print?: PrintPadding;
     /** See {@link AssembleBookHtmlOptions.printArea}. */
@@ -73,6 +75,8 @@ export declare function renderChapters(inputDir: string, opts?: {
  */
 export declare function renderChaptersToFile(inputDir: string, outDir: string, opts?: {
     title?: string;
+    /** See {@link AssembleBookHtmlOptions.language}. */
+    language?: string;
     /** See {@link AssembleBookHtmlOptions.print}. */
     print?: PrintPadding;
     /** See {@link AssembleBookHtmlOptions.printArea}. */

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

@@ -0,0 +1,43 @@
+import type MarkdownIt from "markdown-it";
+/**
+ * LaTeX math — `$…$` in a line, `$$…$$` on its own lines — typeset by
+ * MathJax (`mathjax-full`, the same engine arXiv and Wikipedia print with).
+ *
+ * Bundled, OPT-IN markdown feature (`gutterpress-math` in
+ * `BUILTIN_OPTIONAL_PLUGINS`, renderer.ts; "Math" in
+ * `BUNDLED_EXTENSIONS`, extension-specifier.ts), exactly like the Callouts
+ * feature: a book that never lists it renders `$` as the character it is.
+ *
+ * WHY SVG. Each formula is written as a drawing of its own glyphs, so the
+ * PDF needs no math font on the machine that builds it, no stylesheet and
+ * no font files in the project, prints the same everywhere, and is laid
+ * out when the Markdown is rendered — so the live preview paginates exactly
+ * like the printed PDF (docs/native-parity-gate.md). The MathML and HTML
+ * outputs of KaTeX and MathJax fail one or other of those: measured on a
+ * machine with no math font, KaTeX's MathML printed broken fractions, and
+ * its HTML output needs ~20 font files copied into every book.
+ *
+ * The `$` grammar is Pandoc's, as every markdown-it math plugin implements
+ * it (ported from markdown-it-katex, MIT, Copyright (c) 2016 Waylon Flinn,
+ * via markdown-it-mathjax3): an opening `$` is not followed by a space, a
+ * closing one is not preceded by a space and not followed by a digit. That
+ * is what keeps "$5 and $10" prose. It lives here rather than in a
+ * dependency because the table rule (table.ts) must know where a formula
+ * ends, so a `|` inside one does not split the cell — one scanner, two users.
+ *
+ * ERRORS are never silent: a formula MathJax cannot typeset renders in red,
+ * as MathJax does, AND is reported on `env.layoutWarnings` (`math_error`,
+ * with the line), the channel the marker parser uses, so the Problems panel
+ * and `gutterpress validate` name the mistake — "Missing close brace",
+ * "Undefined control sequence \fraction". MathJax's `noerrors` and
+ * `noundefined` packages, which would swallow exactly those, are left out.
+ *
+ * `\newcommand` definitions persist for the rest of the book's render and no
+ * further: the TeX state is created per renderer, so one build cannot see
+ * another's macros. Styling is in `GUTTERPRESS_CSS` (gutterpress-css.ts),
+ * MathJax's own rules for its output.
+ */
+/** Index of the `$` that closes the inline formula opened at `start`; -1 when
+ * it opens none; -2 for an empty `$$`, which is never inline math. */
+export declare function findInlineMathEnd(src: string, start: number, max: number): number;
+export default function gpMath(md: MarkdownIt): void;

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

@@ -319,13 +319,14 @@ export interface LoadedPlugin {
  * error. (attrs/footnote/deflist are NOT here — they are always-on defaults
  * applied unconditionally below.)
  *
- * `gutterpress-gfm-alerts` (#237) is keyed differently from its four
- * siblings: it is not a real npm package, it is Gutterpress's OWN code
- * (gfm-alerts.ts) registered under a name that reads like one, matching the
- * shape "keyed by npm name" is written for. There is nothing to install
- * either way — the lookup below always wins before any npm resolution is
- * attempted (`plugins.ts`'s `loadPlugin`) — so a real npm package never
- * existing under this exact name costs nothing.
+ * `gutterpress-gfm-alerts` (#237) and `gutterpress-math` are keyed
+ * differently from the four markdown-it-* entries: they are not real npm
+ * packages, they are Gutterpress's OWN code (gfm-alerts.ts, math.ts)
+ * registered under names that read like one, matching the shape "keyed by
+ * npm name" is written for. There is nothing to install either way — the
+ * lookup below always wins before any npm resolution is attempted
+ * (`plugins.ts`'s `loadPlugin`) — so a real npm package never existing
+ * under either name costs nothing.
  */
 export declare const BUILTIN_OPTIONAL_PLUGINS: Record<string, GutterpressPlugin>;
 /**
@@ -376,7 +377,9 @@ export declare const BUILTIN_OPTIONAL_PLUGINS: Record<string, GutterpressPlugin>
  *
  * @param customPlugins - Optional array of custom plugins to load
  */
-export declare function createMarkdownRenderer(customPlugins?: LoadedPlugin[]): MarkdownIt;
+export declare function createMarkdownRenderer(customPlugins?: LoadedPlugin[], options?: {
+    language?: string;
+}): MarkdownIt;
 /**
  * Apply loaded plugins to a markdown-it instance.
  *

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

@@ -0,0 +1,46 @@
+import type MarkdownIt from "markdown-it";
+/**
+ * GFM tables, with one change to how a row is split into cells.
+ *
+ * This is markdown-it's own table rule (`lib/rules_block/table.mjs`, MIT,
+ * Copyright (c) 2014 Vitaly Puzrin, Alex Kocharin), re-registered under the
+ * same name with its `escapedSplit` replaced by {@link splitCells}:
+ *
+ *   - markdown-it splits a row at every unescaped `|` BEFORE any inline
+ *     syntax is parsed (the GFM spec's rule), so a `|` inside a code span
+ *     or a formula splits the cell, and the cells past the header's count
+ *     are silently dropped. Here an inline span is opaque to the split: a
+ *     code span always, and a `$…$` formula when the math feature is on
+ *     (math.ts re-registers this rule with its own scanner). `\|` still
+ *     escapes a pipe in plain cell text; inside a span nothing is touched,
+ *     so `\|` in a formula is LaTeX's own `\|`.
+ *   - a row with MORE cells than the header is reported
+ *     (`table_extra_cells` on `env.layoutWarnings`, the channel Gutterpress's
+ *     marker parser uses) instead of losing them without a word.
+ *
+ * Everything else is the upstream rule, verbatim where possible, so a table
+ * renders and paginates exactly as before.
+ */
+/**
+ * Where to resume scanning a row after the span that starts at `start`
+ * (the character there is the span's opening delimiter): just past the
+ * span, or just past the opening delimiter when it opens nothing. Always
+ * greater than `start`.
+ */
+export type SpanScanner = (src: string, start: number, max: number) => number;
+/** The scanners a row is split with, by the character code that opens each span. */
+export type SpanScanners = Readonly<Record<number, SpanScanner>>;
+/** A CommonMark code span: a run of backticks closed by a run of the same length. */
+export declare const scanCodeSpan: SpanScanner;
+/** What core splits with: code spans. The math feature adds `$` (math.ts). */
+export declare const DEFAULT_SPANS: SpanScanners;
+/**
+ * Replace markdown-it's table rule with the span-aware one. Core applies it
+ * with code spans; a feature that adds an inline span (math) applies it
+ * again with its own scanner added, and the later registration wins.
+ * `at` resets the rule's `alt` chains, so upstream's are given again: a
+ * table may interrupt a paragraph.
+ */
+export declare function gpTable(md: MarkdownIt, options?: {
+    spans?: SpanScanners;
+}): void;

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

@@ -0,0 +1,12 @@
+import type MarkdownIt from "markdown-it";
+/**
+ * The quotation marks straight quotes print as — markdown-it's `quotes`
+ * option: outer open, outer close, inner open, inner close — for the book's
+ * language (manifest `language`, a BCP 47 tag). A language not listed gets
+ * the English marks. Only the languages whose convention is settled are
+ * here; add one with its source, not from memory. The desktop's selection
+ * search must fold every mark here; its test reads this table.
+ */
+export declare const QUOTES: Record<string, string | string[]>;
+export declare function quotesFor(language?: string): string | string[];
+export declare function gpTypography(md: MarkdownIt): void;

package/dist/lib/npm-plugin-installer.d.ts

@@ -22,7 +22,7 @@ export interface InstalledNpmPlugin {
     installRoot: string;
     /** Previous same-version directory held until the manifest commits. */
     backupRoot: string | null;
-    /** Folders THIS install created (`plugins/`, `plugins/npm/`, `plugins/npm/<name>/`), outermost first. */
+    /** Folders THIS install created (`extensions/`, `extensions/npm/`, `extensions/npm/<name>/`), outermost first. */
     createdDirs: string[];
     warnings: string[];
 }

package/dist/lib/plugin-vendor.d.ts

@@ -1,5 +1,7 @@
-/** Project-relative folder shared by local and vendored npm plugins. */
-export declare const PLUGINS_DIR = "plugins";
+/** Project-relative folder every extension a book carries lives under: vendored npm copies in `npm/`, imports beside them. */
+export declare const EXTENSIONS_DIR = "extensions";
+/** Where books vendored before 0.11.23 keep their npm copies. Read, never written. */
+export declare const LEGACY_PLUGINS_DIR = "plugins";
 export declare const VENDORED_NPM_DIR = "npm";
 export interface ParsedNpmPluginSpec {
     name: string;
@@ -15,8 +17,14 @@ export declare function isValidNpmPackageName(name: string): boolean;
 /** Parse `name`, `name@selector`, `@scope/name`, or `@scope/name@selector`. */
 export declare function parseNpmPluginSpec(input: string): ParsedNpmPluginSpec;
 export declare function isExactNpmVersion(version: string): boolean;
-/** Root containing one pinned package's private `node_modules` tree. */
+/** Root containing one pinned package's private `node_modules` tree — where an install writes. */
 export declare function vendoredNpmPluginRoot(projectDir: string, name: string, version: string): string;
+/**
+ * Every root a pinned package's copy may live at: the current folder first,
+ * then the one books vendored before 0.11.23 used. Resolution, removal and
+ * pruning all go through this list so they agree on where a copy can be.
+ */
+export declare function vendoredNpmPluginRoots(projectDir: string, name: string, version: string): string[];
 /** npm-compatible package location within a versioned vendor root. */
 export declare function vendoredNpmPluginPackageDir(installRoot: string, name: string): string;
 export declare function toPosixPath(value: string): string;

package/dist/lib/presets.d.ts

@@ -8,7 +8,7 @@ import type { ResolvedConfig } from "../schema/manifest.types";
  * Every preset value is overridable from the manifest, leaf by leaf
  * (resolveConfig's mergeShape; precedence cli > manifest > target > preset).
  */
-export interface VendorPreset extends Omit<ResolvedConfig, "title" | "authors" | "preset" | "targets" | "page"> {
+export interface VendorPreset extends Omit<ResolvedConfig, "title" | "authors" | "language" | "preset" | "targets" | "page"> {
     /** This preset's id: what the manifest's `preset:` names and a resolved config reports. */
     id: PresetId;
     /**

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

@@ -1,7 +1,7 @@
 /** Entries every book ignores, in the order they are appended. */
-export declare const PROJECT_GITIGNORE_ENTRIES: readonly ["dist/", "plugins/npm/"];
+export declare const PROJECT_GITIGNORE_ENTRIES: readonly ["dist/", "extensions/npm/"];
 /**
- * Make sure `<projectDir>/.gitignore` ignores `dist/` and `plugins/npm/`,
+ * Make sure `<projectDir>/.gitignore` ignores `dist/` and `extensions/npm/`,
  * creating the file or appending what is missing. Returns the entries the
  * author's own rules re-include (left alone) so a caller can warn.
  */

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

@@ -6,7 +6,7 @@ import { type CustomPageOptions } from "./page-size.ts";
  * into the binary via `embedded-assets.ts`. `"book"` is the default; the others
  * give non-technical authors a head start for common formats (#29).
  */
-export type ProjectTemplateId = "book" | "zine" | "technical";
+export type ProjectTemplateId = "book" | "zine" | "technical" | "paper";
 /**
  * How (or whether) to put the new project under local version history.
  *
@@ -43,12 +43,10 @@ export interface CreateProjectOptions {
      */
     templateDir?: string;
     /**
-     * Which vendor preset the new book is designed for (ADR 0008). REQUIRED
-     * when scaffolding a built-in template — creation flows make the author
-     * choose; the resolveConfig dtrpg fallback exists for hand-written
-     * manifests, not for tooling. Written into the generated manifest as an
-     * explicit `preset:` line. Ignored with `templateDir`: a saved template's
-     * manifest carries its preset as part of the captured design.
+     * Which preset the new book is designed for (ADR 0008), written into the
+     * generated manifest as an explicit `preset:` line. Optional: left out, the
+     * template's own `preset:` stands (every starter carries one, and a saved
+     * template's manifest carries its preset as part of the captured design).
      */
     preset?: PresetId;
     /**
@@ -137,7 +135,7 @@ export interface AdoptFolderOptions {
  * Adopt an EXISTING folder as a gutterpress project, in place (no new subfolder).
  * Writes a `manifest.yaml` (using the folder's existing top-level `.md` files as
  * `source.files`, or scaffolding a `chapter-01.md` when there are none), copies
- * a starter `styles/book.css`, ensures `dist/` and `plugins/npm/` are gitignored
+ * a starter `styles/book.css`, ensures `dist/` and `extensions/npm/` are gitignored
  * (see `ensureProjectGitignore`), and optionally initialises local version history.
  *
  * NON-DESTRUCTIVE (global never-overwrite rule): refuses if the folder is

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

@@ -1,5 +1,6 @@
+import type { ProjectTemplateId } from "./project-scaffold.ts";
 /** The built-in templates shipped as embedded assets. */
-export declare const BUILT_IN_TEMPLATE_IDS: readonly ["book", "zine", "technical"];
+export declare const BUILT_IN_TEMPLATE_IDS: readonly ["book", "zine", "technical", "paper"];
 /** Author-friendly metadata for one template (built-in or custom). */
 export interface TemplateInfo {
     /** Stable id. For built-ins, the {@link ProjectTemplateId}; for custom, a slug. */
@@ -22,6 +23,10 @@ export interface TemplateInfo {
     /** The `targets:` this template's manifest declares, when it has one. */
     targets?: string[];
 }
+export declare const BUILT_IN_META: Record<ProjectTemplateId, {
+    label: string;
+    description: string;
+}>;
 /**
  * List the built-in templates. The `preset`/`targets` each one starts a book
  * from are read from that template's own embedded manifest — one source of

package/dist/lib/snippets.d.ts

@@ -74,7 +74,8 @@ export declare function deleteSnippet(projectDir: string, fileName: string): Pro
 /**
  * One plugin-declared marker (a "component", `export const markers`) the
  * project can use, with the example snippet the editor inserts for it.
- * Unrelated to the `gutterpress.components` catalog file, which nothing reads.
+ * Unrelated to the `gutterpress.components` catalog file, which the desktop's
+ * class catalog reads for class completions.
  */
 export interface MarkerComponent {
     /** The marker name, without `@` — e.g. `term-box`. */

package/dist/lib/style-resolver.d.ts

@@ -14,8 +14,7 @@ export declare function relDisplay(projectDir: string, absPath: string): string;
  * BOTH the renderer (to `<link>` them) and the editor (to edit them), so they
  * can never disagree. Returns project-relative paths:
  *   1. the manifest `styles:` list, if it has any entries; else
- *   2. the first conventional stylesheet the project actually has
- *      (`FALLBACK_PRIORITY`); else
+ *   2. `styles/book.css`, when the project has it; else
  *   3. the first discovered `.css` anywhere we scan (deterministic); else
  *   4. `[]` — the project has no stylesheet (an honest empty, never a phantom
  *      link to a missing file).

package/dist/manifest-eagfhba6.yaml

@@ -0,0 +1,19 @@
+title: "{{TITLE}}"
+authors:
+  - "{{AUTHOR}}"
+language: en
+source:
+  files:
+    - chapter-01.md
+styles:
+  - styles/book.css
+# A paper prints on US Letter; for A4 set width 595 and height 842.
+page:
+  width: 612
+  height: 792
+extensions:
+  - markdown-it-sup
+  - gutterpress-math
+  # The built-in academic look. Style over it from styles/book.css.
+  - academic
+preset: book

package/dist/{manifest.schema-399bx3vc.json → manifest.schema-t7nx2stg.json}

@@ -11,6 +11,13 @@
       "default": "Document",
       "examples": ["My Book Title", "Technical Documentation", "Game Module"]
     },
+    "language": {
+      "type": "string",
+      "description": "The book's language as a BCP 47 tag. It is the lang of the built HTML, which hyphenation follows, and sets the quotation marks straight quotes print as.",
+      "default": "en",
+      "pattern": "^[a-zA-Z]{2,3}(-[a-zA-Z0-9]{2,8})*$",
+      "examples": ["en", "de", "de-CH", "fr", "pt-BR"]
+    },
     "authors": {
       "type": "array",
       "description": "List of document authors.",
@@ -37,7 +44,7 @@
     },
     "styles": {
       "type": "array",
-      "description": "Project-relative CSS files to <link> into the rendered book, applied in order. If omitted, Gutterpress discovers one: styles/book.css (what `gutterpress new` scaffolds), else four legacy names kept only for pre-existing projects — css/print.css, css/index.css, css/style.css, css/main.css — else the first discovered .css, else none. New projects should set this explicitly or use styles/book.css.",
+      "description": "Project-relative CSS files to <link> into the rendered book, applied in order. If omitted, Gutterpress discovers one: styles/book.css (what `gutterpress new` scaffolds), else the first .css file found in the project root, styles/ or css/, else none. New projects should set this explicitly or use styles/book.css.",
       "items": {
         "type": "string",
         "minLength": 1,
@@ -51,7 +58,7 @@
     },
     "extensions": {
       "type": "array",
-      "description": "Extensions, in load order: markdown-it plugins, looks (stylesheets), component libraries — anything from npm or a folder. Each entry is a specifier: a bundled feature name (markdown-it-mark, markdown-it-sub, markdown-it-sup, markdown-it-abbr, gutterpress-gfm-alerts), a path starting with ./ or ../ (relative to this file), or an npm package name, optionally pinned as name@version. A later entry loads later: its markdown runs after earlier entries' and its CSS wins ties. The project's own `styles` always load after every extension.",
+      "description": "Extensions, in load order: markdown-it plugins, looks (stylesheets), component libraries — anything from npm or a folder. Each entry is a specifier: a bundled name (a markdown feature: markdown-it-mark, markdown-it-sub, markdown-it-sup, markdown-it-abbr, gutterpress-gfm-alerts, gutterpress-math; or a built-in look: clean-book, zine, technical-doc, academic), a path starting with ./ or ../ (relative to this file), or an npm package name, optionally pinned as name@version. A later entry loads later: its markdown runs after earlier entries' and its CSS wins ties. The project's own `styles` always load after every extension.",
       "items": {
         "oneOf": [
           {
@@ -200,17 +207,17 @@
     },
     "page": {
       "type": "object",
-      "description": "Expected page geometry, in POINTS. VALIDATION BOUNDS ONLY — these values do NOT set the trim size. The real PDF page size comes from the CSS `@page` rule in your stylesheet; these numbers are only what the `pdf.print.page-size` check compares the produced PDF against. Set them to the trim size you expect so a CSS mistake gets caught — and note that a bleed-inclusive @page size will legitimately differ from the trim size recorded here.",
+      "description": "Page geometry, in POINTS (1in = 72pt): the trim size the book prints at. The build writes it as the default `@page { size }` unless a stylesheet's own plain `@page` rule sets a size, in which case that rule wins, and the `pdf.print.page-size` check compares the produced PDF against these numbers either way. A bleed-inclusive @page size legitimately differs from the trim recorded here.",
       "properties": {
         "width": {
           "type": "number",
-          "description": "Expected page width in points (1in = 72pt). Validation bound only — the CSS @page rule sets the real width. Preset defaults: dtrpg 621, book 432 (6in).",
+          "description": "Page width in points (1in = 72pt): the trim the book prints at unless a stylesheet's plain @page rule sets its own, and what validation compares against. Preset defaults: dtrpg 621, book 432 (6in).",
           "exclusiveMinimum": 0,
           "examples": [612, 621, 432]
         },
         "height": {
           "type": "number",
-          "description": "Expected page height in points (1in = 72pt). Validation bound only — the CSS @page rule sets the real height. Preset defaults: dtrpg 810, book 648 (9in).",
+          "description": "Page height in points (1in = 72pt): the trim the book prints at unless a stylesheet's plain @page rule sets its own, and what validation compares against. Preset defaults: dtrpg 810, book 648 (9in).",
           "exclusiveMinimum": 0,
           "examples": [792, 810, 648]
         },

package/dist/{new-1pawj2qf.js → new-mhs46pw3.js}

@@ -3,38 +3,38 @@ import {
   EXTENSION_KINDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-ke86zsz6.js";
+} from "./cli-xq6djqbj.js";
 import {
   resolveGhostscript
-} from "./cli-1hxxwbaq.js";
+} from "./cli-evg8sbht.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-8kg0wjdt.js";
+import"./cli-pz4bn98t.js";
 import"./cli-2ppw6q9v.js";
 import"./cli-eyyggect.js";
 import {
   isToolAvailable
 } from "./cli-asap4t1z.js";
-import"./cli-habkc5ng.js";
+import"./cli-a35w7wzg.js";
 import"./cli-v5mp7a6q.js";
 import {
-  PRESETS,
   PRESET_IDS,
   TARGETS,
-  TARGET_IDS
-} from "./cli-zj5xaepv.js";
-import"./cli-ntwqmdnw.js";
-import"./cli-kx4hbnx2.js";
+  TARGET_IDS,
+  loadManifest,
+  resolveConfig
+} from "./cli-sdmv4bba.js";
+import"./cli-pwwfxdgb.js";
+import"./cli-aqh6brew.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-cjftezxr.js";
-import"./cli-1ngqzg8s.js";
+import"./cli-kh8v4vvw.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";
-import"./cli-h3phdstf.js";
+import"./cli-y28j019d.js";
 import"./cli-37x76zdn.js";
 
 // src/commands/new.ts
@@ -52,15 +52,15 @@ var newArgs = {
   },
   prefix: {
     type: "string",
-    description: 'Class/custom-property prefix an extension claims (default: its slug, e.g. "field-notes-"); --kind plugin|theme only'
+    description: 'Class/custom-property prefix an extension claims (default: its slug, e.g. "field-notes-"); --kind plugin|look only'
   },
   description: {
     type: "string",
-    description: "One-line description recorded in the extension's metadata; --kind plugin|theme only"
+    description: "One-line description recorded in the extension's metadata; --kind plugin|look only"
   },
   preset: {
     type: "string",
-    description: `Vendor preset the book is designed for: ${PRESET_IDS.join(", ")} (required; custom also needs --page-width/--page-height)`
+    description: `Preset the book is designed for: ${PRESET_IDS.join(", ")} (default: the template's; custom also needs --page-width/--page-height)`
   },
   author: {
     type: "string",
@@ -192,7 +192,7 @@ async function runExtensionScaffold(kind, name, parentDir, args) {
 var new_default = defineCommand({
   meta: {
     name: "new",
-    description: "Create a new Gutterpress book, plugin or theme from a starter template"
+    description: "Create a new Gutterpress book, plugin or look from a starter template"
   },
   args: newArgs,
   async run({ args, rawArgs }) {
@@ -228,8 +228,8 @@ var new_default = defineCommand({
       template = args.template;
     }
     const preset = typeof args.preset === "string" && args.preset ? args.preset : undefined;
-    if (!preset || !PRESET_IDS.includes(preset)) {
-      console.error(preset ? `Unknown preset "${preset}". Choose one of: ${PRESET_IDS.join(", ")}.` : `A preset is required: --preset <${PRESET_IDS.join("|")}>. ` + `Use "dtrpg" for DriveThruRPG print-on-demand, "book" for a neutral 6x9in trade book, ` + `or "custom" with --page-width/--page-height (points; 72pt = 1in).`);
+    if (preset && !PRESET_IDS.includes(preset)) {
+      console.error(`Unknown preset "${preset}". Choose one of: ${PRESET_IDS.join(", ")}. ` + `"dtrpg" is DriveThruRPG print-on-demand, "book" a neutral 6x9in trade book, ` + `"custom" takes --page-width/--page-height (points; 72pt = 1in).`);
       process.exit(EXIT_CODES.USAGE);
     }
     let targets;
@@ -261,10 +261,11 @@ var new_default = defineCommand({
         customPage,
         versionHistory: args.git === false ? "none" : "local-git"
       });
-      const effectiveTargets = targets ?? [...PRESETS[preset].defaultTargets];
+      const written = resolveConfig({}, await loadManifest(result.projectDir));
       console.log(`Created book: ${result.projectDir}`);
       console.log(`  manifest: ${result.manifestPath}`);
-      console.log(`  publish targets: ${effectiveTargets.length > 0 ? effectiveTargets.join(", ") : "none"}`);
+      console.log(`  preset: ${written.preset}`);
+      console.log(`  publish targets: ${written.targets.length > 0 ? written.targets.join(", ") : "none"}`);
       console.log(`  start writing in: ${result.openFile}`);
       if (result.versionHistory === "local-git") {
         console.log("  version history: enabled (local snapshots)");
@@ -272,7 +273,7 @@ var new_default = defineCommand({
         console.log(`  version history: not enabled (${result.versionHistoryError})`);
       }
       const neededTools = [
-        ...new Set(effectiveTargets.flatMap((id) => TARGETS[id]?.requiredTools ?? []))
+        ...new Set(written.targets.flatMap((id) => TARGETS[id]?.requiredTools ?? []))
       ];
       const missingTools = [];
       for (const tool of neededTools) {

package/dist/{plugins-fr4fnzhb.js → plugins-1sxe0dkz.js}

@@ -8,10 +8,10 @@ import {
   loadPlugins,
   loadPluginsWithCss,
   loadPublishFunction
-} from "./cli-ntwqmdnw.js";
-import"./cli-kx4hbnx2.js";
-import"./cli-cjftezxr.js";
-import"./cli-h3phdstf.js";
+} from "./cli-pwwfxdgb.js";
+import"./cli-aqh6brew.js";
+import"./cli-kh8v4vvw.js";
+import"./cli-y28j019d.js";
 import"./cli-37x76zdn.js";
 export {
   loadPublishFunction,

package/dist/{plugins-g4dgw7mn.js → plugins-2cek4mz1.js}

@@ -8,8 +8,8 @@ import {
   loadPlugins,
   loadPluginsWithCss,
   loadPublishFunction
-} from "./index-4v7e621e.js";
-import"./index-r7jcsk6h.js";
+} from "./index-2bjcghze.js";
+import"./index-5x42amh8.js";
 import"./index-37x76zdn.js";
 export {
   loadPublishFunction,

package/dist/{preflight-ept9q57t.js → preflight-3k2b1x8e.js}

@@ -1,34 +1,33 @@
 import {
   executeValidation,
   reportMissingTools
-} from "./cli-ke86zsz6.js";
-import"./cli-1hxxwbaq.js";
+} from "./cli-xq6djqbj.js";
+import"./cli-evg8sbht.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-8kg0wjdt.js";
+import"./cli-pz4bn98t.js";
 import"./cli-2ppw6q9v.js";
 import"./cli-eyyggect.js";
 import"./cli-asap4t1z.js";
-import"./cli-habkc5ng.js";
+import"./cli-a35w7wzg.js";
 import"./cli-v5mp7a6q.js";
 import {
   publishTargetFor
-} from "./cli-zj5xaepv.js";
-import"./cli-ntwqmdnw.js";
+} from "./cli-sdmv4bba.js";
+import"./cli-pwwfxdgb.js";
 import {
   log
-} from "./cli-kx4hbnx2.js";
+} from "./cli-aqh6brew.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-cjftezxr.js";
-import"./cli-1ngqzg8s.js";
+import"./cli-kh8v4vvw.js";
 import {
   BuildError,
   EXIT_CODES
 } from "./cli-46ycxe6r.js";
-import"./cli-h3phdstf.js";
+import"./cli-y28j019d.js";
 import"./cli-37x76zdn.js";
 
 // src/commands/preflight.ts