gutterpress 0.11.16-alpha.5 → 0.11.16

package/dist/index.js

@@ -48,7 +48,7 @@ import {
   describeExtension,
   diagnoseProjectRemote,
   disconnectPublishCredential,
-  ensureGitignoreHasDist,
+  ensureProjectGitignore,
   escapeYamlScalar,
   executeAndReport,
   executeValidation,
@@ -119,6 +119,8 @@ import {
   resolveGoogleClientSecret,
   resolvePublishFormat,
   resolvePublishRequest,
+  restoreFailureMessage,
+  restorePinnedExtensions,
   revokeGoogleCredential,
   ruleRemoteUrls,
   ruleRiskyProps,
@@ -146,7 +148,7 @@ import {
   testRemoteAccess,
   updateExtensions,
   validateProjectExtensions
-} from "./index-nk2mt7gp.js";
+} from "./index-40achhs8.js";
 import {
   BUILD_DIAGNOSTIC_CODES
 } from "./index-qep93v0z.js";
@@ -212,6 +214,8 @@ export {
   ruleRemoteUrls,
   revokeGoogleCredential,
   restoreVersionWithBackup,
+  restorePinnedExtensions,
+  restoreFailureMessage,
   resolvePublishRequest,
   resolvePublishFormat,
   resolveLogger,
@@ -290,7 +294,7 @@ export {
   executeValidation,
   executeAndReport,
   escapeYamlScalar,
-  ensureGitignoreHasDist,
+  ensureProjectGitignore,
   disconnectPublishCredential,
   diagnoseProjectRemote,
   detectProjectSource,

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

@@ -82,6 +82,8 @@ export interface BuiltInStyleSet {
     name: string;
     description: string;
 }
+/** One key per book folder, however the path is spelled (Windows paths are case-insensitive). */
+export declare function projectKey(projectDir: string): string;
 /**
  * Two specifiers name the same extension when they are equal, or when both
  * are npm specifiers for the same package (a re-install re-pins the version
@@ -146,6 +148,17 @@ export interface AddExtensionOptions extends NpmPluginInstallOptions {
  * Returns the described entry.
  */
 export declare function addExtension(projectDir: string, specifier: string, options?: AddExtensionOptions): Promise<ProjectExtensionEntry>;
+/**
+ * Download one pinned npm extension again (`name@<exact version>`): the same
+ * verified transaction as {@link addExtension}, minus the manifest write — the
+ * pin is already there and is never changed. Returns the install's warnings.
+ */
+export declare function restoreNpmExtension(projectDir: string, name: string, version: string, exportName: string | undefined, options?: NpmPluginInstallOptions & {
+    /** Every version of `name` an enabled manifest entry pins — never pruned. */
+    keepVersions?: readonly string[];
+}): Promise<string[]>;
+/** True when `plugins/npm/<name>/<version>/` is absent or has no loadable entry — what the loader calls "not installed" or "incomplete". */
+export declare function vendoredCopyNeedsInstall(projectDir: string, name: string, version: string): Promise<boolean>;
 /** One pinned npm extension against npm's `latest` tag. */
 export interface ExtensionUpdateCheck {
     /** The specifier as written in the manifest (`name@current`). */

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

@@ -0,0 +1,74 @@
+import type { NpmPluginInstallOptions } from "./npm-plugin-installer.ts";
+export interface RestorePinnedOptions extends NpmPluginInstallOptions {
+    /** An explicit `--manifest` file; the book folder is then that file's folder. */
+    manifestPath?: string;
+    /**
+     * Progress for a UI: nothing is reported when every copy is present; else a
+     * `start` (the packages to download), one `package` event as each starts
+     * and ends, and an `end`. A caller that joins a run already in flight for
+     * the same book gets that run's result but no events.
+     */
+    onProgress?: (event: RestoreProgress) => void;
+}
+/** One step of a restore, for a progress indicator. `spec` is `name@version`. */
+export type RestoreProgress = {
+    type: "start";
+    specs: string[];
+} | {
+    type: "package";
+    spec: string;
+    index: number;
+    total: number;
+    state: "downloading" | "done" | "failed";
+    message?: string;
+} | {
+    type: "end";
+    installed: string[];
+    failed: RestoreFailure[];
+};
+export interface RestoreFailure {
+    /** `name@version`, as pinned. */
+    use: string;
+    message: string;
+}
+export interface RestoreResult {
+    /** File name of the manifest the pins were read from (`manifest.yaml`), or null when the folder has none. */
+    manifestFile: string | null;
+    /** `name@version` of each package downloaded. */
+    installed: string[];
+    failed: RestoreFailure[];
+    warnings: string[];
+    /** npm could not be reached, so every package still missing was reported as failed without being tried. */
+    offline: boolean;
+}
+/**
+ * Download every pinned npm extension of the book whose copy is missing or
+ * incomplete. Never throws for a failed download — failures come back in
+ * `failed` so each caller can decide (the CLI fails fast, preview and the
+ * desktop degrade). An unreadable manifest restores nothing: whoever reads it
+ * next reports the real problem.
+ */
+export declare function restorePinnedExtensions(projectDir: string, options?: RestorePinnedOptions): Promise<RestoreResult>;
+/** What went wrong, which extension, and how to retry — one failure as a sentence. */
+export declare function restoreFailureMessage(failure: RestoreFailure, manifestFile: string | null): string;
+/**
+ * One sentence for a restore that could not reach npm: which extensions are
+ * missing, and that they have to be installed while online — after which the
+ * book works offline.
+ */
+export declare function restoreOfflineMessage(failed: RestoreFailure[], manifestFile: string | null): string;
+/**
+ * The restore step every command and host path that loads a book's plugins
+ * runs first: restore, print one line per downloaded package, and either fail
+ * fast (build, export, validate and the checks: a final artifact must never
+ * silently omit author-configured formatting) or, for the live preview, warn
+ * and carry on so one missing package cannot blank the whole preview.
+ *
+ * It is called from the shared "load the book's plugins" seams themselves
+ * (`loadBuildPlugins`, `executeValidation`), not from each command, so a new
+ * command that builds or checks cannot forget it. The loader stays offline.
+ */
+export declare function restoreForCommand(dir: string, options: {
+    manifestPath?: string;
+    failFast: boolean;
+}): Promise<void>;

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-2 { columns: 2; column-gap: var(--gp-column-gap, 1.5em); }\n.gp-columns-3 { columns: 3; column-gap: var(--gp-column-gap, 1.5em); }\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, 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";
 /**
  * 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/npm-plugin-installer.d.ts

@@ -22,8 +22,16 @@ export interface InstalledNpmPlugin {
     installRoot: string;
     /** Previous same-version directory held until the manifest commits. */
     backupRoot: string | null;
+    /** Folders THIS install created (`plugins/`, `plugins/npm/`, `plugins/npm/<name>/`), outermost first. */
+    createdDirs: string[];
     warnings: string[];
 }
+/**
+ * Remove folders a failed install created — innermost first, and only while
+ * they are still empty, so a folder that gained anything else (a local plugin
+ * in `plugins/`, another package's copy) is never touched.
+ */
+export declare function removeEmptyDirs(dirs: readonly string[]): Promise<void>;
 /**
  * Download and publish a fresh vendor tree for one npm plugin. Never reuses
  * bytes: a same-version reinstall downloads again and replaces the tree (the

package/dist/lib/project-gitignore.d.ts

@@ -0,0 +1,10 @@
+/** Entries every book ignores, in the order they are appended. */
+export declare const PROJECT_GITIGNORE_ENTRIES: readonly ["dist/", "plugins/npm/"];
+/**
+ * Make sure `<projectDir>/.gitignore` ignores `dist/` and `plugins/npm/`,
+ * creating the file or appending what is missing. Returns the entries the
+ * author's own rules re-include (left alone) so a caller can warn.
+ */
+export declare function ensureProjectGitignore(projectDir: string): Promise<{
+    negated: string[];
+}>;

package/dist/lib/project-scaffold.d.ts

@@ -143,31 +143,11 @@ export interface AdoptFolderOptions {
  * Adopt an EXISTING folder as a gutterpress project, in place (no new subfolder).
  * Writes a `manifest.yaml` (using the folder's existing top-level `.md` files as
  * `source.files`, or scaffolding a `chapter-01.md` when there are none), copies
- * a starter `styles/book.css`, ensures `dist/` is gitignored (see
- * `ensureGitignoreHasDist`), and optionally initialises local version history.
+ * a starter `styles/book.css`, ensures `dist/` and `plugins/npm/` are gitignored
+ * (see `ensureProjectGitignore`), and optionally initialises local version history.
  *
  * NON-DESTRUCTIVE (global never-overwrite rule): refuses if the folder is
  * already a project, and never overwrites an existing `manifest.yaml`,
  * `styles/book.css`, `.gitignore`, or any markdown file.
  */
 export declare function adoptFolder(options: AdoptFolderOptions): Promise<CreateProjectResult>;
-/**
- * Ensure `<projectDir>/.gitignore` excludes the build output directory
- * (`dist/` — lib/output-paths.ts's `DIST_DIRNAME`).
- *
- * Confirmed bug this closes: no scaffolded project ever got a `.gitignore`,
- * and gutterpress's auto-snapshot feature is ON BY DEFAULT and auto-pushes.
- * Every `gutterpress build` writes a fresh, incompressible PDF (plus any copied
- * assets) into `dist/<title-slug>/`; without an ignore rule, the very next
- * snapshot commits and pushes it. That grows `.git` by a full PDF on every
- * build and, once a single artifact crosses GitHub's 100MB per-file limit,
- * the push is rejected outright — for a non-technical author with no way to
- * `git filter-repo` their way out.
- *
- * NEVER overwrites an existing `.gitignore` (global never-delete-user-data
- * rule): if the file already excludes `dist/` in some common spelling
- * (`dist`, `dist/`, `/dist/`, …) it is left untouched; otherwise the line is
- * APPENDED, not prepended or reformatted, so any content the author already
- * has stays exactly as they wrote it.
- */
-export declare function ensureGitignoreHasDist(projectDir: string): Promise<void>;

package/dist/lib/validation-exec.d.ts

@@ -20,8 +20,9 @@ export interface ValidationExecutionArgs {
      * `runQualityGates`, via `loadBuildPlugins`) so this run does not load
      * plugins itself when the build already has. `undefined` (the default —
      * every standalone `validate`/`preflight` invocation, and the desktop
-     * Problems panel) makes {@link executeValidation} load plugins itself,
-     * degrade-and-report. An explicit `[]` is honored as-is, not treated as
+     * Problems panel) makes {@link executeValidation} restore the book's
+     * missing pinned extensions (failing the run if it cannot) and then load
+     * plugins itself, degrade-and-report. An explicit `[]` is honored as-is, not treated as
      * "unset".
      */
     pluginStylePaths?: string[];

package/dist/{new-c9b5wwpe.js → new-wsjsrm7w.js}

@@ -7,15 +7,15 @@ import {
   TARGET_IDS,
   scaffoldExtension,
   scaffoldProject
-} from "./cli-4d4xegsw.js";
+} from "./cli-ev175hx9.js";
 import {
   resolveGhostscript
-} from "./cli-6s4pkvbx.js";
+} from "./cli-0prrt9e4.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-cg03zvez.js";
+} from "./cli-182j48xc.js";
 import"./cli-wqy8hnnh.js";
 import {
   EXIT_CODES

package/dist/{preflight-mnpqsnsz.js → preflight-0fjjnk9e.js}

@@ -2,17 +2,18 @@ import {
   executeValidation,
   publishTargetFor,
   reportMissingTools
-} from "./cli-4d4xegsw.js";
+} from "./cli-ev175hx9.js";
 import {
   log
-} from "./cli-6s4pkvbx.js";
+} from "./cli-0prrt9e4.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-cg03zvez.js";
+} from "./cli-182j48xc.js";
 import"./cli-wqy8hnnh.js";
 import {
+  BuildError,
   EXIT_CODES
 } from "./cli-46ycxe6r.js";
 import"./cli-kkzka31p.js";
