gutterpress 0.11.23-alpha.7 → 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/publish/google-drive.d.ts

@@ -38,17 +38,25 @@ export interface DriveFolder {
  * page — an author with more than one page of app-created folders would
  * otherwise see the destinations picker silently miss folders past the
  * first 100. (`ensureFolder`'s find-by-name lookup uses its own single
- * server-side query, {@link findFolderByName} below, and doesn't paginate.) */
+ * server-side query, {@link findFoldersByName} below, and doesn't paginate.) */
 export declare function listFolders(fetchImpl: typeof fetch, accessToken: string): Promise<DriveFolder[]>;
-/** Look up one folder by id (for verifying a manifest-recorded `folderId`
- * still exists and isn't trashed). Returns null when it's gone. */
+/** Look up one folder by id (for verifying a recorded `folderId` is reachable
+ * with this account). Returns null when it isn't: trashed or deleted, or never
+ * opened through Gutterpress by this account — `drive.file` answers 404 for a
+ * folder this connection can't see, so the cases are one (#452). */
 export declare function getFolderById(fetchImpl: typeof fetch, accessToken: string, folderId: string): Promise<DriveFolder | null>;
 /** Create a folder at My Drive root. */
 export declare function createFolder(fetchImpl: typeof fetch, accessToken: string, name: string): Promise<DriveFolder>;
+/** App-visible folders with exactly this name, most recently modified first,
+ * at most `limit` of them — a single server-side query (the same `q=` pattern
+ * as {@link findFileInFolder}), not a client-side scan of every app-created
+ * folder. `ensureFolder` asks for one; a caller that must know whether
+ * several share the name (#452: the CLI says which it used) asks for two. */
+export declare function findFoldersByName(fetchImpl: typeof fetch, accessToken: string, name: string, limit?: number): Promise<DriveFolder[]>;
 /** Find-or-create a folder by name at My Drive root (D5's name-resolution
  * path, used when the manifest has no recorded `folderId` yet). One query,
  * not a client-side scan of every app-created folder — see
- * {@link findFolderByName}. */
+ * {@link findFoldersByName}. */
 export declare function ensureFolder(fetchImpl: typeof fetch, accessToken: string, name: string): Promise<DriveFolder>;
 export interface DriveFile {
     id: string;

package/dist/lib/publish/manifest-publish.d.ts

@@ -25,6 +25,12 @@ export declare function setPublishProviderConfig(projectDir: string, providerId:
  *   override). A folder inside the book is shared, and is written relative to
  *   it (an absolute in-book path is rewritten) so it means the same thing on
  *   every computer. An absolute path is never written to the manifest.
+ * - their own Google Drive folder for the book (`myFolderId`, `myFolder`; #452),
+ *   chosen when the book's folder is out of their reach or just for them. It is
+ *   recorded with the book's folder it stands in for (`myFolderFor`: the
+ *   manifest's `folderId`, else its `folder` name) and the account it was
+ *   chosen with (`myFolderAccount`), so it lapses when either changes (see
+ *   providers/gdrive.ts). Clearing `myFolderId` clears the whole record.
  *
  * Only the values passed are classified; the manifest is not rewritten unless
  * one of them changes it. Empty values clear. Returns the settings as the

package/dist/lib/publish/providers/gdrive-folder.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Which Google Drive folder one person publishes to (#452), for the `gdrive`
+ * provider (gdrive.ts). The book's folder in the manifest is the team's; a
+ * person whose Google connection can't reach it publishes to a folder of their
+ * own, kept in their private store for the book, and that folder stands in for
+ * the book's only while the book's folder and their account are the ones it
+ * was chosen for.
+ */
+import { type DriveFolder } from "../google-drive.ts";
+import type { PublishDestinationStatus, PublishProduct, PublishRequest } from "../types.ts";
+/** Default folder name when the manifest sets neither `folder` nor
+ * `folderId` (D5, ratified: one shared "Gutterpress" folder, not
+ * per-book-title folders). */
+export declare const DEFAULT_FOLDER_NAME = "Gutterpress";
+/**
+ * Where this person publishes (#452). The book's folder is the team's: an id,
+ * checked with the account this person publishes with (`drive.file` answers 404
+ * for a folder it can't see, so "not shared with Gutterpress", "another
+ * account" and "trashed" are one case), or a name, which each person finds or
+ * creates in their own Drive. Their own folder, from their private store,
+ * stands in for it while it was chosen for the book's current folder and with
+ * the account they publish with now; one recorded against another folder or
+ * account no longer applies, and is dropped once the book's folder is
+ * reachable. Never writes the manifest or creates a folder.
+ */
+export declare function resolveFolder(req: PublishRequest, accessToken: string): Promise<PublishDestinationStatus>;
+/** The folder an upload goes to. An unreachable one fails, naming it and how
+ * to publish elsewhere: publishing never creates a folder in its place. */
+export declare function uploadFolder(where: PublishDestinationStatus, fetchImpl: typeof fetch, accessToken: string): Promise<PublishProduct>;
+export declare function toDestination(folder: DriveFolder): PublishProduct;

package/dist/lib/publish/run-publish.d.ts

@@ -10,6 +10,11 @@ export interface RunPublishOptions {
     artifactPath?: string;
     /** Stop after preflight — report issues without contacting the platform. */
     dryRun?: boolean;
+    /**
+     * Provider settings for this run only, laid over the saved ones and never
+     * written anywhere: the CLI's `--folder-id` / `--folder` (#452).
+     */
+    settings?: Record<string, string>;
     /**
      * The provider, when the caller has already resolved it (the CLI does, to
      * map a failed restore to its own exit code): no second lookup or restore.
@@ -39,7 +44,7 @@ export interface RunPublishResult {
  * with a preflight error over one bad manifest field.
  */
 export declare function resolvePublishFormat(info: PublishProviderInfo, providerConfig: Record<string, unknown>): PublishArtifactFormat;
-type RequestOptions = Pick<RunPublishOptions, "projectDir" | "providerId" | "manifestPath" | "artifactPath">;
+type RequestOptions = Pick<RunPublishOptions, "projectDir" | "providerId" | "manifestPath" | "artifactPath" | "settings">;
 /**
  * Resolve the {@link PublishRequest} for a BUILT-IN provider from the
  * project's manifest — for hosts that call individual provider methods

package/dist/lib/publish/types.d.ts

@@ -206,12 +206,13 @@ export interface PublishDeps {
     credentialAccount?: string;
     /**
      * The person's PRIVATE publishing values for a book (see
-     * {@link PublishSelectionsStore}): which saved account to use and an output
-     * folder outside the book. When given, they win over the manifest's
-     * `publish.<id>` values in every request. Absent (the CLI today): the
-     * manifest alone.
+     * {@link PublishSelectionsStore}): which saved account to use, an output
+     * folder outside the book, and their own Drive folder when the book's is out
+     * of their reach (#452). When given, they win over the manifest's
+     * `publish.<id>` values in every request, and a provider may drop one that
+     * no longer applies. Absent (the CLI today): the manifest alone.
      */
-    selections?: Pick<PublishSelectionsStore, "settings">;
+    selections?: Pick<PublishSelectionsStore, "settings" | "setSettings">;
 }
 /**
  * The TokenStore key for a publishing provider credential. Named accounts use a
@@ -252,6 +253,50 @@ export interface PublishProduct {
     title: string;
     url?: string;
 }
+/**
+ * Where one person publishes among a provider's destinations, and whether they
+ * must choose one (#452, gdrive's folders). The book's destination is the
+ * team's, in the manifest; a person whose account can't reach it chooses their
+ * own, kept in their private settings for the book.
+ */
+export type PublishDestinationStatus = 
+/** The book has no destination yet: the first choice is the book's. */
+{
+    state: "unset";
+}
+/** The book's destination, reachable with this person's account. */
+ | {
+    state: "book";
+    destination: PublishProduct;
+}
+/** The book names its destination by name only: each person's own of that
+ *  name. `destination` is this account's most recently changed one (absent:
+ *  it is created on the first publish); `several` when more share the name. */
+ | {
+    state: "by-name";
+    name: string;
+    destination?: PublishProduct;
+    several: boolean;
+}
+/** This person's own destination stands in for the book's. */
+ | {
+    state: "mine";
+    destination: PublishProduct;
+    book: {
+        title: string;
+        reachable: boolean;
+    };
+}
+/** Out of reach with this person's account: the book's destination, or their
+ *  own (`mine`, its title) when they have one. They must choose another. */
+ | {
+    state: "unreachable";
+    book: {
+        title: string;
+        reachable: boolean;
+    };
+    mine?: string;
+};
 /** Listing metadata for {@link PublishProvider.updateListing}. */
 export interface PublishListingMetadata {
     title?: string;
@@ -304,6 +349,8 @@ export interface PublishProvider {
     listDestinations?(req: PublishRequest): Promise<PublishProduct[]>;
     /** Create a new destination (gdrive: a Drive folder at My Drive root). */
     createDestination?(req: PublishRequest, name: string): Promise<PublishProduct>;
+    /** Where this person publishes now, and whether they must choose (#452). */
+    destinationStatus?(req: PublishRequest): Promise<PublishDestinationStatus>;
 }
 /**
  * Resolve the credential for a provider: the CI env var wins, then the token

package/dist/lib/remote-auth/converge-merge.d.ts

@@ -29,11 +29,11 @@ export interface ConvergeResult {
     keptBothFiles: KeptBothFile[];
 }
 /** Snapshot message for the equalization commit (driver-unreachable cases). */
-export declare const CONVERGE_PREPARE_MESSAGE = "Getting your changes ready to combine with the online version";
+export declare const CONVERGE_PREPARE_MESSAGE = "Getting your changes ready to combine with the online copy's changes";
 /** Snapshot message for the post-merge restore commit (kept-both/edits). */
-export declare const CONVERGE_RESTORE_MESSAGE = "Kept both versions of the files that can't be combined";
+export declare const CONVERGE_RESTORE_MESSAGE = "Kept both takes of the files that can't be combined";
 /** The merge commit message. */
-export declare const CONVERGE_MERGE_MESSAGE = "Combined your changes with the online version";
+export declare const CONVERGE_MERGE_MESSAGE = "Combined your changes with the online copy's";
 /**
  * diff3 merge that NEVER reports a conflict: clean hunks merge exactly like
  * git's default driver; clashing hunks keep BOTH versions inside standard

package/dist/lib/remote-auth/sync-messages.d.ts

@@ -19,8 +19,8 @@ export declare const MSG_BUSY = "The online copy is changing very quickly right
  * VERSIONS are what broke, and (backing up always has an online copy, so this
  * always applies here) "Repair the online copy" is the way back.
  */
-export declare const MSG_HISTORY_UNREADABLE = "This book's versions can't be read, so backing up can't continue. Your writing is safe \u2014 every file is still here on this computer. Use \"Repair the online copy\" (in Book setup \u2192 Online copy) to get versions and backing up working again.";
-export declare const MSG_UNRELATED = "This book and the online copy have no versions in common, so they can't be combined. Either the online copy's address points at a different book, or this book's own versions were lost and started over. Your writing is safe \u2014 every file is still here on this computer. Check the online copy's address; if it is correct, use \"Repair the online copy\" (in Book setup \u2192 Online copy).";
+export declare const MSG_HISTORY_UNREADABLE = "This book's versions can't be read, so backing up can't continue. Your writing is safe \u2014 every file is still here on this computer. Use \"Repair the online copy\" in Book setup to get versions and backing up working again.";
+export declare const MSG_UNRELATED = "This book and the online copy have no versions in common, so they can't be combined. Either the online copy's address points at a different book, or this book's own versions were lost and started over. Your writing is safe \u2014 every file is still here on this computer. Check the online copy's address; if it is correct, use \"Repair the online copy\" in Book setup.";
 export declare const MSG_NO_REMOTE = "This book doesn't have an online copy yet.";
 export declare const MSG_SSH_REMOTE = "This book's online copy uses an SSH address (git@\u2026), which Gutterpress can't back up to. Switch it to the web (HTTPS) address to back up from here.";
 export declare const MSG_NO_BRANCH = "This book isn't on a named revision, so it can't be backed up right now.";

package/dist/lib/root-tokens.d.ts

@@ -0,0 +1,76 @@
+/**
+ * A stylesheet's root-level custom properties — the design settings Book
+ * setup shows — read and written with postcss (#454).
+ *
+ * "Root-level" means a declaration in a `:root` rule that is not inside
+ * `@media`, `@supports` or any other conditional group (and, postcss being a
+ * parser, never one in a comment). A `:root` inside a cascade layer counts,
+ * tagged with its layer. Values are read as written, so a `;` inside
+ * `url("data:…")` is part of the value, and a write changes only the
+ * declarations it names: every other byte of the sheet is kept.
+ *
+ * Host-side only: postcss never reaches the desktop's SPA (architecture rules
+ * §8). The desktop reads these through its `style/book-css` route and writes
+ * through `style/edit-tokens` (`book-css.ts`).
+ *
+ * **Token annotations (issue #244).** Theme authors curate what the guided
+ * panel shows with a tiny comment grammar in the `:root` block — no new file
+ * format, no schema, and (since it's ordinary CSS comments) no risk to a
+ * plain browser or a build that never heard of Gutterpress. Three
+ * directives, each written in a block comment right before the declaration it
+ * describes:
+ *
+ * - `@group <name>` — show the token under a "<name>" heading instead of the
+ *   Fonts/Colors/Sizes/Other bucket its kind would choose.
+ * - `@label <text>` — the label shown instead of the default one.
+ * - `@internal` — leave the token out of the panel. The CSS is untouched.
+ *
+ * Each directive applies to the NEXT custom-property declaration only and is
+ * consumed by it. A block has defaults too (#435): `@group` and `@internal`
+ * in the comments directly BEFORE the `:root` selector apply to every
+ * declaration in the block that carries no directive of its own; a
+ * declaration's own `@group`, `@label` or `@internal` still wins for that
+ * declaration (its own `@group` or `@label` shows it even inside an
+ * `@internal` block). Several directives can share one comment (`@label X
+ * @group Y`) or be spread across consecutive comments. A comment with none of
+ * them is prose and changes nothing.
+ */
+/** One root-level custom property, as a stylesheet declares it. */
+export interface RootToken {
+    /** The property name, e.g. `--color-accent`. */
+    name: string;
+    /**
+     * The value as written, comments and the space before its `;` included, so
+     * writing it back restores the declaration byte for byte (`!important` is
+     * not part of it, and stays on the declaration).
+     */
+    value: string;
+    /** An `@label` annotation's text. */
+    label?: string;
+    /** An `@group` annotation (the declaration's own, else its block's). */
+    group?: string;
+    /** The cascade layer the `:root` rule sits in, dotted (`ext.look.theme`); absent when unlayered. */
+    layer?: string;
+}
+/** One pending change: a token's new value, or null to remove the book's declaration of it. */
+export interface TokenUpdate {
+    name: string;
+    value: string | null;
+}
+/**
+ * Every root-level custom property a stylesheet declares, in source order,
+ * with its annotations; an `@internal` one is left out. Throws postcss's
+ * `CssSyntaxError` for a sheet it cannot parse.
+ */
+export declare function rootTokens(css: string): RootToken[];
+/**
+ * Apply a batch of token updates to a book's stylesheets, in cascade order,
+ * folding each onto the result of the last so none is lost. A value is set
+ * where the book already declares the token — every root-level declaration
+ * of it in the LAST sheet that has one, the one that wins — and otherwise
+ * added to `sheets[target]`. A null value removes the token from every
+ * sheet, so what the looks set shows through. Returns the sheets' new text;
+ * a sheet nothing changed comes back as it was given. Throws postcss's
+ * `CssSyntaxError` for a sheet it cannot parse.
+ */
+export declare function applyTokenUpdates(sheets: readonly string[], target: number, updates: readonly TokenUpdate[]): string[];

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

@@ -17,10 +17,8 @@ export interface VersionChanges {
     /** Changed files beyond the ones listed (the list is capped). */
     more: number;
 }
-/** A history entry with what it changed and where it is kept. */
+/** A history entry and where it is kept. */
 export interface VersionEntry extends SnapshotEntry {
-    changes: VersionFileChange[];
-    moreChanges: number;
     /** True = online too; false = on this computer only; null = no online copy to compare with. */
     backedUp: boolean | null;
 }
@@ -29,30 +27,42 @@ export declare const VERSION_CHANGES_SHOWN = 8;
 /** The size hint for a text file that changed between two versions. */
 export declare function changeHint(filepath: string, before: string, after: string): string;
 /**
- * The files `oid` changed against its first parent (every file, for a
- * version with no parent), sorted by path and capped to
+ * The files version `oid` of the book changed against its first parent
+ * (every file, for a version with no parent), sorted by path and capped to
  * {@link VERSION_CHANGES_SHOWN}.
  */
-export declare function listVersionChanges(dir: string, oid: string, options?: {
-    cache?: object;
-}): Promise<VersionChanges>;
+export declare function listVersionChanges(projectDir: string, oid: string): Promise<VersionChanges>;
 /**
- * A history page with each version's changes and whether it is backed up.
- * Versions come newest-first, and everything older than the first backed-up
- * one is backed up too, so the ancestry walk runs only over the versions
- * that are on this computer only.
+ * A history page with whether each version is backed up: whether it is the
+ * online tip or one of its earlier versions. Versions come newest-first, and
+ * everything older than the first backed-up one is backed up too. The rest
+ * share ONE breadth-first walk back from the tip, step for step the walk
+ * `git.isDescendent` makes (a shallow commit's parents are not followed; a
+ * missing object ends the walk, and a version not reached by then is not
+ * backed up): asking `isDescendent` once per version walked the whole history
+ * again for every version on this computer only.
  */
 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/{manifest-79zsgkpn.yaml → manifest-0vwaskj2.yaml}

@@ -8,7 +8,7 @@ styles:
   - styles/book.css
 # Page size and margins in points (72 = 1 in): US Letter with 1 in margins
 # (A4 is width 595, height 842); text stays 0.25 in (18) inside the trim.
-# Change them under Setup > Book.
+# Change them in Book setup.
 page:
   width: 612
   height: 792

package/dist/{manifest-2kc56wvw.yaml → manifest-aya31jwt.yaml}

@@ -9,7 +9,7 @@ extensions:
   - technical-doc
 # Page size and margins in points (72 = 1 in): US Letter (8.5 x 11 in) with
 # 0.9 in top and bottom and 1 in side margins; text stays 0.25 in (18) inside
-# the trim. Change them under Setup > Book.
+# the trim. Change them in Book setup.
 page:
   width: 612
   height: 792

package/dist/{manifest-41ddzm13.yaml → manifest-mffah3hr.yaml}

@@ -8,7 +8,7 @@ styles:
 extensions:
   - clean-book
 # Page margins in points (72 = 1 in): top, bottom, inside (the binding edge)
-# and outside. Change them, and the page size, under Setup > Book.
+# and outside. Change them, and the page size, in Book setup.
 page:
   margin:
     top: 61.2

package/dist/{manifest-sqzm4681.yaml → manifest-wbcv8cbp.yaml}

@@ -8,8 +8,8 @@ styles:
 extensions:
   - zine
 # Page size and margins in points (72 = 1 in): Digest (5.5 x 8.5 in) with
-# 0.4 in margins; text stays 0.25 in (18) inside the trim. Change them under
-# Setup > Book.
+# 0.4 in margins; text stays 0.25 in (18) inside the trim. Change them in
+# Book setup.
 page:
   width: 396
   height: 612

package/dist/{manifest.schema-93sd7zje.json → manifest.schema-0jgj0jt1.json}

@@ -242,7 +242,7 @@
         },
         "margin": {
           "type": "object",
-          "description": "Page margins, in points (1in = 72pt): the space between the trim and the text on each edge. `inside` is the binding edge (the left of a right-hand page, the right of a left-hand one), `outside` the other. When set, the book prints with these margins and any `@page` margin in a stylesheet is overridden; when left out, the stylesheets' `@page` margins apply (a look's design), else 1in. Setup > Book in the app edits it. All four edges are required together.",
+          "description": "Page margins, in points (1in = 72pt): the space between the trim and the text on each edge. `inside` is the binding edge (the left of a right-hand page, the right of a left-hand one), `outside` the other. When set, the book prints with these margins and any `@page` margin in a stylesheet is overridden, except where a named page sets its own (`@page full { margin: 0 }`); when left out, the stylesheets' `@page` margins apply (a look's design), else 1in. Setup > Book in the app edits it. All four edges are required together.",
           "properties": {
             "top": { "type": "number", "description": "Top margin in points.", "minimum": 0, "examples": [61.2, 72] },
             "bottom": { "type": "number", "description": "Bottom margin in points.", "minimum": 0, "examples": [61.2, 72] },

package/dist/{new-88rkrv71.js → new-d61n5cn0.js}

@@ -3,18 +3,18 @@ import {
   EXTENSION_KINDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-3cvq3n1c.js";
+} from "./cli-pnrararp.js";
 import {
   resolveGhostscript
-} from "./cli-mmgtqnmr.js";
+} from "./cli-0ep11b0q.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-58fsk6d7.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,16 @@ import {
   TARGET_IDS,
   loadManifest,
   resolveConfig
-} from "./cli-6pv84kf3.js";
-import"./cli-wyg7qstd.js";
-import"./cli-eatdqx3z.js";
+} from "./cli-88arpdke.js";
+import"./cli-tgnyvra3.js";
+import"./cli-9n9kg58f.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
 } from "./cli-d8xjns66.js";
-import"./cli-5ba6bm6z.js";
+import"./cli-x7gcdg6w.js";
+import"./cli-65gy8ask.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";

package/dist/{page-rules-ytj9p04v.css → page-rules-vnja6grt.css}

@@ -7,8 +7,8 @@
  *   to a CSS `@page name`.
  *
  *   NOT the page geometry. The trim size and the margins are the BOOK's,
- *   recorded in its manifest (`preset:`, `page:` — Setup > Book in the
- *   app) and written by the build after every stylesheet, so a `size` here
+ *   recorded in its manifest (`preset:`, `page:` — set in Book setup) and
+ *   written by the build after every stylesheet, so a `size` here
  *   would be ignored (and reported) and a `margin` here would hold only
  *   until the author sets margins in the app. Design the furniture below to
  *   sit in whatever margin the book gives it.

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

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

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

@@ -8,9 +8,9 @@ import {
   loadPlugins,
   loadPluginsWithCss,
   loadPublishFunction
-} from "./cli-wyg7qstd.js";
-import"./cli-eatdqx3z.js";
-import"./cli-5ba6bm6z.js";
+} from "./cli-tgnyvra3.js";
+import"./cli-9n9kg58f.js";
+import"./cli-x7gcdg6w.js";
 import"./cli-y28j019d.js";
 import"./cli-37x76zdn.js";
 export {