gutterpress 0.11.20-alpha.3 → 0.11.20-alpha.4

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

@@ -31,7 +31,10 @@
  *   .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 75%.        the % resolves against the page box).
+ *   .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).
+ *                   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).
  *   .gp-shape     — wraps text to a floated image's alpha silhouette
@@ -47,16 +50,14 @@
  *                   frame instead, BY DESIGN: that is how a pin is scoped to
  *                   a card rather than a sheet. Page-level furniture must
  *                   therefore be authored outside such a wrapper.
- *                   Centered on both axes unless combined with the edge
- *                   modifiers .gp-top/.gp-bottom/.gp-left/.gp-right.
- *   .gp-flush     — with .gp-pin + an edge, the art sits on the PAPER's
- *                   edge rather than on the text block's. No CSS rule here:
- *                   the class is a marker both ENGINES implement (see
- *                   engine/shared/flush.ts), because reaching the paper
- *                   requires freeing that page's margin — per page — and
- *                   relocating the furniture that lived in it, neither of
- *                   which a stylesheet can do. Inert without .gp-pin + an
- *                   edge word, and inert under plain markdown-it.
+ *                   Centered in the text block unless combined with the
+ *                   edge modifiers .gp-top/.gp-bottom/.gp-left/.gp-right;
+ *                   an edge pin sits on the printer's ART-SAFE line of that
+ *                   edge and never moves the text — see "the pin box" below.
+ *   .gp-flush     — with .gp-pin + an edge, the escape hatch: the art runs
+ *                   to the PAPER's edge, past the printer's safe area. It
+ *                   only zeroes the pin box's insets (the rule after the
+ *                   edge modifiers). Inert without .gp-pin + an edge word.
  *   .gp-bleed     — forces its own page (break-before) and spans it
  *                   edge-to-edge horizontally. This does NOT cancel the
  *                   top/bottom margins, extend past the trim into printer
@@ -102,12 +103,12 @@
  *                   paragraph with other inline content keeps its margin.
  *
  * Rule ORDER within the gp-* block is the contract: flow positions → sizes
- * → spacing → .gp-pin → pin-edge modifiers. Everything is flat 0-1-0
- * specificity, so combining classes resolves by source order: a later flow
- * position wins (left < right < center < full < bleed); an explicit size's
- * max-width:100% lifts the floats' 50% cap; .gp-pin's margin:0 /
- * max-width:100% beat the float declarations; the edge modifiers beat
- * .gp-pin's center defaults.
+ * → spacing → .gp-pin → pin-edge modifiers → .gp-flush. Everything else is
+ * flat 0-1-0 specificity, so combining classes resolves by source order: a
+ * later flow position wins (left < right < center < full < bleed); an
+ * explicit size's max-width:100% lifts the floats' 50% cap; .gp-pin's
+ * margin:0 / max-width:100% beat the float declarations; the edge modifiers
+ * beat .gp-pin's center defaults.
  *
  * .gp-pin semantics, stated honestly: it pins within its @page/@spread
  * CONTAINER, not "the sheet edge". A .page div that fragments across
@@ -120,12 +121,29 @@
  * compiler's engine.abspos.leak diagnostic catches the raw-HTML cases the
  * token walk can't see.
  *
+ * The PIN BOX — where a pin may sit, and why the text never moves. An edge
+ * pin has to be able to reach the paper, and Chromium's printable area IS
+ * the page area (engine/shared/pin-edges.ts has the measurements), so both
+ * engines free the page margin on each edge a pin names: print through a
+ * generated named page, the preview through the run's strip geometry. The
+ * page root gets that margin back as padding, on top of any of its own
+ * (`box-decoration-break: clone`), so its content box — the text — is the
+ * author's content box, same size, same place, same breaks, wherever the art
+ * 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
+ * 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.
+ *
  * Pin CSS mechanics (all three are load-bearing, verified by
- * paged-css-image-pin.test.ts): `inset: 0` is REQUIRED — abspos
- * self-alignment aligns within the inset-modified containing block, and
- * with auto insets that collapses to the static-position rectangle, where
- * alignment does nothing. The center defaults must be EXPLICIT — `normal`
- * alignment behaves as `start` for abspos replaced elements, not center.
+ * marker-css-image-pin.test.ts): four non-auto insets are REQUIRED — abspos
+ * self-alignment aligns within the inset-modified containing block (the pin
+ * box), and with auto insets that collapses to the static-position
+ * rectangle, where alignment does nothing. The center defaults must be
+ * EXPLICIT — `normal` alignment behaves as `start` for abspos replaced
+ * elements, not center.
  * And `justify-self` on .gp-left/.gp-right does double duty (flow float +
  * pin edge) because self-alignment does not apply to in-flow floats — it is
  * inert until .gp-pin makes the element abspos. If Chrome ever ships
