gutterpress 0.11.20-alpha.4 → 0.11.20-beta.1

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

@@ -18,7 +18,7 @@
  * Also ships the author-facing `gp-*` image/block vocabulary (CLAUDE.md §0 —
  * a behavior broadly useful to non-technical authors belongs in core, not a
  * project layer). markdown-it-attrs is bundled by
- * default (renderer.ts), so `![Art](x.jpg){.gp-right .gp-small}` already
+ * default (renderer.ts), so `![Art](x.jpg){.gp-right .gp-size-30}` already
  * attaches the classes to the rendered `<img>` — these rules are what make
  * them actually do something print-safe. One vocabulary, no aliases: there
  * is no duplicate way to spell each layout (the desktop editor rewrites the
@@ -29,11 +29,11 @@
  *   .gp-right     — floats right, text wraps.
  *   .gp-center    — centers a block element.
  *   .gp-full      — fills the page's content width.
- *   .gp-small     — width 25% of the column. Sizes compose with any
- *   .gp-medium    — width 50%.        position (including .gp-pin, where
- *   .gp-large     — width 60%.        the % resolves against the page
- *   .gp-xl        — width 80%.        root: the page box, reaching the
- *   .gp-xxl       — width 90%.        paper on an edge a pin uses).
+ *   .gp-size-10 … .gp-size-90
+ *                 — width 10% … 90% of the column, in 10% steps. Sizes
+ *                   compose with any position (including .gp-pin, where
+ *                   the % resolves against the page root: the page box,
+ *                   reaching the paper on an edge a pin uses).
  *                   There is no 100% step: that is .gp-full, a position.
  *   .gp-tight     — float/shape clearance 0.5em (sets --gp-gap; default 1em).
  *   .gp-loose     — float/shape clearance 2em (sets --gp-gap).
@@ -132,7 +132,7 @@
  * is pinned. The pin's containing
  * block is the root's padding box, and the engine sets `--gp-pin-<edge>` on
  * the root to the art-safe line's distance from the sheet edge (the bleed
- * plus page.artSafe on the top, bottom and outside edge; page.safe at the
+ * plus page.artSafe on the top, bottom and outside edge; page.gutter at the
  * binding, from the manifest); `.gp-pin` reads them as its four insets.
  * `.gp-flush` zeroes them on the pin: the paper's edge. Under plain
  * markdown-it nothing sets them and every inset is 0.
