@ponchia/ui 0.5.0 → 0.6.3

package/css/spark.css

@@ -0,0 +1,62 @@
+/* ==========================================================================
+   spark — opt-in inline datawords (word-sized microcharts).
+
+   A trend-in-a-sentence for generated reports and dense tables — the inline
+   counterpart to the scalar `ui-delta` / `ui-num` / `ui-stat`. Pure CSS, no
+   measurement, SSR-static, print-survivable. Not imported by core.css.
+
+   Boundary: the HOST normalises each point to 0..1 and sets it as `--v` on a
+   `.ui-spark__bar`; Bronto only paints the geometry. It refuses raw values and
+   min/max/scale computation. A bare spark is opaque to assistive tech, so the
+   container MUST carry a host-written `role="img"` + `aria-label` text
+   equivalent (e.g. "weekly signups, trending up"). Colour is never the only
+   channel — pair it with that label.
+   ========================================================================== */
+
+.ui-spark {
+  align-items: flex-end;
+  block-size: 1em;
+  display: inline-flex;
+  gap: 1px;
+  inline-size: max-content;
+  vertical-align: -0.15em;
+}
+
+.ui-spark__bar {
+  background: currentColor;
+  block-size: max(1px, calc(var(--v, 0) * 100%));
+  border-radius: 0.5px;
+  flex: 0 0 0.25em;
+  min-inline-size: 2px;
+}
+
+/* Emphasise / tone a single bar — the rationed accent or a status tone. The
+   meaning still has to be in the aria-label (WCAG 1.4.1). */
+.ui-spark__bar--accent {
+  background: var(--accent);
+}
+
+.ui-spark__bar--pos {
+  background: var(--success);
+}
+
+.ui-spark__bar--neg {
+  background: var(--danger);
+}
+
+/* Forced colours would force the bar backgrounds to the system surface and the
+   chart would vanish — repaint the bars in the system text colour so the shape
+   survives (the tone distinction is carried by the required aria-label). */
+@media (forced-colors: active) {
+  .ui-spark__bar {
+    background: CanvasText;
+  }
+}
+
+/* Print: the bars are currentColor fills the print economy would drop. */
+@media print {
+  .ui-spark__bar {
+    -webkit-print-color-adjust: exact;
+    print-color-adjust: exact;
+  }
+}

package/css/spotlight.css

@@ -66,7 +66,7 @@
   color: var(--text);
   display: grid;
   gap: var(--space-sm);
-  max-inline-size: 22rem;
+  max-inline-size: min(22rem, calc(100vw - 2rem));
   padding: var(--space-md);
   pointer-events: auto;
 }

package/css/table.css

@@ -35,6 +35,11 @@
   position: sticky;
   text-transform: uppercase;
   inset-block-start: 0;
+
+  /* Keep the sticky header above body cells — cheap insurance for the
+     sticky-header + pinned/positioned-column combo, where an un-z-indexed th
+     scrolls under a positioned cell. (audit C30.) */
+  z-index: 1;
 }
 
 .ui-table td {
@@ -154,8 +159,10 @@
   padding: var(--space-sm) var(--space-md);
 }
 
