gutterpress 0.11.23-beta.1 → 0.11.23-beta.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\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";
+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, plus one\n   bound of ours on the hidden MathML copy (#469, below). Inert in a book\n   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  /* Ours (#469). The browser lays the copy out in whatever math font it has,\n     so it can be wider than the formula's SVG; ending a line, it crossed the\n     column edge and Chromium shrank the whole print to fit. MathJax makes the\n     container position: relative with the copy at its top left, so 100% is\n     the formula's width. Clip and overflow still hide the copy and its MathML\n     still reaches screen readers; only its box changes. Not the 1px\n     visually-hidden box MathJax 2 used: its docs note VoiceOver on iOS could\n     not reach a formula by touch in it. */\n  max-width: 100% !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/source-provider.d.ts

@@ -1,3 +1,4 @@
+import { type ReadCommitResult } from "isomorphic-git";
 import type { ProjectCapabilities, ProjectSource } from "./project-source.ts";
 /**
  * isomorphic-git object cache scoped to ONE operation and released with it.
@@ -182,6 +183,32 @@ export declare function hasPendingChanges(dir: string, cache?: GitCache): Promis
  * as dirty (the WORKDIR-vs-STAGE-only check silently drops it).
  */
 export declare function hasUncommittedChanges(dir: string, cache?: GitCache): Promise<boolean>;
+/**
+ * A walk back through a repo's history in the order `git.log` lists it (the
+ * newest commit time first), visiting each commit once (#472). `git.log` has
+ * no visited set: after a merge it lists a commit again, with everything older,
+ * and the repeats used up a page. Starting the next page's log at the last id
+ * also dropped the side of a merge that id does not descend from. Shared with
+ * the online-only versions (`commitsAhead`, #477), which walks two tips at once.
+ */
+export interface HistoryWalk {
+    /** Commits read but not listed yet, sorted so the newest is last. */
+    tips: ReadCommitResult[];
+    /** Every commit ever put in `tips`. */
+    queued: Set<string>;
+    /** `.git/shallow`: commits whose parents a shallow clone does not have. */
+    shallow: Set<string>;
+    /** Commits read ahead (see {@link nextInHistory}), not queued yet. */
+    readAhead: Map<string, ReadCommitResult>;
+}
+/** A walk back from `heads` (the history of each of them, together). */
+export declare function startHistoryWalk(dir: string, cache: GitCache, heads: string[]): Promise<HistoryWalk>;
+/**
+ * The walk's next commit, newest first; undefined once the history is done.
+ * `needed` is how many more commits the page needs, to bound a read-ahead
+ * (none for 1: a caller that cannot tell how far it will go reads one by one).
+ */
+export declare function nextInHistory(dir: string, walk: HistoryWalk, cache: GitCache, needed: number): Promise<ReadCommitResult | undefined>;
 /**
  * Lock-free snapshot of the full working tree (stage everything + commit).
  *

package/dist/lib/version-changes.d.ts

@@ -45,14 +45,24 @@ export declare function listVersionChanges(projectDir: string, oid: string): Pro
 export declare function describeVersions(projectDir: string, entries: SnapshotEntry[]): Promise<VersionEntry[]>;
 /**
  * The commits reachable from `fromOid` that `baseOid`'s history does not
- * have, newest first, down to (not including) their merge base. None when
- * the two share no history.
+ * have (`git rev-list fromOid ^baseOid`), each once, newest first in the
+ * order Version history lists versions, up to `limit`. None when the two
+ * share no history: that is another book's online copy, which Sync refuses.
+ *
+ * One walk back from both tips, newest commit time first (#477). What
+ * `baseOid` reaches is marked, and a marked commit marks its parents, even
+ * ones already walked: a commit both tips reach is never listed, by whatever
+ * path `fromOid` reaches it (a criss-cross merge has two merge bases). The
+ * walk goes on while an unmarked commit is queued, so a version dated before
+ * the commits it builds on (a collaborator's clock behind) is still found;
+ * then until every marked commit queued is {@link CLOCK_SKEW_SECONDS} older
+ * than the oldest version listed.
  */
-export declare function commitsAhead(dir: string, fromOid: string, baseOid: string, cache?: object, limit?: number): Promise<SnapshotEntry[]>;
+export declare function commitsAhead(dir: string, fromOid: string, baseOid: string, cache?: Record<string, unknown>, limit?: number): Promise<SnapshotEntry[]>;
 /**
  * What is online that this computer has not got: fetch the book's branch
  * (remote-tracking ref only — no merge, no checkout, safe on a dirty tree)
- * and describe the commits above the merge base. Quiet on every failure,
+ * and describe the commits this computer has not got. Quiet on every failure,
  * reporting why, like `checkRemoteUpdates`.
  */
 export declare function listOnlineVersions(options: {

package/dist/{new-jtk028rf.js → new-d61n5cn0.js}

@@ -3,18 +3,18 @@ import {
   EXTENSION_KINDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-989eg8jz.js";
+} from "./cli-pnrararp.js";
 import {
   resolveGhostscript
-} from "./cli-vhav8g82.js";
+} from "./cli-0ep11b0q.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-k087gj0p.js";
+import"./cli-pd2cje5b.js";
 import"./cli-5crpmz42.js";
 import"./cli-eyyggect.js";
 import {
   isToolAvailable
 } from "./cli-asap4t1z.js";
-import"./cli-31anr0r9.js";
+import"./cli-v0evdpdf.js";
 import"./cli-v5mp7a6q.js";
 import {
   PRESET_IDS,
@@ -22,15 +22,15 @@ import {
   TARGET_IDS,
   loadManifest,
   resolveConfig
-} from "./cli-e31jshz6.js";
-import"./cli-ttj95aex.js";
-import"./cli-1fy1pm9d.js";
+} from "./cli-88arpdke.js";
+import"./cli-tgnyvra3.js";
+import"./cli-9n9kg58f.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-s1zt779w.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-65gy8ask.js";
 import {
   EXIT_CODES

package/dist/{plugins-bcbe7xs8.js → plugins-0hhw6s17.js}

@@ -8,7 +8,7 @@ import {
   loadPlugins,
   loadPluginsWithCss,
   loadPublishFunction
-} from "./index-a4j3xcfp.js";
+} from "./index-80vg3ed6.js";
 import"./index-5x42amh8.js";
 import"./index-37x76zdn.js";
 export {

package/dist/{plugins-zsm6wv79.js → plugins-e0n46s6m.js}

@@ -8,9 +8,9 @@ import {
   loadPlugins,
   loadPluginsWithCss,
   loadPublishFunction
-} from "./cli-ttj95aex.js";
-import"./cli-1fy1pm9d.js";
-import"./cli-s1zt779w.js";
+} from "./cli-tgnyvra3.js";
+import"./cli-9n9kg58f.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-y28j019d.js";
 import"./cli-37x76zdn.js";
 export {

package/dist/{preflight-cs6mj1d6.js → preflight-fjayhjr5.js}

@@ -1,28 +1,28 @@
 import {
   executeValidation,
   reportMissingTools
-} from "./cli-989eg8jz.js";
-import"./cli-vhav8g82.js";
+} from "./cli-pnrararp.js";
+import"./cli-0ep11b0q.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-k087gj0p.js";
+import"./cli-pd2cje5b.js";
 import"./cli-5crpmz42.js";
 import"./cli-eyyggect.js";
 import"./cli-asap4t1z.js";
-import"./cli-31anr0r9.js";
+import"./cli-v0evdpdf.js";
 import"./cli-v5mp7a6q.js";
 import {
   publishTargetFor
-} from "./cli-e31jshz6.js";
-import"./cli-ttj95aex.js";
+} from "./cli-88arpdke.js";
+import"./cli-tgnyvra3.js";
 import {
   log
-} from "./cli-1fy1pm9d.js";
+} from "./cli-9n9kg58f.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-s1zt779w.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-65gy8ask.js";
 import {
   BuildError,

package/dist/{preview-d1j1g4qf.js → preview-h815jrfb.js}

@@ -3,23 +3,23 @@ import {
   runBuild,
   splitOutPath,
   startPreviewServer
-} from "./cli-989eg8jz.js";
-import"./cli-vhav8g82.js";
+} from "./cli-pnrararp.js";
+import"./cli-0ep11b0q.js";
 import {
   previewArgs
 } from "./cli-75qkn0k5.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-k087gj0p.js";