@@ -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-small { width: 25%; max-width: 100%; }\n.gp-medium { width: 50%; max-width: 100%; }\n.gp-large { width: 60%; max-width: 100%; }\n.gp-xl { width: 80%; max-width: 100%; }\n.gp-xxl { 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";
 /**
  * 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/page-size.d.ts

@@ -37,7 +37,8 @@ export declare function isPositivePoints(value: unknown): value is number;
 /**
  * Write the manifest's `page:` bounds. `tolerance` defaults to whatever the
  * block already carries, so re-sizing a book never silently resets a
- * hand-tuned tolerance.
+ * hand-tuned tolerance. The block's other keys stay as written; a `page:`
+ * that is not a map is replaced.
  */
 export declare function writePageBounds(doc: Document, page: CustomPageOptions): void;
 /** The size (points) a choice means: `custom` brings its own, the others are the preset's. */
@@ -59,8 +60,9 @@ export declare function readPageSetup(projectDir: string): Promise<PageSetup>;
 /**
  * Change a book's page size: the manifest's `preset:` + `page:` bounds and the
  * stylesheet's `@page` size, together. Mirrors what the wizard records —
- * `dtrpg` / `book` carry their own bounds (any `page:` block is removed so it
- * cannot shadow them), `custom` records the typed trim. Nothing is written
+ * `dtrpg` / `book` carry their own bounds (the `page:` block's width, height
+ * and tolerance are removed so they cannot shadow them; its print-area keys
+ * stay), `custom` records the typed trim. Nothing is written
  * unless the whole choice validates and the stylesheet parses.
  */
 export declare function setPageSetup(projectDir: string, choice: PageSizeChoice): Promise<PageSetup>;

package/dist/{manifest.schema-13dfax80.json → manifest.schema-c4wfpg6g.json}

@@ -228,15 +228,21 @@
         },
         "safe": {
           "type": "number",
-          "description": "The TEXT rule, in points: how far inside the trim glyphs must stay, on every edge. For DriveThruRPG it is the \"text at least 0.5in inside the trim\" rule. The preview's overlay outlines it (dashed) and flags text outside it, and the `pdf.print.safe-margins` check fails a PDF whose text is closer. An image pinned to the binding edge (`.gp-pin`) sits on it, and to any edge where `artSafe` is not set; no book CSS moves it. Preset default: dtrpg 36 (0.5in), book 18 (0.25in); custom none.",
+          "description": "The TEXT rule, in points: how far inside the trim glyphs must stay, on every edge (the binding edge too, unless `gutter` is set). For DriveThruRPG it is the \"text at least 0.5in inside the trim\" rule. The preview's overlay outlines it (dashed) and flags text outside it, and the `pdf.print.safe-margins` check fails a PDF whose text is closer. An image pinned to an edge (`.gp-pin`) where `artSafe` is not set sits on it; no book CSS moves it. Preset default: dtrpg 36 (0.5in), book 18 (0.25in); custom none.",
           "minimum": 0,
           "examples": [18, 36]
         },
         "artSafe": {
           "type": "number",
-          "description": "The ART rule, in points: how far inside the trim art that does not bleed (images, backgrounds, borders, rules) must stay on the top, bottom and OUTER edge; at the binding edge art uses `safe`. For DriveThruRPG it is the \"non-bleeding art at least 0.25in from the outside edges (0.5in at the binding)\" rule. Art that runs out to the page's edge is a bleed and is not judged on that edge. The preview's overlay outlines it (dotted) and flags art outside it, and an image pinned to the top, bottom or outer edge (`.gp-pin`) sits on it unless it carries `.gp-flush`. Absent = the same as `safe`. Preset default: dtrpg 18 (0.25in); book and custom none.",
+          "description": "The ART rule, in points: how far inside the trim art that does not bleed (images, backgrounds, borders, rules) must stay on the top, bottom and OUTER edge; at the binding edge art uses `gutter`. For DriveThruRPG it is the \"non-bleeding art at least 0.25in from the outside edges (0.5in at the binding)\" rule. Art that runs out to the page's edge is a bleed and is not judged on that edge. The preview's overlay outlines it (dotted) and flags art outside it, and an image pinned to the top, bottom or outer edge (`.gp-pin`) sits on it unless it carries `.gp-flush`. Absent = the same as `safe`. Preset default: dtrpg 18 (0.25in); book and custom none.",
           "minimum": 0,
           "examples": [18]
+        },
+        "gutter": {
+          "type": "number",
+          "description": "The binding allowance, in points: how far content stays from the spine, measured from the trim at the binding edge (the left edge of a right-hand page, the right edge of a left-hand one). It stands in for `safe` there, for text and for art alike: the preview's overlay draws and judges that edge against it, the `pdf.print.safe-margins` check fails text closer to the spine than it, and an image pinned to the binding edge (`.gp-pin`) sits on it. The other edges keep `safe` and `artSafe`. Use it when your book keeps its text further from the spine than the printer's minimum: the Field Guide keeps 0.75in (54) where DriveThruRPG asks for 0.5in. Absent = the same as `safe`. Presets leave it unset.",
+          "minimum": 0,
+          "examples": [54]
         }
       }
     },

package/dist/{new-s4f0tnya.js → new-zwfmqf9t.js}

@@ -7,17 +7,17 @@ import {
   TARGET_IDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-0ey902sx.js";
+} from "./cli-4d25xvs2.js";
 import {
   resolveGhostscript
-} from "./cli-h4tfmpg3.js";
+} from "./cli-tsdrvrff.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-fmksazej.js";
+} from "./cli-gxqxn3sf.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-61vd4ews.js";
+import"./cli-cyej3p9v.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";

package/dist/{preflight-7ck4rbsq.js → preflight-pfhbrhdb.js}

