gutterpress 0.11.20-alpha.2 → 0.11.20-alpha.4

package/dist/index.js

@@ -154,14 +154,15 @@ import {
   testRemoteAccess,
   updateExtensions,
   validateProjectExtensions
-} from "./index-razpty47.js";
+} from "./index-t13p8y08.js";
 import"./index-ht1bcqdd.js";
 import {
   BUILD_DIAGNOSTIC_CODES
-} from "./index-6xwtb7cw.js";
+} from "./index-ad95fws8.js";
 import {
   BuildError
-} from "./index-3nr5rzzp.js";
+} from "./index-gm5xbx5w.js";
+import"./index-sth219v1.js";
 import {
   DEFAULT_PRINT_OPTS,
   assertMilestone,

package/dist/lib/build-fingerprint.d.ts

@@ -5,6 +5,14 @@ type PdfxFingerprintConfig = {
     stripAnnotations: boolean | null;
     /** How near-black text was separated (#331); null when no PDF/X pass ran. Provenance only. */
     blackText?: "icc" | "k-only" | null;
+    /**
+     * How pages with transparency were handled (#385): `pdfx.transparency`,
+     * `pdfx.flattenPages` and `pdfx.rasterDpi`. null when no PDF/X pass ran
+     * (and, for rasterDpi, when unset). Provenance only.
+     */
+    transparency?: "flatten-page" | "preserve-text" | null;
+    flattenPages?: number[] | null;
+    rasterDpi?: number | null;
 };
 export type BuildFingerprintInput = {
     command: "build";

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

@@ -70,6 +70,12 @@ export interface ExtensionMetadata {
      * does the merge.
      */
     snippets?: string;
+    /**
+     * npm `engines.gutterpress` — the Gutterpress versions the extension works
+     * with, as a semver range (e.g. `">=0.11.20-alpha.3"`). Checked when the
+     * extension loads ({@link assertSupportsThisGutterpress}).
+     */
+    gutterpressRange?: string;
     /**
      * The removed `engineStyles` field (#266), carried through from the
      * `gutterpress` block ONLY so {@link assertExtensionContained} can reject it
@@ -119,6 +125,13 @@ export declare function extensionCarries(meta: ExtensionMetadata): ExtensionCarr
  * doctrine {@link readExtensionMeta}'s tolerant JSON parse already follows).
  */
 export declare function pathEscapesFolder(rel: string): boolean;
+/**
+ * Refuse to load an extension whose `engines.gutterpress` range excludes this
+ * Gutterpress, so a book built with too old a version fails with the fix
+ * instead of quietly printing differently. Prereleases count: 0.12.0-alpha.1
+ * satisfies `>=0.11.20`.
+ */
+export declare function assertSupportsThisGutterpress(meta: ExtensionMetadata, ref: string): void;
 /**
  * Every path an extension declares must live INSIDE its own folder — an
  * extension is self-contained by contract (apply/install copies the whole

package/dist/lib/ghostscript.d.ts

@@ -1,3 +1,4 @@
+import type { UnsplittableReason } from "./pdf-inspect";
 /**
  * Resolve the Ghostscript command on every supported platform.
  *
@@ -8,38 +9,39 @@
  */
 export declare function resolveGhostscript(targetPlatform?: NodeJS.Platform, env?: NodeJS.ProcessEnv): Promise<string | undefined>;
 /**
- * Whether `pdfBytes` uses any live PDF transparency — the PDF 1.4 imaging
- * feature, in ALL the forms Chromium emits it, not just alpha-channel images:
+ * The 1-based page numbers of `pdfBytes` that use live PDF transparency — the
+ * PDF 1.4 imaging feature, in ALL the forms Chromium emits it, not just
+ * alpha-channel images:
  *
  *  - a transparency **group** (`/Group << /S /Transparency >>`), which is what
  *    CSS `opacity`, `mix-blend-mode` and friends compile down to;
  *  - an **image soft mask** (`/SMask` on an image XObject, pointing at a real
  *    mask rather than the literal `/None` an opaque image also carries) — an
  *    RGBA source image;
- *  - a **graphics-state** soft mask or constant alpha (`/SMask`, `/ca`, `/CA`
- *    on an `/ExtGState`).
+ *  - a **graphics-state** soft mask, constant alpha (`/ca`, `/CA` below 1) or
+ *    non-Normal blend mode (`/BM`) on an `/ExtGState` — soft `rgba()`
+ *    shadows and fills.
  *
  * PDF/X-1a and PDF/X-3 (as this codebase generates them, `-dCompatibilityLevel=1.3`
  * in {@link convertToPdfxCmyk}) are both based on PDF 1.3, which predates the
  * PDF 1.4 transparency model entirely — live transparency has nothing a
  * PDF-1.3 file can represent it with. Ghostscript's only PDF/X-compliant
  * option is to flatten the page it appears ON down to a single raster image
- * (B.10, measured: a book with alpha-channel artwork loses every embedded
- * font and all searchable text in its PDF/X output, identically on both
- * engines — this is a Ghostscript/PDF-1.3 property, not an engine bug).
- * Detecting it lets the build warn the author PRECISELY, instead of them
- * discovering a fontless PDF/X file after the fact.
+ * (B.10, measured: text and fonts on that page are lost, identically on both
+ * engines — a Ghostscript/PDF-1.3 property, not an engine bug).
+ * {@link flattenTransparentPages} (opt-in, `pdfx.transparency: preserve-text`)
+ * can instead keep the text live on the pages this returns.
  *
- * This walks the parsed object graph rather than scanning raw bytes. A byte
- * scan is NOT sufficient and produced a false "all clear" in review: image
+ * This walks each page's parsed object graph rather than scanning raw bytes. A
+ * byte scan is NOT sufficient and produced a false "all clear" in review: image
  * XObjects are streams, so their dicts do sit uncompressed at top level, but
  * `/ExtGState` and `/Group` dicts are plain objects that Chromium packs into
  * **object streams** (`/Type /ObjStm`, deflate-compressed), where no regex can
- * see them. Measured on four books with known Ghostscript outcomes, this
- * predicate is exactly right on all four; the byte scan silently missed the
- * CSS-`opacity` book, which rasterizes to zero embedded fonts.
+ * see them. Fonts, `/Parent` (which leads to every other page) and `/Annots`
+ * are not followed: an annotation's appearance stream is not page content, and
+ * PDF/X builds strip annotations before conversion.
  */
-export declare function hasLiveTransparency(pdfBytes: Uint8Array): Promise<boolean>;
+export declare function transparentPages(pdfBytes: Uint8Array): Promise<number[]>;
 /**
  * 1-based numbers of the pages that paint a `/ShadingType 1` shading whose
  * function is `/FunctionType 4` (a PostScript calculator function).
@@ -56,7 +58,7 @@ export declare function hasLiveTransparency(pdfBytes: Uint8Array): Promise<boole
  *
  * Walks page resources (and form XObjects they draw) rather than every
  * object, so only shadings a page can actually paint are reported. Like
- * {@link hasLiveTransparency}, it never fails a build: an unparseable PDF
+ * {@link transparentPages}, it never fails a build: an unparseable PDF
  * reports no pages.
  */
 export declare function findPostScriptShadingPages(pdfBytes: Uint8Array): Promise<number[]>;
@@ -81,6 +83,58 @@ export declare function findPostScriptShadingPages(pdfBytes: Uint8Array): Promis
  *     directly (pdf-lib, in-process, no second external tool).
  */
 export declare function stripAnnotations(pdfPath: string, stagingDir: string): Promise<void>;
+/** Why a transparent page is flattened whole under `preserve-text` instead of split. */
+export type FallbackCause = Exclude<UnsplittableReason, "no-text"> | "listed" | "gradient";
+/**
+ * Sort each page that uses transparency (1-based, from {@link transparentPages})
+ * for `pdfx.transparency: preserve-text`:
+ * - `split`: its artwork is flattened and its text kept live
+ *   ({@link flattenTransparentPages});
+ * - `artOnly`: it shows no text, so there is nothing to keep and Ghostscript
+ *   flattens it whole, which is as good;
+ * - `kept`: it has text but is flattened whole anyway, with the cause the
+ *   build reports. The author's `pdfx.flattenPages` list wins, then the
+ *   text's own reason (`unsplittableTextReasons`), then a repeating or conic
+ *   gradient (#386), whose PostScript-function shading the artwork pass
+ *   distorts.
+ * Every transparent page lands in exactly one group.
+ */
+export declare function planTransparentPages(transparent: number[], reasons: Map<number, UnsplittableReason>, flattenPages: number[], gradientPages: number[]): {
+    split: number[];
+    artOnly: number[];
+    kept: Map<number, FallbackCause>;
+};
+/**
+ * Make the pages in `pages` (1-based; the `split` group of
+ * {@link planTransparentPages}) free of transparency while keeping
+ * their text live, so PDF/X (PDF 1.3) conversion has nothing left to flatten
+ * into a single bitmap. Opt-in: `pdfx.transparency: preserve-text`.
+ *
+ * Per affected page, two Ghostscript passes split it in two and pdf-lib
+ * stacks the halves back on the ORIGINAL page object:
+ *
+ *  1. ARTWORK — `pdfimage24 -dFILTERTEXT -r<dpi>` drops the glyphs and
+ *     composites everything left (soft shadows, alpha images, opacity) into
+ *     one opaque image (300 DPI unless `pdfx.rasterDpi` says otherwise),
+ *     straight from the source;
+ *  2. TEXT — `-dFILTERIMAGE -dFILTERVECTOR` keeps only the glyphs. It needs
+ *     `-dNOTRANSPARENCY`: without it Chromium's transparency groups and
+ *     `/ca`/`/SMask` ExtGStates survive in the text-only file and the next
+ *     step flattens the page anyway. That is only faithful for text with no
+ *     transparency of its own, which is why callers leave other pages out;
+ *  3. the page's content is replaced by the artwork with the text drawn on
+ *     top. Editing the original page keeps its boxes (Media/Crop/Trim/Bleed),
+ *     annotations, the document's metadata, outlines and labels exactly as
+ *     they were; only its `/Contents`, `/Resources` and `/Group` change.
+ *
+ * Pages not listed are never touched. Known limits, both consequences of
+ * splitting a page into "picture" and "text": the page's vector chrome
+ * (rules, backgrounds, shapes) becomes the picture, and text is always the
+ * top layer, so text another element covers shows through.
+ */
+export declare function flattenTransparentPages(pdfPath: string, pageNumbers: number[], stagingDir: string, 
+/** artwork resolution (`pdfx.rasterDpi`) */
+dpi?: number): Promise<void>;
 type PdfxFlavor = "x1a" | "x3";
 /**
  * Stamp the Creator metadata field on an existing PDF.

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

@@ -1,5 +1,6 @@
 import { type LoadedPlugin } from "./renderer";
 import { type PrintPadding } from "../../engine/shared/synthesis.ts";
+import { type PrintAreaSource } from "../../engine/shared/print-area.ts";
 /** Reader injected by the host: resolve a project-root-relative file → its text. */
 export type ReadText = (relPath: string) => Promise<string>;
 /**
@@ -9,8 +10,8 @@ export type ReadText = (relPath: string) => Promise<string>;
  * `type`s (`ambiguous_marker_token`, `unrecognized_marker_token`,
  * `extra_bare_marker_token`, `unknown_marker`, `nested_spread`,
  * `continue_without_section`, `spread_without_pages`, `spread_eof_close`,
- * `page_outside_spread`, `pin_outside_page`, `unknown_gp_class` — the last
- * emitted by `gp-pin-scope.js`'s `gp_pin_scope_check`, same as
+ * `page_outside_spread`, `pin_outside_page`, `unknown_gp_class`, `flush_art` —
+ * the last two emitted by `gp-pin-scope.js`'s `gp_pin_scope_check`, same as
  * `pin_outside_page`, see #226).
  *
  * #240 (declarative container components) adds three more, all emitted by
@@ -126,6 +127,15 @@ export interface AssembleBookHtmlOptions {
      * engine/shared/synthesis.ts) and the two page counts agree.
      */
     print?: PrintPadding;
+    /**
+     * The project's print area — the resolved manifest's `page` block plus its
+     * preset id and printer spec — written as `<meta name="gp-print-area">`
+     * (engine/shared/print-area.ts) into EVERY assembled book, preview, build
+     * and publish alike: the preview's print overlays judge the ink against it,
+     * and both engines place pinned art on its art-safe line. Metadata only:
+     * nothing renders from it but what reads it.
+     */
+    printArea?: PrintAreaSource;
     plugins?: LoadedPlugin[];
     pluginCss?: string;
     /** Add a layout-neutral source-file id to source-mapped preview blocks. */

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

@@ -31,7 +31,10 @@
  *   .gp-full      — fills the page's content width.
  *   .gp-small     — width 25% of the column. Sizes compose with any
  *   .gp-medium    — width 50%.        position (including .gp-pin, where
- *   .gp-large     — width 75%.        the % resolves against the page box).
+ *   .gp-large     — width 60%.        the % resolves against the page
+ *   .gp-xl        — width 80%.        root: the page box, reaching the
+ *   .gp-xxl       — width 90%.        paper on an edge a pin uses).
+ *                   There is no 100% step: that is .gp-full, a position.
  *   .gp-tight     — float/shape clearance 0.5em (sets --gp-gap; default 1em).
  *   .gp-loose     — float/shape clearance 2em (sets --gp-gap).
  *   .gp-shape     — wraps text to a floated image's alpha silhouette
@@ -47,16 +50,14 @@
  *                   frame instead, BY DESIGN: that is how a pin is scoped to
  *                   a card rather than a sheet. Page-level furniture must
  *                   therefore be authored outside such a wrapper.
- *                   Centered on both axes unless combined with the edge
- *                   modifiers .gp-top/.gp-bottom/.gp-left/.gp-right.
- *   .gp-flush     — with .gp-pin + an edge, the art sits on the PAPER's
- *                   edge rather than on the text block's. No CSS rule here:
- *                   the class is a marker both ENGINES implement (see
- *                   engine/shared/flush.ts), because reaching the paper
- *                   requires freeing that page's margin — per page — and
- *                   relocating the furniture that lived in it, neither of
- *                   which a stylesheet can do. Inert without .gp-pin + an
- *                   edge word, and inert under plain markdown-it.
+ *                   Centered in the text block unless combined with the
+ *                   edge modifiers .gp-top/.gp-bottom/.gp-left/.gp-right;
+ *                   an edge pin sits on the printer's ART-SAFE line of that
+ *                   edge and never moves the text — see "the pin box" below.
+ *   .gp-flush     — with .gp-pin + an edge, the escape hatch: the art runs
+ *                   to the PAPER's edge, past the printer's safe area. It
+ *                   only zeroes the pin box's insets (the rule after the
+ *                   edge modifiers). Inert without .gp-pin + an edge word.
  *   .gp-bleed     — forces its own page (break-before) and spans it
  *                   edge-to-edge horizontally. This does NOT cancel the
  *                   top/bottom margins, extend past the trim into printer
@@ -102,12 +103,12 @@
  *                   paragraph with other inline content keeps its margin.
  *
  * Rule ORDER within the gp-* block is the contract: flow positions → sizes
- * → spacing → .gp-pin → pin-edge modifiers. Everything is flat 0-1-0
- * specificity, so combining classes resolves by source order: a later flow
- * position wins (left < right < center < full < bleed); an explicit size's
- * max-width:100% lifts the floats' 50% cap; .gp-pin's margin:0 /
- * max-width:100% beat the float declarations; the edge modifiers beat
- * .gp-pin's center defaults.
+ * → spacing → .gp-pin → pin-edge modifiers → .gp-flush. Everything else is
+ * flat 0-1-0 specificity, so combining classes resolves by source order: a
+ * later flow position wins (left < right < center < full < bleed); an
+ * explicit size's max-width:100% lifts the floats' 50% cap; .gp-pin's
+ * margin:0 / max-width:100% beat the float declarations; the edge modifiers
+ * beat .gp-pin's center defaults.
  *
  * .gp-pin semantics, stated honestly: it pins within its @page/@spread
  * CONTAINER, not "the sheet edge". A .page div that fragments across
@@ -120,12 +121,29 @@
  * compiler's engine.abspos.leak diagnostic catches the raw-HTML cases the
  * token walk can't see.
  *
+ * The PIN BOX — where a pin may sit, and why the text never moves. An edge
+ * pin has to be able to reach the paper, and Chromium's printable area IS
+ * the page area (engine/shared/pin-edges.ts has the measurements), so both
+ * engines free the page margin on each edge a pin names: print through a
+ * generated named page, the preview through the run's strip geometry. The
+ * page root gets that margin back as padding, on top of any of its own
+ * (`box-decoration-break: clone`), so its content box — the text — is the
+ * author's content box, same size, same place, same breaks, wherever the art
+ * is pinned. The pin's containing
+ * block is the root's padding box, and the engine sets `--gp-pin-<edge>` on
+ * the root to the art-safe line's distance from the sheet edge (the bleed
+ * plus page.artSafe on the top, bottom and outside edge; page.safe at the
+ * binding, from the manifest); `.gp-pin` reads them as its four insets.
+ * `.gp-flush` zeroes them on the pin: the paper's edge. Under plain
+ * markdown-it nothing sets them and every inset is 0.
+ *
  * Pin CSS mechanics (all three are load-bearing, verified by
- * paged-css-image-pin.test.ts): `inset: 0` is REQUIRED — abspos
- * self-alignment aligns within the inset-modified containing block, and
- * with auto insets that collapses to the static-position rectangle, where
- * alignment does nothing. The center defaults must be EXPLICIT — `normal`
- * alignment behaves as `start` for abspos replaced elements, not center.
+ * marker-css-image-pin.test.ts): four non-auto insets are REQUIRED — abspos
+ * self-alignment aligns within the inset-modified containing block (the pin
+ * box), and with auto insets that collapses to the static-position
+ * rectangle, where alignment does nothing. The center defaults must be
+ * EXPLICIT — `normal` alignment behaves as `start` for abspos replaced
+ * elements, not center.
  * And `justify-self` on .gp-left/.gp-right does double duty (flow float +
  * pin edge) because self-alignment does not apply to in-flow floats — it is
  * inert until .gp-pin makes the element abspos. If Chrome ever ships
