@uniweb/kit 0.10.4 → 0.10.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/kit",
-  "version": "0.10.4",
+  "version": "0.10.6",
   "description": "Standard component library for Uniweb foundations",
   "type": "module",
   "exports": {
@@ -42,8 +42,8 @@
     "fuse.js": "^7.0.0",
     "shiki": "^3.0.0",
     "tailwind-merge": "^3.6.0",
-    "@uniweb/semantic-parser": "1.2.0",
     "@uniweb/core": "0.8.0",
+    "@uniweb/semantic-parser": "1.2.0",
     "@uniweb/scene": "0.1.2"
   },
   "peerDependencies": {

package/src/callout-tokens.css

@@ -6,10 +6,16 @@
  *   @import "@uniweb/kit/callout-tokens.css";
  *
  * OPT-IN, and that is the point. kit's render engine emits a concept block as
- * a plain bordered box carrying `data-concept="<tag>"` and decides nothing
- * about how it looks, because what a callout looks like is a foundation's
- * design. This file is the answer for the foundations that do not want to make
- * that decision — the common look, themed, in one import.
+ * a bare `<div data-concept="<tag>">` — no classes, no box, nothing decided,
+ * because what a callout looks like is a foundation's design. Without an
+ * import like this one a concept block is unstyled and reads as plain prose,
+ * which is the correct default for a tag nobody has designed for yet.
+ *
+ * So this file supplies the WHOLE look, not just the colours: the frame, the
+ * padding and the spacing as well as the tint. An earlier version set only
+ * `border-color` and `background-color`, which on a bare div with no border
+ * width and no padding rendered as a tinted band running edge to edge — the
+ * right hue and nothing else.
  *
  * ── Why five names may live here when they may not live in a component ──
  *
@@ -38,13 +44,25 @@
  *
  * ── Tags with no rule ──
  *
- * A concept block whose tag is not one of the five keeps the engine's plain
- * bordered box. That is deliberate: an unrecognized concept should look
+ * A concept block whose tag is not one of the five gets the neutral frame
+ * above and no tint. That is deliberate: an unrecognized concept should look
  * unremarkable rather than borrow a severity it was never given.
  */
 
+/*
+ * The frame. `--border` is the neutral fallback, so a tag with no rule of its
+ * own below still reads as a deliberate box rather than as loose prose.
+ *
+ * The margin is stated here because the engine emits an unclassed div: a prose
+ * container styles the elements it knows, and this is not one of them, so
+ * without this a callout would sit flush against the paragraph above it and
+ * against the next callout.
+ */
 [data-concept] {
+  border: 1px solid var(--border);
   border-radius: var(--radius, 0.5rem);
+  padding: 1rem 1.25rem;
+  margin: 1.5rem 0;
 }
 
 [data-concept="note"],

package/src/prose-tokens.css

@@ -101,3 +101,31 @@
 .prose :is(h1, h2, h3, h4) {
   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; }