@@ -2,17 +2,17 @@ import {
   executeValidation,
   publishTargetFor,
   reportMissingTools
-} from "./cli-0ey902sx.js";
+} from "./cli-4d25xvs2.js";
 import {
   log
-} from "./cli-h4tfmpg3.js";
+} from "./cli-tsdrvrff.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-fmksazej.js";
+} from "./cli-gxqxn3sf.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-61vd4ews.js";
+import"./cli-cyej3p9v.js";
 import {
   BuildError,
   EXIT_CODES

package/dist/preview/file-watcher.d.ts

@@ -53,6 +53,7 @@ export declare function generateAndWriteHtml(inputPath: string, tempDir: string,
         bleed?: number;
         safe?: number;
         artSafe?: number;
+        gutter?: number;
     };
     preset?: string;
     spec?: PrintSpec;

package/dist/{preview-j91sxadd.js → preview-6bc098rf.js}

@@ -6,10 +6,10 @@ import {
   runBuild,
   splitOutPath,
   startPreviewServer
-} from "./cli-0ey902sx.js";
+} from "./cli-4d25xvs2.js";
 import {
   log
-} from "./cli-h4tfmpg3.js";
+} from "./cli-tsdrvrff.js";
 import {
   UsageError,
   parseFormat,
@@ -17,9 +17,9 @@ import {
   rejectExtraPositionals,
   rejectUnknownFlags,
   resolvePort
-} from "./cli-fmksazej.js";
+} from "./cli-gxqxn3sf.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-61vd4ews.js";
+import"./cli-cyej3p9v.js";
 import {
   BuildError
 } from "./cli-46ycxe6r.js";

package/dist/{publish-f12xaenm.js → publish-pev62kc6.js}

@@ -11,18 +11,18 @@ import {
   publishProviderFor,
   resolvePublishFormat,
   runPublish
-} from "./cli-0ey902sx.js";
+} from "./cli-4d25xvs2.js";
 import {
   FileTokenStore,
   log
-} from "./cli-h4tfmpg3.js";
+} from "./cli-tsdrvrff.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-fmksazej.js";
+} from "./cli-gxqxn3sf.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-61vd4ews.js";
+import"./cli-cyej3p9v.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";

package/dist/render.js