@@ -133,16 +151,14 @@
  * 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: 75%; 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   inset:0 and the explicit centers are load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  inset: 0;\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/* 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-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";
 /**
  * GP_CLASSES — every class an author may legitimately write with a `gp-`
  * prefix: the `.gp-*` selectors in `GUTTERPRESS_CSS` above, the two
  * structural classes `markers.js`'s `MARKER_CSS` styles (`gp-page-break`,
- * `gp-column-break`), and two classes the marker plugin EMITS but that carry
- * no CSS rule of their own — `gp-continued` (a `@continue`d section's marker,
- * for author/theme styling — see markers.js's header) and `gp-flush` (a
- * `.gp-pin` edge modifier implemented in the engine's layout code, not CSS —
- * see the `.gp-flush` doctrine note above).
+ * `gp-column-break`), and one class the marker plugin EMITS but that carries
+ * no CSS rule of its own — `gp-continued` (a `@continue`d section's marker,
+ * for author/theme styling — see markers.js's header).
  *
  * This is the vocabulary `gp-pin-scope.js`'s `unknown_gp_class` diagnostic
  * (#226) checks every author-facing class against: any `gp-`-prefixed class
@@ -151,8 +167,8 @@ export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary.
  * classes are none of core's business.
  *
  * `gutterpress-css.test.ts` asserts this set and the `.gp-*` selectors
- * textually present in `GUTTERPRESS_CSS` + `MARKER_CSS` agree (modulo the two
- * marker-only exceptions above), so the two cannot silently drift apart —
+ * textually present in `GUTTERPRESS_CSS` + `MARKER_CSS` agree (modulo the
+ * marker-only exception above), so the two cannot silently drift apart —
  * whoever adds a class to one CSS block and forgets this list finds out from
  * a failing test, not from a future bug report.
  */

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

@@ -2,6 +2,7 @@ import { type LayoutWarning } from "./assemble";
 import { type AssetCopy } from "../asset-inline";
 import type { LoadedPlugin, PluginStyleGroup } from "./renderer";
 import type { PrintPadding } from "../../engine/shared/synthesis.ts";
+import type { PrintAreaSource } from "../../engine/shared/print-area.ts";
 export type { LayoutWarning } from "./assemble";
 /**
  * THE canonical "which markdown files make up this book, and in what order?"
@@ -33,6 +34,8 @@ export declare function renderChapters(inputDir: string, opts?: {
     title?: string;
     /** See {@link AssembleBookHtmlOptions.print}. */
     print?: PrintPadding;
+    /** See {@link AssembleBookHtmlOptions.printArea}. */
+    printArea?: PrintAreaSource;
     styles?: string[];
     files?: string[] | null;
     plugins?: LoadedPlugin[];
@@ -72,6 +75,8 @@ export declare function renderChaptersToFile(inputDir: string, outDir: string, o
     title?: string;
     /** See {@link AssembleBookHtmlOptions.print}. */
     print?: PrintPadding;
+    /** See {@link AssembleBookHtmlOptions.printArea}. */
+    printArea?: PrintAreaSource;
     styles?: string[];
     files?: string[] | null;
     plugins?: LoadedPlugin[];

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

@@ -222,19 +222,19 @@
         },
         "bleed": {
           "type": "number",
-          "description": "A bleed, in points, that the page width x height ALREADY CONTAINS on the top, bottom and OUTER edges (none on the binding edge) — how DriveThruRPG's interior file is cut (8.625 x 11.25in for an 8.5 x 11in book). It tells the preview's safe area & bleed overlay and the `pdf.print.safe-margins` check where the trim is, and changes nothing in the PDF. Preset default: dtrpg 9 (0.125in); book and custom none.",
+          "description": "A bleed, in points, that the page width x height ALREADY CONTAINS on the top, bottom and OUTER edges (none on the binding edge) — how DriveThruRPG's interior file is cut (8.625 x 11.25in for an 8.5 x 11in book). It tells the preview's safe area & bleed overlay, the `pdf.print.safe-margins` check and pinned art where the trim is, and by itself changes nothing in the PDF. Preset default: dtrpg 9 (0.125in); book and custom none.",
           "minimum": 0,
           "examples": [9]
         },
         "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. It changes nothing in the PDF, and 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. 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.",
           "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. Preview overlay only: it changes nothing in the PDF. 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 `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.",
           "minimum": 0,
           "examples": [18]
         }