-/* --- Loading state: set aria-busy + .ui-table--loading on the wrap --- */
-.ui-table--loading {
+/* --- Loading state: set aria-busy + .ui-table-wrap--loading on the wrap. The
+   modifier is named for the element it goes ON (the wrap), not `.ui-table`, so
+   the BEM host matches the documented placement. (component audit C19.) --- */
+.ui-table-wrap--loading {
   opacity: 0.6;
   pointer-events: none;
 }

package/css/term.css

@@ -0,0 +1,110 @@
+/* ==========================================================================
+   term — opt-in inline glossary term + definition, and an end-of-report glossary.
+
+   The accessible upgrade of the famously touch/keyboard-broken `abbr[title]`: a
+   dotted-underline term whose definition lives in real, reachable DOM via the
+   native `[popover]` + `popovertarget` pairing, plus a `ui-glossary` `<dl>` block
+   that collects every term at the end of a document. Jargon that explains itself
+   inline and gathers into a reference — dead-centre on the explanation pillar.
+   Pure CSS over native popover, no kernel. Not imported by core.css.
+
+   Boundary: the HOST owns the wiring. The term is a `<button class="ui-term"
+   popovertarget="…">`; the definition is `<div class="ui-def" popover id="…">`.
+   That native pairing gives keyboard + touch + light-dismiss for free — no JS.
+   The glossary is a plain `<dl>`; the printed document leans on it because
+   popovers don't print (see docs/term.md). Anchor positioning is a gated
+   enhancement; without it the definition opens centred in the top layer.
+   ========================================================================== */
+
+/* The inline term marker — a real <button> so it is keyboard- and touch-
+   reachable (the abbr[title] failure). Reset to inline text, keep a dotted
+   underline as the "has a definition" cue. */
+.ui-term {
+  background: none;
+  border: 0;
+  color: inherit;
+  cursor: help;
+  font: inherit;
+  padding: 0;
+  text-decoration: underline;
+  text-decoration-color: var(--line-strong);
+  text-decoration-style: dotted;
+  text-underline-offset: 0.2em;
+}
+
+@media (hover: hover) {
+  .ui-term:hover {
+    text-decoration-color: var(--accent);
+  }
+}
+
+.ui-term:focus-visible {
+  outline: 2px solid var(--focus-ring);
+  outline-offset: 2px;
+}
+
+/* The definition — a native popover. Reset the UA popover chrome to the Bronto
+   raised-surface card. */
+.ui-def {
+  background: var(--surface-raised);
+  border: 1px solid var(--line);
+  border-radius: var(--radius-md);
+  box-shadow: var(--shadow-raised);
+  color: var(--text);
+  font-family: var(--sans);
+  font-size: var(--text-sm);
+  line-height: 1.5;
+  margin: 0;
+  max-inline-size: 22rem;
+  padding: var(--space-sm) var(--space-md);
+}
+
+/* Progressive enhancement: anchor the definition to its term where CSS anchor
+   positioning exists, so it opens beside the word and flips at the viewport
+   edge. The host sets the matching `anchor-name` on the term (see docs). Without
+   support the popover keeps its centred top-layer fallback. */
+@supports (anchor-name: --x) {
+  .ui-def {
+    inset: auto;
+    margin-block-start: 0.4rem;
+    position-area: block-end span-inline-end;
+    position-try-fallbacks: flip-block, flip-inline;
+  }
+}
+
+/* --- Glossary — the end-of-document <dl> the terms collect into. --- */
+
+.ui-glossary {
+  border-block-start: 1px solid var(--line);
+  display: grid;
+  gap: var(--space-2xs) var(--space-md);
+  grid-template-columns: minmax(6rem, max-content) 1fr;
+  margin: 0;
+  padding-block-start: var(--space-md);
+}
+
+.ui-glossary__term {
+  color: var(--text);
+  font-family: var(--mono);
+  font-size: var(--text-xs);
+  font-weight: 600;
+  letter-spacing: var(--tracking-wide);
+}
+
+.ui-glossary__def {
+  color: var(--text-dim);
+  font-size: var(--text-sm);
+  margin: 0;
+}
+
+/* Narrow viewports: stack each term over its definition. */
+@media (max-width: 32rem) {
+  .ui-glossary {
+    grid-template-columns: 1fr;
+    gap: 0.15rem var(--space-md);
+  }
+
+  .ui-glossary__def {
+    margin-block-end: var(--space-xs);
+  }
+}

package/css/textref.css

@@ -0,0 +1,63 @@
+/* ==========================================================================
+   textref — opt-in deep-link-to-the-cited-sentence provenance primitive.
+
+   A citation that jumps to the EXACT quoted text. The link's href is a URL
+   Text Fragment (`#…:~:text=`); the browser scrolls to the match and highlights
+   it for free, and Bronto owns the on-brand `::target-text` paint. The inline
+   counterpart to the static `ui-src` / `ui-citation` trust layer (sources.css),
+   which can label a source but not point inside it. Pure CSS + a host-built URL,
+   no kernel, SSR-static. Not imported by core.css.
+
+   Boundary: the HOST builds the fragment URL and sets it as the link's href.
+   The encoder is a three-line pure function (see docs/textref.md) — Bronto does
+   not ship runtime here, it owns the affordance class + the highlight paint.
+   `::target-text` is global by design: any text-fragment landing on the page
+   gets the brand highlight once this leaf is imported. On engines without Text
+   Fragments the link still navigates to the section; the highlight is additive.
+   ========================================================================== */
+
+.ui-textref {
+  --textref-highlight: var(--accent-soft);
+
+  color: var(--accent-text);
+  text-decoration: underline;
+  text-decoration-style: dotted;
+  text-underline-offset: 0.2em;
+}
+
+/* A small leading caret signals "this jumps to the quoted text", distinct from
+   a plain external link. currentColor only — no raw paint. */
+.ui-textref::before {
+  content: '\201F'; /* double high-reversed-9 quote — a quote-jump cue */
+  margin-inline-end: 0.15em;
+}
+
+@media (hover: hover) {
+  .ui-textref:hover {
+    text-decoration-style: solid;
+  }
+}
+
+.ui-textref:focus-visible {
+  outline: 2px solid var(--focus-ring);
+  outline-offset: 2px;
+}
+
+/* The browser-painted highlight on the matched fragment. Scoped to the page
+   the link lands on; the accent-soft wash is the same rationed-accent surface
+   the rest of the trust layer uses. `--textref-highlight` lets a host retune it
+   per-surface. */
+::target-text {
+  background-color: var(--textref-highlight, var(--accent-soft));
+  color: var(--text);
+}
+
+/* Forced colours: the accent wash collapses to the system surface and the match
+   would be invisible — repaint with the system selection colours so the jump
+   target still reads. */
+@media (forced-colors: active) {
+  ::target-text {
+    background-color: Highlight;
+    color: HighlightText;
+  }
+}

package/css/toc.css

@@ -0,0 +1,91 @@
+/* ==========================================================================
+   toc — opt-in scrollspy table-of-contents rail for long reports.
+
+   A sticky contents list whose entry for the section currently in view is
+   highlighted, so a reader of a long generated report always knows where they
+   are. Long-document orientation, on the generated-reports pillar. Degrades to a
+   plain anchored list with zero JS. Not imported by core.css.
+
+   Boundary: the HOST owns the section IDs and the anchor list; Bronto owns the
+   rail's classes + the active treatment. The active state keys on the standard
+   `aria-current="true"` hook. CSS alone cannot know which section is in view, so
+   the host mirrors the in-view section onto its link's `aria-current` — either
+   statically (server-rendered "current page") or with a small IntersectionObserver
+   (~15 lines, copy-paste recipe in docs/toc.md). No Bronto kernel ships for it;
+   the rail is fully useful as a static sticky list without the observer.
+   ========================================================================== */
+
+.ui-toc {
+  --toc-top: var(--space-md);
+
+  align-self: start;
+  font-family: var(--mono);
+  font-size: var(--text-xs);
+  inset-block-start: var(--toc-top);
+  letter-spacing: var(--tracking-wide);
+  position: sticky;
+}
+
+/* An optional eyebrow heading for the rail. */
+.ui-toc__title {
+  color: var(--text-dim);
+  font-size: var(--text-2xs);
+  margin-block-end: var(--space-xs);
+  text-transform: uppercase;
+}
+
+.ui-toc__list {
+  display: grid;
+  gap: 1px;
+  list-style: none;
+  margin: 0;
+  padding: 0;
+}
+
+/* Nested lists indent for sub-sections. */
+.ui-toc__list .ui-toc__list {
+  margin-inline-start: var(--space-sm);
+}
+
+.ui-toc__link {
+  border-inline-start: 2px solid var(--line);
+  color: var(--text-dim);
+  display: block;
+  padding: 0.3rem var(--space-sm);
+  text-decoration: none;
+  transition: color var(--duration-fast) var(--ease-standard);
+}
+
+/* The section in view. Keys on `aria-current` (the framework rule every other
+   nav surface here uses) so a host that sets only aria-current still lights up. */
+.ui-toc__link[aria-current]:not([aria-current='false']) {
+  border-inline-start-color: var(--accent);
+  color: var(--accent-text);
+}
+
+.ui-toc__link:focus-visible {
+  outline: 2px solid var(--focus-ring);
+  outline-offset: -2px;
+}
+
+@media (hover: hover) {
+  .ui-toc__link:hover:not([aria-current]:not([aria-current='false'])) {
+    color: var(--text);
+  }
+}
+
+/* Forced colours: the accent border + text collapse to the system surface and
+   the active entry loses its only cue — re-assert with the system highlight. */
+@media (forced-colors: active) {
+  .ui-toc__link[aria-current]:not([aria-current='false']) {
+    border-inline-start-color: Highlight;
+    color: Highlight;
+  }
+}
+
+/* Reduced motion: drop the colour transition. */
+@media (prefers-reduced-motion: reduce) {
+  .ui-toc__link {
+    transition: none;
+  }
+}

package/css/tokens.css

@@ -3,7 +3,7 @@
    Single source of truth: tokens/index.js (`cssVars`). Edit token VALUES
    there, then run `npm run tokens:css:build`. The four :root blocks below are
    emitted from cssVars — the dark palette is authored ONCE (not the former two
-   CSS blocks + the JS mirror). check-tokens.mjs gates this file against cssVars.
+   CSS blocks + the JS mirror). Drift-checked by `npm run check:fresh` (scripts/check-fresh.mjs).
    The Doto @font-face lives in fonts.css; override --display / --dot-font to
    self-host. CSS-only presets (density / contrast / OLED) are hand-authored
    below the marker — they are intentionally not part of the JS token model.