@@ -1229,11 +1229,15 @@ var GUTTERPRESS_CSS = `
 
 /* sizes — AFTER the flow positions so max-width:100% lifts the floats' 50%
    cap at equal specificity */
-.gp-small { width: 25%; max-width: 100%; }
-.gp-medium { width: 50%; max-width: 100%; }
-.gp-large { width: 60%; max-width: 100%; }
-.gp-xl { width: 80%; max-width: 100%; }
-.gp-xxl { width: 90%; max-width: 100%; }
+.gp-size-10 { width: 10%; max-width: 100%; }
+.gp-size-20 { width: 20%; max-width: 100%; }
+.gp-size-30 { width: 30%; max-width: 100%; }
+.gp-size-40 { width: 40%; max-width: 100%; }
+.gp-size-50 { width: 50%; max-width: 100%; }
+.gp-size-60 { width: 60%; max-width: 100%; }
+.gp-size-70 { width: 70%; max-width: 100%; }
+.gp-size-80 { width: 80%; max-width: 100%; }
+.gp-size-90 { width: 90%; max-width: 100%; }
 
 /* float clearance presets — consumed by var(--gp-gap) in the float rules
    above and by .gp-shape's shape-margin below; --gp-gap itself is
@@ -1431,11 +1435,15 @@ var GP_CLASSES = new Set([
   "gp-center",
   "gp-full",
   "gp-bleed",
-  "gp-small",
-  "gp-medium",
-  "gp-large",
-  "gp-xl",
-  "gp-xxl",
+  "gp-size-10",
+  "gp-size-20",
+  "gp-size-30",
+  "gp-size-40",
+  "gp-size-50",
+  "gp-size-60",
+  "gp-size-70",
+  "gp-size-80",
+  "gp-size-90",
   "gp-tight",
   "gp-loose",
   "gp-columns",
@@ -1537,10 +1545,10 @@ import markdownItAttrs from "markdown-it-attrs";
 import markdownItFootnote from "markdown-it-footnote";
 
 // src/lib/markdown/gp-pin-scope.js
-function warn2(env, line, type, message, marker) {
+function warn2(env, line, type, message, severity) {
   if (!env.layoutWarnings)
     env.layoutWarnings = [];
-  env.layoutWarnings.push({ line, type, message, marker });
+  env.layoutWarnings.push(severity ? { line, type, message, severity } : { line, type, message });
 }
 function editDistance2(a, b) {
   let prev = Array.from({ length: b.length + 1 }, (_, j) => j);
@@ -1583,7 +1591,7 @@ function checkFlushArt(token, env, line) {
     return;
   if (!classes.some((c) => PIN_EDGES.includes(c)))
     return;
-  warn2(env, line, "flush_art", FLUSH_ART_MSG);
+  warn2(env, line, "flush_art", FLUSH_ART_MSG, "info");
 }
 function elementNameFor(token) {
   switch (token.type) {
@@ -2387,6 +2395,7 @@ function printAreaMeta(page) {
     bleed: page.bleed ?? 0,
     safe: page.safe ?? 0,
     artSafe: page.artSafe,
+    gutter: page.gutter,
     preset: page.preset,
     spec: page.spec
   });

package/dist/schema/manifest.types.d.ts

@@ -178,22 +178,34 @@ export interface GutterpressManifest {
         bleed?: number;
         /**
          * The TEXT rule (pt): glyphs stay at least this far inside the trim on
-         * EVERY edge — DriveThruRPG's "keep text 0.5in inside the trim" (`dtrpg`
-         * sets 36). The preview's overlay outlines it and flags text outside it,
-         * and `pdf.print.safe-margins` fails a built PDF whose text is closer. An
-         * image pinned to the binding edge sits on it (and to any edge, where
-         * `artSafe` is not set); nothing in a book's CSS moves it.
+         * EVERY edge, the binding edge too unless the book sets a `gutter` —
+         * DriveThruRPG's "keep text 0.5in inside the trim" (`dtrpg` sets 36). The
+         * preview's overlay outlines it and flags text outside it, and
+         * `pdf.print.safe-margins` fails a built PDF whose text is closer. An
+         * image pinned to an edge where `artSafe` is not set sits on it; nothing
+         * in a book's CSS moves it.
          */
         safe?: number;
         /**
          * The ART rule (pt): art that does not bleed — images, backgrounds,
          * borders, rules — stays at least this far inside the trim on the top,
-         * bottom and OUTER edge; at the binding edge it uses `safe`. DriveThruRPG's
+         * bottom and OUTER edge; at the binding edge it uses `gutter`. DriveThruRPG's
          * "keep non-bleeding art 0.25in from the outside edges" (`dtrpg` sets 18).
          * An image pinned to the top, bottom or outer edge (`.gp-pin`) sits on this
          * line unless it carries `.gp-flush`. Absent = the same as `safe`.
          */
         artSafe?: number;
+        /**
+         * The binding allowance (pt): how far content stays from the spine — the
+         * binding edge, the left of a right-hand page and the right of a left-hand
+         * one — measured from the trim. It stands in for `safe` at the binding
+         * edge, for text and for art alike, so a book that keeps its text further
+         * from the spine than the printer's minimum says so here, not in its CSS
+         * (the Field Guide keeps 0.75in = 54 where DriveThruRPG asks for 0.5in).
+         * An image pinned to the binding edge sits on it. The other edges keep
+         * `safe` and `artSafe`. Absent = the same as `safe`; presets leave it unset.
+         */
+        gutter?: number;
     };
     ink?: {
         maxTac?: number;
@@ -327,6 +339,8 @@ export interface ResolvedConfig {
         safe?: number;
         /** The art rule's inset from the trim in pt, top/bottom/outer edge (see the manifest field); absent = same as `safe`. */
         artSafe?: number;
+        /** The binding edge's inset from the trim in pt, text and art alike (see the manifest field); absent = same as `safe`. */
+        gutter?: number;
     };
     ink: {
         maxTac: number;

package/dist/{validate-pb5gysvr.js → validate-x00gjxgb.js}

@@ -1,16 +1,16 @@
 import {
   executeAndReport
-} from "./cli-0ey902sx.js";
+} from "./cli-4d25xvs2.js";
 import {
   log
-} from "./cli-h4tfmpg3.js";
+} from "./cli-tsdrvrff.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-fmksazej.js";
+} from "./cli-gxqxn3sf.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-61vd4ews.js";
+import"./cli-cyej3p9v.js";
 import {
   BuildError,
   EXIT_CODES

package/package.json

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