@@ -190,7 +191,7 @@ var preflight_default = defineCommand({
       });
     } catch (error) {
       log.error(error instanceof Error ? error.message : String(error));
-      process.exit(error instanceof UsageError ? error.exitCode : EXIT_CODES.USAGE);
+      process.exit(error instanceof UsageError || error instanceof BuildError ? error.exitCode : EXIT_CODES.USAGE);
     }
     if (!execution)
       return;

package/dist/{preview-kcqapj66.js → preview-azy06gw0.js}

@@ -3,13 +3,14 @@ import {
 } from "./cli-75qkn0k5.js";
 import {
   openPath,
+  restoreForCommand,
   runBuild,
   splitOutPath,
   startPreviewServer
-} from "./cli-4d4xegsw.js";
+} from "./cli-ev175hx9.js";
 import {
   log
-} from "./cli-6s4pkvbx.js";
+} from "./cli-0prrt9e4.js";
 import {
   UsageError,
   parseFormat,
@@ -17,7 +18,7 @@ import {
   rejectExtraPositionals,
   rejectUnknownFlags,
   resolvePort
-} from "./cli-cg03zvez.js";
+} from "./cli-182j48xc.js";
 import"./cli-wqy8hnnh.js";
 import {
   BuildError
@@ -52,6 +53,7 @@ var preview_default = defineCommand({
         if (typeof args.manifest === "string") {
           throw new UsageError("--manifest is only supported by preview --format pdf or pdfx; live HTML preview discovers the book manifest from its input directory.");
         }
+        await restoreForCommand(inputPath ?? process.cwd(), { failFast: false });
         await startPreviewServer({
           input: inputPath,
           port: resolvePort(args.port),
@@ -68,6 +70,7 @@ var preview_default = defineCommand({
       }
       const pdfxFlavor = parsePdfxFlavor(args["pdfx-flavor"], format);
       const { outDir, pdfFileOverride } = splitOutPath(typeof args.out === "string" ? args.out : undefined, format);
+      const manifestPath = typeof args.manifest === "string" ? args.manifest : undefined;
       const result = await runBuild({
         inputDir: inputPath,
         format,
@@ -75,7 +78,7 @@ var preview_default = defineCommand({
         pdfFileOverride,
         pdfxFlavor,
         iccPath: typeof args.icc === "string" ? args.icc : undefined,
-        manifestPath: typeof args.manifest === "string" ? args.manifest : undefined,
+        manifestPath,
         stripAnnotations: typeof args["strip-annotations"] === "boolean" ? args["strip-annotations"] : undefined,
         skipLint: !!args["skip-lint"],
         skipPreValidate: !!args["skip-pre-validate"],

package/dist/{publish-zf218d0c.js → publish-8db67m2h.js}

@@ -11,16 +11,16 @@ import {
   publishProviderFor,
   resolvePublishFormat,
   runPublish
-} from "./cli-4d4xegsw.js";
+} from "./cli-ev175hx9.js";
 import {
   FileTokenStore,
   log
-} from "./cli-6s4pkvbx.js";
+} from "./cli-0prrt9e4.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-cg03zvez.js";
+} from "./cli-182j48xc.js";
 import"./cli-wqy8hnnh.js";
 import {
   EXIT_CODES
@@ -55,7 +55,8 @@ function stdinLooksPiped() {
 }
 function emitResult(result, json) {
   if (json) {
-    console.log(JSON.stringify(result, null, 2));
+    process.stdout.write(JSON.stringify(result, null, 2) + `
+`);
     return;
   }
   for (const issue of result.issues) {
@@ -173,7 +174,8 @@ var publish_default = defineCommand({
         };
       }));
       if (json) {
-        console.log(JSON.stringify(rows, null, 2));
+        process.stdout.write(JSON.stringify(rows, null, 2) + `
+`);
       } else {
         for (const r of rows) {
           const status = r.kind === "guided" ? "no key needed" : r.connected ? "connected" : "not connected";

package/dist/render.js

@@ -457,16 +457,23 @@ function resolveMarkerDeclaration(name, rawDecl, rawRegistry, originOf) {
   }
   return { name, baseKind: name, ...resolveContainerShape(name, pluginName, rawDecl) };
 }
+var CORE_MARKER_OWNER = "Gutterpress";
+var CORE_DECLARED_MARKERS = {
+  columns: {
+    class: "gp-columns",
+    variants: { 1: "gp-columns-1", 2: "gp-columns-2", 3: "gp-columns-3", 4: "gp-columns-4", 5: "gp-columns-5" }
+  }
+};
 function buildDeclaredMarkerRegistry(sources) {
   const rawRegistry = new Map;
   const originOf = new Map;
-  for (const { pluginName, markers } of sources) {
+  for (const { pluginName, markers } of [{ pluginName: CORE_MARKER_OWNER, markers: CORE_DECLARED_MARKERS }, ...sources]) {
     if (!markers)
       continue;
     for (const [name, rawDecl] of Object.entries(markers)) {
       validateDeclaredMarkerName(name, pluginName);
-      if (KNOWN_KINDS.includes(name)) {
-        throw new Error(`Plugin "${pluginName}" declares marker "@${name}", which is a core Gutterpress marker name ` + `(${KNOWN_KINDS.map((k) => `@${k}`).join(", ")}). Core marker names cannot be shadowed — ` + `rename the plugin's marker.`);
+      if (KNOWN_KINDS.includes(name) || pluginName !== CORE_MARKER_OWNER && name in CORE_DECLARED_MARKERS) {
+        throw new Error(`Plugin "${pluginName}" declares marker "@${name}", which is a core Gutterpress marker name ` + `(${[...KNOWN_KINDS, ...Object.keys(CORE_DECLARED_MARKERS)].map((k) => `@${k}`).join(", ")}). ` + `Core marker names cannot be shadowed — ` + `rename the plugin's marker.`);
       }
       if (rawRegistry.has(name)) {
         throw new Error(`Marker "@${name}" is declared by both plugin "${originOf.get(name)}" and plugin "${pluginName}". ` + `Declared marker names must be unique across every loaded plugin — rename one of them.`);
@@ -531,6 +538,9 @@ function scanForUnknownDeclaredMarkers(state, declaredMarkers) {
     }
   }
 }
+function variantClassFor(decl, word) {
+  return word && decl.variants && Object.hasOwn(decl.variants, word) ? decl.variants[word] : "";
+}
 function warnUnknownVariant(env, meta, decl) {
   const word = meta.name;
   if (!word)
@@ -546,7 +556,7 @@ function plugin(md, pluginOptions = {}) {
     preferPagesInSpreads: false,
     ...pluginOptions
   };
-  const declaredMarkers = options.declaredMarkers instanceof Map && options.declaredMarkers.size > 0 ? options.declaredMarkers : null;
+  const declaredMarkers = options.declaredMarkers instanceof Map && options.declaredMarkers.size > 0 ? options.declaredMarkers : buildDeclaredMarkerRegistry([]);
   const declaredWords = declaredKindWords(declaredMarkers);
   function markerBlock(state, startLine, endLine, silent) {
     const pos = state.bMarks[startLine] + state.tShift[startLine];
@@ -659,7 +669,7 @@ function plugin(md, pluginOptions = {}) {
         attrs: meta.attrs || {},
         labelled: false
       };
-      const variantClass = variant && decl.variants && decl.variants[variant] || "";
+      const variantClass = variantClassFor(decl, variant);
       const baseClass = [decl.classBase, variantClass].filter(Boolean).join(" ");
       addClasses(t, baseClass, meta.attrs && meta.attrs.class ? meta.attrs.class : "");
       attachDataAttrs(t, decl.baseKind, variant, meta.attrs || {});
@@ -770,7 +780,7 @@ function plugin(md, pluginOptions = {}) {
       const attrs = meta.attrs || {};
       const variant = meta.name || decl.presetVariant || null;
       warnUnknownVariant(state.env, meta, decl);
-      const variantClass = variant && decl.variants && decl.variants[variant] || "";
+      const variantClass = variantClassFor(decl, variant);
       const cls = [decl.classBase, variantClass, attrs.class].filter(Boolean).join(" ");
       return {
         kind: "section",
@@ -1105,9 +1115,19 @@ var GUTTERPRESS_CSS = `
    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-2 { columns: 2; column-gap: var(--gp-column-gap, 1.5em); }
-.gp-columns-3 { columns: 3; column-gap: var(--gp-column-gap, 1.5em); }
+   --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 {
+  column-gap: var(--gp-column-gap, 1.5em);
+}
+.gp-columns { columns: 2; }
+.gp-columns-1 { columns: 1; }
+.gp-columns-2 { columns: 2; }
+.gp-columns-3 { columns: 3; }
+.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
@@ -1308,8 +1328,12 @@ var GP_CLASSES = new Set([
   "gp-large",
   "gp-tight",
   "gp-loose",
+  "gp-columns",
+  "gp-columns-1",
   "gp-columns-2",
   "gp-columns-3",
+  "gp-columns-4",
+  "gp-columns-5",
   "gp-columns-all",
   "gp-columns-flow",
   "gp-columns-balanced",

package/dist/{validate-mh9r5qzx.js → validate-e7mw1xyd.js}

@@ -1,16 +1,17 @@
 import {
   executeAndReport
-} from "./cli-4d4xegsw.js";
+} from "./cli-ev175hx9.js";
 import {
   log
-} from "./cli-6s4pkvbx.js";
+} from "./cli-0prrt9e4.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-cg03zvez.js";
+} from "./cli-182j48xc.js";
 import"./cli-wqy8hnnh.js";
 import {
+  BuildError,
   EXIT_CODES
 } from "./cli-46ycxe6r.js";
 import"./cli-kkzka31p.js";
@@ -96,7 +97,7 @@ var validate_default = defineCommand({
       }, format);
     } catch (error) {
       log.error(error instanceof Error ? error.message : String(error));
-      process.exit(error instanceof UsageError ? error.exitCode : EXIT_CODES.USAGE);
+      process.exit(error instanceof UsageError || error instanceof BuildError ? error.exitCode : EXIT_CODES.USAGE);
     }
     if (!result.ok) {
       process.exit(EXIT_CODES.FINDINGS);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gutterpress",
-  "version": "0.11.16-alpha.5",
+  "version": "0.11.16",
   "description": "Markdown-to-PDF converter for professional print layout using a native Chromium print engine and Ghostscript.",
   "author": "itlackey",
   "license": "MPL-2.0",
@@ -66,6 +66,7 @@
     "fflate": "0.8.3",
     "glob": "^13.0.0",
     "htmlhint": "^1.9.2",
+    "ignore": "^5.3.2",
     "isomorphic-git": "^1.38.4",
     "markdown-it": "^14.3.2",
     "markdown-it-abbr": "^2.0.0",