@@ -31,6 +31,8 @@
   --sans: 'Inter', 'SF Pro Text', -apple-system, BlinkMacSystemFont, 'Segoe UI', system-ui, sans-serif;
   --dot-font: 'Doto', var(--mono);
   --display: var(--dot-font);
+  --display-weight: 700;
+  --display-weight-strong: 800;
   --text-2xs: 0.68rem;
   --text-xs: 0.76rem;
   --text-sm: 0.86rem;
@@ -122,6 +124,7 @@
   --accent-ramp-end: #ffffff;
   --accent-strong: color-mix(in srgb, var(--accent) 83%, #000);
   --accent-text: var(--accent-strong);
+  --on-accent: var(--button-text);
   --accent-soft: color-mix(in srgb, var(--accent) 10%, transparent);
   --success: #2f7d4f;
   --success-soft: rgb(47, 125, 79, 0.12);
@@ -165,6 +168,7 @@
     --accent-ramp-end: #000000;
     --accent-strong: color-mix(in srgb, var(--accent) 84%, #fff);
     --accent-text: var(--accent-strong);
+    --on-accent: var(--button-text);
     --accent-soft: color-mix(in srgb, var(--accent) 14%, transparent);
     --success: #4ec27e;
     --success-soft: rgb(78, 194, 126, 0.14);
@@ -203,6 +207,7 @@
   --accent-ramp-end: #000000;
   --accent-strong: color-mix(in srgb, var(--accent) 84%, #fff);
   --accent-text: var(--accent-strong);
+  --on-accent: var(--button-text);
   --accent-soft: color-mix(in srgb, var(--accent) 14%, transparent);
   --success: #4ec27e;
   --success-soft: rgb(78, 194, 126, 0.14);
@@ -311,3 +316,46 @@
     --panel-soft: #1a1a1a;
   }
 }
+
+/* --------------------------------------------------------------------------
+   Print — force an ink-on-white document regardless of the on-screen theme.
+   The palette tokens are [data-theme]-scoped raw values, so `color-scheme`
+   alone can't flip them: re-point the neutrals to achromatic ink/paper and the
+   status/accent hues to their light-theme (print-legible) values. This lifts
+   the same remap report.css scopes to `.ui-report` up to :root, so a bare
+   .ui-card / .ui-statgrid / .ui-table (the markup an external LLM emits) also
+   prints dark-on-white instead of light-grey text or a dark panel on white.
+   Lives here, in the exempt tier-definition file, because it is a token-value
+   override (ADR-0001), not component styling. CSS-only, like the presets above.
+
+   Selector is `:root:root:root` (specificity 0,3,0), not a bare `:root`: a media
+   query adds NO specificity, so a bare `:root` (0,1,0) loses the cascade to the
+   on-screen dark palette at `:root[data-theme='dark']` (0,2,0) and the OLED
+   surface at `:root[data-theme='dark'][data-surface='oled']` (0,3,0) — i.e. a
+   dark-mode user would print a near-black `.ui-card` on white paper, the exact
+   opposite of what this block promises. Tripling `:root` matches the OLED rule's
+   specificity and wins on source order (this block is last), so the remap also
+   beats the `prefers-color-scheme: dark` blocks. Neutralise the OLED-only dark
+   surfaces (--bg / --bg-elevated / --panel-strong) too, or they'd leak through.
+   -------------------------------------------------------------------------- */
+@media print {
+  :root:root:root {
+    color-scheme: light;
+
+    --text: #111;
+    --text-soft: #2a2a2a;
+    --text-dim: #555;
+    --bg: #fff;
+    --bg-elevated: #fff;
+    --panel: #fff;
+    --panel-strong: #fff;
+    --panel-soft: #f7f7f7;
+    --line: #d9d9d9;
+    --line-strong: #b3b3b3;
+    --success: #2f7d4f;
+    --danger: #c01622;
+    --warning: #806414;
+    --info: #1f63c4;
+    --accent: #d71921;
+  }
+}

package/css/tree.css

@@ -0,0 +1,134 @@
+/* ==========================================================================
+   tree — opt-in hierarchy outline on nested native <details name> disclosures.
+
+   A depth-indented outline for hierarchies: file trees, report contents, nested
+   generated-content provenance, object graphs. Built on nested native
+   `<details>` (optionally `name` exclusive-accordion groups) so open/close,
+   keyboard toggling and animation come from the platform — this leaf is the
+   hierarchy LAYER (rails, indent, chevron), it does NOT reinvent the disclosure
+   grammar that `ui-accordion` already owns. Pure CSS, SSR-static. Not imported
+   by core.css.
+
+   Boundary: the HOST owns the nesting and the labels. A11y honesty — a native
+   `<details>` group is a disclosure group, NOT an ARIA `tree`; do not bolt on
+   `role="tree"`/`treeitem` without the roving-focus keyboard model it implies.
+   That kernel is intentionally NOT shipped here; it lands behind a real consumer
+   (see docs/tree.md). The visuals below work on the full browser floor with zero
+   JS.
+   ========================================================================== */
+
+.ui-tree {
+  color: var(--text);
+  font-family: var(--mono);
+  font-size: var(--text-sm);
+  line-height: 1.5;
+}
+
+/* A branch is a <details>; a leaf is a plain row with no disclosure. Both are
+   rows in the outline. */
+.ui-tree__branch,
+.ui-tree__leaf {
+  display: block;
+}
+
+/* Nested rows indent and carry a hairline guide rail back to their parent. */
+.ui-tree__branch .ui-tree__branch,
+.ui-tree__branch .ui-tree__leaf {
+  border-inline-start: 1px solid var(--line);
+  margin-inline-start: 0.5rem;
+  padding-inline-start: var(--space-sm);
+}
+
+/* The summary is the clickable branch row; reset the native marker, lay it out
+   as label + twist. */
+.ui-tree__summary {
+  align-items: center;
+  cursor: pointer;
+  display: flex;
+  gap: var(--space-2xs);
+  list-style: none;
+  padding-block: var(--space-2xs);
+}
+
+.ui-tree__summary::-webkit-details-marker {
+  display: none;
+}
+
+/* Twist chevron — a currentColor caret that rotates open. */
+.ui-tree__summary::before {
+  block-size: 0.4rem;
+  border-block-end: 1.5px solid var(--text-dim);
+  border-inline-end: 1.5px solid var(--text-dim);
+  content: '';
+  flex: 0 0 auto;
+  inline-size: 0.4rem;
+  transform: rotate(-45deg);
+  transition: transform var(--duration-fast) var(--ease-spring);
+}
+
+.ui-tree__branch[open] > .ui-tree__summary::before {
+  border-color: var(--accent);
+  transform: rotate(45deg);
+}
+
+.ui-tree__branch[open] > .ui-tree__summary {
+  color: var(--accent-text);
+}
+
+/* A leaf has no chevron; align its label with branch labels via a spacer the
+   width of the chevron + gap. */
+.ui-tree__leaf {
+  align-items: center;
+  display: flex;
+  gap: var(--space-2xs);
+  padding-block: var(--space-2xs);
+}
+
+.ui-tree__leaf::before {
+  content: '';
+  flex: 0 0 auto;
+  inline-size: 0.4rem;
+}
+
+.ui-tree__label {
+  min-inline-size: 0;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+
+/* Auto-height open/close, gated exactly like ui-accordion (Chrome 131+/Safari
+   18.4+; Firefox snaps). Strict progressive enhancement + reduced-motion. */
+@supports selector(::details-content) {
+  @media (prefers-reduced-motion: no-preference) {
+    .ui-tree {
+      interpolate-size: allow-keywords;
+    }
+
+    .ui-tree__branch::details-content {
+      block-size: 0;
+      overflow: hidden;
+      transition:
+        block-size var(--duration-base) var(--ease-out),
+        content-visibility var(--duration-base) allow-discrete;
+    }
+
+    .ui-tree__branch[open]::details-content {
+      block-size: auto;
+    }
+  }
+}
+
+/* Reduced motion: no chevron spin. */
+@media (prefers-reduced-motion: reduce) {
+  .ui-tree__summary::before {
+    transition: none;
+  }
+}
+
+/* Forced colours: keep the open branch distinguishable when accent flattens. */
+@media (forced-colors: active) {
+  .ui-tree__branch[open] > .ui-tree__summary::before {
+    border-color: Highlight;
+  }
+}

package/css/workbench.css

@@ -19,7 +19,7 @@
   padding: var(--space-md);
 }
 
-.ui-inspector__header {
+.ui-inspector__head {
   align-items: baseline;
   border-block-end: 1px solid var(--line);
   display: flex;