+import"./cli-pd2cje5b.js";
 import"./cli-5crpmz42.js";
 import"./cli-eyyggect.js";
 import"./cli-asap4t1z.js";
-import"./cli-31anr0r9.js";
+import"./cli-v0evdpdf.js";
 import"./cli-v5mp7a6q.js";
-import"./cli-e31jshz6.js";
-import"./cli-ttj95aex.js";
+import"./cli-88arpdke.js";
+import"./cli-tgnyvra3.js";
 import {
   log
-} from "./cli-1fy1pm9d.js";
+} from "./cli-9n9kg58f.js";
 import {
   UsageError,
   parseFormat,
@@ -28,7 +28,7 @@ import {
   rejectUnknownFlags,
   resolvePort
 } from "./cli-d8xjns66.js";
-import"./cli-s1zt779w.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-65gy8ask.js";
 import {
   BuildError

package/dist/{publish-7yw4jyrt.js → publish-ft39zgma.js}

@@ -10,30 +10,30 @@ import {
   resolvePublishFormat,
   resolvePublishProvider,
   runPublish
-} from "./cli-989eg8jz.js";
+} from "./cli-pnrararp.js";
 import {
   FileTokenStore
-} from "./cli-vhav8g82.js";
+} from "./cli-0ep11b0q.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-k087gj0p.js";
+import"./cli-pd2cje5b.js";
 import"./cli-5crpmz42.js";
 import"./cli-eyyggect.js";
 import"./cli-asap4t1z.js";
