gp-dimm-city 1.9.0 → 1.10.0

package/CHANGELOG.md

@@ -7,6 +7,82 @@ cut a version that has no `## [X.Y.Z]` heading below.
 
 ## [Unreleased]
 
+## [1.10.0] - 2026-10-31
+
+### Changed
+
+- **Needs Gutterpress 0.11.22 or later** (was 0.11.20-alpha.3), in
+  `engines.gutterpress` and the README. With `size` gone from
+  `styles/page-rules.css` (below), the page size comes from the book's
+  manifest, which Gutterpress writes from 0.11.22 on. On 0.11.21 a book would
+  fall back to Letter (the design guide's full-bleed plates fail its build);
+  now Gutterpress refuses to load the extension there and says to update.
+  Margins set in Book setup > Book > Margins (`page.margin`, new in
+  Gutterpress 0.11.23) leave the full-bleed plates and named pages theirs
+  from 0.11.23-beta.1 (dimm-city/gutterpress#454).
+- **Full-page art plates are the sheet the book prints.** `.dc-specialty-art`
+  and `.dc-full-page` / `@page full-bleed` take their size from
+  `--gp-page-width` / `--gp-page-height` (Gutterpress 0.11.23-beta.1 on), so
+  they follow the book's page size instead of a copy of the `dtrpg` sheet; on
+  0.11.22 they fall back to that sheet. At that sheet the PDF is identical.
+- **Tests and the guide build run on Gutterpress 0.11.23.** The dev
+  dependency moves from 0.11.20-alpha.3, three releases behind, to the 0.11.23
+  line the 1.10 release targets. The guide is 172 pages, four fewer than on
+  0.11.23-alpha.6: Gutterpress now keeps the guide's own `break-before: auto`
+  on specialty specimens in doc pages (dimm-city/gutterpress#476), so the
+  blank pages it put before them are gone; the Part 2 example still opens its
+  spread on a left page. The design
+  guide's manifest uses 0.11.23's flat shape: `chapters:` (was
+  `source.files`), no `page.tolerance` (the preset's), and no
+  `validate.source.markdownlint` (the repo's `.markdownlint.jsonc` is found by
+  walking up to the repository root).
+- **Docs follow Gutterpress 0.11.23.** Vendored copies live under
+  `extensions/npm/` (a book vendored earlier keeps `plugins/npm/` until its
+  next `ext add` or `ext update`), the app adds an npm extension on Book
+  setup's Extensions tab, and the README and `package.json` give the same minimum
+  Gutterpress version. The README's `ext list` sample shows
+  1.9.0 with the badges in the order Gutterpress prints them.
+- **The design guide and the snippets type the plain spellings** (`---`, `--`,
+  `...`, `-`, `'`). `source.characters` findings on the guide drop from 367 to
+  0 (its six minus signs are typed on purpose, and Gutterpress no longer
+  flags them from 0.11.23-beta.1), and the five snippets paste into a book
+  with none.
+
+### Removed
+
+- **`size` from `styles/page-rules.css`'s `@page`.** Gutterpress 0.11.23
+  writes the manifest's page size after every stylesheet and reports a `size`
+  in a look as `printsafe/page-size-in-stylesheet` on every build. The sheet is
+  the same 8.625 × 11.25 in.
+- **`--page-width` and `--page-height` from `dc-palette.css`.** They copied
+  the `dtrpg` sheet and did not follow a book's page size; read
+  `--gp-page-width` / `--gp-page-height` instead.
+- **`gutterpress.tokensFile` from `package.json`.** Gutterpress 0.11.23 reads
+  every enabled look's `:root` tokens and no longer reads the field.
+- **The `lint` npm script and the `gutterpress lint` row in the design guide.**
+  The command does not exist; the print-safety lint runs inside
+  `gutterpress build` and `gutterpress validate`, and
+  `gutterpress validate <book> --category source` runs the source checks
+  alone.
+
+### Fixed
+
+- **`@outcome` rolls and ladder bands accept `--`.** `11--19` prints as
+  11–19 and a ladder table typed that way is recognised; the `–` spelling
+  still works. The character check asks for `--`, and Gutterpress 0.11.23's
+  example books type it.
+- **An alert's first paragraph is typeset like any other.** `---`, `--`, `...`
+  and straight quotes inside `> [!NOTE]`, `> [!VIBE]` and the other alert
+  blocks printed as typed, and `&mdash;` printed as `<>`, in the paragraph
+  that followed the marker; later paragraphs were fine. The marker is now cut
+  from the text markdown-it had already typeset rather than re-parsed. The six
+  em dashes the guide had to leave typed for this (chapters 5 and 11) type
+  `---` now.
+- **The guide keeps its six minus signs.** The `−1` (U+2212) in chapters 6,
+  11, 304 and 306 print as typed; a minus is not a hyphen and is not converted
+  to one. The character check flags them until Gutterpress 0.11.23 stops
+  asking for `-`.
+
 ## [1.9.0] - 2026-10-26
 
 ### Changed

package/README.md

@@ -8,10 +8,11 @@ the package renders them and prints them.
 
 ## Install
 
-**In the Gutterpress app:** open the book, then Project settings → Features →
-*Find more on npm* (search "dimm city") or *Install from npm* and enter
-`gp-dimm-city`. Confirm the install prompt. The package appears under Features
-with a "+ look" badge, and its sheets and snippets are live in the preview.
+**In the Gutterpress app:** open the book, then Book setup → Extensions, search
+npm for `gp-dimm-city` and click Add (or add it by exact name under *Other ways
+to add*). The package joins Your extensions, and its sheets and snippets are
+live in the preview. The
+[desktop guide](https://github.com/dimm-city/gutterpress/blob/main/docs/desktop-guide/06-plugins.md) has the rest.
 
 **From the command line**, in the folder that holds the book:
 
@@ -20,22 +21,22 @@ gutterpress ext add gp-dimm-city my-book
 ```
 
 Either way Gutterpress downloads the package from npm, verifies the registry
-hash, writes a copy under `my-book/plugins/npm/`, and pins the exact version
+hash, writes a copy under `my-book/extensions/npm/`, and pins the exact version
 in the manifest:
 
 ```yaml
 extensions:
-  - gp-dimm-city@1.5.0
+  - gp-dimm-city@1.9.0
 ```
 
-**Commit the manifest, not `plugins/npm/`.** The downloaded copy is not part of
-the book's history: Gutterpress adds `plugins/npm/` to the book's `.gitignore`.
-The pin in the manifest is what you commit. On a fresh clone, the first build,
-export or `gutterpress validate` downloads exactly the pinned version through
-the same verified path (this needs the network once); after that the book works
-offline.
+**Commit the manifest, not `extensions/npm/`.** The downloaded copy is not part
+of the book's history: Gutterpress adds `extensions/npm/` to the book's
+`.gitignore`. The pin in the manifest is what you commit. On a fresh clone, the
+first build, export or `gutterpress validate` downloads exactly the pinned
+version through the same verified path (this needs the network once); after that
+the book works offline.
 
-`gutterpress ext list my-book` shows `gp-dimm-city@1.5.0 [npm; markdown, styles, components, snippets]`.
+`gutterpress ext list my-book` shows `gp-dimm-city@1.9.0 [npm; markdown, styles, snippets, components]`.
 
 ## What you get
 
@@ -114,9 +115,10 @@ Also in the box:
 
 ## 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.
+Requires Gutterpress **0.11.22** or later, the first that prints the book at
+its manifest's page size (this look no longer sets one). Since 0.11.0 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
@@ -126,8 +128,10 @@ gutterpress preview my-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
-the manifest's `page:` in step with it.
+*Specialty* as you write. The `dtrpg` preset sets the sheet, Letter with
+bleed. The look's page margins are a starting point: from Gutterpress
+0.11.23, Book setup > Book > Margins (`page.margin` in the manifest) sets
+the book's own, and the full-bleed plates and named pages keep theirs.
 
 ## Author overrides
 
@@ -229,7 +233,11 @@ gutterpress ext add gp-dimm-city@1.5.0 my-book
 ```
 
 Installing a version removes the book's copies of other versions of this
-package, so there is nothing to clean up by hand. Commit the manifest change.
+package, so there is nothing to clean up by hand. A book vendored before
+Gutterpress 0.11.23 keeps working from its `plugins/npm/` copy until its next
+`ext add` or `ext update`, which moves the package to `extensions/npm/`, removes
+the old copies and the empty `plugins/` folder, and replaces the `.gitignore`
+line. Commit the manifest change.
 
 Rebuild and compare before you commit — the Dimm City books gate every bump
 with a render-parity run (text runs, image placement, and a pixel comparison

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gp-dimm-city",
-  "version": "1.9.0",
+  "version": "1.10.0",
   "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",
@@ -55,7 +55,6 @@
       "styles/page-rules.css",
       "styles/dc-native.css"
     ],
-    "tokensFile": "styles/dc-palette.css",
     "components": "components.yaml",
     "snippets": "snippets"
   },
@@ -63,18 +62,17 @@
     "dev": "gutterpress preview design-guide --open",
     "build": "gutterpress build design-guide --format pdf --out .build/design-guide.pdf",
     "build:html": "gutterpress build design-guide --format html --out .build/design-guide-site",
-    "lint": "gutterpress lint design-guide",
     "test": "bun test",
     "test:update-snapshot": "bun test --update-snapshots",
     "book-diff": "bun scripts/book-diff.mjs",
     "pack:check": "npm pack --dry-run"
   },
   "devDependencies": {
-    "gutterpress": "0.11.20-alpha.3",
+    "gutterpress": "0.11.23",
     "markdown-it": "^14.1.0"
   },
   "engines": {
-    "gutterpress": ">=0.11.20-alpha.3"
+    "gutterpress": ">=0.11.22"
   },
   "peerDependencies": {
     "markdown-it": ">=14"

package/plugin.js

@@ -386,9 +386,9 @@ const OUTCOME_NAMES = { crit: 'Crit', hit: 'Hit', mixed: 'Hard Choice', miss: 'M
 // Any other set of bands (six bands, three, a split at 10) is NOT a ladder.
 const LADDER_TIER_OF_BAND = { '20': 'crit', '11-19': 'hit', '6-10': 'mixed', '2-5': 'miss', '1': 'fail' };
 
-// "11 – 19" → [11, 19], "**20**" → [20, 20]; anything that is not a number or a range → null.
+// "11 – 19" → [11, 19], "11--19" → [11, 19], "**20**" → [20, 20]; anything that is not a number or a range → null.
 function parseBand(cell) {
-  const text = cell.replace(/[*_`\s]/g, '').replace(/[\u2010-\u2015\u2212]/g, '-');
+  const text = cell.replace(/[*_`\s]/g, '').replace(/[\u2010-\u2015\u2212]|-{2,3}/g, '-');
   const m = /^(\d{1,3})(?:-(\d{1,3}))?$/.exec(text);
   if (!m) return null;
   const [lo, hi] = [Number(m[1]), Number(m[2] ?? m[1])];
@@ -423,7 +423,7 @@ function outcomeRowsHtml(rows, md, head = []) {
     : '  <div class="dc-outcomes-label">Outcomes</div>\n';
   rows.forEach(({ tier, name, roll, text }) => {
     html += '  <div class="dc-outcome-row ' + tier + '">\n';
-    html += '    <span class="dc-outcome-key tier-' + tier + '"><span class="dc-outcome-name">' + esc(name) + '</span><span class="dc-outcome-roll">' + esc(roll) + '</span></span>\n';
+    html += '    <span class="dc-outcome-key tier-' + tier + '"><span class="dc-outcome-name">' + esc(name) + '</span><span class="dc-outcome-roll">' + esc(roll.replace(/(\d)\s*--\s*(\d)/g, '$1\u2013$2')) + '</span></span>\n';
     html += '    <span class="dc-outcome-text">' + md.renderInline(text) + '</span>\n';
     html += '  </div>\n';
   });
@@ -663,7 +663,8 @@ function dcAlertsTransform(state) {
     if (closeIdx === -1 || firstInlineIdx === -1) { newTokens.push(tok); continue; }
 
     const inlineTok = tokens[firstInlineIdx];
-    const match = inlineTok && inlineTok.content.match(DC_ALERT_PATTERN);
+    const lead = inlineTok && inlineTok.children && inlineTok.children[0];
+    const match = lead && lead.type === 'text' && inlineTok.content.match(DC_ALERT_PATTERN);
     if (!match) { newTokens.push(tok); continue; }
 
     const alertType = match[1].toUpperCase();
@@ -680,7 +681,8 @@ function dcAlertsTransform(state) {
     newTokens.push(openTok);
 
     // Strip [!TYPE] prefix from first inline; suppress its paragraph wrapper if empty.
-    const prefixMatch = inlineTok.content.match(/^\[![A-Z_]+\][ \t]*/i);
+    const markerPrefix = /^\[![A-Z_]+\][ \t]*/i;
+    const prefixMatch = inlineTok.content.match(markerPrefix);
     const stripped = prefixMatch
       ? inlineTok.content.slice(prefixMatch[0].length).trim()
       : inlineTok.content;
@@ -697,11 +699,18 @@ function dcAlertsTransform(state) {
       if (!t) continue;
       if (j === firstInlineIdx) {
         if (stripped === '') continue;
-        const strippedTok = new state.Token('inline', '', 0);
-        strippedTok.content = stripped;
-        strippedTok.children = [];
-        state.md.inline.parse(stripped, state.md, state.env, strippedTok.children);
-        newTokens.push(strippedTok);
+        // The core rules have already typeset the children, so take the marker
+        // off the lead text (and the line break it leaves at the front) and
+        // keep the rest; re-parsing would skip replacements, smartquotes and
+        // text_join.
+        lead.content = lead.content.replace(markerPrefix, '');
+        if (lead.content === '') {
+          inlineTok.children.shift();
+          const next = inlineTok.children[0];
+          if (next && (next.type === 'softbreak' || next.type === 'hardbreak')) inlineTok.children.shift();
+        }
+        inlineTok.content = stripped;
+        newTokens.push(inlineTok);
         continue;
       }
       if (stripped === '' && wrapsInParagraph) {

package/snippets/npc-stat-compact.md

@@ -4,9 +4,9 @@
 
 > {{flavor}}
 
-{{hp}} HP — {{damage}} Damage
+{{hp}} HP --- {{damage}} Damage
 
-{{role}} — {{size}}
+{{role}} --- {{size}}
 
 ##### Traits
 

package/snippets/npc-stat.md

@@ -4,8 +4,8 @@
 
 > {{flavor}}
 
-{{hp}} HP — {{damage}} Damage
-{{role}} — {{size}}
+{{hp}} HP --- {{damage}} Damage
+{{role}} --- {{size}}
 
 ##### Traits
 

package/snippets/outcome.md

@@ -1,9 +1,9 @@
 @outcome
 
 20 | Triumph | {{triumph}}
-11–19 | Success | {{success}}
-6–10 | Hard Choice | {{hard-choice}}
-2–5 | Failure | {{failure}}
+11--19 | Success | {{success}}
+6--10 | Hard Choice | {{hard-choice}}
+2--5 | Failure | {{failure}}
 1 | Catastrophe | {{catastrophe}}
 
 @end-outcome

package/snippets/toc-page.md

@@ -10,6 +10,6 @@
 
 @toc
 
-1. [{{chapter}}](#{{id}}) — {{blurb}}
+1. [{{chapter}}](#{{id}}) --- {{blurb}}
 
 @end-toc

package/snippets/toc.md

@@ -1,5 +1,5 @@
 @toc
 
-1. [{{chapter}}](#{{id}}) — {{blurb}}
+1. [{{chapter}}](#{{id}}) --- {{blurb}}
 
 @end-toc

package/styles/components/chrome.css

@@ -430,8 +430,8 @@ hr {
 
 /* ── Specialty art full-page plate ─────────────────────────────────────────── */
 .dc-specialty-art {
-  width: var(--page-width);
-  height: var(--page-height);
+  width: var(--gp-page-width, 8.625in);
+  height: var(--gp-page-height, 11.25in);
   /* Its break is in page-templates.css (SPECIALTY BREAK CONTROL). */
   margin: 0;
   overflow: hidden;

package/styles/dc-palette.css

@@ -170,9 +170,10 @@
   --outer-margin:  0.625in; /* outer (non-binding) page margin */
   --sidebar-width: 3.05in;
 
-  /* ── Page Geometry ────────────────────────────────────────────────────── */
-  --page-width:     8.625in;
-  --page-height:    11.25in;
+  /* ── Page Geometry ──────────────────────────────────────────────────────
+     The sheet is the book's (its manifest's preset or page size); a rule that
+     needs its size reads Gutterpress's --gp-page-width / --gp-page-height
+     (0.11.23 on), with the dtrpg sheet as the fallback for 0.11.22. */
   --binding-margin: 0.5in;
 
   /* ── Shapes ───────────────────────────────────────────────────────────── */

package/styles/page-rules.css

@@ -49,14 +49,12 @@
    Default page template — Letter+bleed for DTRPG (8.625 x 11.25)
    --------------------------------------------------------------------------- */
 
-/* `size` stays a literal on purpose. Chromium resolves var() in @page margins
-   — measured: `@page :left { margin-left: var(--om) }` put text at exactly
-   0.625in on a verso page — so the margins below name their tokens. The trim
-   SIZE is the one value where a var() that failed to resolve would silently
-   produce a differently-sized book, and it is duplicated by --page-width /
-   --page-height in dc-palette.css: change both together. */
+/* The sheet size comes from the book's manifest: Gutterpress 0.11.23 writes
+   `@page { size }` after every stylesheet, so a `size` here is ignored and
+   reported. A rule that needs the sheet's size reads --gp-page-width /
+   --gp-page-height, which Gutterpress publishes from what it prints (0.11.23
+   on; the rules fall back to the dtrpg sheet on 0.11.22). */
 @page {
-  size: 8.625in 11.25in;
   margin: var(--page-margin) var(--outer-margin) var(--bottom-margin);
   background-color: var(--bg);
 }

package/styles/page-templates.css

@@ -93,10 +93,10 @@
 /* Empty full-bleed pages need explicit geometry so the engine allocates a page.
    The height is core's published content box for THIS page's context
    (core's `gp-page-full-bleed` is margin: 0, so its content box IS the sheet)
-   rather than `var(--page-height)`: a non-zero margin on that page would
+   rather than the sheet's height: a non-zero margin on that page would
    push the plate past the page box with nothing to catch it. */
 :is(.dc-full-page, .gp-page-full-bleed) {
-  width: var(--page-width);
+  width: var(--gp-page-width, 8.625in);
   height: var(--gp-content-h, 11.25in);
   background-color: var(--bg);
   break-before: page;