@adia-ai/web-components 0.8.32 → 0.8.34

package/components/tag/tag.css

@@ -14,19 +14,26 @@ tag-ui[removable]:not([disabled]):hover {
        default at construction time. A bare `<tag-ui text="…">` therefore
        never gets a physical `variant="default"` attribute; these
        `:where(:scope)` zero-specificity tokens are what it actually
-       renders. Solid neutral inverse (was `--a-bg-muted` quiet chrome
-       pre-#794) — same pair the family variants and the redundant
+       renders. Solid neutral (was `--a-bg-muted` quiet chrome pre-#794)
+       — same pair the family variants and the redundant
        `:scope[variant="default"]` rule below carry, for the rare case
        `variant="default"` IS reflected explicitly (SSR/a2ui-producer
-       markup). Opt out via `[tone="muted"]`. */
-    --tag-bg:           var(--md-sys-color-neutral-on-surface);
-    --tag-fg:           var(--md-sys-color-neutral-background);
+       markup). Opt out via `[tone="muted"]`. Uses the real
+       `--md-sys-color-neutral`/`-on-neutral` pair (operator ruling,
+       2026-08-10) — the true parallel to `-primary`/`-on-primary` etc.,
+       not the `-on-surface`/`-background` ink/page tokens this rule
+       borrowed pre-#794's cross-check. */
+    --tag-bg:           var(--md-sys-color-neutral);
+    --tag-fg:           var(--md-sys-color-neutral-on-neutral);
     --tag-border:       transparent;
     --tag-radius:       var(--a-radius-full);
     --tag-px:           var(--a-space-1-5);
     --tag-py:           var(--a-space-0-5);
     --tag-gap:          var(--a-space-1);
-    --tag-font:         var(--a-ui-sm);
+    /* One rung down the --a-ui-* scale (gh#965): tags read as metadata
+       chrome, not body copy. Whole tier ladder shifts with it (sm=2xs,
+       lg=sm) so the tiers stay one rung apart. */
+    --tag-font:         var(--a-ui-xs);
 
     /* ── Size tiers (gh#779) — md (above) is the pixel-identical default;
        [size="sm"|"lg"] below re-point the active tokens. Component-owned
@@ -41,8 +48,8 @@ tag-ui[removable]:not([disabled]):hover {
     --tag-px-lg:  var(--a-space-2);
     --tag-py-sm:  var(--a-space-px);
     --tag-py-lg:  var(--a-space-1);
-    --tag-font-sm: var(--a-ui-xs);
-    --tag-font-lg: var(--a-ui-md);
+    --tag-font-sm: var(--a-ui-2xs);
+    --tag-font-lg: var(--a-ui-sm);
     --tag-font-family:  var(--a-font-family-ui);
     --tag-dismiss-size: 1rem;
     --tag-bg-hover:     var(--a-bg-hover);
@@ -122,85 +129,94 @@ tag-ui[removable]:not([disabled]):hover {
   }
 
   /* ── Variants ──
-     Default tone is `solid` for the four family variants:
-     `--a-{family}-bg` (saturated surface) + `--a-{family}-fg` (on-strong
-     text, near-white in both schemes by design). Reads as a status pill
-     where the chip IS the state. Opt out per-tag via [tone="muted"] for
-     metadata-chip surfaces in dense lists. */
-  /* `accent` is brand-primary emphasis for non-semantic labels — mirrors
-     <badge-ui>'s `accent` variant token-for-token (--a-primary-bg /
-     on-primary for the solid fill), applied to tag-ui's own solid-default
-     tone shape. Not a status color — no success/warning/danger implication. */
-  :scope[variant="accent"] {
-    --tag-bg: var(--a-primary-bg);
-    --tag-fg: var(--md-sys-color-primary-on-primary);
+     Default tone is `muted` for the family variants (gh#864): the
+     tinted-container pair — `--md-sys-color-{family}-container` (tinted
+     surface) + `-on-surface` (scheme-flipping text). Tag and badge had
+     been implementing each OTHER's reported default formula (gh#794
+     flipped tag's bare default to solid a day before gh#845 ratified
+     badge's register, with no cross-check between the two changes) — this
+     restores tag's own. Opt into the saturated stamp per-tag via
+     [tone="solid"] below. This does NOT touch the family-less `default`
+     variant below, which stays solid unconditionally (gh#794, unrelated
+     to the gh#864 swap). */
+  /* `primary` is brand emphasis for non-semantic labels — mirrors
+     <badge-ui>'s `primary` variant token-for-token (--md-sys-color-primary-
+     container / -on-surface for the tinted fill; `accent` retired, gh#874).
+     Not a status color — no success/warning/danger implication. */
+  :scope[variant="primary"] {
+    --tag-bg: var(--md-sys-color-primary-container);
+    --tag-fg: var(--md-sys-color-primary-on-surface);
   }
 
   :scope[variant="info"] {
-    --tag-bg: var(--a-info-bg);
-    --tag-fg: var(--md-sys-color-info-on-info);
+    --tag-bg: var(--md-sys-color-info-container);
+    --tag-fg: var(--md-sys-color-info-on-surface);
   }
 
   :scope[variant="success"] {
-    --tag-bg: var(--a-success-bg);
-    --tag-fg: var(--md-sys-color-success-on-success);
+    --tag-bg: var(--md-sys-color-success-container);
+    --tag-fg: var(--md-sys-color-success-on-surface);
   }
 
-  /* Same shape as the sibling families since the Material static-token
-     migration: amber fill + the palette's own fixed-light on-color
-     (`on-warning`, white in both schemes per Material's on-color law).
-     The pre-migration dark-brown-text override is gone — its
-     lower-than-siblings contrast is a known, operator-accepted
-     consequence (TKT-0018, wontfix pending palette adjustment). */
   :scope[variant="warning"] {
-    --tag-bg: var(--a-warning-bg);
-    --tag-fg: var(--md-sys-color-warning-on-warning);
+    --tag-bg: var(--md-sys-color-warning-container);
+    --tag-fg: var(--md-sys-color-warning-on-surface);
   }
 
   :scope[variant="danger"] {
-    --tag-bg: var(--a-danger-bg);
-    --tag-fg: var(--md-sys-color-danger-on-danger);
+    --tag-bg: var(--md-sys-color-danger-container);
+    --tag-fg: var(--md-sys-color-danger-on-surface);
   }
 
   /* `default` (no family) is solid by default (gh#794) — the same
-     high-contrast neutral inverse the family variants already carry.
-     A bare `<tag-ui text="…">` is now a stamped pill, not quiet chrome.
-     Opt OUT to the pre-#794 quiet-chrome look via `[tone="muted"]`
-     (below) on metadata/citation chips in dense lists or tables where
-     the saturated look competes for attention (gh#778's oversized-pill
-     complaint) — same escape hatch the family variants already use. */
+     high-contrast neutral inverse it has always carried. A bare
+     `<tag-ui text="…">` is a stamped pill, not quiet chrome. Unaffected by
+     the gh#864 family-variant swap above. Opt OUT to the pre-#794 quiet-
+     chrome look via `[tone="muted"]` (below) on metadata/citation chips
+     in dense lists or tables where the saturated look competes for
+     attention (gh#778's oversized-pill complaint). */
   :scope[variant="default"] {
-    --tag-bg: var(--md-sys-color-neutral-on-surface);
-    --tag-fg: var(--md-sys-color-neutral-background);
+    --tag-bg: var(--md-sys-color-neutral);
+    --tag-fg: var(--md-sys-color-neutral-on-neutral);
   }
 
   /* ── Tone modifier — orthogonal to [variant] ──
-     `[tone="muted"]` opts each family variant OUT of the solid default
-     into the canonical muted pair: `--a-{family}-muted` (tinted surface)
-     + `--a-{family}-text` (scheme-flipping text). Same shape <badge-ui>
-     uses as its default. Use on metadata chips in dense lists where the
-     saturated default would compete for attention. */
-  :scope[tone="muted"][variant="info"] {
-    --tag-bg: var(--md-sys-color-info-container);
-    --tag-fg: var(--md-sys-color-info-on-surface);
+     `[tone="solid"]` opts each family variant INTO the saturated-fill pair
+     (gh#864 — this used to be the family variants' unconditional default;
+     see the Variants comment above): `--a-{family}-bg` (saturated surface)
+     + Material's on-color (`-on-{family}`, near-white by the fixed-light-
+     on-color law). Same shape <tag-ui>'s family-less `default` variant
+     still carries unconditionally. Use for a single hero tag that should
+     stamp its state.
+
+     Warning uses --a-warning-bg (semantics.css L3 redirect to the bright-
+     amber -20-tint) rather than the raw family token — see also
+     <badge-ui>'s identical workaround. */
+  :scope[tone="solid"][variant="info"] {
+    --tag-bg: var(--a-info-bg);
+    --tag-fg: var(--md-sys-color-info-on-info);
   }
-  :scope[tone="muted"][variant="success"] {
-    --tag-bg: var(--md-sys-color-success-container);
-    --tag-fg: var(--md-sys-color-success-on-surface);
+  :scope[tone="solid"][variant="success"] {
+    --tag-bg: var(--a-success-bg);
+    --tag-fg: var(--md-sys-color-success-on-success);
   }
-  :scope[tone="muted"][variant="warning"] {
-    --tag-bg: var(--md-sys-color-warning-container);
-    --tag-fg: var(--md-sys-color-warning-on-surface);
+  /* Same shape as the sibling families since the Material static-token
+     migration: amber fill + the palette's own fixed-light on-color
+     (`on-warning`, white in both schemes per Material's on-color law).
+     The pre-migration dark-brown-text override is gone — its
+     lower-than-siblings contrast is a known, operator-accepted
+     consequence (TKT-0018, wontfix pending palette adjustment). */
+  :scope[tone="solid"][variant="warning"] {
+    --tag-bg: var(--a-warning-bg);
+    --tag-fg: var(--md-sys-color-warning-on-warning);
   }
-  :scope[tone="muted"][variant="danger"] {
-    --tag-bg: var(--md-sys-color-danger-container);
-    --tag-fg: var(--md-sys-color-danger-on-surface);
+  :scope[tone="solid"][variant="danger"] {
+    --tag-bg: var(--a-danger-bg);
+    --tag-fg: var(--md-sys-color-danger-on-danger);
   }
-  /* Mirrors <badge-ui>'s default (muted) accent pair —
-     --md-sys-color-primary-container / -on-surface. */
-  :scope[tone="muted"][variant="accent"] {
-    --tag-bg: var(--md-sys-color-primary-container);
-    --tag-fg: var(--md-sys-color-primary-on-surface);
+  :scope[tone="solid"][variant="primary"] {
+    --tag-bg: var(--a-primary-bg);
+    --tag-fg: var(--md-sys-color-primary-on-primary);
   }
   /* gh#794: the pre-#794 quiet-chrome look for the variant-less default —
      same values the `:where(:scope)` base tokens carried before the
@@ -213,7 +229,7 @@ tag-ui[removable]:not([disabled]):hover {
      `installProps()` reflect() path only fires on a property SET) —
      the same reason the `[tone="solid"]` fallback below uses this same
      `:not()` shape instead of `[variant="default"]`. */
-  :scope[tone="muted"]:not([variant="info"]):not([variant="success"]):not([variant="warning"]):not([variant="danger"]):not([variant="accent"]) {
+  :scope[tone="muted"]:not([variant="info"]):not([variant="success"]):not([variant="warning"]):not([variant="danger"]):not([variant="primary"]) {
     --tag-bg: var(--a-bg-muted);
     --tag-fg: var(--md-sys-color-neutral-on-surface);
   }
@@ -222,13 +238,13 @@ tag-ui[removable]:not([disabled]):hover {
      since gh#794 (the variant-less default is solid unconditionally
      above) but kept so `tone="solid"` stays a valid, harmless, explicit
      statement of intent for consumers who set it directly.
-     [variant="accent"] is excluded — it already has an explicit solid
-     pair above (the plain [variant="accent"] rule) that this higher-
-     specificity fallback would otherwise clobber when tone="solid" is
-     set explicitly alongside it. */
-  :scope[tone="solid"]:not([variant="info"]):not([variant="success"]):not([variant="warning"]):not([variant="danger"]):not([variant="accent"]) {
-    --tag-bg: var(--md-sys-color-neutral-on-surface);
-    --tag-fg: var(--md-sys-color-neutral-background);
+     [variant="primary"] is excluded — its solid pair is the explicit
+     `[tone="solid"][variant="primary"]` rule above (gh#864: the bare
+     `[variant="primary"]` rule is container-tinted now, not solid) — this
+     `:not()` keeps the neutral-only fallback from ever matching primary. */
+  :scope[tone="solid"]:not([variant="info"]):not([variant="success"]):not([variant="warning"]):not([variant="danger"]):not([variant="primary"]) {
+    --tag-bg: var(--md-sys-color-neutral);
+    --tag-fg: var(--md-sys-color-neutral-on-neutral);
   }
 
   /* ── `[tone="outline"]` — transparent bg + family-colored border + text ──
@@ -255,15 +271,15 @@ tag-ui[removable]:not([disabled]):hover {
     --tag-fg:     var(--md-sys-color-danger-on-surface);
     --tag-border: var(--md-sys-color-danger-outline);
   }
-  /* Mirrors <badge-ui>'s outline accent pair —
+  /* Mirrors <badge-ui>'s outline primary pair —
      --md-sys-color-primary-on-surface / -primary-outline. */
-  :scope[tone="outline"][variant="accent"] {
+  :scope[tone="outline"][variant="primary"] {
     --tag-fg:     var(--md-sys-color-primary-on-surface);
     --tag-border: var(--md-sys-color-primary-outline);
   }
   /* Outline on neutral (no family) — fg-muted text + subtle border.
-     [variant="accent"] excluded — see the [tone="solid"] fallback note above. */
-  :scope[tone="outline"]:not([variant="info"]):not([variant="success"]):not([variant="warning"]):not([variant="danger"]):not([variant="accent"]) {
+     [variant="primary"] excluded — see the [tone="solid"] fallback note above. */
+  :scope[tone="outline"]:not([variant="info"]):not([variant="success"]):not([variant="warning"]):not([variant="danger"]):not([variant="primary"]) {
     --tag-fg:     var(--a-fg-muted);
     --tag-border: var(--md-sys-color-neutral-outline);
   }
@@ -279,7 +295,7 @@ tag-ui[removable]:not([disabled]):hover {
   :scope[size="md"] {
     --tag-px:  var(--a-space-1-5);
     --tag-py:  var(--a-space-0-5);
-    --tag-font: var(--a-ui-sm);
+    --tag-font: var(--a-ui-xs);
   }
   :scope[size="lg"] {
     --tag-px:  var(--tag-px-lg);

package/components/tag/tag.d.ts

@@ -41,15 +41,21 @@ export class UITag extends UIElement {
   /** Tag label. Renderer routes this to the `text` attribute, rendered via CSS attr(text) on ::after. */
   textContent: string;
   /** Fill style — orthogonal to [variant]. Three values:
-  - `solid` (default — for EVERY variant, including the family-less
-    `default`, since gh#794) — saturated bg + on-strong (near-white)
-    text. The chip IS the state. A bare `<tag-ui text="…">` renders
-    this look with no attributes at all.
-  - `muted` — tinted bg with scheme-paired text. Matches <badge-ui>'s
-    default look, and is the pre-gh#794 look for the family-less
-    `default` variant. Use on metadata / citation chips in dense
-    lists or tables where the saturated default would compete for
-    attention (gh#778's oversized-pill concern).
+  - `muted` (default for the family variants — info/success/warning/
+    danger/primary — gh#864: tag and badge were swapped relative to
+    their reported default formulas; this restores tag's own)
+    — tinted bg with scheme-paired text. Matches <badge-ui>'s
+    `[tone="muted"]` look. Use on metadata / citation chips in dense
+    lists or tables where a saturated fill would compete for
+    attention (gh#778's oversized-pill concern). Does NOT apply to
+    the family-less `default` variant, which stays solid
+    unconditionally (gh#794, unaffected by gh#864) — a bare
+    `<tag-ui text="…">` still renders that solid look with no
+    attributes at all.
+  - `solid` — saturated bg + on-strong (near-white) text. The chip
+    IS the state. Opt in explicitly for a family variant (gh#864),
+    or it's already the unconditional look for the family-less
+    `default` variant (gh#794).
   - `outline` — transparent bg + family-colored border + family-colored
     text. The lightest visual weight; good in dense data tables or
     faceted filter rows where multiple chips would otherwise compete.
@@ -58,8 +64,8 @@ prop — see tag.class.js) so its schema `default` here is documentation
 of the rendered-by-default look, not a reflected attribute value.
  */
   tone: 'solid' | 'muted' | 'outline';
-  /** Semantic variant — `default | accent | info | success | warning | danger`. `accent` is brand-primary emphasis for non-semantic labels — a filter chip or taxonomy tag that shouldn't imply a success/warning/danger state. Mirrors <badge-ui>'s `accent` variant token-for-token. */
-  variant: 'default' | 'accent' | 'info' | 'success' | 'warning' | 'danger';
+  /** Semantic variant — `default | info | success | warning | danger | primary`. `primary` is brand emphasis for non-semantic labels — a filter chip or taxonomy tag that shouldn't imply a success/warning/danger state. Mirrors <badge-ui>'s `primary` variant token-for-token (`accent` retired, gh#874 — the capability survives renamed, sibling parity with badge preserved). */
+  variant: 'default' | 'info' | 'success' | 'warning' | 'danger' | 'primary';
 
   addEventListener(type: 'remove', listener: (ev: TagRemoveEvent) => unknown, options?: boolean | AddEventListenerOptions): void;
   addEventListener<K extends keyof HTMLElementEventMap>(

package/components/tag/tag.yaml

@@ -46,31 +46,38 @@ props:
     type: string
     dynamic: true
   variant:
-    description: Semantic variant — `default | accent | info | success | warning | danger`.
-      `accent` is brand-primary emphasis for non-semantic labels — a filter chip
+    description: Semantic variant — `default | info | success | warning | danger | primary`.
+      `primary` is brand emphasis for non-semantic labels — a filter chip
       or taxonomy tag that shouldn't imply a success/warning/danger state. Mirrors
-      <badge-ui>'s `accent` variant token-for-token.
+      <badge-ui>'s `primary` variant token-for-token (`accent` retired, gh#874 —
+      the capability survives renamed, sibling parity with badge preserved).
     type: string
     default: default
     enum:
       - default
-      - accent
       - info
       - success
       - warning
       - danger
+      - primary
   tone:
     description: |
       Fill style — orthogonal to [variant]. Three values:
-        - `solid` (default — for EVERY variant, including the family-less
-          `default`, since gh#794) — saturated bg + on-strong (near-white)
-          text. The chip IS the state. A bare `<tag-ui text="…">` renders
-          this look with no attributes at all.
-        - `muted` — tinted bg with scheme-paired text. Matches <badge-ui>'s
-          default look, and is the pre-gh#794 look for the family-less
-          `default` variant. Use on metadata / citation chips in dense
-          lists or tables where the saturated default would compete for
-          attention (gh#778's oversized-pill concern).
+        - `muted` (default for the family variants — info/success/warning/
+          danger/primary — gh#864: tag and badge were swapped relative to
+          their reported default formulas; this restores tag's own)
+          — tinted bg with scheme-paired text. Matches <badge-ui>'s
+          `[tone="muted"]` look. Use on metadata / citation chips in dense
+          lists or tables where a saturated fill would compete for
+          attention (gh#778's oversized-pill concern). Does NOT apply to
+          the family-less `default` variant, which stays solid
+          unconditionally (gh#794, unaffected by gh#864) — a bare
+          `<tag-ui text="…">` still renders that solid look with no
+          attributes at all.
+        - `solid` — saturated bg + on-strong (near-white) text. The chip
+          IS the state. Opt in explicitly for a family variant (gh#864),
+          or it's already the unconditional look for the family-less
+          `default` variant (gh#794).
         - `outline` — transparent bg + family-colored border + family-colored
           text. The lightest visual weight; good in dense data tables or
           faceted filter rows where multiple chips would otherwise compete.
@@ -78,7 +85,7 @@ props:
       prop — see tag.class.js) so its schema `default` here is documentation
       of the rendered-by-default look, not a reflected attribute value.
     type: string
-    default: solid
+    default: muted
     enum:
       - solid
       - muted
@@ -132,12 +139,16 @@ a2ui:
       vertically; vertical lists of dismissable items are an
       <action-list-ui> use case, not <tag-ui>.
     - >-
-      Bare <tag-ui text="…"> (no [tone]) renders the high-contrast
-      solid pill by default (gh#794). In dense tables, tight metadata
-      rows, or citation/footnote strips where many tags sit close
-      together, set [tone="muted"] to keep the quieter tinted look
-      instead — a wall of solid pills reads as visual noise there
+      A family-less <tag-ui text="…"> (no [variant], no [tone]) renders
+      the high-contrast solid pill by default (gh#794). In dense tables,
+      tight metadata rows, or citation/footnote strips where many tags
+      sit close together, set [tone="muted"] to keep the quieter tinted
+      look instead — a wall of solid pills reads as visual noise there
       (gh#778).
+    - >-
+      A family [variant] (info/success/warning/danger/primary) with no
+      [tone] renders the tinted-container look by default (gh#864). Set
+      [tone="solid"] for a saturated status stamp instead.
 anti_patterns: []
 examples:
   - name: basic-tag

package/components/toast/toast.a2ui.json

@@ -40,7 +40,7 @@
       "default": ""
     },
     "variant": {
-      "description": "Semantic variant — `default | info | success | warning | danger`. `primary` and `muted` are style hints; canonical \"neutral but interesting\" tone is `info`.",
+      "description": "Semantic variant — `default | info | success | warning | danger | primary`. `primary` is the brand-emphasis fill (mirrors badge-ui/button-ui's `primary`); canonical \"neutral but interesting\" tone is `info`.",
       "type": "string",
       "enum": [
         "default",
@@ -48,9 +48,7 @@
         "success",
         "warning",
         "danger",
-        "primary",
-        "muted",
-        "neutral"
+        "primary"
       ],
       "default": "info"
     }

package/components/toast/toast.css

@@ -148,18 +148,6 @@ toast-ui[data-closing][position="top-left"] {
     --toast-border: var(--md-sys-color-primary-outline-variant);
   }
 
-  /* `muted` and `neutral` are semantic aliases of the base canvas
-     surface — same tokens as the unstyled `:scope`, declared explicitly
-     so the yaml enum and the CSS contract agree. Use cases: quiet
-     status nudges that shouldn't carry tonal weight (e.g. "Draft
-     saved" without success-green). Mirrors alert-ui's pattern. */
-  :where(:scope[variant="muted"]),
-  :where(:scope[variant="neutral"]) {
-    --toast-bg:     var(--a-bg-subtle);
-    --toast-fg:     var(--md-sys-color-neutral-on-surface);
-    --toast-border: var(--md-sys-color-neutral-outline-variant);
-  }
-
   /* ── Message slot ── */
 
   [slot="message"] {

package/components/toast/toast.yaml

@@ -37,8 +37,9 @@ props:
     default: ""
   variant:
     description: >-
-      Semantic variant — `default | info | success | warning | danger`.
-      `primary` and `muted` are style hints; canonical "neutral but
+      Semantic variant — `default | info | success | warning | danger |
+      primary`. `primary` is the brand-emphasis fill (mirrors
+      badge-ui/button-ui's `primary`); canonical "neutral but
       interesting" tone is `info`.
     type: string
     default: info
@@ -49,8 +50,6 @@ props:
       - warning
       - danger
       - primary
-      - muted
-      - neutral
 events: {}
 usage: |-
   §224 (v0.5.9): `UIToast.show()` routes through `UIFeed.post()` — the

package/core/element.js

@@ -176,12 +176,43 @@ export class UIElement extends HTMLElement {
     // compliant environments: the value already matches (the property
     // setter's Object.is check short-circuits), so this never causes an
     // extra render pass on browsers/environments that already got it right.
+    // The whole pre-sync loop runs UNTRACKED: connectedCallback commonly
+    // fires synchronously inside a PARENT's render effect (template-created
+    // children connect during stamp()), and the gh#961 branch below READS
+    // `this[key]` — a tracked read there subscribes the parent's effect to
+    // this child's signals, so any later child-prop write (a `.checked`
+    // template apply) re-dirties the parent, which re-stamps fresh
+    // children, whose own mount-reads re-subscribe: the unbounded
+    // parent↔child oscillation the signals drain-loop guard traps (the
+    // admin-settings/switch-ui/button-ui loop on gh#961). Same rationale
+    // as the untracked(connected()) wrapper below.
+    untracked(() => {
     for (const [key, cfg] of Object.entries(ctor.properties)) {
       const attr = cfg.attribute ?? key.toLowerCase();
       if (this.hasAttribute(attr)) {
         this[key] = parseAttr(this.getAttribute(attr), cfg.type ?? String);
+      } else if (cfg.reflect && cfg.type === Boolean && this[key] === true) {
+        // gh#961 — stamp the initial attribute for a TRUE-default reflected
+        // boolean. installProps seeds the signal with the default but can't
+        // touch attributes (constructor restriction), and the property
+        // setter's Object.is short-circuit means a later same-value set
+        // (e.g. chat-thread's #syncEmptyFromChildren recomputing `empty:
+        // true` on first connect) never reflects either — so CSS gates like
+        // `chat-thread:not([empty]) > chat-empty` and
+        // `editor-canvas:not([empty]) > editor-canvas-empty` read the
+        // wrong state forever. Deliberately scoped to Boolean-true ONLY:
+        // reflecting string/number defaults here stamps `text=""`-shaped
+        // attributes framework-wide, flipping `[attr]` CSS gates and
+        // cascading re-renders into the signals drain-loop guard (the
+        // full-reflect attempt documented on gh#961). A false default is
+        // already a DOM no-op (removeAttribute on an absent attribute).
+        // The setAttribute replays attributeChangedCallback → parseAttr →
+        // same value → Object.is short-circuit: no signal write, no
+        // render pass.
+        this.setAttribute(attr, '');
       }
     }
+    });
     // connected() commonly reads this element's reactive properties via
     // template-literal interpolation (`${this.label}` etc.) to stamp its
     // inner DOM. If the outer call path is inside another effect (e.g.

package/core/signals.js

@@ -32,7 +32,9 @@ function flushSigs() {
   while ((q = pending)) {
     if (++loops > 100) {
       pending = null;
-      console.error(`signals: drain loop exceeded 100 iterations`);
+      // Name the still-dirty effect hosts — a bare count is undiagnosable
+      // (gh#961's oscillation took host attribution to even locate).
+      console.error(`signals: drain loop exceeded 100 iterations`, JSON.stringify([...q].map(s => s.host || '?')));
       break;
     }
     pending = null;