-import"./cli-31anr0r9.js";
+import"./cli-v0evdpdf.js";
 import"./cli-v5mp7a6q.js";
 import {
   loadManifestWithPath
-} from "./cli-e31jshz6.js";
-import"./cli-ttj95aex.js";
+} from "./cli-88arpdke.js";
+import"./cli-tgnyvra3.js";
 import {
   log
-} from "./cli-1fy1pm9d.js";
+} from "./cli-9n9kg58f.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-s1zt779w.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-65gy8ask.js";
 import {
   BuildError,

package/dist/render.js

@@ -1431,8 +1431,9 @@ img.gp-shape {
 
 /* Math (the bundled gutterpress-math feature, math.ts): MathJax's own rules
    for the <mjx-container> SVG output it emits, from its SVG output jax's
-   stylesheet, less the ones for its interactive menu and tooltips. Inert in
-   a book without formulas. */
+   stylesheet, less the ones for its interactive menu and tooltips, plus one
+   bound of ours on the hidden MathML copy (#469, below). Inert in a book
+   without formulas. */
 mjx-container[jax="SVG"] { direction: ltr; }
 mjx-container[jax="SVG"] > svg { overflow: visible; min-height: 1px; min-width: 1px; }
 mjx-container[jax="SVG"] > svg a { fill: blue; stroke: blue; }
@@ -1449,6 +1450,15 @@ mjx-assistive-mml {
   border: 0px !important;
   display: block !important;
   width: auto !important;
+  /* Ours (#469). The browser lays the copy out in whatever math font it has,
+     so it can be wider than the formula's SVG; ending a line, it crossed the
+     column edge and Chromium shrank the whole print to fit. MathJax makes the
+     container position: relative with the copy at its top left, so 100% is
+     the formula's width. Clip and overflow still hide the copy and its MathML
+     still reaches screen readers; only its box changes. Not the 1px
+     visually-hidden box MathJax 2 used: its docs note VoiceOver on iOS could
+     not reach a formula by touch in it. */
+  max-width: 100% !important;
   overflow: hidden !important;
   user-select: none;
 }

package/dist/{source-provider-n7vehh6t.js → source-provider-j1w7byeq.js}

@@ -16,6 +16,7 @@ import {
   isNoChangesError,
   listRevisions,
   listWorkdirChanges,
+  nextInHistory,
   providerFor,
   readRevisionRefs,
   resolveGitAuthor,
@@ -24,10 +25,11 @@ import {
   snapshotStagingMarkerPath,
   snapshotWorkingTreeUnlocked,
   stageChanges,
+  startHistoryWalk,
   switchBranch,
   whenGitIdle,
   withRepoLock
-} from "./cli-31anr0r9.js";
+} from "./cli-v0evdpdf.js";
 import"./cli-v5mp7a6q.js";
 import"./cli-y28j019d.js";
 import"./cli-37x76zdn.js";
@@ -35,6 +37,7 @@ export {
   withRepoLock,
   whenGitIdle,
   switchBranch,
+  startHistoryWalk,
   stageChanges,
   snapshotWorkingTreeUnlocked,
   snapshotStagingMarkerPath,
@@ -43,6 +46,7 @@ export {
   resolveGitAuthor,
   readRevisionRefs,
   providerFor,
+  nextInHistory,
   listWorkdirChanges,
   listRevisions,
   isNoChangesError,

package/dist/{source-provider-tgzet3j5.js → source-provider-tjaf303m.js}

@@ -16,6 +16,7 @@ import {
   isNoChangesError,
   listRevisions,
   listWorkdirChanges,
+  nextInHistory,
   providerFor,
   readRevisionRefs,
   resolveGitAuthor,
@@ -24,10 +25,11 @@ import {
   snapshotStagingMarkerPath,
   snapshotWorkingTreeUnlocked,
   stageChanges,
+  startHistoryWalk,
   switchBranch,
   whenGitIdle,
   withRepoLock
-} from "./index-cw03e9p4.js";
+} from "./index-7j3hkwya.js";
 import"./index-5x42amh8.js";
 import"./index-v5mp7a6q.js";
 import"./index-37x76zdn.js";
@@ -35,6 +37,7 @@ export {
   withRepoLock,
   whenGitIdle,
   switchBranch,
+  startHistoryWalk,
   stageChanges,
   snapshotWorkingTreeUnlocked,
   snapshotStagingMarkerPath,
@@ -43,6 +46,7 @@ export {
   resolveGitAuthor,
   readRevisionRefs,
   providerFor,
+  nextInHistory,
   listWorkdirChanges,
   listRevisions,
   isNoChangesError,

package/dist/test-helpers/vocabulary.d.ts

@@ -0,0 +1,12 @@
+/**
+ * The words a writer never sees, as ONE list for every vocabulary test (#448).
+ *
+ * TEST-ONLY, like testkit.ts. The rules are docs/ux-design-contract.md's
+ * "Vocabulary (what an Author reads)"; this is the list the tests hold
+ * writer-facing strings to, so a word is banned in one place. Each test keeps
+ * its own exceptions (an author's own note, the SSH hint's `git@…` address).
+ */
+/** Matched against lowercased text. */
+export declare const BANNED_TERMS: readonly RegExp[];
+/** The banned terms `text` uses (lowercased); empty when it reads right. */
+export declare function bannedTermsIn(text: string): string[];

package/dist/{validate-rkcdnzhw.js → validate-b201dbrb.js}

@@ -1,25 +1,25 @@
 import {
   executeAndReport
-} from "./cli-989eg8jz.js";
-import"./cli-vhav8g82.js";
+} from "./cli-pnrararp.js";
+import"./cli-0ep11b0q.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-k087gj0p.js";
+import"./cli-pd2cje5b.js";
 import"./cli-5crpmz42.js";
 import"./cli-eyyggect.js";
 import"./cli-asap4t1z.js";
-import"./cli-31anr0r9.js";
+import"./cli-v0evdpdf.js";
 import"./cli-v5mp7a6q.js";
-import"./cli-e31jshz6.js";
-import"./cli-ttj95aex.js";
+import"./cli-88arpdke.js";
+import"./cli-tgnyvra3.js";
 import {
   log
-} from "./cli-1fy1pm9d.js";
+} from "./cli-9n9kg58f.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-s1zt779w.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-65gy8ask.js";
 import {
   BuildError,

package/package.json

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