gutterpress 0.10.11 → 0.11.1

package/README.md

@@ -537,7 +537,7 @@ An extension folder (or npm package) describes itself in its **`package.json`**
 
 `main` is the markdown-it plugin — npm's own convention — so a plain markdown-it plugin package needs nothing else at all. A look needs only `gutterpress.styles` (an ordered list, relative to the folder); a component library carries both. `gutterpress.markdown` exists for the one case `main` can't express: a package whose `main` is not the plugin. Folders still carrying the removed `gutterpress.json` or `theme.json` fail to load with a message showing the package.json that replaces them.
 
-Order is load order: a later entry's markdown runs after earlier entries' (and sees their output) and its CSS wins ties; the project's own `styles:` always load after every extension. There is no `priority` and no `path:`/`name:` wrapper — a manifest still carrying `plugins:` fails with a message that prints the same entries rewritten as `extensions:`. The `engine:` and `engineStyles:` keys are gone too (there is one engine; move any `engineStyles` entries to the end of `styles:`).
+Order is load order: a later entry's markdown runs after earlier entries' (and sees their output) and its CSS wins ties — each extension's stylesheets are wrapped in their own cascade layer (`@layer ext.<name>`), declared in list order, so this holds however an extension writes its CSS; the project's own `styles:` stay unlayered and load after every extension, beating all of them at any specificity. There is no `priority` and no `path:`/`name:` wrapper — a manifest still carrying `plugins:` fails with a message that prints the same entries rewritten as `extensions:`. The `engine:` and `engineStyles:` keys are gone too (there is one engine; move any `engineStyles` entries to the end of `styles:`).
 
 Pinned npm packages and their runtime dependencies live under `plugins/npm/`,
 with a receipt that records the exact graph and hashes the complete tree. They

package/dist/{README-7x5akcns.md → README-3nj919rm.md}

@@ -134,14 +134,16 @@ settled by that one line rather than by which sheet `package.json`'s
 `gutterpress.styles` lists last, so splitting a sheet or reordering that list
 can no longer silently flip who wins.
 
-The trap, and it catches everyone once: a rule left OUTSIDE all the layers is
-fully unlayered, and unlayered CSS beats layered CSS at any specificity. So
-one stray rule at the bottom of `components.css` will out-rank every rule in
-`book.css`. Adopt the convention for a whole sheet at a time.
-
-These layers are unlayered relative to Gutterpress core (which uses
-`gp.marker` and `gp.vocab`), so every rule here still beats core exactly as it
-did before layers existed.
+The trap, and it catches everyone once: a rule left OUTSIDE all the layers
+beats every layered rule in the theme at any specificity. So one stray rule
+at the bottom of `components.css` will out-rank every rule in `book.css`.
+Adopt the convention for a whole sheet at a time.
+
+Gutterpress wraps the whole theme in a cascade layer of its own
+(`ext.<name>`), after core's `gp.marker`/`gp.vocab` and before the book's own
+`styles:`. These layers nest inside it: they settle ties between the theme's
+own files, every one of them beats core, and the book's own rules beat every
+one of them.
 
 ### 3. Authors write semantic markdown
 

package/dist/{README-3zk4tgnj.md → README-8b33qbjw.md}

@@ -110,27 +110,20 @@ Marker names are global across every plugin a book loads. Two plugins
 declaring `@callout` is a hard load error naming both — which is a good
 outcome, and another reason to prefix.
 
-### 5. Put your CSS in your own cascade layer
-
-`styles/plugin.css` wraps everything in `@layer {{SLUG}}`.
-
-Extension CSS lands in the book in `extensions:` list order, and always before
-the book's own `styles:`. In CSS an unlayered rule beats a layered one at any
-specificity. So an unlayered plugin sheet outranks every rule in a book whose
-look uses the recommended
-`@layer tokens, base, components, templates, pages, book;` convention — the
-author edits their CSS and nothing happens.
-
-Inside a layer, the book's own unlayered `styles:` always beat you, which is
-right. Against the LOOK's layers, position decides: a layer sorts by where it
-is first declared, so with this plugin listed above the look in `extensions:`
-its layer sorts first and is the weakest thing in the book — the right place
-for a plugin to sit. Listed below the look, its component rules win ties over
-the look's layered rules instead. Either way the author moves one line to
-change it; that is the whole point of the list.
-
-Adopt it for the whole file: a rule left outside the layer is unlayered and
-beats everything inside it, including your own.
+### 5. Leave the cascade to Gutterpress
+
+Gutterpress wraps every extension's CSS in a cascade layer of its own
+(`@layer ext.<name>`), in `extensions:` list order, before the book's own
+`styles:`. So `styles/plugin.css` needs no `@layer` of its own: the book's
+unlayered `styles:` always beat you, at any specificity, which is right — a
+plugin should be the easiest thing in the book to override — and against a
+look, position decides. Listed above the look, this plugin's layer sorts first
+and the look wins ties; listed below it, the plugin's component rules win.
+Either way the author moves one line to change it; that is the whole point of
+the list.
+
+If you do declare layers inside this sheet, they nest inside your extension's
+layer and only settle ties between your own rules.
 
 ## Theming: the token pattern
 

package/dist/api/index.js

@@ -124,12 +124,12 @@ import {
   syncProject,
   testRemoteAccess,
   validateProjectExtensions
-} from "../index-03cqyyyk.js";
+} from "../index-qmvmvetj.js";
 import {
   BuildError,
   DEFAULT_PRINT_OPTS,
   readyProbeExpr
-} from "../index-5dgxeevv.js";
+} from "../index-6n15e1ze.js";
 import {
   AUTO_SNAPSHOT_MESSAGE,
   HISTORY_PAGE_LIMIT,

package/dist/{audit-ebbbhpx7.js → audit-9vv4ncjv.js}

@@ -1,15 +1,15 @@
 import {
   executeAndReport
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   EXIT_CODES

package/dist/{build-zrajk3s2.js → build-ea05bvs0.js}

@@ -1,18 +1,18 @@
 import {
   runBuild,
   splitOutPath
-} from "./cli-hz44te1m.js";
+} from "./cli-cwv73tkx.js";
 import {
   log
-} from "./cli-36r50yr3.js";
+} from "./cli-y4vrycpn.js";
 import {
   UsageError,
   parseFormat,
   parsePdfxFlavor,
   rejectExtraPositionals,
   rejectUnknownFlags
-} from "./cli-gxq7yz5f.js";
-import"./cli-k8f9eb12.js";
+} from "./cli-6gg8vwaj.js";
+import"./cli-sekhwex4.js";
 import"./cli-c41yr7he.js";
 import {
   BuildError

package/dist/{cli-gxq7yz5f.js → cli-6gg8vwaj.js}

@@ -4,7 +4,7 @@ import {
 // package.json
 var package_default = {
   name: "gutterpress",
-  version: "0.10.11",
+  version: "0.11.1",
   description: "Markdown-to-PDF converter for professional print layout using a native Chromium print engine and Ghostscript.",
   author: "itlackey",
   license: "MPL-2.0",