use-wc 1.0.0-pre.78 → 1.0.0-pre.79

package/custom-elements.json

@@ -89,76 +89,6 @@
         }
       ]
     },
-    {
-      "kind": "javascript-module",
-      "path": "src/elements/use-avatar/use-avatar.ts",
-      "declarations": [
-        {
-          "kind": "class",
-          "description": "`use-avatar` renders a small, fixed-size, clipped container for a person or entity's\nlikeness. Slot in an `<img>` (or `<picture>`) for a photo, an inline `<svg>` for a\ngenerated or stylized mark, or arbitrary markup (a `<div>` of initials, a calendar badge);\nwhatever is slotted is centered and clipped to the avatar's shape. With nothing slotted,\n`use-avatar` falls back to initials derived from the `name` attribute.\n\n```html\n<use-avatar><img src=\"ada.jpg\" alt=\"\" /></use-avatar>\n<use-avatar name=\"Riley Quinn\"></use-avatar>\n<use-avatar><svg viewBox=\"0 0 32 32\">…</svg></use-avatar>\n```\n\nSize it with plain CSS — `inline-size` for the size and `aspect-ratio` for the proportions —\nfrom a stylesheet, a style attribute, or the design system's theme layer. The element takes no\ncustom properties of its own: it is a query container, so the initials scale from whatever box\nit ends up with. A non-square `aspect-ratio` suits a wide thumbnail or poster.\n\nThe element clips its content but gives it no shape of its own — that is the theme's, through\nthe affordance classes it defines: `.circle` (the themed default), `.square`, `.squircle` in\n`theme/avatar.css`. A circle only reads right at a `1` ratio, so a wide avatar wants one of the\nothers.\n\nThe element takes no ARIA role of its own. A slotted `<img>` carries its own `alt`, and the\ninitials fallback is plain text in the accessibility tree — an avatar is decorative beside a\nname far more often than it is the name itself, so labelling it here would mean announcing\nthat name twice.",
-          "name": "UseAvatar",
-          "cssParts": [
-            {
-              "description": "The span that renders the `name` fallback.",
-              "name": "initials"
-            }
-          ],
-          "slots": [
-            {
-              "description": "The avatar's content: an `<img>`/`<picture>`, an `<svg>`, or arbitrary markup. Left empty, the `name` attribute's initials are shown instead, as the slot's own fallback. A photo fills the frame and crops; anything else keeps its own size, capped at the frame. Give an `<svg>` a `width`/`height` — without one it defaults to filling the box, and a rounded shape will clip its corners.",
-              "name": ""
-            }
-          ],
-          "members": [
-            {
-              "kind": "field",
-              "name": "name",
-              "type": {
-                "text": "string"
-              },
-              "default": "\"\"",
-              "attribute": "name",
-              "reflects": true
-            }
-          ],
-          "attributes": [
-            {
-              "description": "The full name, used for the initials fallback (first + last whitespace-separated token, uppercased) when the slot is empty.",
-              "name": "name",
-              "type": {
-                "text": "string"
-              },
-              "default": "\"\"",
-              "fieldName": "name"
-            }
-          ],
-          "superclass": {
-            "name": "LitElement",
-            "package": "lit"
-          },
-          "tagName": "use-avatar",
-          "customElement": true
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "UseAvatar",
-          "declaration": {
-            "name": "UseAvatar",
-            "module": "src/elements/use-avatar/use-avatar.ts"
-          }
-        },
-        {
-          "kind": "custom-element-definition",
-          "name": "use-avatar",
-          "declaration": {
-            "name": "UseAvatar",
-            "module": "src/elements/use-avatar/use-avatar.ts"
-          }
-        }
-      ]
-    },
     {
       "kind": "javascript-module",
       "path": "src/elements/use-badge/use-badge.ts",
@@ -302,6 +232,76 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/elements/use-avatar/use-avatar.ts",
+      "declarations": [
+        {
+          "kind": "class",
+          "description": "`use-avatar` renders a small, fixed-size, clipped container for a person or entity's\nlikeness. Slot in an `<img>` (or `<picture>`) for a photo, an inline `<svg>` for a\ngenerated or stylized mark, or arbitrary markup (a `<div>` of initials, a calendar badge);\nwhatever is slotted is centered and clipped to the avatar's shape. With nothing slotted,\n`use-avatar` falls back to initials derived from the `name` attribute.\n\n```html\n<use-avatar><img src=\"ada.jpg\" alt=\"\" /></use-avatar>\n<use-avatar name=\"Riley Quinn\"></use-avatar>\n<use-avatar><svg viewBox=\"0 0 32 32\">…</svg></use-avatar>\n```\n\nSize it with plain CSS — `inline-size` for the size and `aspect-ratio` for the proportions —\nfrom a stylesheet, a style attribute, or the design system's theme layer. The element takes no\ncustom properties of its own: it is a query container, so the initials scale from whatever box\nit ends up with. A non-square `aspect-ratio` suits a wide thumbnail or poster.\n\nThe element clips its content but gives it no shape of its own — that is the theme's, through\nthe affordance classes it defines: `.circle` (the themed default), `.square`, `.squircle` in\n`theme/avatar.css`. A circle only reads right at a `1` ratio, so a wide avatar wants one of the\nothers.\n\nThe element takes no ARIA role of its own. A slotted `<img>` carries its own `alt`, and the\ninitials fallback is plain text in the accessibility tree — an avatar is decorative beside a\nname far more often than it is the name itself, so labelling it here would mean announcing\nthat name twice.",
+          "name": "UseAvatar",
+          "cssParts": [
+            {
+              "description": "The span that renders the `name` fallback.",
+              "name": "initials"
+            }
+          ],
+          "slots": [
+            {
+              "description": "The avatar's content: an `<img>`/`<picture>`, an `<svg>`, or arbitrary markup. Left empty, the `name` attribute's initials are shown instead, as the slot's own fallback. A photo fills the frame and crops; anything else keeps its own size, capped at the frame. Give an `<svg>` a `width`/`height` — without one it defaults to filling the box, and a rounded shape will clip its corners.",
+              "name": ""
+            }
+          ],
+          "members": [
+            {
+              "kind": "field",
+              "name": "name",
+              "type": {
+                "text": "string"
+              },
+              "default": "\"\"",
+              "attribute": "name",
+              "reflects": true
+            }
+          ],
+          "attributes": [
+            {
+              "description": "The full name, used for the initials fallback (first + last whitespace-separated token, uppercased) when the slot is empty.",
+              "name": "name",
+              "type": {
+                "text": "string"
+              },
+              "default": "\"\"",
+              "fieldName": "name"
+            }
+          ],
+          "superclass": {
+            "name": "LitElement",
+            "package": "lit"
+          },
+          "tagName": "use-avatar",
+          "customElement": true
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "UseAvatar",
+          "declaration": {
+            "name": "UseAvatar",
+            "module": "src/elements/use-avatar/use-avatar.ts"
+          }
+        },
+        {
+          "kind": "custom-element-definition",
+          "name": "use-avatar",
+          "declaration": {
+            "name": "UseAvatar",
+            "module": "src/elements/use-avatar/use-avatar.ts"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/elements/use-calendar-base/use-calendar-base.ts",
@@ -837,6 +837,48 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/elements/use-control-set/use-control-set.ts",
+      "declarations": [
+        {
+          "kind": "class",
+          "description": "Groups adjacent controls — buttons and text-style inputs alike — into one visual unit: shared\nborders between touching children, rounded corners only on the two outer ends, and a hovered\nor focused child's border lifted above its neighbors so the whole border reads clearly.\n\n`use-control-set` renders no shadow DOM and no template of its own — it exists only as a\ndedicated tag for `theme/control-set.css` to style, the same way `use-layout` is a bare\nprimitive rather than a specific look. A classic split button is a text button followed by an\nicon-only trigger for a `use-menu`:\n\n```html\n<use-control-set>\n  <button type=\"button\">Save</button>\n  <button type=\"button\" popovertarget=\"save-options\" aria-label=\"More save options\">\n    <use-caret></use-caret>\n  </button>\n</use-control-set>\n<use-menu id=\"save-options\" aria-label=\"More save options\">\n  <button role=\"menuitem\">Save as&hellip;</button>\n</use-menu>\n```\n\nA search box with an attached submit button follows the same shape, mixing a text input with a\nbutton:\n\n```html\n<use-control-set>\n  <input type=\"search\" placeholder=\"Search\" />\n  <button type=\"submit\">Go</button>\n</use-control-set>\n```\n\nA child is a `<button>`, anything wearing `.appearance-button`, an `<input>` (other than a\ncheckbox/radio/range/file), a `<select>`, a `<textarea>`, or anything wearing\n`.appearance-input` — see `theme/control-set.css` for exactly which selectors read which\nradius/border tokens.\n\nHow the touching sides render is themeable rather than fixed: `--usewc-layout-control-set-gap`\n(default: a negative overlap equal to the child's own border, for a seamless merged line) and\n`--usewc-effect-control-set-border-radius-sequential` (default: `0`, for square touching\ncorners) can both be overridden — a positive gap and a small radius reads as a looser, softer\nset instead of a fused one.",
+          "name": "UseControlSet",
+          "slots": [
+            {
+              "description": "The grouped controls.",
+              "name": ""
+            }
+          ],
+          "members": [],
+          "superclass": {
+            "name": "LitElement",
+            "package": "lit"
+          },
+          "tagName": "use-control-set",
+          "customElement": true
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "UseControlSet",
+          "declaration": {
+            "name": "UseControlSet",
+            "module": "src/elements/use-control-set/use-control-set.ts"
+          }
+        },
+        {
+          "kind": "custom-element-definition",
+          "name": "use-control-set",
+          "declaration": {
+            "name": "UseControlSet",
+            "module": "src/elements/use-control-set/use-control-set.ts"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/elements/use-date-input/use-date-input.ts",

package/dist/design-system.css

@@ -506,6 +506,38 @@
       }
     }
 
+    &:not([type="file"]):has(> use-caret:empty, > svg:only-child) {
+      /*
+       * :empty on use-caret checks for no text nodes at all, not just "no element siblings" —
+       * that's what makes it safe to key square sizing off of: a caret with a label
+       * (<use-caret>Menu</use-caret>) never matches. svg:only-child has no such guarantee (a text
+       * node beside the svg still passes), so icon-only buttons without a use-caret wrapper should
+       * carry no other content.
+       */
+      /* aspect-ratio doesn't reliably resolve here — as a flex item inside use-control-set (or
+       any flex/grid ancestor), its hypothetical main size can be computed from content before the
+       cross size the ratio needs is definite, leaving width and height mismatched. Computing the
+       square's side explicitly, from the same ingredients that already determine a normal
+       button's natural height, is a real square by construction — and it keeps this button the
+       same height as a text sibling in the same use-control-set, rather than shrinking to 1lh. */
+      padding-inline: 0;
+      --usewc-layout-button-icon-only-size: calc(
+        var(--usewc-layout-button-line-height) +
+          (var(--usewc-layout-button-padding-block) + var(--usewc-layout-button-border)) * 2
+      );
+      inline-size: var(--usewc-layout-button-icon-only-size);
+      block-size: var(--usewc-layout-button-icon-only-size);
+
+      /* The default caret glyph is a 50% tint of currentColor for a caret beside a label — as
+       the button's only content, it reads better at full strength, so this overrides the token
+       rather than the color directly; it inherits into use-caret's shadow tree from here. */
+      --usewc-effect-dropdown-trigger-icon-background-color: currentColor;
+
+      use-theme-escape & {
+        all: revert-layer;
+      }
+    }
+
     &::file-selector-button {
       margin-inline-end: var(--usewc-layout-input-gap-inline);
     }
@@ -652,6 +684,69 @@
   }
 }
 
+/* `use-control-set` groups adjacent controls into one visual unit — buttons, text-style inputs,
+   and anything else, custom elements included, that renders its own themed border-radius earlier
+   in the cascade. Rather than enumerating every control family (which would leave out any custom
+   input component this file doesn't know about) and reading each one's own radius token by name
+   (which would leave out any component using a token this file has never heard of), the rule
+   below matches every direct child indiscriminately and reads back each one's *already-computed*
+   radius with `revert-layer` — the value it would have had from an earlier layer if this layer
+   didn't exist. That's the exact radius button.css, input.css, select.css, or a future custom
+   element's own theme file already gave it, with no name to keep in sync here.
+
+   This still needs `[type="file"]` and `.appearance-native` excluded: a file input gets a
+   completely different treatment in input.css, and `.appearance-native` is this system's opt-out
+   of theming altogether — neither should be squared off as if it were a themed control.
+
+   This lives in its own layer, imported after `input.css`, `button.css`, and every other control
+   family's stylesheet in `theme.css`, specifically so the touching-side overrides below can use a
+   plain, ordinary-specificity selector: cascade layers are compared before specificity, so a
+   later layer wins over an earlier one regardless of how each rule's own selector weighs in — no
+   need to fight any control's own selector list for a specificity win the way an override nested
+   inside one of them would. `revert-layer` itself also depends on this layer ordering — it rolls
+   back to the *previous* layer's value, so it only reaches button.css/input.css's own radius
+   because this file's layer comes after theirs.
+
+   The container only sets `display` and `isolation` — `isolation: isolate` scopes the hover
+   `z-index` below to just this set's own children, so a lifted border can't bleed into stacking
+   elsewhere on the page. Touching sides merge by default (`--usewc-layout-control-set-gap` is a
+   negative overlap equal to the button border, and `--usewc-effect-control-set-border-radius-sequential`
+   is `0`), both themeable — see `tokens/semantic.css` for the defaults. The button border is the
+   one hardcoded assumption left: it and the input border round to the same rendered pixel at
+   ordinary font sizes even though one is `rem`-based and the other `em`-based, so a single gap
+   default reads as seamless for any mix of children without needing a per-child value. */
+@layer use-theme.control-set {
+  use-control-set {
+    display: inline-flex;
+    isolation: isolate;
+  }
+
+  use-control-set > *:not([type="file"], .appearance-native) {
+    margin-inline-start: var(--usewc-layout-control-set-gap);
+    border-radius: var(--usewc-effect-control-set-border-radius-sequential);
+
+    /* first-child and last-child both apply to a lone child, restoring its full radius. */
+    &:first-child {
+      margin-inline-start: 0;
+      border-start-start-radius: revert-layer;
+      border-end-start-radius: revert-layer;
+    }
+
+    &:last-child {
+      border-start-end-radius: revert-layer;
+      border-end-end-radius: revert-layer;
+    }
+
+    &:where(:hover, :focus-visible, :focus-within) {
+      z-index: 1;
+    }
+
+    use-theme-escape & {
+      all: revert-layer;
+    }
+  }
+}
+
 @layer use-theme.code {
   code,
   .appearance-code {

package/dist/docs/use-control-set.md

@@ -0,0 +1,49 @@
+# `use-control-set`
+
+Groups adjacent controls — buttons and text-style inputs alike — into one visual unit: shared
+borders between touching children, rounded corners only on the two outer ends, and a hovered
+or focused child's border lifted above its neighbors so the whole border reads clearly.
+
+`use-control-set` renders no shadow DOM and no template of its own — it exists only as a
+dedicated tag for `theme/control-set.css` to style, the same way `use-layout` is a bare
+primitive rather than a specific look. A classic split button is a text button followed by an
+icon-only trigger for a `use-menu`:
+
+```html
+<use-control-set>
+  <button type="button">Save</button>
+  <button type="button" popovertarget="save-options" aria-label="More save options">
+    <use-caret></use-caret>
+  </button>
+</use-control-set>
+<use-menu id="save-options" aria-label="More save options">
+  <button role="menuitem">Save as&hellip;</button>
+</use-menu>
+```
+
+A search box with an attached submit button follows the same shape, mixing a text input with a
+button:
+
+```html
+<use-control-set>
+  <input type="search" placeholder="Search" />
+  <button type="submit">Go</button>
+</use-control-set>
+```
+
+A child is a `<button>`, anything wearing `.appearance-button`, an `<input>` (other than a
+checkbox/radio/range/file), a `<select>`, a `<textarea>`, or anything wearing
+`.appearance-input` — see `theme/control-set.css` for exactly which selectors read which
+radius/border tokens.
+
+How the touching sides render is themeable rather than fixed: `--usewc-layout-control-set-gap`
+(default: a negative overlap equal to the child's own border, for a seamless merged line) and
+`--usewc-effect-control-set-border-radius-sequential` (default: `0`, for square touching
+corners) can both be overridden — a positive gap and a small radius reads as a looser, softer
+set instead of a fused one.
+
+## Slots
+
+| Name | Description |
+| --- | --- |
+| `` | The grouped controls. |

package/dist/tokens.css

@@ -553,6 +553,15 @@
   --usewc-font-button-extra-large-size: var(--usewc-font-size-20);
   --usewc-layout-button-extra-large-line-height: var(--usewc-line-height-32);
 
+  /* Control set — `use-control-set` (see `theme/control-set.css`), grouping adjacent buttons
+     and/or text-style inputs into one visual unit. The gap is a negative overlap equal to the
+     button border by default, so touching borders merge into one seamless line; a theme can
+     widen it to a real positive gap instead. `-sequential` names the radius the same way
+     `grid.css`'s adjacent selected-row band does — the edge a child shares with its neighbor, `0`
+     by default (square) but able to take a small nonzero value instead of a hard corner. */
+  --usewc-layout-control-set-gap: calc(-1 * var(--usewc-layout-button-border));
+  --usewc-effect-control-set-border-radius-sequential: 0;
+
   /* Badge — a rose fill with white text: a warm pink-red that stays clear of the danger red's
      hue and the primary blue, so a count badge doesn't read as an error or a button. The fill
      is a fixed shade in both themes (like the primary/danger fills), so no dark-mode override

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "use-wc",
-  "version": "1.0.0-pre.78",
+  "version": "1.0.0-pre.79",
   "private": false,
   "homepage": "https://usewc.com",
   "bugs": "https://github.com/dang-rabbits/use-wc/issues",

package/vscode.html-custom-data.json

@@ -19,18 +19,6 @@
       ],
       "references": []
     },
-    {
-      "name": "use-avatar",
-      "description": "`use-avatar` renders a small, fixed-size, clipped container for a person or entity's\nlikeness. Slot in an `<img>` (or `<picture>`) for a photo, an inline `<svg>` for a\ngenerated or stylized mark, or arbitrary markup (a `<div>` of initials, a calendar badge);\nwhatever is slotted is centered and clipped to the avatar's shape. With nothing slotted,\n`use-avatar` falls back to initials derived from the `name` attribute.\n\n```html\n<use-avatar><img src=\"ada.jpg\" alt=\"\" /></use-avatar>\n<use-avatar name=\"Riley Quinn\"></use-avatar>\n<use-avatar><svg viewBox=\"0 0 32 32\">…</svg></use-avatar>\n```\n\nSize it with plain CSS — `inline-size` for the size and `aspect-ratio` for the proportions —\nfrom a stylesheet, a style attribute, or the design system's theme layer. The element takes no\ncustom properties of its own: it is a query container, so the initials scale from whatever box\nit ends up with. A non-square `aspect-ratio` suits a wide thumbnail or poster.\n\nThe element clips its content but gives it no shape of its own — that is the theme's, through\nthe affordance classes it defines: `.circle` (the themed default), `.square`, `.squircle` in\n`theme/avatar.css`. A circle only reads right at a `1` ratio, so a wide avatar wants one of the\nothers.\n\nThe element takes no ARIA role of its own. A slotted `<img>` carries its own `alt`, and the\ninitials fallback is plain text in the accessibility tree — an avatar is decorative beside a\nname far more often than it is the name itself, so labelling it here would mean announcing\nthat name twice.\n---\n\n\n### **Slots:**\n - _default_ - The avatar's content: an `<img>`/`<picture>`, an `<svg>`, or arbitrary markup. Left empty, the `name` attribute's initials are shown instead, as the slot's own fallback. A photo fills the frame and crops; anything else keeps its own size, capped at the frame. Give an `<svg>` a `width`/`height` — without one it defaults to filling the box, and a rounded shape will clip its corners.\n\n### **CSS Parts:**\n - **initials** - The span that renders the `name` fallback.",
-      "attributes": [
-        {
-          "name": "name",
-          "description": "The full name, used for the initials fallback (first + last whitespace-separated token, uppercased) when the slot is empty.",
-          "values": []
-        }
-      ],
-      "references": []
-    },
     {
       "name": "use-badge",
       "description": "`use-badge` renders a small indicator anchored to another element's corner, using\n[CSS anchor positioning](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_anchor_positioning)\ninstead of the classic `position: absolute` + negative-offset trick. This lets the badge live\nanywhere in the DOM rather than being a child of the element it decorates. A badge's shape,\ncolor, and positioning ship built in — reading from the design system's tokens when\n`tokens.css` is loaded, and falling back to sensible defaults otherwise — so no theme is\nrequired to get a working, visible badge.\n\nPoint a badge at its target with the `anchortarget` attribute, set to the target's `id`\n(named to avoid colliding with the `anchor` content attribute HTML is gaining natively):\n\n```html\n<button type=\"button\" id=\"inbox\">Inbox</button>\n<use-badge anchortarget=\"inbox\">99+</use-badge>\n```\n\nThe badge and its anchor must live in the same DOM tree — a badge cannot reach an anchor\ninside another component's shadow root, and an anchor's `anchor-name` set inside a shadow\ntree's stylesheet is not visible here. No positioned ancestor or shared containing block is\nrequired: anchor positioning resolves the badge's location straight from the anchor's own\ngeometry, so the badge can sit anywhere else in the DOM tree.\n\nWithout a resolved anchor — `anchortarget` unset, pointing at a missing id, or `anchorElement`\nnever assigned — the badge has no `:state(anchored)` and renders as a plain inline chip in\nnormal document flow, still using the same color/shape styling.\n\nSome components render their host as `display: contents`, which has no box of its own for CSS\nanchor positioning to resolve against. If the anchor computes a non-empty `--usewc-anchor-name`\ncustom property, the badge uses that dashed-ident as its `position-anchor` directly instead of\ngenerating and writing its own onto the anchor — letting a component publish the name of a\nreal, box-generating part of itself (already established for its own purposes) for badges to\ntarget instead of its host, even though that part lives inside the component's own shadow root.\nThis mechanism is shared with `use-menu`/`use-anchored` via `AnchorController`; components\nwithout a `display: contents` host don't need to publish anything.\n\n**Known Firefox limitation:** anchoring across a shadow root boundary this way — the case\n`--usewc-anchor-name` exists for — is mispositioned in Firefox as of this writing. Verified\ndirectly: `anchor()`'s logical `start`/`end` keywords resolve backwards on both axes\nspecifically for a cross-shadow-root anchor reference, in Firefox only — the same anchor()\ncalls resolve correctly for a same-tree anchor in Firefox, and cross-shadow anchoring resolves\ncorrectly in Chromium and Safari. A badge anchored to a plain element (button, input, anything\nthat isn't itself relying on this escape hatch) is unaffected in every engine, including\nFirefox.\n\n## Side effects\n\nThe badge is a sibling of its anchor rather than a child, so **as a side effect, a badge\nmutates its anchor element**: it appends its own id to the anchor's `aria-describedby`\n(preserving any ids already there, the same way `anchor-name` is appended rather than\nreplaced) to keep its content connected to the anchor for assistive technology. This means a\nbadge's content, or its `aria-label` when set, is announced as part of interacting with the\nanchor, e.g. \"Inbox button, 3\". A `dot` badge has no content of its own, so set `aria-label`\ndirectly on `<use-badge>` for a meaningful description (e.g. `aria-label=\"3 unread messages\"`);\nwithout one, the description contributes nothing and the anchor announces as before.\n\nAvoid adding `aria-hidden` to `<use-badge>` if you rely on this: while the description\ncomputation is specified to still read a hidden node when it's the direct target of\n`aria-describedby`, support for that specific case is inconsistent across browsers and screen\nreaders.\n\nSet `options=\"noaria\"` to opt a badge out of this and leave the anchor's `aria-describedby`\nuntouched, e.g. when the anchor already documents the badge's meaning some other way.\n---\n\n\n### **Slots:**\n - _default_ - Badge content, e.g. a count or short label. Ignored when `dot` is set.",
@@ -63,6 +51,18 @@
       ],
       "references": []
     },
+    {
+      "name": "use-avatar",
+      "description": "`use-avatar` renders a small, fixed-size, clipped container for a person or entity's\nlikeness. Slot in an `<img>` (or `<picture>`) for a photo, an inline `<svg>` for a\ngenerated or stylized mark, or arbitrary markup (a `<div>` of initials, a calendar badge);\nwhatever is slotted is centered and clipped to the avatar's shape. With nothing slotted,\n`use-avatar` falls back to initials derived from the `name` attribute.\n\n```html\n<use-avatar><img src=\"ada.jpg\" alt=\"\" /></use-avatar>\n<use-avatar name=\"Riley Quinn\"></use-avatar>\n<use-avatar><svg viewBox=\"0 0 32 32\">…</svg></use-avatar>\n```\n\nSize it with plain CSS — `inline-size` for the size and `aspect-ratio` for the proportions —\nfrom a stylesheet, a style attribute, or the design system's theme layer. The element takes no\ncustom properties of its own: it is a query container, so the initials scale from whatever box\nit ends up with. A non-square `aspect-ratio` suits a wide thumbnail or poster.\n\nThe element clips its content but gives it no shape of its own — that is the theme's, through\nthe affordance classes it defines: `.circle` (the themed default), `.square`, `.squircle` in\n`theme/avatar.css`. A circle only reads right at a `1` ratio, so a wide avatar wants one of the\nothers.\n\nThe element takes no ARIA role of its own. A slotted `<img>` carries its own `alt`, and the\ninitials fallback is plain text in the accessibility tree — an avatar is decorative beside a\nname far more often than it is the name itself, so labelling it here would mean announcing\nthat name twice.\n---\n\n\n### **Slots:**\n - _default_ - The avatar's content: an `<img>`/`<picture>`, an `<svg>`, or arbitrary markup. Left empty, the `name` attribute's initials are shown instead, as the slot's own fallback. A photo fills the frame and crops; anything else keeps its own size, capped at the frame. Give an `<svg>` a `width`/`height` — without one it defaults to filling the box, and a rounded shape will clip its corners.\n\n### **CSS Parts:**\n - **initials** - The span that renders the `name` fallback.",
+      "attributes": [
+        {
+          "name": "name",
+          "description": "The full name, used for the initials fallback (first + last whitespace-separated token, uppercased) when the slot is empty.",
+          "values": []
+        }
+      ],
+      "references": []
+    },
     {
       "name": "use-calendarday",
       "description": "A helper component for customizing specific days within `use-calendar`.\nContent placed inside this element will replace the default day number display.\n---\n\n\n### **Slots:**\n - **default** - slot for custom day content (replaces the day number)",
@@ -75,6 +75,12 @@
       "attributes": [],
       "references": []
     },
+    {
+      "name": "use-control-set",
+      "description": "Groups adjacent controls — buttons and text-style inputs alike — into one visual unit: shared\nborders between touching children, rounded corners only on the two outer ends, and a hovered\nor focused child's border lifted above its neighbors so the whole border reads clearly.\n\n`use-control-set` renders no shadow DOM and no template of its own — it exists only as a\ndedicated tag for `theme/control-set.css` to style, the same way `use-layout` is a bare\nprimitive rather than a specific look. A classic split button is a text button followed by an\nicon-only trigger for a `use-menu`:\n\n```html\n<use-control-set>\n  <button type=\"button\">Save</button>\n  <button type=\"button\" popovertarget=\"save-options\" aria-label=\"More save options\">\n    <use-caret></use-caret>\n  </button>\n</use-control-set>\n<use-menu id=\"save-options\" aria-label=\"More save options\">\n  <button role=\"menuitem\">Save as&hellip;</button>\n</use-menu>\n```\n\nA search box with an attached submit button follows the same shape, mixing a text input with a\nbutton:\n\n```html\n<use-control-set>\n  <input type=\"search\" placeholder=\"Search\" />\n  <button type=\"submit\">Go</button>\n</use-control-set>\n```\n\nA child is a `<button>`, anything wearing `.appearance-button`, an `<input>` (other than a\ncheckbox/radio/range/file), a `<select>`, a `<textarea>`, or anything wearing\n`.appearance-input` — see `theme/control-set.css` for exactly which selectors read which\nradius/border tokens.\n\nHow the touching sides render is themeable rather than fixed: `--usewc-layout-control-set-gap`\n(default: a negative overlap equal to the child's own border, for a seamless merged line) and\n`--usewc-effect-control-set-border-radius-sequential` (default: `0`, for square touching\ncorners) can both be overridden — a positive gap and a small radius reads as a looser, softer\nset instead of a fused one.\n---\n\n\n### **Slots:**\n - _default_ - The grouped controls.",
+      "attributes": [],
+      "references": []
+    },
     {
       "name": "use-date-input",
       "description": "Displays a date picker using segmented inputs for year, month, and day.\n\nUses browser locale for formatting and ARIA labels.\n---\n",