gp-dimm-city 1.0.0 → 1.0.1

package/CHANGELOG.md

@@ -7,7 +7,32 @@ cut a version that has no `## [X.Y.Z]` heading below.
 
 ## [Unreleased]
 
-## [1.0.0] - unreleased
+## [1.0.1] - 2026-09-25
+
+### Changed
+
+- **The layer statement drops `book`**: `dc-fonts.css` now declares `@layer
+  dc.tokens, dc.base, dc.components, dc.templates, dc.pages;`. Gutterpress
+  0.11.0 wraps every extension's CSS in its own cascade layer (`@layer
+  ext.gp-dimm-city` for this package), so the package's own `dc.*` layers are
+  now sublayers nested inside that wrapper rather than top-level layers, and
+  a `book` sublayer declared here would only be reachable from inside this
+  package — a consuming book's separate `styles:` sheet can't nest into it.
+  Nothing in this package or any known consuming book ever put rules inside
+  `@layer book`, so there is no rendered change.
+
+### Docs
+
+- **README quick start now requires Gutterpress 0.11.0+** and drops the
+  `gutterpress ext remove ./extensions/clean-book` workaround: Gutterpress
+  now layers every extension's CSS itself (in `extensions:` list order), so
+  this package's rules can no longer be jumped by an unlayered starter look,
+  and `gutterpress new` no longer scaffolds one anyway. The "Your own CSS"
+  section no longer recommends wrapping book overrides in `@layer book` —
+  a book's own `styles:` sheets are unlayered by the engine and already beat
+  this whole package at any specificity.
+
+## [1.0.0] - 2026-09-25
 
 First release as a standalone package. Extracted from the private
 `dimm-city/dc-op-manual` repository, where it lived at `dc-design-guide/` as a

package/README.md

@@ -67,20 +67,16 @@ byte for byte on every build.
 
 ## Quick start
 
+Requires Gutterpress **0.11.0** or later — it wraps every extension's CSS in
+its own cascade layer, so a book no longer needs a starter look removed
+before this package can win the cascade.
+
 ```sh
 gutterpress new "My Book" --preset dtrpg
-gutterpress ext remove ./extensions/clean-book my-book && rm -r my-book/extensions
 gutterpress ext add gp-dimm-city my-book
 gutterpress preview my-book
 ```
 
-The second line matters. `gutterpress new` gives every book a starter look
-(`./extensions/clean-book`), and a look's CSS is unlayered, so it beats this
-package's layered rules on anything the look styles — plain prose comes out in
-the starter's serif instead of Titillium Web. This package *is* the look;
-remove the starter before adding it. (In the app: Project settings → Look →
-remove *Clean book*.)
-
 Then insert the *Toc Page*, *Credits Page* and *Chapter Start Page* snippets
 to lay down the front matter, and reach for *Skill*, *Learning Path* and
 *Specialty* as you write. `page-rules.css` sets a Letter page with bleed; keep
@@ -88,34 +84,28 @@ the manifest's `page:` in step with it.
 
 ## Your own CSS: the layer convention
 
-List your sheets under `styles:` in the manifest. Extension styles always load
-first, so yours come after. Wrap them in the `book` layer:
+List your sheets under `styles:` in the manifest. Gutterpress (0.11.0+) wraps
+this whole package in its own cascade layer, `@layer ext.gp-dimm-city`, and
+keeps the book's own `styles:` unlayered — so anything you write there beats
+every rule in this package at any specificity, with no layer of your own to
+declare:
 
 ```css
-@layer book {
-  #chapter-03 { --dc-section-accent: var(--hud-magenta); }
-}
+#chapter-03 { --dc-section-accent: var(--hud-magenta); }
 ```
 
-The package declares `@layer dc.tokens, dc.base, dc.components, dc.templates,
-dc.pages, book;` in its first sheet. `book` is last, so anything you put there
-outranks every `dc.*` rule without a specificity contest. Two things to know:
-
-- `dc-native.css` is deliberately **unlayered** so it beats every layered rule
-  — a book that must override it lists an **unlayered** sheet after the
-  extension; the last unlayered sheet wins.
-- Do not invent layer names. A layer the package's statement does not name is
-  created where it is first used, which puts it *after* `book` and silently
-  above your own overrides.
+The package's own sheets are layered internally (`@layer dc.tokens, dc.base,
+dc.components, dc.templates, dc.pages`, nested inside `ext.gp-dimm-city`), and
+`dc-native.css` stays last and unlayered within that internal stack — that's
+a package-internal ordering concern, not something your book needs to work
+around.
 
 Never write bare `.dc-*` rules in a book to change a component; that fights
 the package on every update. Reset the component's public tokens on a context
 selector instead:
 
 ```css