@@ -133,16 +151,14 @@
  * carrying gp-left could start shifting; that is standards-tracking per
  * CLAUDE.md ("Chrome wins once it ships"), not a bug in the author's book.
  */
-export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary. One vocabulary, gp-* only \u2014 the\n   pre-vocabulary utility names (.center/.float-left/.float-right/\n   .full-width/.full-bleed) were REMOVED when gp-* shipped; books rename\n   the classes in their markdown (see the migration note). Source ORDER is\n   the contract \u2014 see the doctrine comment above. */\n\n/* flow positions */\n.gp-left {\n  float: left;\n  margin: 0 var(--gp-gap, 1em) var(--gp-gap, 1em) 0;\n  max-width: 50%;\n}\n.gp-right {\n  float: right;\n  margin: 0 0 var(--gp-gap, 1em) var(--gp-gap, 1em);\n  max-width: 50%;\n}\n.gp-center {\n  display: block;\n  float: none;\n  margin-left: auto;\n  margin-right: auto;\n  max-width: 100%;\n}\n.gp-full {\n  display: block;\n  float: none;\n  width: 100%;\n  max-width: 100%;\n}\n@page gp-full-bleed { margin-left: 0; margin-right: 0; }\n.gp-bleed {\n  display: block;\n  float: none;\n  break-before: page;\n  page: gp-full-bleed;\n  max-width: none;\n  width: 100%;\n  margin-left: 0;\n  margin-right: 0;\n}\n\n/* sizes \u2014 AFTER the flow positions so max-width:100% lifts the floats' 50%\n   cap at equal specificity */\n.gp-small { width: 25%; max-width: 100%; }\n.gp-medium { width: 50%; max-width: 100%; }\n.gp-large { width: 75%; max-width: 100%; }\n\n/* float clearance presets \u2014 consumed by var(--gp-gap) in the float rules\n   above and by .gp-shape's shape-margin below; --gp-gap itself is\n   author-settable CSS */\n.gp-tight { --gp-gap: 0.5em; }\n.gp-loose { --gp-gap: 2em; }\n\n/* column runs \u2014 plain CSS Multi-column, emitted by the core @columns marker\n   (markers.js): @columns [1-5] ... @end-columns is the ONE way to lay\n   content out in columns, and @column-break moves to the next column.\n   The classes below are the CSS that marker emits, not author vocabulary.\n\n   Permanent vocabulary, not a shim: Chromium implements multicol natively\n   and these rules are the standard properties verbatim, so there is no\n   spec gap here to remove later. Deliberately minimal \u2014 column-fill is\n   NOT set (the CSS initial balance applies).\n   Themes style a run through two tokens instead of writing column rules:\n     --gp-column-gap   default 1.5em\n     --gp-column-rule  default none (any column-rule shorthand value)\n   Both hooks sit at zero specificity (:where), so any author rule wins.\n   .gp-columns is two columns on its own; a count class (bare @columns\n   emits gp-columns-2) wins because it comes later at the same specificity. */\n:where(.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5) {\n  column-gap: var(--gp-column-gap, 1.5em);\n  column-rule: var(--gp-column-rule, none);\n}\n.gp-columns { columns: 2; }\n.gp-columns-1 { columns: 1; }\n.gp-columns-2 { columns: 2; }\n.gp-columns-3 { columns: 3; }\n.gp-columns-4 { columns: 4; }\n.gp-columns-5 { columns: 5; }\n\n/* fragmentation controls \u2014 generic pagination utilities for any element,\n   independent of the column vocabulary above (a book reached for\n   these just as often outside a multicol run: keeping a card whole,\n   forcing a section to start a fresh page). Standard properties only \u2014\n   this project is Chromium-only (CLAUDE.md), so there are no legacy\n   page-break-* twins to also emit. One name each. */\n.gp-no-break { break-inside: avoid; }\n.gp-break-before { break-before: page; }\n\n/* shape wrap \u2014 text follows the image's alpha silhouette instead of its\n   rectangular box. shape-outside only applies to floats, so this is inert\n   without .gp-left/.gp-right (and under .gp-pin, which un-floats). The\n   shape URL cannot be written in CSS (url() contexts can't read attr()),\n   so the image renderer rule (images.ts) mirrors the src into an inline\n   --gp-shape:url(...) custom property whenever it sees this class --\n   authors only ever type the class. threshold 0.2 ignores near-transparent\n   anti-aliasing halos; shape-margin shares the float-gap vocabulary. */\nimg.gp-shape {\n  shape-outside: var(--gp-shape);\n  shape-image-threshold: 0.2;\n  shape-margin: var(--gp-gap, 1em);\n}\n\n/* pin \u2014 within the nearest positioned ancestor (.page/.spread, rule above).\n   inset:0 and the explicit centers are load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  inset: 0;\n  align-self: center;\n  justify-self: center;\n  margin: 0;\n  max-width: 100%;\n}\n\n/* pin edge modifiers \u2014 AFTER .gp-pin to beat its center defaults;\n   justify-self is inert on in-flow floats, so gp-left/gp-right safely do\n   double duty as flow float + pin edge */\n.gp-top { align-self: start; }\n.gp-bottom { align-self: end; }\n.gp-left { justify-self: start; }\n.gp-right { justify-self: end; }\n\n/* wrapper-margin neutralization (same pattern and rationale as the\n   .gp-bleed paragraph-margin note in the doctrine comment; for pin, the\n   emptied paragraph would otherwise leave a phantom margin gap in flow) */\n:where(p:has(> img.gp-bleed:only-child)) { margin: 0; }\n:where(p:has(> img.gp-pin:only-child)) { margin: 0; }\n\n/* depth \u2014 a named ladder for z-index, so books stop hand-tuning bare\n   integers. A real book measured 21 z-index declarations using only four\n   distinct values (-1, 0, 1, 2), each written literally at its use site.\n   The custom properties are the author-settable surface (a book needing a\n   deeper stack raises them once); the classes are the shorthand.\n\n   NOT named \"layer\": CSS Paged Media 3 \u00A73.1 already defines \"page layers\"\n   (page background, canvas, borders, contents, margin boxes) and those are\n   parts of the PAGE BOX, not a z-ladder for content. Reusing the word for a\n   different concept would collide with the spec vocabulary this project\n   tracks. The pin EDGE modifiers already own .gp-top/.gp-bottom, so the\n   ladder avoids those words too.\n\n   .gp-behind is the one that earns its place: it puts a pinned image UNDER\n   the page's text, which is otherwise impossible to express without a bare\n   negative z-index. \"Above\" needs no class \u2014 an out-of-flow pin already\n   paints above in-flow content.\n\n   Two things silently defeat .gp-behind, neither visible at the use site:\n     - a stacking context on the .page/.spread ancestor (z-index, isolation,\n       opacity, filter, transform on it traps the negative layer inside).\n       Core keeps .page/.spread at 'position: relative; z-index: auto'\n       precisely so they are not stacking contexts.\n     - a clipping ancestor (overflow other than visible) \u2014 but only where\n       the art actually overhangs that ancestor's clip box on a clipped\n       axis: the overhang is cut off, the same mechanism that clips a\n       .gp-bleed plate back to the wrapper's width. Clipping never reorders\n       layers \u2014 within-bounds art under a clipping .page prints whole and\n       still behind (measured; see the build audit's comment in\n       engine/compiler/build.ts), and a static wrapper's overflow never\n       binds an abspos .gp-pin at all.\n   The build-time engine.layer.trapped audit reports both against the live\n   ancestor chain. printsafe/page-containment is only an early source hint for\n   declarations written directly on .page/.spread. */\n:root {\n  --gp-z-behind: -1;\n  --gp-z-base: 0;\n  --gp-z-raised: 1;\n  --gp-z-front: 2;\n}\n.gp-behind { z-index: var(--gp-z-behind); }\n.gp-base   { z-index: var(--gp-z-base); }\n.gp-raised { z-index: var(--gp-z-raised); }\n.gp-front  { z-index: var(--gp-z-front); }\n\n/* GFM-style alert/callout boxes (#237) \u2014 the DOM gfm-alerts.ts emits from\n   \"> [!TYPE]\" blockquote syntax when a project opts into the bundled\n   gutterpress-gfm-alerts feature (BUILTIN_OPTIONAL_PLUGINS, renderer.ts).\n   The plugin is optional and inert by default; these rules are equally\n   inert wherever the classes never appear, exactly like every other\n   utility above, so shipping them costs nothing to a book that has not\n   turned the feature on.\n\n   This is authored-COMPONENT vocabulary, not the @marker structural family\n   (markers.js/MARKER_CSS) \u2014 CLAUDE.md \u00A76 splits the two core CSS blocks by\n   ROLE, and an author-facing box an author invokes via inline syntax is the\n   same role as every other gp-* utility here, not page/chapter/section DOM.\n\n   Deliberately minimal (CLAUDE.md \"thin over capable\" / the issue's own\n   \"a rule and a label\"): a left border plus a bold label, :where()'d to\n   zero specificity so a theme's own (unlayered) rule for any of these\n   classes wins outright regardless of selector weight \u2014 see the\n   cascade-layers note atop this file. Five semantic accent colors (the same\n   NOTE/TIP/IMPORTANT/WARNING/CAUTION hues GitHub's own alerts use \u2014 a\n   long-established, non-proprietary convention, not DC branding) are\n   exposed as :root custom properties, the same author-settable-surface\n   pattern as the --gp-z-* ladder above: a book retints every alert of one\n   type by overriding a single property, no specificity fight required.\n   --gp-alert-color cascades from the type modifier down to .gp-alert-title\n   through ordinary CSS inheritance (the title is always a DOM descendant of\n   the box), so it is set in exactly five places, not ten. */\n:root {\n  --gp-alert-note-color: #0969da;\n  --gp-alert-tip-color: #1a7f37;\n  --gp-alert-important-color: #8250df;\n  --gp-alert-warning-color: #9a6700;\n  --gp-alert-caution-color: #cf222e;\n}\n:where(.gp-alert) {\n  margin: 1em 0;\n  padding: 0.5em 1em;\n  border-left: 0.25em solid var(--gp-alert-color, currentColor);\n}\n:where(.gp-alert-title) {\n  margin: 0 0 0.5em;\n  font-weight: bold;\n  color: var(--gp-alert-color, inherit);\n}\n:where(.gp-alert-note)      { --gp-alert-color: var(--gp-alert-note-color); }\n:where(.gp-alert-tip)       { --gp-alert-color: var(--gp-alert-tip-color); }\n:where(.gp-alert-important) { --gp-alert-color: var(--gp-alert-important-color); }\n:where(.gp-alert-warning)   { --gp-alert-color: var(--gp-alert-warning-color); }\n:where(.gp-alert-caution)   { --gp-alert-color: var(--gp-alert-caution-color); }\n";
+export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary. One vocabulary, gp-* only \u2014 the\n   pre-vocabulary utility names (.center/.float-left/.float-right/\n   .full-width/.full-bleed) were REMOVED when gp-* shipped; books rename\n   the classes in their markdown (see the migration note). Source ORDER is\n   the contract \u2014 see the doctrine comment above. */\n\n/* flow positions */\n.gp-left {\n  float: left;\n  margin: 0 var(--gp-gap, 1em) var(--gp-gap, 1em) 0;\n  max-width: 50%;\n}\n.gp-right {\n  float: right;\n  margin: 0 0 var(--gp-gap, 1em) var(--gp-gap, 1em);\n  max-width: 50%;\n}\n.gp-center {\n  display: block;\n  float: none;\n  margin-left: auto;\n  margin-right: auto;\n  max-width: 100%;\n}\n.gp-full {\n  display: block;\n  float: none;\n  width: 100%;\n  max-width: 100%;\n}\n@page gp-full-bleed { margin-left: 0; margin-right: 0; }\n.gp-bleed {\n  display: block;\n  float: none;\n  break-before: page;\n  page: gp-full-bleed;\n  max-width: none;\n  width: 100%;\n  margin-left: 0;\n  margin-right: 0;\n}\n\n/* sizes \u2014 AFTER the flow positions so max-width:100% lifts the floats' 50%\n   cap at equal specificity */\n.gp-small { width: 25%; max-width: 100%; }\n.gp-medium { width: 50%; max-width: 100%; }\n.gp-large { width: 60%; max-width: 100%; }\n.gp-xl { width: 80%; max-width: 100%; }\n.gp-xxl { width: 90%; max-width: 100%; }\n\n/* float clearance presets \u2014 consumed by var(--gp-gap) in the float rules\n   above and by .gp-shape's shape-margin below; --gp-gap itself is\n   author-settable CSS */\n.gp-tight { --gp-gap: 0.5em; }\n.gp-loose { --gp-gap: 2em; }\n\n/* column runs \u2014 plain CSS Multi-column, emitted by the core @columns marker\n   (markers.js): @columns [1-5] ... @end-columns is the ONE way to lay\n   content out in columns, and @column-break moves to the next column.\n   The classes below are the CSS that marker emits, not author vocabulary.\n\n   Permanent vocabulary, not a shim: Chromium implements multicol natively\n   and these rules are the standard properties verbatim, so there is no\n   spec gap here to remove later. Deliberately minimal \u2014 column-fill is\n   NOT set (the CSS initial balance applies).\n   Themes style a run through two tokens instead of writing column rules:\n     --gp-column-gap   default 1.5em\n     --gp-column-rule  default none (any column-rule shorthand value)\n   Both hooks sit at zero specificity (:where), so any author rule wins.\n   .gp-columns is two columns on its own; a count class (bare @columns\n   emits gp-columns-2) wins because it comes later at the same specificity. */\n:where(.gp-columns, .gp-columns-1, .gp-columns-2, .gp-columns-3, .gp-columns-4, .gp-columns-5) {\n  column-gap: var(--gp-column-gap, 1.5em);\n  column-rule: var(--gp-column-rule, none);\n}\n.gp-columns { columns: 2; }\n.gp-columns-1 { columns: 1; }\n.gp-columns-2 { columns: 2; }\n.gp-columns-3 { columns: 3; }\n.gp-columns-4 { columns: 4; }\n.gp-columns-5 { columns: 5; }\n\n/* fragmentation controls \u2014 generic pagination utilities for any element,\n   independent of the column vocabulary above (a book reached for\n   these just as often outside a multicol run: keeping a card whole,\n   forcing a section to start a fresh page). Standard properties only \u2014\n   this project is Chromium-only (CLAUDE.md), so there are no legacy\n   page-break-* twins to also emit. One name each. */\n.gp-no-break { break-inside: avoid; }\n.gp-break-before { break-before: page; }\n\n/* shape wrap \u2014 text follows the image's alpha silhouette instead of its\n   rectangular box. shape-outside only applies to floats, so this is inert\n   without .gp-left/.gp-right (and under .gp-pin, which un-floats). The\n   shape URL cannot be written in CSS (url() contexts can't read attr()),\n   so the image renderer rule (images.ts) mirrors the src into an inline\n   --gp-shape:url(...) custom property whenever it sees this class --\n   authors only ever type the class. threshold 0.2 ignores near-transparent\n   anti-aliasing halos; shape-margin shares the float-gap vocabulary. */\nimg.gp-shape {\n  shape-outside: var(--gp-shape);\n  shape-image-threshold: 0.2;\n  shape-margin: var(--gp-gap, 1em);\n}\n\n/* pin \u2014 within the nearest positioned ancestor (.page/.spread, rule above).\n   The four insets are the pin box: 0 (the text block's edge) unless an\n   engine set --gp-pin-<edge> on the page root for an edge a pin uses (the\n   art-safe line). Non-auto insets and the explicit centers are\n   load-bearing; see doctrine comment. */\n.gp-pin {\n  position: absolute;\n  top: var(--gp-pin-top, 0px);\n  right: var(--gp-pin-right, 0px);\n  bottom: var(--gp-pin-bottom, 0px);\n  left: var(--gp-pin-left, 0px);\n  align-self: center;\n  justify-self: center;\n  margin: 0;\n  max-width: 100%;\n}\n\n/* pin edge modifiers \u2014 AFTER .gp-pin to beat its center defaults;\n   justify-self is inert on in-flow floats, so gp-left/gp-right safely do\n   double duty as flow float + pin edge */\n.gp-top { align-self: start; }\n.gp-bottom { align-self: end; }\n.gp-left { justify-self: start; }\n.gp-right { justify-self: end; }\n\n/* the escape hatch \u2014 the paper's edge, past the printer's safe area: the\n   pin box loses its art-safe insets. Set on the pin itself, so it beats the\n   values the page root hands down. */\n.gp-pin.gp-flush {\n  --gp-pin-top: 0px;\n  --gp-pin-right: 0px;\n  --gp-pin-bottom: 0px;\n  --gp-pin-left: 0px;\n}\n\n/* wrapper-margin neutralization (same pattern and rationale as the\n   .gp-bleed paragraph-margin note in the doctrine comment; for pin, the\n   emptied paragraph would otherwise leave a phantom margin gap in flow) */\n:where(p:has(> img.gp-bleed:only-child)) { margin: 0; }\n:where(p:has(> img.gp-pin:only-child)) { margin: 0; }\n\n/* depth \u2014 a named ladder for z-index, so books stop hand-tuning bare\n   integers. A real book measured 21 z-index declarations using only four\n   distinct values (-1, 0, 1, 2), each written literally at its use site.\n   The custom properties are the author-settable surface (a book needing a\n   deeper stack raises them once); the classes are the shorthand.\n\n   NOT named \"layer\": CSS Paged Media 3 \u00A73.1 already defines \"page layers\"\n   (page background, canvas, borders, contents, margin boxes) and those are\n   parts of the PAGE BOX, not a z-ladder for content. Reusing the word for a\n   different concept would collide with the spec vocabulary this project\n   tracks. The pin EDGE modifiers already own .gp-top/.gp-bottom, so the\n   ladder avoids those words too.\n\n   .gp-behind is the one that earns its place: it puts a pinned image UNDER\n   the page's text, which is otherwise impossible to express without a bare\n   negative z-index. \"Above\" needs no class \u2014 an out-of-flow pin already\n   paints above in-flow content.\n\n   Two things silently defeat .gp-behind, neither visible at the use site:\n     - a stacking context on the .page/.spread ancestor (z-index, isolation,\n       opacity, filter, transform on it traps the negative layer inside).\n       Core keeps .page/.spread at 'position: relative; z-index: auto'\n       precisely so they are not stacking contexts.\n     - a clipping ancestor (overflow other than visible) \u2014 but only where\n       the art actually overhangs that ancestor's clip box on a clipped\n       axis: the overhang is cut off, the same mechanism that clips a\n       .gp-bleed plate back to the wrapper's width. Clipping never reorders\n       layers \u2014 within-bounds art under a clipping .page prints whole and\n       still behind (measured; see the build audit's comment in\n       engine/compiler/build.ts), and a static wrapper's overflow never\n       binds an abspos .gp-pin at all.\n   The build-time engine.layer.trapped audit reports both against the live\n   ancestor chain. printsafe/page-containment is only an early source hint for\n   declarations written directly on .page/.spread. */\n:root {\n  --gp-z-behind: -1;\n  --gp-z-base: 0;\n  --gp-z-raised: 1;\n  --gp-z-front: 2;\n}\n.gp-behind { z-index: var(--gp-z-behind); }\n.gp-base   { z-index: var(--gp-z-base); }\n.gp-raised { z-index: var(--gp-z-raised); }\n.gp-front  { z-index: var(--gp-z-front); }\n\n/* GFM-style alert/callout boxes (#237) \u2014 the DOM gfm-alerts.ts emits from\n   \"> [!TYPE]\" blockquote syntax when a project opts into the bundled\n   gutterpress-gfm-alerts feature (BUILTIN_OPTIONAL_PLUGINS, renderer.ts).\n   The plugin is optional and inert by default; these rules are equally\n   inert wherever the classes never appear, exactly like every other\n   utility above, so shipping them costs nothing to a book that has not\n   turned the feature on.\n\n   This is authored-COMPONENT vocabulary, not the @marker structural family\n   (markers.js/MARKER_CSS) \u2014 CLAUDE.md \u00A76 splits the two core CSS blocks by\n   ROLE, and an author-facing box an author invokes via inline syntax is the\n   same role as every other gp-* utility here, not page/chapter/section DOM.\n\n   Deliberately minimal (CLAUDE.md \"thin over capable\" / the issue's own\n   \"a rule and a label\"): a left border plus a bold label, :where()'d to\n   zero specificity so a theme's own (unlayered) rule for any of these\n   classes wins outright regardless of selector weight \u2014 see the\n   cascade-layers note atop this file. Five semantic accent colors (the same\n   NOTE/TIP/IMPORTANT/WARNING/CAUTION hues GitHub's own alerts use \u2014 a\n   long-established, non-proprietary convention, not DC branding) are\n   exposed as :root custom properties, the same author-settable-surface\n   pattern as the --gp-z-* ladder above: a book retints every alert of one\n   type by overriding a single property, no specificity fight required.\n   --gp-alert-color cascades from the type modifier down to .gp-alert-title\n   through ordinary CSS inheritance (the title is always a DOM descendant of\n   the box), so it is set in exactly five places, not ten. */\n:root {\n  --gp-alert-note-color: #0969da;\n  --gp-alert-tip-color: #1a7f37;\n  --gp-alert-important-color: #8250df;\n  --gp-alert-warning-color: #9a6700;\n  --gp-alert-caution-color: #cf222e;\n}\n:where(.gp-alert) {\n  margin: 1em 0;\n  padding: 0.5em 1em;\n  border-left: 0.25em solid var(--gp-alert-color, currentColor);\n}\n:where(.gp-alert-title) {\n  margin: 0 0 0.5em;\n  font-weight: bold;\n  color: var(--gp-alert-color, inherit);\n}\n:where(.gp-alert-note)      { --gp-alert-color: var(--gp-alert-note-color); }\n:where(.gp-alert-tip)       { --gp-alert-color: var(--gp-alert-tip-color); }\n:where(.gp-alert-important) { --gp-alert-color: var(--gp-alert-important-color); }\n:where(.gp-alert-warning)   { --gp-alert-color: var(--gp-alert-warning-color); }\n:where(.gp-alert-caution)   { --gp-alert-color: var(--gp-alert-caution-color); }\n";
 /**
  * GP_CLASSES — every class an author may legitimately write with a `gp-`
  * prefix: the `.gp-*` selectors in `GUTTERPRESS_CSS` above, the two
  * structural classes `markers.js`'s `MARKER_CSS` styles (`gp-page-break`,
- * `gp-column-break`), and two classes the marker plugin EMITS but that carry
- * no CSS rule of their own — `gp-continued` (a `@continue`d section's marker,
- * for author/theme styling — see markers.js's header) and `gp-flush` (a
- * `.gp-pin` edge modifier implemented in the engine's layout code, not CSS —
- * see the `.gp-flush` doctrine note above).
+ * `gp-column-break`), and one class the marker plugin EMITS but that carries
+ * no CSS rule of its own — `gp-continued` (a `@continue`d section's marker,
+ * for author/theme styling — see markers.js's header).
  *
  * This is the vocabulary `gp-pin-scope.js`'s `unknown_gp_class` diagnostic
  * (#226) checks every author-facing class against: any `gp-`-prefixed class
@@ -151,8 +167,8 @@ export declare const GUTTERPRESS_CSS = "\n/* gp-* author image/block vocabulary.
  * classes are none of core's business.
  *
  * `gutterpress-css.test.ts` asserts this set and the `.gp-*` selectors
- * textually present in `GUTTERPRESS_CSS` + `MARKER_CSS` agree (modulo the two
- * marker-only exceptions above), so the two cannot silently drift apart —
+ * textually present in `GUTTERPRESS_CSS` + `MARKER_CSS` agree (modulo the
+ * marker-only exception above), so the two cannot silently drift apart —
  * whoever adds a class to one CSS block and forgets this list finds out from
  * a failing test, not from a future bug report.
  */

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

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

package/dist/lib/pdf-inspect.d.ts

@@ -134,6 +134,51 @@ export interface OpPass {
     fonts: FontRef[];
 }
 export declare function getOpPass(doc: PDFDocumentProxy): Promise<OpPass>;
+/**
+ * Why a page is not split from its artwork: its text cannot be (the first
+ * three), or it shows no text at all, so there is none to keep (`no-text`).
+ */
+export type UnsplittableReason = "text-transparency" | "type3-font" | "text-pattern-or-clip" | "no-text";
+/**
+ * For each 1-based page that `pdfx.transparency: preserve-text` must not split,
+ * the first reason found; pages absent from the map can be split. `pages`
+ * limits the scan to those pages (the build passes the transparent ones only,
+ * so the rest of the book is never decoded).
+ *
+ * A page's text cannot be split when text SHOWS while transparency is in effect: constant alpha
+ * (`ca`/`CA` < 1), a non-Normal blend mode, an active soft mask, or any
+ * enclosing transparency group that is composited translucent, blended or
+ * masked, or is a knockout group. (Chromium draws `opacity` and
+ * `mix-blend-mode` content as a group form XObject under such a state, and
+ * resets the state INSIDE the group, so the state at the point the group
+ * begins is what counts.) Such text cannot be lifted out of its page and drawn
+ * opaque on top of a flattened picture without changing how it looks, so
+ * `pdfx.transparency: preserve-text` leaves those pages alone.
+ *
+ * Also flagged: any page that sets a Type 3 font. Chromium (Skia) emits Type 3
+ * for glyphs it can only draw as paths, e.g. the synthetic bold of a
+ * single-weight webfont. Their glyph procedures are vector paths, which the
+ * text pass's `-dFILTERVECTOR` strips, so the text would print nothing.
+ *
+ * Also flagged: text painted with a pattern (`scn`/`SCN` to a tiling pattern
+ * or shading), as Chromium emits for SVG `<text fill="url(#…)">` and gradient
+ * text fills, and text used as a clip (render modes 4-7, `background-clip:
+ * text`). The artwork pass removes the glyphs and the text pass's
+ * `-dFILTERIMAGE`/`-dFILTERVECTOR` removes their paint, so they would vanish.
+ *
+ * A plain isolated group composited at alpha 1 / Normal / no mask is NOT
+ * counted: painting it is the same as painting its content inline, and
+ * Chromium wraps the content of EVERY page in one as soon as any element of
+ * the document uses a blend mode (measured on Chromium 141), which would
+ * otherwise rule out every page of such a book. The page's OWN `/Group` is
+ * likewise ignored.
+ *
+ * Walks PDF.js's operator list, which has already inlined form XObjects
+ * between `paintFormXObjectBegin/End` and reports their `/Group` as
+ * `beginGroup/endGroup`. Graphics state is tracked per save/restore (a form
+ * XObject is an implicit save/restore).
+ */
+export declare function unsplittableTextReasons(pdfBytes: Uint8Array, pages?: number[]): Promise<Map<number, UnsplittableReason>>;
 /**
  * Does page `pageNum` (1-based) paint anything at all? False for a page with
  * no content and for one whose operators only set state or clip. A path op

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

@@ -155,9 +155,21 @@
           "enum": ["icc", "k-only"],
           "default": "icc"
         },
+        "transparency": {
+          "type": "string",
+          "description": "What a PDF/X build does with a page that uses transparency (an alpha-channel image, a soft `rgba()` shadow, CSS `opacity` or `mix-blend-mode`), which PDF/X (PDF 1.3) cannot represent. `flatten-page` leaves the page to Ghostscript, which rasterizes the WHOLE page: it looks right but loses the page's text and fonts. `preserve-text` flattens only the artwork to a picture (300 DPI, or `rasterDpi`) and draws the text live on top, so the page stays searchable. Text is then always the top layer (text another element covers shows through). A page whose text is translucent or blended, set in a Type 3 font (e.g. a synthetic bold or a text stroke), filled with a pattern or used as a clip, or that has a repeating or conic gradient, falls back to `flatten-page`, and so does any page listed in `flattenPages`. Set `validate.assets.allowAlpha: true` to use alpha-channel images. Same for every preset: `flatten-page`.",
+          "enum": ["flatten-page", "preserve-text"],
+          "default": "flatten-page"
+        },
+        "flattenPages": {
+          "type": "array",
+          "description": "With `transparency: preserve-text`: pages (1-based, the numbers the build reports) left to Ghostscript's whole-page flattening even if they could be split, e.g. a page whose look depends on a cover or tint painted over its text. Page numbers move when the book reflows. Default: none.",
+          "items": { "type": "integer", "minimum": 1 },
+          "examples": [[4, 13]]
+        },
         "rasterDpi": {
           "type": "integer",
-          "description": "Resolution (DPI) of the picture Ghostscript makes of a page it flattens in a PDF/X build because the page uses transparency (PDF/X-1a and X-3 cannot hold it). Lower is smaller and softer; vector content on other pages and the book's own images are not resampled. Unset: Ghostscript's default, 720.",
+          "description": "Resolution (DPI) of every picture made from a page that uses transparency: the whole pages Ghostscript flattens and the `preserve-text` artwork. Vector content and the book's own images are not resampled. Unset: Ghostscript's default (720) for whole pages, 300 for `preserve-text` artwork.",
           "minimum": 72,
           "maximum": 1200,
           "examples": [300]
@@ -210,19 +222,19 @@
         },
         "bleed": {
           "type": "number",
-          "description": "A bleed, in points, that the page width x height ALREADY CONTAINS on the top, bottom and OUTER edges (none on the binding edge) — how DriveThruRPG's interior file is cut (8.625 x 11.25in for an 8.5 x 11in book). It tells the preview's safe area & bleed overlay and the `pdf.print.safe-margins` check where the trim is, and changes nothing in the PDF. Preset default: dtrpg 9 (0.125in); book and custom none.",
+          "description": "A bleed, in points, that the page width x height ALREADY CONTAINS on the top, bottom and OUTER edges (none on the binding edge) — how DriveThruRPG's interior file is cut (8.625 x 11.25in for an 8.5 x 11in book). It tells the preview's safe area & bleed overlay, the `pdf.print.safe-margins` check and pinned art where the trim is, and by itself changes nothing in the PDF. Preset default: dtrpg 9 (0.125in); book and custom none.",
           "minimum": 0,
           "examples": [9]
         },
         "safe": {
           "type": "number",
-          "description": "The TEXT rule, in points: how far inside the trim glyphs must stay, on every edge. For DriveThruRPG it is the \"text at least 0.5in inside the trim\" rule. The preview's overlay outlines it (dashed) and flags text outside it, and the `pdf.print.safe-margins` check fails a PDF whose text is closer. It changes nothing in the PDF, and no book CSS moves it. Preset default: dtrpg 36 (0.5in), book 18 (0.25in); custom none.",
+          "description": "The TEXT rule, in points: how far inside the trim glyphs must stay, on every edge. For DriveThruRPG it is the \"text at least 0.5in inside the trim\" rule. The preview's overlay outlines it (dashed) and flags text outside it, and the `pdf.print.safe-margins` check fails a PDF whose text is closer. An image pinned to the binding edge (`.gp-pin`) sits on it, and to any edge where `artSafe` is not set; no book CSS moves it. Preset default: dtrpg 36 (0.5in), book 18 (0.25in); custom none.",
           "minimum": 0,
           "examples": [18, 36]
         },
         "artSafe": {
           "type": "number",
-          "description": "The ART rule, in points: how far inside the trim art that does not bleed (images, backgrounds, borders, rules) must stay on the top, bottom and OUTER edge; at the binding edge art uses `safe`. For DriveThruRPG it is the \"non-bleeding art at least 0.25in from the outside edges (0.5in at the binding)\" rule. Art that runs out to the page's edge is a bleed and is not judged on that edge. The preview's overlay outlines it (dotted) and flags art outside it. Preview overlay only: it changes nothing in the PDF. Absent = the same as `safe`. Preset default: dtrpg 18 (0.25in); book and custom none.",
+          "description": "The ART rule, in points: how far inside the trim art that does not bleed (images, backgrounds, borders, rules) must stay on the top, bottom and OUTER edge; at the binding edge art uses `safe`. For DriveThruRPG it is the \"non-bleeding art at least 0.25in from the outside edges (0.5in at the binding)\" rule. Art that runs out to the page's edge is a bleed and is not judged on that edge. The preview's overlay outlines it (dotted) and flags art outside it, and an image pinned to the top, bottom or outer edge (`.gp-pin`) sits on it unless it carries `.gp-flush`. Absent = the same as `safe`. Preset default: dtrpg 18 (0.25in); book and custom none.",
           "minimum": 0,
           "examples": [18]
         }

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

@@ -7,20 +7,21 @@ import {
   TARGET_IDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-zacevwcy.js";
+} from "./cli-0ey902sx.js";
 import {
   resolveGhostscript
-} from "./cli-gh0ym80r.js";
+} from "./cli-h4tfmpg3.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-7z29z4wz.js";
+} from "./cli-fmksazej.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-j802s31j.js";
+import"./cli-61vd4ews.js";
 import {
   EXIT_CODES
 } from "./cli-46ycxe6r.js";
+import"./cli-sth219v1.js";
 import"./cli-eyyggect.js";
 import {
   isToolAvailable

package/dist/pdf-inspect-zdmy7qca.js

@@ -0,0 +1,35 @@
+import {
+  DOC_CACHE_MAX,
+  clearPdfCache,
+  countLinkAnnotations,
+  getImageResolutions,
+  getOpPass,
+  getOutlineCount,
+  getPageLabels,
+  getPageSize,
+  getTextPass,
+  isLoadable,
+  loadPdf,
+  pageHasMarks,
+  pendingGraceDestroyCount,
+  retainPdfCache,
+  unsplittableTextReasons
+} from "./cli-sth219v1.js";
+import"./cli-37x76zdn.js";
+export {
+  unsplittableTextReasons,
+  retainPdfCache,
+  pendingGraceDestroyCount,
+  pageHasMarks,
+  loadPdf,
+  isLoadable,
+  getTextPass,
+  getPageSize,
+  getPageLabels,
+  getOutlineCount,
+  getOpPass,
+  getImageResolutions,
+  countLinkAnnotations,
+  clearPdfCache,
+  DOC_CACHE_MAX
+};

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

@@ -2,21 +2,22 @@ import {
   executeValidation,
   publishTargetFor,
   reportMissingTools
-} from "./cli-zacevwcy.js";
+} from "./cli-0ey902sx.js";
 import {
   log
-} from "./cli-gh0ym80r.js";
+} from "./cli-h4tfmpg3.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-7z29z4wz.js";
+} from "./cli-fmksazej.js";
 import"./cli-ht1bcqdd.js";
-import"./cli-j802s31j.js";
+import"./cli-61vd4ews.js";
 import {
   BuildError,
   EXIT_CODES
 } from "./cli-46ycxe6r.js";
+import"./cli-sth219v1.js";
 import"./cli-eyyggect.js";
 import"./cli-asap4t1z.js";
 import"./cli-5qr3z0qa.js";