gp-dimm-city 1.1.3 → 1.1.4

package/CHANGELOG.md

@@ -7,6 +7,26 @@ cut a version that has no `## [X.Y.Z]` heading below.
 
 ## [Unreleased]
 
+## [1.1.4] - 2026-10-09
+
+### Changed
+
+- **The columns contract is refined.** Page and section column layouts
+  stay in `page-templates.css`. A component may lay out its own insides in
+  columns in its own sheet, on a selector rooted in its `.dc-*` class (the
+  two-column skill cards, the card grid). The integrity test enforces that
+  rule in place of an exception list. No CSS moved.
+- The integrity test's remaining exceptions are genuine hooks: the outcome
+  tiers, the chapter classes gutterpress adds itself, and the design
+  guide's page labels.
+- `docs/css-roadmap.md` records what the CSS review left to do, and in
+  which order.
+
+### Removed
+
+- Two unused design-guide classes: `dg-face-sample` and the
+  `dc-banner-demo` section class.
+
 ## [1.1.3] - 2026-10-09
 
 ### Removed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gp-dimm-city",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "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

@@ -18,7 +18,7 @@
    - Component-scoped public custom properties (--dc-alert-bg, etc.)
 
    MUST NOT CONTAIN:
-   - columns:N rules of any kind (→ page-templates.css)
+   - page/section columns:N layouts (→ page-templates.css)
    - @page declarations or named-page assignments (→ page-rules.css)
    - div.chapter scaffolding (→ the consuming book's own sheet)
    - :root token definitions (→ dc-component-defaults.css)

package/styles/components/section.css

@@ -743,8 +743,8 @@ h3 + .section {
      [repeat for 6+ specialties]
      @end-section
 
-   The column-flow rules (columns:2) live in page-templates.css
-   per the architectural contract. Here we own only the chrome-reset (the
+   The page/section column rules live in page-templates.css; the grid's own
+   columns:2 is a component-internal layout and lives below. Here we also own the chrome-reset (the
    .dc-card-grid section has no card background/shadow — it's a pure layout
    wrapper) plus the per-card density tweaks so all 8 specialty cards fit
    comfortably on one page. */

package/styles/page-templates.css

@@ -4,9 +4,10 @@
 
    ── ARCHITECTURAL CONTRACT ────────────────────────────────────────────────
    OWNS:
-   - ALL THEME columns:N rules — this is the ONLY file that may set columns on
-     a theme selector. Components are always single-flow. It may NOT set
-     columns on core's `.gp-columns-*` (only their `--gp-column-gap`).
+   - ALL page and section columns:N layouts — this is the ONLY file that may
+     set columns on a page template or section run. A component may column its
+     OWN internals in its own sheet (cards.css, section.css .dc-card-grid). It
+     may NOT set columns on core's `.gp-columns-*` (only their `--gp-column-gap`).
    - .page.* content layout rules (columns, flex, grid on page content divs)
    - .page base geometry, .column-break
    - .dc-full-page full-bleed geometry (its named-page assignment,
@@ -26,8 +27,9 @@
    - @media screen rules (print-only project)
 
    COLUMN OWNERSHIP RULE (narrowed, dc#41): if a THEME rule sets columns:N on a PAGE TEMPLATE (.page.*) in this
-   project, it belongs here and ONLY here. Any columns:N found in another file
-   is a bug. Core's `.gp-columns-2` / `.gp-columns-3` are the generic column
+   project, it belongs here and ONLY here. A columns:N on a page/section
+   selector found in another file is a bug (a component's own-internals layout
+   in its sheet is not). Core's `.gp-columns-2` / `.gp-columns-3` are the generic column
    vocabulary and are NOT this file's to redefine — this file may only set
    their `--gp-column-gap`. See the column-runs block below.