@adia-ai/web-components 0.8.45 → 0.8.46

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog — @adia-ai/web-components
 
+## [0.8.46] — 2026-08-22
+
+
+### Maintenance
+- **`components/` touched in this release window** (31 file(s), e.g. `card/card.css`) — carried by the entries above.
+- **`dist/` bundles rebuilt** in this cut's window (4 file(s)) — regenerated from the source changes described above, not independent edits.
+- **`patterns/` touched in this release window** (6 file(s), e.g. `chart-in-card/chart-in-card.examples.html`) — carried by the entries above.
+- **`styles/` touched in this release window** (1 file(s), e.g. `styles/components.css`) — carried by the entries above.
+
 ## [0.8.45] — 2026-08-20
 
 ### Added

package/components/card/card.css

@@ -427,29 +427,18 @@
     border-radius: 0;
   }
 
-  /* Guide/value/legend safety inset (gh#1095) — [bleed]'s zero-inset is
-     only collision-free for the bare-marks case: a sparkline (its
-     renderer never emits axis ticks, gridlines, value labels, or a
-     legend — chart.class.js #renderSparkline), or any other chart-ui
-     type with BOTH [no-grid] and [no-values] set (the author opted
-     out of every text element). A chart that still draws guides or
-     value text — or is paired with a <chart-legend-ui> — needs
-     clearance from the card's frame, or that text collides with the
-     card edge and clips under the corner-rounded `overflow: hidden`
-     (:scope, top of file). Restore the card's own inset automatically
-     for those cases rather than relying on every author to remember —
-     the :has() selector's specificity already beats the plain [bleed]
-     reset above regardless of source order. Pairing a legend with a
-     genuinely full-bleed chart still works — put the legend in its OWN
-     section below, wired via chart-legend-ui[for="<chart id>"], which
-     never enters this selector (see chart-in-card.examples.html's
-     "Full-bleed chart + legend band" example). */
-  & > section[bleed]:has(> chart-ui:not([type="sparkline"]):not([no-grid])),
-  & > section[bleed]:has(> chart-ui:not([type="sparkline"]):not([no-values])),
-  & > section[bleed]:has(> chart-legend-ui) {
-    margin: var(--card-inset);
-    padding: 0;
-  }
+  /* [bleed] is unconditionally author-controlled (gh#1801, operator ruling
+     2026-08-20 — supersedes gh#1095's mechanical auto-restore, removed
+     here). A full-bleed chart-ui that still draws gridlines, value labels,
+     or is paired with a <chart-legend-ui> can clip that text under the
+     card's corner-rounded `overflow: hidden` (:scope, top of file) — this
+     is now the AUTHOR's responsibility to avoid, not something this
+     stylesheet silently repairs by re-inserting an inset the author
+     explicitly opted out of. card.yaml's `bleed` prop docs and
+     chart-in-card.examples.html both carry the clipping-hazard note and
+     the recommended mitigation: render value/guide text as overlay chips
+     INSET within the plot area (never hanging outside it) rather than
+     relying on card margin for clearance. */
 
   /* ═══════ Footer ═══════
      Margin-based inset. Flex row for actions.

package/components/card/card.yaml

@@ -161,6 +161,17 @@ a2ui:
     row 2 without needing slot="description".
   - Multiple <section> siblings are allowed and stack vertically. [bleed] on a section removes its margin for edge-to-edge
     content (tables, charts); [padding] adds a canvas-scrim background for hero regions.
+  - >-
+    [bleed] is unconditionally author-controlled — card.css never restores
+    the section's inset on your behalf (gh#1801, operator ruling
+    2026-08-20; supersedes gh#1095's removed auto-restore guard). A
+    full-bleed <chart-ui> that still draws gridlines or value labels, or is
+    paired with a <chart-legend-ui>, can clip that text under the card's
+    own corner-rounded overflow:hidden — keeping it clear of the card
+    frame is YOUR responsibility as the author, e.g. by rendering value/
+    guide text as overlay chips INSET within the plot area rather than
+    hanging outside it, or by placing a <chart-legend-ui> in its own
+    non-bled section. See chart-in-card.examples.html for the pattern.
   - >-
     When neither [raw] nor [frameless] is present, a <table-ui> placed
     directly inside a <section bleed> automatically renders chromeless

package/components/chart/chart.a2ui.json

@@ -62,7 +62,7 @@
       "default": null
     },
     "data": {
-      "description": "JS property (set programmatically — `el.data = [...]`). An array of plain objects; each object's keys are named by the `x` and `y` attributes — e.g. `<chart-ui x=\"month\" y=\"revenue\">` consumes `[{month:'Jan', revenue:3200}, {month:'Feb', revenue:4100}]`. The Chart.js `{labels, datasets}` envelope is NOT chart-ui's API — passing it (or any non-array value) renders an empty chart. May also be supplied declaratively as a JSON-array `data=\"[…]\"` attribute, hydrated once at connect. Custom accessor on the element class, not a reflected attribute.",
+      "description": "JS property (set programmatically — `el.data = [...]`). An array of plain objects; each object's keys are named by the `x` and `y` attributes — e.g. `<chart-ui x=\"month\" y=\"revenue\">` consumes `[{month:'Jan', revenue:3200}, {month:'Feb', revenue:4100}]`. The Chart.js `{labels, datasets}` envelope is NOT chart-ui's API — passing it (or any non-array value) renders an empty chart. May also be supplied declaratively as a JSON-array `data=\"[…]\"` attribute, hydrated once at connect. Custom accessor on the element class, not a reflected attribute. A datum object carrying a truthy `provisional` key (ADR-0081) renders that period's type-specific incomplete-period treatment (hollow/dashed bar, dashed line + faded area, hollow ring dot) on cartesian types; a no-op on radial/part-to-whole types and sparkline (gh#1690's N/A list). Provisional state is per-datum data-shape, not a chart-ui attribute — see ADR-0081 §3.",
       "$ref": "common_types.json#/$defs/DynamicObjectList"
     },
     "dots": {
@@ -87,6 +87,16 @@
       ],
       "default": "abbr"
     },
+    "labels": {
+      "description": "Chart 2.0 axis-label mode (ADR-0081). Unset (default, \"\") always resolves to `outside` — today's pre-2.0 outside-the-plot axis labels, byte-for-byte unchanged. Set explicitly to `chip` to opt into the pill-treated overlay labels inset within the plot box (never hanging outside it) — the resolved value reflects onto the host as `data-labels-resolved=\"chip\"|\"outside\"`. Deliberately explicit-opt-in rather than auto-detected from full-bleed ancestry (`section[bleed]`/ `card-ui[padding=\"none\"]`): an earlier draft auto-activated chip mode on any full-bleed composition, which silently changed the rendering of every ALREADY-SHIPPED full-bleed chart the moment it shipped — this build's own 60-fixture Charts visual-eval floor caught it (2 `comp-chart-in-card-n-*` regressions). `chart-in-card` compositions opt in explicitly once their own examples are updated (gh#1805).",
+      "type": "string",
+      "enum": [
+        "",
+        "chip",
+        "outside"
+      ],
+      "default": ""
+    },
     "loading": {
       "description": "Show a skeleton placeholder instead of the chart body. Set to true while data is being fetched; clear once data arrives. Preserves the element's aspect-ratio dimensions so the skeleton occupies the same space the chart will fill. Parity with stat-ui[loading] and table-ui[loading] (§FB-12, v0.6.27).",
       "type": "boolean",
@@ -137,6 +147,11 @@
       "type": "number",
       "default": 0.4
     },
+    "today": {
+      "description": "Names the datum whose x-axis value marks \"today\" (ADR-0081). Unset (default, \"\") renders no marker — additive. Compared against each datum's x-key value via a loose string comparison (`String(datum[x]) === String(today)`), so category axes (\"month\", \"region\") work the same as literal date strings; chart-ui never auto-derives today from the clock. Renders a baseline dot + a short band tick (REQ-F-008) on cartesian types (bar, line, area, scatter, multi-line, stacked-bar, grouped-bar, composed); a no-op on every radial/part-to-whole type and on sparkline (gh#1690's N/A list). Fallback (not the primary mechanism): a datum already carrying a truthy `today` key is treated as an equivalent marker even with this attribute unset.",
+      "type": "string",
+      "default": ""
+    },
     "x": {
       "description": "Data key for x-axis (category) values",
       "type": "string",