package/dist/{new-8yah8z91.js → new-s4f0tnya.js}

@@ -7,17 +7,17 @@ import {
   TARGET_IDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-9k2tb493.js";
+} from "./cli-0ey902sx.js";
 import {
   resolveGhostscript
-} from "./cli-y9bcya7r.js";
+} from "./cli-h4tfmpg3.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-hn9pk0hp.js";
+} from "./cli-fmksazej.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-x4p99w8d.js";
+import"./cli-61vd4ews.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";

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

@@ -2,17 +2,17 @@ import {
   executeValidation,
   publishTargetFor,
   reportMissingTools
-} from "./cli-9k2tb493.js";
+} from "./cli-0ey902sx.js";
 import {
   log
-} from "./cli-y9bcya7r.js";
+} from "./cli-h4tfmpg3.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-hn9pk0hp.js";
+} from "./cli-fmksazej.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-x4p99w8d.js";
+import"./cli-61vd4ews.js";
 import {
   BuildError,
   EXIT_CODES

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

@@ -20,17 +20,11 @@ import type { PrintPadding } from '../engine/shared/synthesis.ts';
  *
  * The book always paginates as ONE document, exactly as the print path does:
  * no per-source wrappers or forced breaks are added, so preview pagination
- * never diverges from the PDF where a source file begins mid-page.
+ * never diverges from the PDF where a source file begins mid-page. The
+ * project's print area is not added here: the markdown assembly writes it
+ * into every book, the preview's included (`AssembleBookHtmlOptions.printArea`).
  */
-export declare function injectPreviewScripts(html: string, page?: {
-    width: number;
-    height: number;
-    bleed?: number;
-    safe?: number;
-    artSafe?: number;
-    preset?: string;
-    spec?: PrintSpec;
-}): string;
+export declare function injectPreviewScripts(html: string): string;
 /**
  * Generate HTML from markdown and write book.html to the temp directory.
  * The desktop's iframe loads `book.html` via a relative URL — same name in

package/dist/{preview-w7v9w36q.js → preview-j91sxadd.js}

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

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

@@ -11,18 +11,18 @@ import {
   publishProviderFor,
   resolvePublishFormat,
   runPublish
-} from "./cli-9k2tb493.js";
+} from "./cli-0ey902sx.js";
 import {
   FileTokenStore,
   log
-} from "./cli-y9bcya7r.js";
+} from "./cli-h4tfmpg3.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-hn9pk0hp.js";
+} from "./cli-fmksazej.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-x4p99w8d.js";
+import"./cli-61vd4ews.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";

package/dist/render.js

@@ -1231,7 +1231,9 @@ var GUTTERPRESS_CSS = `
    cap at equal specificity */
 .gp-small { width: 25%; max-width: 100%; }
 .gp-medium { width: 50%; max-width: 100%; }
-.gp-large { width: 75%; max-width: 100%; }
+.gp-large { width: 60%; max-width: 100%; }
+.gp-xl { width: 80%; max-width: 100%; }
+.gp-xxl { 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
@@ -1289,10 +1291,16 @@ img.gp-shape {
 }
 
 /* pin — within the nearest positioned ancestor (.page/.spread, rule above).
-   inset:0 and the explicit centers are load-bearing; see doctrine comment. */
+   The four insets are the pin box: 0 (the text block's edge) unless an
+   engine set --gp-pin-<edge> on the page root for an edge a pin uses (the
+   art-safe line). Non-auto insets and the explicit centers are
+   load-bearing; see doctrine comment. */
 .gp-pin {
   position: absolute;
-  inset: 0;
+  top: var(--gp-pin-top, 0px);
+  right: var(--gp-pin-right, 0px);
+  bottom: var(--gp-pin-bottom, 0px);
+  left: var(--gp-pin-left, 0px);
   align-self: center;
   justify-self: center;
   margin: 0;
@@ -1307,6 +1315,16 @@ img.gp-shape {
 .gp-left { justify-self: start; }
 .gp-right { justify-self: end; }
 
+/* the escape hatch — the paper's edge, past the printer's safe area: the
+   pin box loses its art-safe insets. Set on the pin itself, so it beats the
+   values the page root hands down. */
+.gp-pin.gp-flush {
+  --gp-pin-top: 0px;
+  --gp-pin-right: 0px;
+  --gp-pin-bottom: 0px;
+  --gp-pin-left: 0px;
+}
+
 /* wrapper-margin neutralization (same pattern and rationale as the
    .gp-bleed paragraph-margin note in the doctrine comment; for pin, the
    emptied paragraph would otherwise leave a phantom margin gap in flow) */
@@ -1416,6 +1434,8 @@ var GP_CLASSES = new Set([
   "gp-small",
   "gp-medium",
   "gp-large",
+  "gp-xl",
+  "gp-xxl",
   "gp-tight",
   "gp-loose",
   "gp-columns",
@@ -1432,6 +1452,7 @@ var GP_CLASSES = new Set([
   "gp-pin",
   "gp-top",
   "gp-bottom",
+  "gp-flush",
   "gp-behind",
   "gp-base",
   "gp-raised",
@@ -1445,8 +1466,7 @@ var GP_CLASSES = new Set([
   "gp-alert-caution",
   "gp-page-break",
   "gp-column-break",
-  "gp-continued",
-  "gp-flush"
+  "gp-continued"
 ]);
 
 // src/lib/markdown/table-align.ts
@@ -1550,6 +1570,21 @@ function hasPinClass(token) {
   const cls = token.attrGet && token.attrGet("class");
   return typeof cls === "string" && cls.split(/\s+/).includes("gp-pin");
 }
+var PIN_EDGES = ["gp-top", "gp-right", "gp-bottom", "gp-left"];
+var FLUSH_ART_MSG = "`.gp-flush` puts this image on the paper's edge, past the printer's safe area. Printers trim up to 0.125in there, so keep it for art that is meant to bleed off the page.";
+function checkFlushArt(token, env, line) {
+  if (token.type !== "image")
+    return;
+  const cls = token.attrGet && token.attrGet("class");
+  if (typeof cls !== "string")
+    return;
+  const classes = cls.split(/\s+/);
+  if (!classes.includes("gp-pin") || !classes.includes("gp-flush"))
+    return;
+  if (!classes.some((c) => PIN_EDGES.includes(c)))
+    return;
+  warn2(env, line, "flush_art", FLUSH_ART_MSG);
+}
 function elementNameFor(token) {
   switch (token.type) {
     case "layout_chapter_open":
@@ -1609,6 +1644,7 @@ function gpPinScope(md) {
       if (token.type === "inline" && token.children) {
         for (const child of token.children) {
           checkUnknownGpClasses(child, state.env, line);
+          checkFlushArt(child, state.env, line);
         }
       }
     }
@@ -2343,6 +2379,20 @@ function lastPageMode(print) {
 }
 var WHICH_VALUES = new Set(["first", "start", "last", "first-except"]);
 
+// src/engine/shared/print-area.ts
+function printAreaMeta(page) {
+  const area = JSON.stringify({
+    width: page.width,
+    height: page.height,
+    bleed: page.bleed ?? 0,
+    safe: page.safe ?? 0,
+    artSafe: page.artSafe,
+    preset: page.preset,
+    spec: page.spec
+  });
+  return `<meta name="gp-print-area" content='${area.replace(/&/g, "&amp;").replace(/'/g, "&#39;")}'>`;
+}
+
 // src/lib/markdown/assemble.ts
 async function assembleBookHtml(opts) {
   const title = opts.title ?? "Document";
@@ -2408,7 +2458,8 @@ ${projectCss.trim()}` : null
 <html lang="en"${printAttrs}>
 <head>
   <meta charset="UTF-8">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">${opts.printArea ? `
+  ${printAreaMeta(opts.printArea)}` : ""}
   <title>${title}</title>${preloadTags}
   <style data-project-css>
 ${inlineCss}

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

@@ -171,17 +171,18 @@ export interface GutterpressManifest {
          * A bleed (pt) the page `width` x `height` ALREADY CONTAINS, on the top,
          * bottom and OUTER edges only (the binding edge has none) — how
          * DriveThruRPG's interior file is cut (8.625 x 11.25in for an 8.5 x 11in
-         * book). It changes nothing in the PDF: it only tells the preview's safe
-         * area & bleed overlay and `pdf.print.safe-margins` where the trim is.
+         * book). By itself it changes nothing in the PDF: it tells the preview's
+         * safe area & bleed overlay, `pdf.print.safe-margins` and pinned art
+         * (`.gp-pin` on an edge sits on the art-safe line) where the trim is.
          */
         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. Like
-         * `bleed`, it changes nothing in the PDF, and nothing in a book's CSS moves
-         * 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.
          */
         safe?: number;
         /**
@@ -189,7 +190,8 @@ export interface GutterpressManifest {
          * 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
          * "keep non-bleeding art 0.25in from the outside edges" (`dtrpg` sets 18).
-         * Absent = the same as `safe`.
+         * 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;
     };

package/dist/{validate-1yh59x0x.js → validate-pb5gysvr.js}

@@ -1,16 +1,16 @@
 import {
   executeAndReport
-} from "./cli-9k2tb493.js";
+} from "./cli-0ey902sx.js";
 import {
   log
-} from "./cli-y9bcya7r.js";
+} from "./cli-h4tfmpg3.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-hn9pk0hp.js";
+} from "./cli-fmksazej.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-x4p99w8d.js";
+import"./cli-61vd4ews.js";
 import {
   BuildError,
   EXIT_CODES

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gutterpress",
-  "version": "0.11.20-alpha.3",
+  "version": "0.11.20-alpha.4",
   "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/engine/shared/flush.d.ts

@@ -1,59 +0,0 @@
-/**
- * `.gp-flush` policy — shared by the compiler and the viewer, like every rule
- * that DECIDES something (see synthesis.ts's header).
- *
- * A pinned image reaches the paper only if the page's own margin is removed
- * on that edge: Chromium's printable area IS the page area — MEASURED, a
- * pinned box pulled into the margin with negative insets fragments onto the
- * NEXT sheet, one moved there with a transform is clipped away entirely, and
- * a margin box in a ~zero margin (1px, with padding/height compensation)
- * simply does not render. So flush is implemented as page GEOMETRY, per page:
- *
- *  - The COMPILER aliases the flush root's own page context under a
- *    generated name (verbatim rule copies — never a resolved flatten, which
- *    is the "re-implement the @page cascade" trap tier2's history records),
- *    zeroes the flushed margins on the alias, and assigns the root to it.
- *  - The VIEWER keeps the author's page context and adjusts the strip
- *    geometry in JS from these same functions.
- *
- * Margin boxes live IN the margin, so the flushed edge's furniture (folio,
- * running head) cannot render natively there — MEASURED, no compensation
- * trick survives. Both renderers therefore keep painting that furniture
- * themselves at its ORIGINAL coordinates: the viewer already synthesizes all
- * furniture as DOM; the compiler injects the flushed edge's boxes into the
- * page root as positioned elements with engine-resolved text. Nothing the
- * author declared is lost — that is the contract this module's box map
- * exists to keep.
- */
-import type { PageGeometry } from "./gcpm-extract.ts";
-export declare const FLUSH_EDGES: readonly ["top", "right", "bottom", "left"];
-export type FlushEdge = (typeof FLUSH_EDGES)[number];
-/** Minimal DOM shape needed by `flushEdgesIn` — keeps this module node-safe. */
-interface QueryRoot {
-    querySelector(sel: string): unknown;
-}
-/**
- * Which edges the flush pins inside `root` ask for, in canonical t/r/b/l
- * order. A `.gp-flush` without `.gp-pin` or without an edge word is inert by
- * construction — every selector here requires all three.
- */
-export declare function flushEdgesIn(root: QueryRoot): FlushEdge[];
-/** Canonical short key for an edge set: "b", "rb", "trbl"… (t/r/b/l order). */
-export declare function flushKey(edges: readonly FlushEdge[]): string;
-/**
- * Generated page name for (author page context, edge set). The `gp--` double
- * dash marks an engine-generated page (the `gp--blank` convention); these
- * exist only in builds that actually contain a flush pin, which is why the
- * width check may treat them as real author contexts.
- */
-export declare function flushPageName(authorPage: string | undefined, edges: readonly FlushEdge[]): string;
-/** The page's margins with the flushed edges freed. */
-export declare function flushMargins(margin: PageGeometry["margin"], edges: readonly FlushEdge[]): PageGeometry["margin"];
-/**
- * Margin boxes that live (wholly or partly) in a flushed edge's margin area —
- * the set both renderers must keep painting themselves. A corner box belongs
- * to BOTH of its edges: `bottom-left-corner` dies when either the bottom or
- * the left margin is freed.
- */
-export declare function marginBoxesOnEdges(edges: readonly FlushEdge[]): string[];
-export {};