@uniweb/kit 0.10.10 → 0.10.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/kit",
-  "version": "0.10.10",
+  "version": "0.10.12",
   "description": "Standard component library for Uniweb foundations",
   "type": "module",
   "exports": {
@@ -8,7 +8,8 @@
     "./xref": "./src/xref/index.js",
     "./theme-tokens.css": "./src/theme-tokens.css",
     "./prose-tokens.css": "./src/prose-tokens.css",
-    "./callout-tokens.css": "./src/callout-tokens.css"
+    "./callout-tokens.css": "./src/callout-tokens.css",
+    "./math-tokens.css": "./src/math-tokens.css"
   },
   "files": [
     "src",
@@ -42,9 +43,9 @@
     "fuse.js": "^7.0.0",
     "shiki": "^3.0.0",
     "tailwind-merge": "^3.6.0",
-    "@uniweb/semantic-parser": "1.2.1",
+    "@uniweb/scene": "0.1.2",
     "@uniweb/core": "0.8.1",
-    "@uniweb/scene": "0.1.2"
+    "@uniweb/semantic-parser": "1.2.1"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/math-tokens.css

@@ -0,0 +1,89 @@
+/*
+ * MathML layout for Temml-produced math.
+ *
+ * Usage — one line in the foundation's stylesheet:
+ *
+ *   @import "@uniweb/kit/math-tokens.css";
+ *
+ * `prose-tokens.css` already imports this, so a foundation using that needs
+ * nothing further. This file exists separately because rendering math and
+ * setting up prose typography are different decisions: the academic template
+ * has 23 equations and no prose column, and while these rules lived inside
+ * prose-tokens it shipped its maths unstyled — matrices with their rows
+ * touching, `=` signs out of line, no equation numbers — with nothing to point
+ * at. Correct metrics are not a typography opt-in.
+ *
+ * press emits the same declarations into its EPUB and Paged.js output, since
+ * those lanes carry their own stylesheets and cannot import this one. The two
+ * copies are pinned by `framework/_contracts/math-css-parity.test.js`.
+ */
+
+/* ─── Math (Temml → MathML) ────────────────────────────────────────────────────
+   Browsers render MathML natively, so it is easy to conclude math needs no CSS.
+   It needs these, for two separate reasons.
+
+   Temml emits class hooks and expects a stylesheet to define them: `tml-left`
+   and `tml-right` carry the `&` column alignment of an `aligned` environment,
+   `tml-jot` its extra row spacing. Undefined, a derivation's `=` signs drift
+   out of line and its rows sit flush. Those three declarations are Temml's own.
+
+   The `math mtd` rule is not. Temml's stylesheet only *adjusts* row spacing for
+   jot, on the stated assumption that mtd already gets 0.5ex of vertical padding
+   "per MathML-Core and user-agent CSS" — but a pristine mtd measures 0px in
+   Chrome (2026-07). A pmatrix or cases carries no tml-* class at all, so
+   Temml's stylesheet alone fixes the derivation and leaves the matrix touching.
+
+   These live here rather than in their own opt-in file because correct math
+   metrics are not a design choice the way callout colours are — a site that
+   sets its typography should not also have to know this.
+
+   press ships the same declarations to the EPUB and Paged.js lanes, which have
+   their own stylesheets and cannot import this one. That duplicate is pinned by
+   `framework/_contracts/math-css-parity.test.js`, not by trust. */
+.tml-right { text-align: right; }
+.tml-left { text-align: left; }
+.tml-sml-pad { padding-left: 0.05em; }
+math mtd { padding-top: 0.5ex; padding-bottom: 0.5ex; }
+math mtable.tml-jot mtd { padding-top: 0.7ex; padding-bottom: 0.7ex; }
+
+/* AMS auto-numbering, for lanes that keep our CSS counter.
+
+   Scoped to :empty because the document lanes cannot rely on it -- Paged.js
+   rewrites counters for its own pagination and strips counter-increment, so
+   every equation rendered as "(0)" (measured 2026-07-31; the declaration
+   survives intact without the polyfill). press therefore writes the numbers
+   into the spans as text, and a span carrying a number is no longer :empty, so
+   the two can never both fire.
+
+   AMS auto-numbering. Which equations number is the AUTHOR's choice, made in
+   LaTeX: `align` and `equation` number, `aligned` and the starred forms do not.
+   Without these two rules that choice was discarded -- `align` and `align*`
+   rendered identically, so an author who asked for numbers silently got none. */
+.tml-eqn:empty::before {
+  counter-increment: tmlEqnNo;
+  content: "(" counter(tmlEqnNo) ")";
+}
+body {
+  counter-reset: tmlEqnNo;
+}
+/* Display math needs CSS block layout, not MathML layout, for an equation TAG
+   to reach the right margin: the tag rides in an mtable whose `width:100%`
+   Chromium ignores under `display: block math`, collapsing the spacer cells so
+   "(1)" sits glued to the equation instead of at the margin.
+
+   `!important` is not decoration. Temml emits `style="display:block math"` on
+   every display formula unconditionally — no option turns it off — so an inline
+   style beats any rule we write, including Temml's own `math.tml-display
+   { display: block }`, which is exactly what this restores. Fixing it here
+   rather than in the generator also repairs math that was already built.
+
+   Scoped with :has() to formulas that actually carry a tag. Switching every
+   display formula to CSS block layout would left-align the lot -- MathML layout
+   is what centres them -- so an unnumbered derivation or matrix keeps
+   `display: block math` and stays centred. Where :has() is unsupported the tag
+   simply does not reach the margin; nothing else changes. */
+math.tml-display:has(.tml-eqn) {
+  display: block !important;
+  width: 100%;
+}
+

package/src/prose-tokens.css

@@ -1,3 +1,16 @@
+/*
+ * Maths is NOT included here. A foundation that renders equations imports
+ * `@uniweb/kit/math-tokens.css` as well — MathML needs its own layout rules,
+ * and prose typography does not imply them.
+ *
+ * They were briefly one file, and that is what shipped the academic template's
+ * equations unstyled: 23 of them, no prose column, so it imported neither. The
+ * fix is not to make prose pull maths in behind the reader's back — that just
+ * restates "prose implies maths" one indirection out, and leaves two ways to
+ * get one stylesheet. Each of kit's entry points owns one concern and the
+ * foundation composes them.
+ */
+
 /*
  * Tailwind Typography, wired to the theme.
  *
@@ -108,64 +121,3 @@
 .prose :is(h1, h2, h3, h4, figure, table, .math-display) {
   scroll-margin-top: calc(var(--header-height, 4rem) + 1rem);
 }
-
-/* ─── Math (Temml → MathML) ────────────────────────────────────────────────────
-   Browsers render MathML natively, so it is easy to conclude math needs no CSS.
-   It needs these, for two separate reasons.
-
-   Temml emits class hooks and expects a stylesheet to define them: `tml-left`
-   and `tml-right` carry the `&` column alignment of an `aligned` environment,
-   `tml-jot` its extra row spacing. Undefined, a derivation's `=` signs drift
-   out of line and its rows sit flush. Those three declarations are Temml's own.
-
-   The `math mtd` rule is not. Temml's stylesheet only *adjusts* row spacing for
-   jot, on the stated assumption that mtd already gets 0.5ex of vertical padding
-   "per MathML-Core and user-agent CSS" — but a pristine mtd measures 0px in
-   Chrome (2026-07). A pmatrix or cases carries no tml-* class at all, so
-   Temml's stylesheet alone fixes the derivation and leaves the matrix touching.
-
-   These live here rather than in their own opt-in file because correct math
-   metrics are not a design choice the way callout colours are — a site that
-   sets its typography should not also have to know this.
-
-   press ships the same declarations to the EPUB and Paged.js lanes, which have
-   their own stylesheets and cannot import this one. That duplicate is pinned by
-   `framework/_contracts/math-css-parity.test.js`, not by trust. */
-.tml-right { text-align: right; }
-.tml-left { text-align: left; }
-.tml-sml-pad { padding-left: 0.05em; }
-math mtd { padding-top: 0.5ex; padding-bottom: 0.5ex; }
-math mtable.tml-jot mtd { padding-top: 0.7ex; padding-bottom: 0.7ex; }
-
-/* AMS auto-numbering. Which equations number is the AUTHOR's choice, made in
-   LaTeX: `align` and `equation` number, `aligned` and the starred forms do not.
-   Without these two rules that choice was discarded -- `align` and `align*`
-   rendered identically, so an author who asked for numbers silently got none. */
-.tml-eqn::before {
-  counter-increment: tmlEqnNo;
-  content: "(" counter(tmlEqnNo) ")";
-}
-body {
-  counter-reset: tmlEqnNo;
-}
-/* Display math needs CSS block layout, not MathML layout, for an equation TAG
-   to reach the right margin: the tag rides in an mtable whose `width:100%`
-   Chromium ignores under `display: block math`, collapsing the spacer cells so
-   "(1)" sits glued to the equation instead of at the margin.
-
-   `!important` is not decoration. Temml emits `style="display:block math"` on
-   every display formula unconditionally — no option turns it off — so an inline
-   style beats any rule we write, including Temml's own `math.tml-display
-   { display: block }`, which is exactly what this restores. Fixing it here
-   rather than in the generator also repairs math that was already built.
-
-   Scoped with :has() to formulas that actually carry a tag. Switching every
-   display formula to CSS block layout would left-align the lot -- MathML layout
-   is what centres them -- so an unnumbered derivation or matrix keeps
-   `display: block math` and stays centred. Where :has() is unsupported the tag
-   simply does not reach the margin; nothing else changes. */
-math.tml-display:has(.tml-eqn) {
-  display: block !important;
-  width: 100%;
-}
-