-@layer book {
-  .chapter-05 .dc-alert { --dc-alert-accent: var(--hud-blue); }
-}
+.chapter-05 .dc-alert { --dc-alert-accent: var(--hud-blue); }
 ```
 
 The tokens each component exposes are listed under `tokens:` in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gp-dimm-city",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Dimm City design system for Gutterpress: the markdown-it macros (@skill, @specialty, @learning-path, @callout, …), print stylesheets, design tokens, fonts and page templates the Dimm City TTRPG books are set in.",
   "type": "module",
   "main": "plugin.js",

package/styles/components/callouts.css

@@ -25,10 +25,10 @@
    - :root token definitions (→ dc-component-defaults.css)
    - @media screen rules (print-only project)
    - Element selectors scoped to page/chapter context classes
-     (→ the book's own sheet (`@layer book`))
+     (→ the book's own sheet (unlayered))
 
    CORE CONSTRAINT — COMPONENT STYLE ISOLATION:
-   If a bare .dc-* rule needs different values in the book's own sheet (`@layer book`), the
+   If a bare .dc-* rule needs different values in the book's own sheet (unlayered), the
    components/*.css value is WRONG — fix it here. The override files own
    layout context only. Never split a component's appearance across files.
 
@@ -75,7 +75,7 @@
      `var(--x, fallback)`. A token declared at :root needs no fallback, and
      an inline fallback that duplicates the :root value is dead weight that
      invites the two to drift (found and corrected during dc#34).
-   - Variants and contexts set tokens on ANCESTORS (the book's own sheet (`@layer book`)
+   - Variants and contexts set tokens on ANCESTORS (the book's own sheet (unlayered)
      chapter/page scopes) or on VARIANT CLASSES on the same element
      (`.dc-ap.free`, `.dc-sidebar.inset`, `.dc-specialty.<name> .dc-X`) —
      never by re-declaring the token on the base component selector itself.
@@ -92,7 +92,7 @@
 
 /* ── Base shell — player-facing: pale cyan HUD panel, blue border ─────────── */
 /* Token defaults for .dc-alert are declared in :root in dc-component-defaults.css.
-   Override at chapter-id scope in the book's own sheet (`@layer book`), or in variant rules below. */
+   Override at chapter-id scope in the book's own sheet (unlayered), or in variant rules below. */
 .dc-alert {
   background: var(--dc-alert-bg);
   border-left: var(--dc-alert-border-width) solid var(--dc-alert-border);

package/styles/components/cards.css

@@ -48,7 +48,7 @@
      6px. The old margin-bottom was exactly 6px, so it was entirely consumed
      and consecutive cards rendered touching (screenshot-confirmed on the
      Augmerc BODYCOVER/BLITZ seam). Same class of fix as .fg-art-portrait's
-     margin-bottom in the book's own sheet (`@layer book`). */
+     margin-bottom in the book's own sheet (unlayered). */
   margin-bottom: calc(var(--dc-card-gap) + 6px);
   max-width: 100%;
   /* 4-way ink outline (2px on each side) + HARD offset poster shadow. The

package/styles/components/chrome.css

@@ -99,7 +99,7 @@ h1.dc-chevron {
   line-height: 1.2;
 }
 
-/* Front-matter chevron font-size overrides moved to the book's own sheet (`@layer book`) per A1
+/* Front-matter chevron font-size overrides moved to the book's own sheet (unlayered) per A1
    layer-ownership (page-context rules belong in the guide-specific override
    file, not the portable component library). Three-judge gate iteration 3. */
 

package/styles/components/section.css

@@ -672,7 +672,7 @@ h3 + .section {
 
    To tune the walkthrough's accent or substrate, override the existing
    --dc-section-accent / --dc-section-bg custom properties at the chapter
-   id scope in the book's own sheet (`@layer book`) — do NOT add bespoke rules here unless an
+   id scope in the book's own sheet (unlayered) — do NOT add bespoke rules here unless an
    observed problem requires it.
 
    OBSERVED PROBLEM (2026-05-25): When the walkthrough's first card uses
@@ -865,7 +865,7 @@ h3 + .section {
 
 
 
-/* Per-book variant assignment lives in the book's own sheet (`@layer book`) using natural
+/* Per-book variant assignment lives in the book's own sheet (unlayered) using natural
    selector chains (chapter id → page template class → section component
    class) that set component CSS custom properties. No utility-variant
    classes here — that would force authors to re-type variant intent. */
@@ -1036,7 +1036,7 @@ h3 + .section {
    declared in :root in dc-component-defaults.css — same values as before this moved
    (the 3in art width: user feedback said the previous 1.85in "Lil Thump
    placeholder image is too small... should take up more of the left side
-   of the page"). Per-page/per-chapter variants override via the book's own sheet (`@layer book`)
+   of the page"). Per-page/per-chapter variants override via the book's own sheet (unlayered)
    context selectors, e.g. `.page....chapter-01 .section.dc-fiction-excerpt`. */
 .section.dc-fiction-excerpt {
   background: var(--dc-fiction-bg);

package/styles/dc-component-defaults.css

@@ -2,7 +2,8 @@
 
 :root {  /* ── Section Component Public Tokens ────────────────────────────────────
      Default theming for .section / @section macros. Chapter-scoped overrides
-     live in the book's own sheet (`@layer book`) and win via the parent-context cascade —
+     live in the book's own sheet (unlayered — it wins over this whole package
+     regardless of specificity) and win via the parent-context cascade —
      typically by applying a .dc-accent-X utility on @chapter / @section
      (see components/*.css "ACCENT IDENTITY UTILITIES" section). */
   --dc-section-bg:     var(--paper-cream);
@@ -12,9 +13,9 @@
      Override surface for per-chapter and per-project theming. These are the
      defaults that were previously declared inside each component class rule.
      Moving them to :root makes them visible to the theming system and lets
-     the book's own sheet (`@layer book`) override them at chapter-id scope instead of having to
+     the book's own sheet override them at chapter-id scope instead of having to
      write a full component selector chain.
-     Set them here; override at chapter id scope in the book's own sheet (`@layer book`).
+     Set them here; override at chapter id scope in the book's own sheet.
      ──────────────────────────────────────────────────────────────────────── */
 
   /* .dc-alert public API */

package/styles/dc-fonts.css

@@ -15,29 +15,32 @@
    - .page.* layout or column rules (→ page-templates.css)
    - .dc-* component/utility styles (→ components/*.css / page-templates.css)
    - Design tokens (→ dc-palette.css, dc-identity.css, dc-component-defaults.css)
-   - Anything a single book needs (→ that book's own sheet, `@layer book`)
+   - Anything a single book needs (→ that book's own sheet, unlayered — no
+     `@layer` needed)
    - @media screen rules (print-only project)
 
    AGENT RULE: "Is this a token or a font?" — if NO, use another file.
 
    ──────────────────────────────────────────────────────────────────────── */
 
-/* Layer order for the whole DC stack, declared here because this is the
-   first sheet the cascade sees — so layer order stops depending on the
-   manifest's file order. `dc-fonts.css` itself is deliberately NOT wrapped
-   in a layer: @font-face inside a layer is legal but pointless (font-family
-   lookup is not a cascade contest). `dc-native.css`, the last sheet in this
-   package, is ALSO deliberately unlayered — not because it is special, but
-   because it is LAST, and anything that must beat unlayered author CSS
-   cannot be layered (see docs/css-architecture.md).
+/* Sublayer order for this package's OWN stack, declared here because this is
+   the first sheet the cascade sees — so layer order stops depending on the
+   manifest's file order. Gutterpress ≥0.11.0 wraps every extension's CSS in
+   `@layer ext.<name>` (this package is `ext.gp-dimm-city`), so this
+   statement declares sublayers nested inside that wrapper, not top-level
+   layers.
 
-   `book` is the layer for a consuming book's own sheets: declared last here,
-   it outranks every dc.* layer, so a book wins any cross-layer tie without
-   fighting specificity. A book that must beat dc-native.css lists an
-   UNLAYERED sheet after it in its manifest instead. Do not invent further
-   layers in a book — a layer this statement does not name sorts after
-   `book`, silently above your own overrides. */
-@layer dc.tokens, dc.base, dc.components, dc.templates, dc.pages, book;
+   `dc-fonts.css` itself is deliberately NOT wrapped in a layer: @font-face
+   inside a layer is legal but pointless (font-family lookup is not a
+   cascade contest). `dc-native.css`, the last sheet in this package, is
+   ALSO deliberately unlayered — not because it is special, but because it
+   is LAST, and anything that must beat the other dc.* sublayers cannot
+   itself be layered. That ordering is internal to this package only: a
+   consuming book's own `styles:` sheets stay unlayered by the engine and
+   beat this whole `ext.gp-dimm-city` stack — dc-native.css included —
+   automatically, at any specificity, so a book needs no layer of its own to
+   win (see docs/css-architecture.md). */
+@layer dc.tokens, dc.base, dc.components, dc.templates, dc.pages;
 
 /* ── WEBFONTS (local) ─────────────────────────────────────────────────────── */
 @font-face {

package/styles/dc-native.css

@@ -2,9 +2,13 @@
    DC-NATIVE.CSS — engine-specific page chrome
    =============================================================================
    The LAST entry in package.json `gutterpress.styles`, and deliberately
-   unlayered, so it beats every layered sheet in this package and in the
-   book. A book's own unlayered sheet listed after the extension still wins
-   over it — that is the one hook a book has above this file.
+   unlayered *within this package's own layer stack* — so it beats every
+   `dc.*` sublayer in this package, which is why it must stay last in the
+   array. Gutterpress ≥0.11.0 wraps the whole package in a layer of its own,
+   `ext.gp-dimm-city`, so from outside the package that unlayered status
+   doesn't matter: the book's own `styles:` sheets stay unlayered by the
+   engine and beat this whole file automatically, at any specificity, with
+   no unlayered-sheet trick required on the book's side.
 
    Mechanics, each measured against Chromium 151 (gutterpress ENGINE.md §5/§8):
    - ONE `@page { background }` rule paints the brick wall across the whole

package/styles/page-templates.css

@@ -317,7 +317,7 @@
        inside the composite.
 
    This block is the SINGLE location where TOC and Credits styling lives —
-   do not split it across the book's own sheet (`@layer book`). */
+   do not split it across the book's own sheet. */
 
 /* Identity tokens for the spread. --dc-intro-accent / --dc-intro-bg feed
    the .dc-intro component's gradient via its own var() fallback chain. */