gutterpress 0.11.17-alpha.5 → 0.11.17-alpha.6

package/dist/{index-5ez30g3a.js → index-2vd5b3vy.js}

@@ -9,7 +9,7 @@ import {
   getAssetsDir,
   lastPageMode,
   parseSize
-} from "./index-5gp6mkmf.js";
+} from "./index-vmcfahe2.js";
 import {
   INSTALL_HINTS,
   execCapture,
@@ -1129,6 +1129,16 @@ function resolveContainerShape(name, pluginName, decl) {
     ...check
   };
 }
+function presetVariantOf(name, pluginName, rawDecl) {
+  const preset = rawDecl.preset !== undefined ? rawDecl.preset : {};
+  if (typeof preset !== "object" || preset === null || Array.isArray(preset)) {
+    throw new Error(`Plugin "${pluginName}"'s marker "@${name}" has a \`preset\` that is not a plain object.`);
+  }
+  if (preset.variant !== undefined && typeof preset.variant !== "string") {
+    throw new Error(`Plugin "${pluginName}"'s marker "@${name}" has a \`preset.variant\` that is not a string.`);
+  }
+  return preset.variant;
+}
 function resolveMarkerDeclaration(name, rawDecl, rawRegistry, originOf) {
   const pluginName = originOf.get(name);
   if (typeof rawDecl !== "object" || rawDecl === null || Array.isArray(rawDecl)) {
@@ -1157,22 +1167,22 @@ function resolveMarkerDeclaration(name, rawDecl, rawRegistry, originOf) {
     if (targetRaw.alias !== undefined) {
       throw new Error(`Plugin "${pluginName}"'s marker "@${name}" aliases "@${rawDecl.alias}", which is itself an alias. ` + `Chained aliases are not supported — alias the base marker directly.`);
     }
-    const preset = rawDecl.preset !== undefined ? rawDecl.preset : {};
-    if (typeof preset !== "object" || preset === null || Array.isArray(preset)) {
-      throw new Error(`Plugin "${pluginName}"'s marker "@${name}" has a \`preset\` that is not a plain object.`);
-    }
-    if (preset.variant !== undefined && typeof preset.variant !== "string") {
-      throw new Error(`Plugin "${pluginName}"'s marker "@${name}" has a \`preset.variant\` that is not a string.`);
-    }
     const container = resolveContainerShape(rawDecl.alias, originOf.get(rawDecl.alias), targetRaw);
-    return { name, baseKind: rawDecl.alias, presetVariant: preset.variant, ...container };
+    return { name, baseKind: rawDecl.alias, presetVariant: presetVariantOf(name, pluginName, rawDecl), ...container };
   }
-  return { name, baseKind: name, ...resolveContainerShape(name, pluginName, rawDecl) };
+  const presetVariant = presetVariantOf(name, pluginName, rawDecl);
+  return {
+    name,
+    baseKind: name,
+    ...presetVariant !== undefined ? { presetVariant } : {},
+    ...resolveContainerShape(name, pluginName, rawDecl)
+  };
 }
 var CORE_MARKER_OWNER = "Gutterpress";
 var CORE_DECLARED_MARKERS = {
   columns: {
     class: "gp-columns",
+    preset: { variant: "2" },
     variants: { 1: "gp-columns-1", 2: "gp-columns-2", 3: "gp-columns-3", 4: "gp-columns-4", 5: "gp-columns-5" }
   }
 };
@@ -1348,20 +1358,35 @@ function plugin(md, pluginOptions = {}) {
       const at = declaredFrameIndex(kind);
       if (at === -1)
         return false;
-      while (declaredFrames.length > at) {
-        const frame = declaredFrames.pop();
-        out.push(new state.Token("layout_component_close", frame.tag, -1));
-      }
+      drainDeclaredFrames(at);
       return true;
     }
-    function drainDeclaredFrames() {
-      while (declaredFrames.length) {
+    function sectionAbove(length) {
+      const section = stack.get("section");
+      return !!section && section.inColumns && declaredFrameIndex("columns") === length - 1;
+    }
+    function sectionHostDepth() {
+      const section = stack.get("section");
+      if (section && !section.inColumns)
+        return 0;
+      return declaredFrameIndex("columns") + 1;
+    }
+    function drainDeclaredFrames(keep = 0) {
+      while (declaredFrames.length > keep) {
+        if (sectionAbove(declaredFrames.length)) {
+          stack.close("section");
+          continue;
+        }
         const frame = declaredFrames.pop();
         out.push(new state.Token("layout_component_close", frame.tag, -1));
       }
     }
     function drainDeclaredFramesAtEof() {
       while (declaredFrames.length) {
+        if (sectionAbove(declaredFrames.length)) {
+          stack.close("section");
+          continue;
+        }
         const frame = declaredFrames.pop();
         if (!frame.decl.autoCloseAtEof) {
           warn(state.env, frame.line || 0, "declared_marker_eof_close", `An open @${frame.kind} reached end-of-document; closing it automatically. Add ` + `@end-${frame.kind} to close it explicitly, or declare autoCloseAt: ["eof"] on this ` + `marker if running to end-of-document is expected.`, null);
@@ -1505,7 +1530,7 @@ function plugin(md, pluginOptions = {}) {
         __component: { component: meta.kind, kind: decl.baseKind, variant, attrs }
       };
     }
-    function openSection(meta) {
+    function openSection(meta, inColumns = false) {
       const t = new state.Token("layout_section_open", "div", 1);
       const component = meta.__component || null;
       addClasses(t, "section", meta.attrs && meta.attrs.class ? meta.attrs.class : "");
@@ -1518,25 +1543,11 @@ function plugin(md, pluginOptions = {}) {
         kind: "section",
         classes: meta.attrs && meta.attrs.class || "",
         sawContent: false,
+        ...inColumns ? { inColumns: true } : {},
         meta: { name: meta.name || null, attrs: { ...meta.attrs || {} }, component },
         openToken: t
       }, t);
     }
-    function breakHost() {
-      return stack.get("section") || stack.get("page") || stack.get("spread");
-    }
-    function gridClassOf(frame) {
-      if (!frame || !frame.classes)
-        return null;
-      return frame.classes.split(/\s+/).find((c) => c.startsWith("gp-grid-")) || null;
-    }
-    function warnBreakInsideGrid(kind, line, meta) {
-      const host = breakHost();
-      const gridClass = gridClassOf(host);
-      if (!gridClass)
-        return;
-      warn(state.env, line, "break_inside_grid", `@${kind} inside a grid container: the enclosing @${host.kind} carries .${gridClass}, so this break's <div> becomes a grid ITEM — it takes a cell of its own, corrupts the grid's placement, and print and the live preview then disagree about which page the content after it lands on. Move the break outside the grid @${host.kind}, or remove it — grid rows already flow and fragment across pages on their own.`, meta);
-    }
     function warnIfEmptyDecoratedSection(closingKind, closingLine) {
       const sec = stack.get("section");
       if (!sec || sec.sawContent)
@@ -1601,14 +1612,15 @@ function plugin(md, pluginOptions = {}) {
         continue;
       }
       if (kind === "section") {
-        drainDeclaredFrames();
+        const keep = sectionHostDepth();
+        drainDeclaredFrames(keep);
         warnIfEmptyDecoratedSection("section", line);
         stack.close("section");
         const spread = stack.get("spread");
         if (spread && spread.noPagesYet) {
           warn(state.env, line, "spread_without_pages", "@section inside a spread without an explicit @page. Allowed (adhoc spread), but explicit @page markers give stronger control.", meta);
         }
-        openSection(meta);
+        openSection(meta, keep > 0);
         continue;
       }
       if (kind === "continue") {
@@ -1617,7 +1629,8 @@ function plugin(md, pluginOptions = {}) {
           warn(state.env, line, "continue_without_section", "@continue used without an open @section; ignoring marker.", meta);
           continue;
         }
-        drainDeclaredFrames();
+        const keep = sectionHostDepth();
+        drainDeclaredFrames(keep);
         const contMeta = {
           name: section.meta.name,
           attrs: { ...section.meta.attrs || {} }
@@ -1632,11 +1645,10 @@ function plugin(md, pluginOptions = {}) {
           cls.push("gp-continued");
         contMeta.attrs.class = cls.join(" ");
         stack.close("section");
-        openSection(contMeta);
+        openSection(contMeta, keep > 0);
         continue;
       }
       if (kind === "page-break") {
-        warnBreakInsideGrid("page-break", line, meta);
         const t = new state.Token("layout_page_break", "div", 0);
         t.meta = { line };
         t.attrSet("class", "gp-page-break");
@@ -1645,7 +1657,6 @@ function plugin(md, pluginOptions = {}) {
         continue;
       }
       if (kind === "column-break") {
-        warnBreakInsideGrid("column-break", line, meta);
         const t = new state.Token("layout_column_break", "div", 0);
         t.meta = { line };
         t.attrSet("class", "gp-column-break");
@@ -1654,7 +1665,7 @@ function plugin(md, pluginOptions = {}) {
         continue;
       }
       if (kind === "end-section") {
-        drainDeclaredFrames();
+        drainDeclaredFrames(sectionHostDepth());
         warnIfEmptyDecoratedSection("end-section", line);
         stack.close("section");
         continue;
@@ -1752,11 +1763,20 @@ body { margin: 0; }
 .gp-column-break { break-after: column; height: 0; font-size: 0; line-height: 0; visibility: hidden; }
 
 :where(h1,h2,h3,h4,h5,h6) { break-after: avoid; }
+/* A lead-in paragraph ("**ROLL A DIE!**" above a roll table, "You will need:"
+   above a list) stays with the table or list it introduces, the way a heading
+   stays with what follows it -- otherwise the label can end a column or page
+   with its table starting on the next (#370). Standard break-after; the
+   :has() selector is Chromium's own. :where() keeps specificity at zero so an
+   author rule such as p { break-after: auto } wins. Deliberately table/ul/ol only,
+   also when a @section wraps it (the second rule): the lead-in then keeps with
+   the section that opens with the table or list. */
+:where(p):has(+ :where(table, ul, ol)) { break-after: avoid; }
+:where(p):has(+ :where(.section) > :where(table, ul, ol):first-child) { break-after: avoid; }
 :where(img, svg, video) { max-width: 100%; }
 :where(p > img:only-child, figure > img) { width: fit-content; max-width: 100%; height: auto; vertical-align: bottom; }
 :where(p) > :where(img:not([class])) { max-height: calc(var(--gp-content-h) - 4px); object-fit: contain; }
 :where(figure) { break-inside: avoid; }
-:where(.section, figure) > :where(:first-child) { break-before: avoid; }
 
 `;
 
@@ -1816,26 +1836,24 @@ var GUTTERPRESS_CSS = `
 .gp-tight { --gp-gap: 0.5em; }
 .gp-loose { --gp-gap: 2em; }
 
-/* column runs — plain CSS Multi-column, exposed as author vocabulary so
-   "put this in two columns" does not require borrowing a styled container
-   from the book's own component layer. That borrowing is what this exists
-   to prevent: a book whose theme paints .section chrome by default gives
-   every author who opens a section just to start a column run a panel they
-   did not ask for, and the book then needs a reset rule to take it back.
-   With a neutral primitive the author opts into columns and nothing else.
+/* column runs — plain CSS Multi-column, emitted by the core @columns marker
+   (markers.js): @columns [1-5] ... @end-columns is the ONE way to lay
+   content out in columns, and @column-break moves to the next column.
+   The classes below are the CSS that marker emits, not author vocabulary.
 
    Permanent vocabulary, not a shim: Chromium implements multicol natively
    and these rules are the standard properties verbatim, so there is no
    spec gap here to remove later. Deliberately minimal — column-fill is
-   NOT set, because the correct value depends on whether the run fragments
-   across pages (auto packs each page's columns; the CSS initial balance is
-   right for a run that fits on one page) and only the author knows which.
-   --gp-column-gap is author-settable.
-   .gp-columns is what the core @columns marker emits (markers.js); on its
-   own it is two columns, and @columns 1 to 5 add the matching count, which
-   wins because it comes later at the same specificity. */
-.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5 {
+   NOT set (the CSS initial balance applies).
+   Themes style a run through two tokens instead of writing column rules:
+     --gp-column-gap   default 1.5em
+     --gp-column-rule  default none (any column-rule shorthand value)
+   Both hooks sit at zero specificity (:where), so any author rule wins.
+   .gp-columns is two columns on its own; a count class (bare @columns
+   emits gp-columns-2) wins because it comes later at the same specificity. */
+:where(.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5) {
   column-gap: var(--gp-column-gap, 1.5em);
+  column-rule: var(--gp-column-rule, none);
 }
 .gp-columns { columns: 2; }
 .gp-columns-1 { columns: 1; }
@@ -1844,54 +1862,8 @@ var GUTTERPRESS_CSS = `
 .gp-columns-4 { columns: 4; }
 .gp-columns-5 { columns: 5; }
 
-/* the per-shape decisions the paragraph above deliberately leaves to the
-   author, named instead of left as raw CSS every book was reinventing
-   (CLAUDE.md §0: "behavior broadly useful to non-technical authors belongs
-   in core").
-   Permanent vocabulary, standard properties verbatim — same rationale as
-   the column/grid runs above. One name each, no aliases:
-     .gp-columns-all       column-span: all      a heading or block that
-                                                  spans every column in the
-                                                  run it sits inside.
-     .gp-columns-flow      column-fill: auto     a run that FRAGMENTS across
-                                                  pages — every page's
-                                                  columns fill instead of
-                                                  only the last one
-                                                  balancing (the dead-column
-                                                  collapse the build's
-                                                  engine.multicol.dead-column
-                                                  warning names this fix
-                                                  for).
-     .gp-columns-balanced  column-fill: balance  a run that fits on ONE
-                                                  page (the CSS initial
-                                                  value — ragged columns
-                                                  would be wrong here). */
-.gp-columns-all { column-span: all; }
-.gp-columns-flow { column-fill: auto; }
-.gp-columns-balanced { column-fill: balance; }
-
-/* grid runs — the SLOTTED counterpart to the column runs above. Grid places
-   each child into the next cell, across then down (deterministic slots: card
-   layouts, stat blocks, image-plus-caption pairs); columns FLOW one text run
-   down then across. Same neutral-primitive rationale as .gp-columns-*, and
-   permanent vocabulary for the same reason: standard CSS Grid verbatim, no
-   spec gap to remove later. MEASURED (Chromium 151, gp-grid evidence pack):
-   grid rows fragment across sheets with EXACT print/viewer parity — 2- and
-   3-col, unequal item heights, mid-row cuts, multi-sheet overflow,
-   break-inside:avoid, gap geometry — so a grid taller than the page is safe,
-   no fit-one-page constraint. Two things to know, not fix:
-     - on a min-height page root (MARKER_CSS), default align-content
-       stretches rows apart to fill the page — identically in both engines.
-       Authors wanting packed rows set align-content: start.
-     - a @page-break / @column-break marker DIRECTLY inside a grid container
-       becomes a grid item and corrupts placement (the one measured parity
-       break); markers.js diagnoses it (break_inside_grid).
-   --gp-grid-gap is author-settable. */
-.gp-grid-2 { display: grid; grid-template-columns: repeat(2, 1fr); gap: var(--gp-grid-gap, 1.5em); }
-.gp-grid-3 { display: grid; grid-template-columns: repeat(3, 1fr); gap: var(--gp-grid-gap, 1.5em); }
-
 /* fragmentation controls — generic pagination utilities for any element,
-   independent of the column/grid vocabulary above (a book reached for
+   independent of the column vocabulary above (a book reached for
    these just as often outside a multicol run: keeping a card whole,
    forcing a section to start a fresh page). Standard properties only —
    this project is Chromium-only (CLAUDE.md), so there are no legacy
@@ -2049,13 +2021,8 @@ var GP_CLASSES = new Set([
   "gp-columns-3",
   "gp-columns-4",
   "gp-columns-5",
-  "gp-columns-all",
-  "gp-columns-flow",
-  "gp-columns-balanced",
   "gp-no-break",
   "gp-break-before",
-  "gp-grid-2",
-  "gp-grid-3",
   "gp-shape",
   "gp-pin",
   "gp-top",
@@ -5674,7 +5641,7 @@ import git from "isomorphic-git";
 // package.json
 var package_default = {
   name: "gutterpress",
-  version: "0.11.17-alpha.5",
+  version: "0.11.17-alpha.6",
   description: "Markdown-to-PDF converter for professional print layout using a native Chromium print engine and Ghostscript.",
   author: "itlackey",
   license: "MPL-2.0",
@@ -10230,7 +10197,7 @@ class PdfOutput {
       const rawPdf = pdfxMode ? path13.join(stage, "raw.pdf") : path13.resolve(pdfFile);
       await fsp2.mkdir(path13.dirname(path13.resolve(pdfFile)), { recursive: true });
       log.info("Rendering HTML to PDF via the Gutterpress engine (native Chromium pagination)");
-      const { buildNativePdf } = await import("./engine-eactk9nn.js");
+      const { buildNativePdf } = await import("./engine-5d1rpxxq.js");
       const engineDiagnostics = await buildNativePdf(htmlFile, rawPdf, {
         title: config.title,
         author: config.authors.length > 0 ? config.authors.join(", ") : undefined,

package/dist/{index-5gp6mkmf.js → index-vmcfahe2.js}

@@ -163,7 +163,7 @@ var preview_shell_default = "./preview-shell-xwn84kqr.js";
 var CGATS21_CRPC1_default = "./CGATS21_CRPC1-g0e3k7kr.icc";
 
 // src/assets/engine/gutterpress-viewer.js
-var gutterpress_viewer_default = "./gutterpress-viewer-1n793gwd.js";
+var gutterpress_viewer_default = "./gutterpress-viewer-ez7k4ha7.js";
 
 // src/assets/engine/gutterpress-agent.js
 var gutterpress_agent_default = "./gutterpress-agent-cazqstr1.js";
@@ -217,7 +217,7 @@ var package_default2 = "./package-aenwjew3.json";
 var README_default2 = "./README-3nj919rm.md";
 
 // src/assets/extension-templates/theme/components.yaml
-var components_default = "./components-dhgv2sm7.yaml";
+var components_default = "./components-zzqdpt3m.yaml";
 
 // src/assets/extension-templates/theme/snippets/callout.md
 var callout_default = "./callout-hv56m16h.md";
@@ -232,7 +232,7 @@ var base_default = "./base-ypqh9n7f.css";
 var components_default2 = "./components-aam0fe2z.css";
 
 // src/assets/extension-templates/theme/styles/page-templates.css
-var page_templates_default = "./page-templates-7md4ev7d.css";
+var page_templates_default = "./page-templates-tx9ryt19.css";
 
 // src/assets/extension-templates/theme/styles/page-rules.css
 var page_rules_default = "./page-rules-nsj3aw42.css";

package/dist/index.js

@@ -152,14 +152,14 @@ import {
   testRemoteAccess,
   updateExtensions,
   validateProjectExtensions
-} from "./index-5ez30g3a.js";
+} from "./index-2vd5b3vy.js";
 import"./index-ht1bcqdd.js";
 import {
   BUILD_DIAGNOSTIC_CODES
-} from "./index-mb8mzwye.js";
+} from "./index-09h3n36d.js";
 import {
   BuildError
-} from "./index-5gp6mkmf.js";
+} from "./index-vmcfahe2.js";
 import {
   DEFAULT_PRINT_OPTS,
   assertMilestone,

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

@@ -133,7 +133,7 @@
  * carrying gp-left could start shifting; that is standards-tracking per
  * CLAUDE.md ("Chrome wins once it ships"), not a bug in the author's book.
  */
-export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary. One vocabulary, gp-* only \u2014 the\n   pre-vocabulary utility names (.center/.float-left/.float-right/\n   .full-width/.full-bleed) were REMOVED when gp-* shipped; books rename\n   the classes in their markdown (see the migration note). Source ORDER is\n   the contract \u2014 see the doctrine comment above. */\n\n/* flow positions */\n.gp-left {\n  float: left;\n  margin: 0 var(--gp-gap, 1em) var(--gp-gap, 1em) 0;\n  max-width: 50%;\n}\n.gp-right {\n  float: right;\n  margin: 0 0 var(--gp-gap, 1em) var(--gp-gap, 1em);\n  max-width: 50%;\n}\n.gp-center {\n  display: block;\n  float: none;\n  margin-left: auto;\n  margin-right: auto;\n  max-width: 100%;\n}\n.gp-full {\n  display: block;\n  float: none;\n  width: 100%;\n  max-width: 100%;\n}\n@page gp-full-bleed { margin-left: 0; margin-right: 0; }\n.gp-bleed {\n  display: block;\n  float: none;\n  break-before: page;\n  page: gp-full-bleed;\n  max-width: none;\n  width: 100%;\n  margin-left: 0;\n  margin-right: 0;\n}\n\n/* sizes \u2014 AFTER the flow positions so max-width:100% lifts the floats' 50%\n   cap at equal specificity */\n.gp-small { width: 25%; max-width: 100%; }\n.gp-medium { width: 50%; max-width: 100%; }\n.gp-large { width: 75%; max-width: 100%; }\n\n/* float clearance presets \u2014 consumed by var(--gp-gap) in the float rules\n   above and by .gp-shape's shape-margin below; --gp-gap itself is\n   author-settable CSS */\n.gp-tight { --gp-gap: 0.5em; }\n.gp-loose { --gp-gap: 2em; }\n\n/* column runs \u2014 plain CSS Multi-column, exposed as author vocabulary so\n   \"put this in two columns\" does not require borrowing a styled container\n   from the book's own component layer. That borrowing is what this exists\n   to prevent: a book whose theme paints .section chrome by default gives\n   every author who opens a section just to start a column run a panel they\n   did not ask for, and the book then needs a reset rule to take it back.\n   With a neutral primitive the author opts into columns and nothing else.\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, because the correct value depends on whether the run fragments\n   across pages (auto packs each page's columns; the CSS initial balance is\n   right for a run that fits on one page) and only the author knows which.\n   --gp-column-gap is author-settable.\n   .gp-columns is what the core @columns marker emits (markers.js); on its\n   own it is two columns, and @columns 1 to 5 add the matching count, which\n   wins because it comes later at the same specificity. */\n.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}\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/* the per-shape decisions the paragraph above deliberately leaves to the\n   author, named instead of left as raw CSS every book was reinventing\n   (CLAUDE.md \u00A70: \"behavior broadly useful to non-technical authors belongs\n   in core\").\n   Permanent vocabulary, standard properties verbatim \u2014 same rationale as\n   the column/grid runs above. One name each, no aliases:\n     .gp-columns-all       column-span: all      a heading or block that\n                                                  spans every column in the\n                                                  run it sits inside.\n     .gp-columns-flow      column-fill: auto     a run that FRAGMENTS across\n                                                  pages \u2014 every page's\n                                                  columns fill instead of\n                                                  only the last one\n                                                  balancing (the dead-column\n                                                  collapse the build's\n                                                  engine.multicol.dead-column\n                                                  warning names this fix\n                                                  for).\n     .gp-columns-balanced  column-fill: balance  a run that fits on ONE\n                                                  page (the CSS initial\n                                                  value \u2014 ragged columns\n                                                  would be wrong here). */\n.gp-columns-all { column-span: all; }\n.gp-columns-flow { column-fill: auto; }\n.gp-columns-balanced { column-fill: balance; }\n\n/* grid runs \u2014 the SLOTTED counterpart to the column runs above. Grid places\n   each child into the next cell, across then down (deterministic slots: card\n   layouts, stat blocks, image-plus-caption pairs); columns FLOW one text run\n   down then across. Same neutral-primitive rationale as .gp-columns-*, and\n   permanent vocabulary for the same reason: standard CSS Grid verbatim, no\n   spec gap to remove later. MEASURED (Chromium 151, gp-grid evidence pack):\n   grid rows fragment across sheets with EXACT print/viewer parity \u2014 2- and\n   3-col, unequal item heights, mid-row cuts, multi-sheet overflow,\n   break-inside:avoid, gap geometry \u2014 so a grid taller than the page is safe,\n   no fit-one-page constraint. Two things to know, not fix:\n     - on a min-height page root (MARKER_CSS), default align-content\n       stretches rows apart to fill the page \u2014 identically in both engines.\n       Authors wanting packed rows set align-content: start.\n     - a @page-break / @column-break marker DIRECTLY inside a grid container\n       becomes a grid item and corrupts placement (the one measured parity\n       break); markers.js diagnoses it (break_inside_grid).\n   --gp-grid-gap is author-settable. */\n.gp-grid-2 { display: grid; grid-template-columns: repeat(2, 1fr); gap: var(--gp-grid-gap, 1.5em); }\n.gp-grid-3 { display: grid; grid-template-columns: repeat(3, 1fr); gap: var(--gp-grid-gap, 1.5em); }\n\n/* fragmentation controls \u2014 generic pagination utilities for any element,\n   independent of the column/grid vocabulary above (a book reached for\n   these just as often outside a multicol run: keeping a card whole,\n   forcing a section to start a fresh page). Standard properties only \u2014\n   this project is Chromium-only (CLAUDE.md), so there are no legacy\n   page-break-* twins to also emit. One name each. */\n.gp-no-break { break-inside: avoid; }\n.gp-break-before { break-before: page; }\n\n/* shape wrap \u2014 text follows the image's alpha silhouette instead of its\n   rectangular box. shape-outside only applies to floats, so this is inert\n   without .gp-left/.gp-right (and under .gp-pin, which un-floats). The\n   shape URL cannot be written in CSS (url() contexts can't read attr()),\n   so the image renderer rule (images.ts) mirrors the src into an inline\n   --gp-shape:url(...) custom property whenever it sees this class --\n   authors only ever type the class. threshold 0.2 ignores near-transparent\n   anti-aliasing halos; shape-margin shares the float-gap vocabulary. */\nimg.gp-shape {\n  shape-outside: var(--gp-shape);\n  shape-image-threshold: 0.2;\n  shape-margin: var(--gp-gap, 1em);\n}\n\n/* pin \u2014 within the nearest positioned ancestor (.page/.spread, rule above).\n   inset:0 and the explicit centers are load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  inset: 0;\n  align-self: center;\n  justify-self: center;\n  margin: 0;\n  max-width: 100%;\n}\n\n/* pin edge modifiers \u2014 AFTER .gp-pin to beat its center defaults;\n   justify-self is inert on in-flow floats, so gp-left/gp-right safely do\n   double duty as flow float + pin edge */\n.gp-top { align-self: start; }\n.gp-bottom { align-self: end; }\n.gp-left { justify-self: start; }\n.gp-right { justify-self: end; }\n\n/* wrapper-margin neutralization (same pattern and rationale as the\n   .gp-bleed paragraph-margin note in the doctrine comment; for pin, the\n   emptied paragraph would otherwise leave a phantom margin gap in flow) */\n:where(p:has(> img.gp-bleed:only-child)) { margin: 0; }\n:where(p:has(> img.gp-pin:only-child)) { margin: 0; }\n\n/* depth \u2014 a named ladder for z-index, so books stop hand-tuning bare\n   integers. A real book measured 21 z-index declarations using only four\n   distinct values (-1, 0, 1, 2), each written literally at its use site.\n   The custom properties are the author-settable surface (a book needing a\n   deeper stack raises them once); the classes are the shorthand.\n\n   NOT named \"layer\": CSS Paged Media 3 \u00A73.1 already defines \"page layers\"\n   (page background, canvas, borders, contents, margin boxes) and those are\n   parts of the PAGE BOX, not a z-ladder for content. Reusing the word for a\n   different concept would collide with the spec vocabulary this project\n   tracks. The pin EDGE modifiers already own .gp-top/.gp-bottom, so the\n   ladder avoids those words too.\n\n   .gp-behind is the one that earns its place: it puts a pinned image UNDER\n   the page's text, which is otherwise impossible to express without a bare\n   negative z-index. \"Above\" needs no class \u2014 an out-of-flow pin already\n   paints above in-flow content.\n\n   Two things silently defeat .gp-behind, neither visible at the use site:\n     - a stacking context on the .page/.spread ancestor (z-index, isolation,\n       opacity, filter, transform on it traps the negative layer inside).\n       Core keeps .page/.spread at 'position: relative; z-index: auto'\n       precisely so they are not stacking contexts.\n     - a clipping ancestor (overflow other than visible) \u2014 but only where\n       the art actually overhangs that ancestor's clip box on a clipped\n       axis: the overhang is cut off, the same mechanism that clips a\n       .gp-bleed plate back to the wrapper's width. Clipping never reorders\n       layers \u2014 within-bounds art under a clipping .page prints whole and\n       still behind (measured; see the build audit's comment in\n       engine/compiler/build.ts), and a static wrapper's overflow never\n       binds an abspos .gp-pin at all.\n   The build-time engine.layer.trapped audit reports both against the live\n   ancestor chain. printsafe/page-containment is only an early source hint for\n   declarations written directly on .page/.spread. */\n:root {\n  --gp-z-behind: -1;\n  --gp-z-base: 0;\n  --gp-z-raised: 1;\n  --gp-z-front: 2;\n}\n.gp-behind { z-index: var(--gp-z-behind); }\n.gp-base   { z-index: var(--gp-z-base); }\n.gp-raised { z-index: var(--gp-z-raised); }\n.gp-front  { z-index: var(--gp-z-front); }\n\n/* GFM-style alert/callout boxes (#237) \u2014 the DOM gfm-alerts.ts emits from\n   \"> [!TYPE]\" blockquote syntax when a project opts into the bundled\n   gutterpress-gfm-alerts feature (BUILTIN_OPTIONAL_PLUGINS, renderer.ts).\n   The plugin is optional and inert by default; these rules are equally\n   inert wherever the classes never appear, exactly like every other\n   utility above, so shipping them costs nothing to a book that has not\n   turned the feature on.\n\n   This is authored-COMPONENT vocabulary, not the @marker structural family\n   (markers.js/MARKER_CSS) \u2014 CLAUDE.md \u00A76 splits the two core CSS blocks by\n   ROLE, and an author-facing box an author invokes via inline syntax is the\n   same role as every other gp-* utility here, not page/chapter/section DOM.\n\n   Deliberately minimal (CLAUDE.md \"thin over capable\" / the issue's own\n   \"a rule and a label\"): a left border plus a bold label, :where()'d to\n   zero specificity so a theme's own (unlayered) rule for any of these\n   classes wins outright regardless of selector weight \u2014 see the\n   cascade-layers note atop this file. Five semantic accent colors (the same\n   NOTE/TIP/IMPORTANT/WARNING/CAUTION hues GitHub's own alerts use \u2014 a\n   long-established, non-proprietary convention, not DC branding) are\n   exposed as :root custom properties, the same author-settable-surface\n   pattern as the --gp-z-* ladder above: a book retints every alert of one\n   type by overriding a single property, no specificity fight required.\n   --gp-alert-color cascades from the type modifier down to .gp-alert-title\n   through ordinary CSS inheritance (the title is always a DOM descendant of\n   the box), so it is set in exactly five places, not ten. */\n:root {\n  --gp-alert-note-color: #0969da;\n  --gp-alert-tip-color: #1a7f37;\n  --gp-alert-important-color: #8250df;\n  --gp-alert-warning-color: #9a6700;\n  --gp-alert-caution-color: #cf222e;\n}\n:where(.gp-alert) {\n  margin: 1em 0;\n  padding: 0.5em 1em;\n  border-left: 0.25em solid var(--gp-alert-color, currentColor);\n}\n:where(.gp-alert-title) {\n  margin: 0 0 0.5em;\n  font-weight: bold;\n  color: var(--gp-alert-color, inherit);\n}\n:where(.gp-alert-note)      { --gp-alert-color: var(--gp-alert-note-color); }\n:where(.gp-alert-tip)       { --gp-alert-color: var(--gp-alert-tip-color); }\n:where(.gp-alert-important) { --gp-alert-color: var(--gp-alert-important-color); }\n:where(.gp-alert-warning)   { --gp-alert-color: var(--gp-alert-warning-color); }\n:where(.gp-alert-caution)   { --gp-alert-color: var(--gp-alert-caution-color); }\n";
+export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary. One vocabulary, gp-* only \u2014 the\n   pre-vocabulary utility names (.center/.float-left/.float-right/\n   .full-width/.full-bleed) were REMOVED when gp-* shipped; books rename\n   the classes in their markdown (see the migration note). Source ORDER is\n   the contract \u2014 see the doctrine comment above. */\n\n/* flow positions */\n.gp-left {\n  float: left;\n  margin: 0 var(--gp-gap, 1em) var(--gp-gap, 1em) 0;\n  max-width: 50%;\n}\n.gp-right {\n  float: right;\n  margin: 0 0 var(--gp-gap, 1em) var(--gp-gap, 1em);\n  max-width: 50%;\n}\n.gp-center {\n  display: block;\n  float: none;\n  margin-left: auto;\n  margin-right: auto;\n  max-width: 100%;\n}\n.gp-full {\n  display: block;\n  float: none;\n  width: 100%;\n  max-width: 100%;\n}\n@page gp-full-bleed { margin-left: 0; margin-right: 0; }\n.gp-bleed {\n  display: block;\n  float: none;\n  break-before: page;\n  page: gp-full-bleed;\n  max-width: none;\n  width: 100%;\n  margin-left: 0;\n  margin-right: 0;\n}\n\n/* sizes \u2014 AFTER the flow positions so max-width:100% lifts the floats' 50%\n   cap at equal specificity */\n.gp-small { width: 25%; max-width: 100%; }\n.gp-medium { width: 50%; max-width: 100%; }\n.gp-large { width: 75%; max-width: 100%; }\n\n/* float clearance presets \u2014 consumed by var(--gp-gap) in the float rules\n   above and by .gp-shape's shape-margin below; --gp-gap itself is\n   author-settable CSS */\n.gp-tight { --gp-gap: 0.5em; }\n.gp-loose { --gp-gap: 2em; }\n\n/* column runs \u2014 plain CSS Multi-column, emitted by the core @columns marker\n   (markers.js): @columns [1-5] ... @end-columns is the ONE way to lay\n   content out in columns, and @column-break moves to the next column.\n   The classes below are the CSS that marker emits, not author vocabulary.\n\n   Permanent vocabulary, not a shim: Chromium implements multicol natively\n   and these rules are the standard properties verbatim, so there is no\n   spec gap here to remove later. Deliberately minimal \u2014 column-fill is\n   NOT set (the CSS initial balance applies).\n   Themes style a run through two tokens instead of writing column rules:\n     --gp-column-gap   default 1.5em\n     --gp-column-rule  default none (any column-rule shorthand value)\n   Both hooks sit at zero specificity (:where), so any author rule wins.\n   .gp-columns is two columns on its own; a count class (bare @columns\n   emits gp-columns-2) wins because it comes later at the same specificity. */\n:where(.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5) {\n  column-gap: var(--gp-column-gap, 1.5em);\n  column-rule: var(--gp-column-rule, none);\n}\n.gp-columns { columns: 2; }\n.gp-columns-1 { columns: 1; }\n.gp-columns-2 { columns: 2; }\n.gp-columns-3 { columns: 3; }\n.gp-columns-4 { columns: 4; }\n.gp-columns-5 { columns: 5; }\n\n/* fragmentation controls \u2014 generic pagination utilities for any element,\n   independent of the column vocabulary above (a book reached for\n   these just as often outside a multicol run: keeping a card whole,\n   forcing a section to start a fresh page). Standard properties only \u2014\n   this project is Chromium-only (CLAUDE.md), so there are no legacy\n   page-break-* twins to also emit. One name each. */\n.gp-no-break { break-inside: avoid; }\n.gp-break-before { break-before: page; }\n\n/* shape wrap \u2014 text follows the image's alpha silhouette instead of its\n   rectangular box. shape-outside only applies to floats, so this is inert\n   without .gp-left/.gp-right (and under .gp-pin, which un-floats). The\n   shape URL cannot be written in CSS (url() contexts can't read attr()),\n   so the image renderer rule (images.ts) mirrors the src into an inline\n   --gp-shape:url(...) custom property whenever it sees this class --\n   authors only ever type the class. threshold 0.2 ignores near-transparent\n   anti-aliasing halos; shape-margin shares the float-gap vocabulary. */\nimg.gp-shape {\n  shape-outside: var(--gp-shape);\n  shape-image-threshold: 0.2;\n  shape-margin: var(--gp-gap, 1em);\n}\n\n/* pin \u2014 within the nearest positioned ancestor (.page/.spread, rule above).\n   inset:0 and the explicit centers are load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  inset: 0;\n  align-self: center;\n  justify-self: center;\n  margin: 0;\n  max-width: 100%;\n}\n\n/* pin edge modifiers \u2014 AFTER .gp-pin to beat its center defaults;\n   justify-self is inert on in-flow floats, so gp-left/gp-right safely do\n   double duty as flow float + pin edge */\n.gp-top { align-self: start; }\n.gp-bottom { align-self: end; }\n.gp-left { justify-self: start; }\n.gp-right { justify-self: end; }\n\n/* wrapper-margin neutralization (same pattern and rationale as the\n   .gp-bleed paragraph-margin note in the doctrine comment; for pin, the\n   emptied paragraph would otherwise leave a phantom margin gap in flow) */\n:where(p:has(> img.gp-bleed:only-child)) { margin: 0; }\n:where(p:has(> img.gp-pin:only-child)) { margin: 0; }\n\n/* depth \u2014 a named ladder for z-index, so books stop hand-tuning bare\n   integers. A real book measured 21 z-index declarations using only four\n   distinct values (-1, 0, 1, 2), each written literally at its use site.\n   The custom properties are the author-settable surface (a book needing a\n   deeper stack raises them once); the classes are the shorthand.\n\n   NOT named \"layer\": CSS Paged Media 3 \u00A73.1 already defines \"page layers\"\n   (page background, canvas, borders, contents, margin boxes) and those are\n   parts of the PAGE BOX, not a z-ladder for content. Reusing the word for a\n   different concept would collide with the spec vocabulary this project\n   tracks. The pin EDGE modifiers already own .gp-top/.gp-bottom, so the\n   ladder avoids those words too.\n\n   .gp-behind is the one that earns its place: it puts a pinned image UNDER\n   the page's text, which is otherwise impossible to express without a bare\n   negative z-index. \"Above\" needs no class \u2014 an out-of-flow pin already\n   paints above in-flow content.\n\n   Two things silently defeat .gp-behind, neither visible at the use site:\n     - a stacking context on the .page/.spread ancestor (z-index, isolation,\n       opacity, filter, transform on it traps the negative layer inside).\n       Core keeps .page/.spread at 'position: relative; z-index: auto'\n       precisely so they are not stacking contexts.\n     - a clipping ancestor (overflow other than visible) \u2014 but only where\n       the art actually overhangs that ancestor's clip box on a clipped\n       axis: the overhang is cut off, the same mechanism that clips a\n       .gp-bleed plate back to the wrapper's width. Clipping never reorders\n       layers \u2014 within-bounds art under a clipping .page prints whole and\n       still behind (measured; see the build audit's comment in\n       engine/compiler/build.ts), and a static wrapper's overflow never\n       binds an abspos .gp-pin at all.\n   The build-time engine.layer.trapped audit reports both against the live\n   ancestor chain. printsafe/page-containment is only an early source hint for\n   declarations written directly on .page/.spread. */\n:root {\n  --gp-z-behind: -1;\n  --gp-z-base: 0;\n  --gp-z-raised: 1;\n  --gp-z-front: 2;\n}\n.gp-behind { z-index: var(--gp-z-behind); }\n.gp-base   { z-index: var(--gp-z-base); }\n.gp-raised { z-index: var(--gp-z-raised); }\n.gp-front  { z-index: var(--gp-z-front); }\n\n/* GFM-style alert/callout boxes (#237) \u2014 the DOM gfm-alerts.ts emits from\n   \"> [!TYPE]\" blockquote syntax when a project opts into the bundled\n   gutterpress-gfm-alerts feature (BUILTIN_OPTIONAL_PLUGINS, renderer.ts).\n   The plugin is optional and inert by default; these rules are equally\n   inert wherever the classes never appear, exactly like every other\n   utility above, so shipping them costs nothing to a book that has not\n   turned the feature on.\n\n   This is authored-COMPONENT vocabulary, not the @marker structural family\n   (markers.js/MARKER_CSS) \u2014 CLAUDE.md \u00A76 splits the two core CSS blocks by\n   ROLE, and an author-facing box an author invokes via inline syntax is the\n   same role as every other gp-* utility here, not page/chapter/section DOM.\n\n   Deliberately minimal (CLAUDE.md \"thin over capable\" / the issue's own\n   \"a rule and a label\"): a left border plus a bold label, :where()'d to\n   zero specificity so a theme's own (unlayered) rule for any of these\n   classes wins outright regardless of selector weight \u2014 see the\n   cascade-layers note atop this file. Five semantic accent colors (the same\n   NOTE/TIP/IMPORTANT/WARNING/CAUTION hues GitHub's own alerts use \u2014 a\n   long-established, non-proprietary convention, not DC branding) are\n   exposed as :root custom properties, the same author-settable-surface\n   pattern as the --gp-z-* ladder above: a book retints every alert of one\n   type by overriding a single property, no specificity fight required.\n   --gp-alert-color cascades from the type modifier down to .gp-alert-title\n   through ordinary CSS inheritance (the title is always a DOM descendant of\n   the box), so it is set in exactly five places, not ten. */\n:root {\n  --gp-alert-note-color: #0969da;\n  --gp-alert-tip-color: #1a7f37;\n  --gp-alert-important-color: #8250df;\n  --gp-alert-warning-color: #9a6700;\n  --gp-alert-caution-color: #cf222e;\n}\n:where(.gp-alert) {\n  margin: 1em 0;\n  padding: 0.5em 1em;\n  border-left: 0.25em solid var(--gp-alert-color, currentColor);\n}\n:where(.gp-alert-title) {\n  margin: 0 0 0.5em;\n  font-weight: bold;\n  color: var(--gp-alert-color, inherit);\n}\n:where(.gp-alert-note)      { --gp-alert-color: var(--gp-alert-note-color); }\n:where(.gp-alert-tip)       { --gp-alert-color: var(--gp-alert-tip-color); }\n:where(.gp-alert-important) { --gp-alert-color: var(--gp-alert-important-color); }\n:where(.gp-alert-warning)   { --gp-alert-color: var(--gp-alert-warning-color); }\n:where(.gp-alert-caution)   { --gp-alert-color: var(--gp-alert-caution-color); }\n";
 /**
  * GP_CLASSES — every class an author may legitimately write with a `gp-`
  * prefix: the `.gp-*` selectors in `GUTTERPRESS_CSS` above, the two

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

@@ -91,11 +91,20 @@ export default function plugin(md: any, pluginOptions?: {}): void;
  * pinned foot up by less than a point and absorbs sub-pixel rounding in the
  * published value. Do not "clean it up" — the sheet it costs is silent.
  *
- * The break/orphan rules below (`break-after` on headings, image sizing,
- * first-child glue) are all `:where()` so they carry zero specificity —
+ * The break/orphan rules below (`break-after` on headings, image sizing)
+ * are all `:where()` so they carry zero specificity —
  * author CSS at any specificity wins outright, reusing this same
  * after-author injection point.
  *
+ * There is deliberately NO `.section > :first-child { break-before: avoid }`
+ * "glue". A first child's break-before propagates to its parent's start
+ * edge, so it made the break BEFORE every section `avoid`: a section after
+ * other content could not move whole to the next page, and Chromium split it
+ * instead, ignoring its own `break-inside: avoid`. Measured with and without
+ * (marker-css-section-break.test.ts): it never prevented a stranded top edge
+ * or heading. Its one useful side effect, a lead-in paragraph travelling with
+ * a following @section that wraps a table, is the explicit rule below.
+ *
  * `vertical-align: bottom` on a lone image is a print-correctness rule, not
  * cosmetics. An `<img>` in a `<p>` is inline-level, so its line box adds
  * half-leading/descender space UNDER the image: an image sized to exactly the
@@ -158,8 +167,7 @@ export default function plugin(md: any, pluginOptions?: {}): void;
  * break-inside rule, at ANY specificity, still wins outright.
  *
  * The companion "spanner + unbreakable box" glue pattern (`column-span: all`
- * followed by a `break-inside: avoid` box, native-engine-styling-guide.md
- * §5) was measured for this same adoption pass and DELIBERATELY NOT
+ * followed by a `break-inside: avoid` box) was measured for this same adoption pass and DELIBERATELY NOT
  * adopted: a `:where()`-zero-specificity override can never win against
  * whatever real-specificity rule gave the box its `break-inside: avoid` in
  * the first place (a synthetic 2-column fixture with the candidate
@@ -169,7 +177,7 @@ export default function plugin(md: any, pluginOptions?: {}): void;
  * a context-blind version of the same idea is actively wrong for at least
  * one real, shipped case (a short, non-fragmenting instance that needed its
  * `avoid` restored after a general fragmenting-context rule took it away).
- * It stays an author remedy, named in the styling guide (`.gp-columns-all`).
+ * Core ships no spanner class: a spanning heading is the end of one @columns run and the start of the next.
  *
  */
-export const MARKER_CSS: "\n/* The UA default of 8px body margin is a screen affordance with no meaning\n   in paged media, and engines disagree about it: a polyfill that treats the\n   page div as the page box drops it, native print keeps it. Left in place it\n   insets EVERY page's content by 8px per side, and -- measured, 300dpi,\n   6x4in sheet -- it is what stops a full-width block from reaching the\n   paper: it lands at 0.080..5.917in of a 6in sheet instead of\n   0.000..6.000in, because width:100% resolves against the BODY content box,\n   not the page's. Zeroing it here (first in the cascade) makes the two\n   agree. Authors who want a body margin still just declare one. */\nbody { margin: 0; }\n\n.gp-page-break { break-before: page; }\n.page { break-before: page; }\n.spread { break-before: page; }\n:where(.page, .spread) { position: relative; display: flow-root; box-sizing: border-box; min-height: calc(var(--gp-content-h, 1px) - 1px); }\n.gp-column-break { break-after: column; height: 0; font-size: 0; line-height: 0; visibility: hidden; }\n\n:where(h1,h2,h3,h4,h5,h6) { break-after: avoid; }\n:where(img, svg, video) { max-width: 100%; }\n:where(p > img:only-child, figure > img) { width: fit-content; max-width: 100%; height: auto; vertical-align: bottom; }\n:where(p) > :where(img:not([class])) { max-height: calc(var(--gp-content-h) - 4px); object-fit: contain; }\n:where(figure) { break-inside: avoid; }\n:where(.section, figure) > :where(:first-child) { break-before: avoid; }\n\n";
+export const MARKER_CSS: "\n/* The UA default of 8px body margin is a screen affordance with no meaning\n   in paged media, and engines disagree about it: a polyfill that treats the\n   page div as the page box drops it, native print keeps it. Left in place it\n   insets EVERY page's content by 8px per side, and -- measured, 300dpi,\n   6x4in sheet -- it is what stops a full-width block from reaching the\n   paper: it lands at 0.080..5.917in of a 6in sheet instead of\n   0.000..6.000in, because width:100% resolves against the BODY content box,\n   not the page's. Zeroing it here (first in the cascade) makes the two\n   agree. Authors who want a body margin still just declare one. */\nbody { margin: 0; }\n\n.gp-page-break { break-before: page; }\n.page { break-before: page; }\n.spread { break-before: page; }\n:where(.page, .spread) { position: relative; display: flow-root; box-sizing: border-box; min-height: calc(var(--gp-content-h, 1px) - 1px); }\n.gp-column-break { break-after: column; height: 0; font-size: 0; line-height: 0; visibility: hidden; }\n\n:where(h1,h2,h3,h4,h5,h6) { break-after: avoid; }\n/* A lead-in paragraph (\"**ROLL A DIE!**\" above a roll table, \"You will need:\"\n   above a list) stays with the table or list it introduces, the way a heading\n   stays with what follows it -- otherwise the label can end a column or page\n   with its table starting on the next (#370). Standard break-after; the\n   :has() selector is Chromium's own. :where() keeps specificity at zero so an\n   author rule such as p { break-after: auto } wins. Deliberately table/ul/ol only,\n   also when a @section wraps it (the second rule): the lead-in then keeps with\n   the section that opens with the table or list. */\n:where(p):has(+ :where(table, ul, ol)) { break-after: avoid; }\n:where(p):has(+ :where(.section) > :where(table, ul, ol):first-child) { break-after: avoid; }\n:where(img, svg, video) { max-width: 100%; }\n:where(p > img:only-child, figure > img) { width: fit-content; max-width: 100%; height: auto; vertical-align: bottom; }\n:where(p) > :where(img:not([class])) { max-height: calc(var(--gp-content-h) - 4px); object-fit: contain; }\n:where(figure) { break-inside: avoid; }\n\n";

package/dist/{new-hzs75cmd.js → new-8xwac8nd.js}

@@ -7,17 +7,17 @@ import {
   TARGET_IDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-82tvm0sg.js";
+} from "./cli-an3pxzzk.js";
 import {
   resolveGhostscript
-} from "./cli-5sg6hcqa.js";
+} from "./cli-0wtnw98y.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-2xpwjanr.js";
+} from "./cli-jjbeqx94.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-c3enmb58.js";
+import"./cli-ycbg7mxk.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";

package/dist/{page-templates-7md4ev7d.css → page-templates-tx9ryt19.css}

@@ -3,7 +3,7 @@
  *
  * OWNS
  *   The layout of a `@page .name` wrapper — how content is arranged WITHIN
- *   one page of the book. Columns, full-bleed art, a centred opener.
+ *   one page of the book. Full-bleed art, a centred opener.
  *
  *   Authored as:
  *
@@ -43,17 +43,10 @@
     max-width: 24em;
   }
 
-  /* A two-column reference page. Core already ships `.gp-columns-2` as
-     general author vocabulary — reach for that first, and use a named
-     template like this only when the page needs more than the columns. */
-  .page.{{PREFIX}}reference {
-    columns: 2;
-    column-gap: var(--{{PREFIX}}space-4);
-    column-rule: 1px solid var(--{{PREFIX}}rule);
-  }
-
+  /* A reference page. Columns are not a template concern: put the content in
+     core's `@columns 2` ... `@end-columns` (and `@column-break`) and core owns
+     the column geometry. This template only styles what sits around them. */
   .page.{{PREFIX}}reference h2 {
-    column-span: all;
     border-block-end: 1px solid var(--{{PREFIX}}rule);
     padding-block-end: var(--{{PREFIX}}space-1);
   }

package/dist/{preflight-4k8dtsfs.js → preflight-62c2r37w.js}

@@ -2,17 +2,17 @@ import {
   executeValidation,
   publishTargetFor,
   reportMissingTools
-} from "./cli-82tvm0sg.js";
+} from "./cli-an3pxzzk.js";
 import {
   log
-} from "./cli-5sg6hcqa.js";
+} from "./cli-0wtnw98y.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-2xpwjanr.js";
+} from "./cli-jjbeqx94.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-c3enmb58.js";
+import"./cli-ycbg7mxk.js";
 import {
   BuildError,
   EXIT_CODES

package/dist/{preview-whg4rwg6.js → preview-qdby30fx.js}

@@ -7,10 +7,10 @@ import {
   runBuild,
   splitOutPath,
   startPreviewServer
-} from "./cli-82tvm0sg.js";
+} from "./cli-an3pxzzk.js";
 import {
   log
-} from "./cli-5sg6hcqa.js";
+} from "./cli-0wtnw98y.js";
 import {
   UsageError,
   parseFormat,
@@ -18,9 +18,9 @@ import {
   rejectExtraPositionals,
   rejectUnknownFlags,
   resolvePort
-} from "./cli-2xpwjanr.js";
+} from "./cli-jjbeqx94.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-c3enmb58.js";
+import"./cli-ycbg7mxk.js";
 import {
   BuildError
 } from "./cli-46ycxe6r.js";

package/dist/{publish-4vtd7qve.js → publish-v9tdq7kc.js}

@@ -11,18 +11,18 @@ import {
   publishProviderFor,
   resolvePublishFormat,
   runPublish
-} from "./cli-82tvm0sg.js";
+} from "./cli-an3pxzzk.js";
 import {
   FileTokenStore,
   log
-} from "./cli-5sg6hcqa.js";
+} from "./cli-0wtnw98y.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-2xpwjanr.js";
+} from "./cli-jjbeqx94.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-c3enmb58.js";
+import"./cli-ycbg7mxk.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";