@coventia/softphone 0.1.0

package/dist/softphone.css

@@ -0,0 +1,1923 @@
+/**
+ * @coventia/softphone/styles.css
+ *
+ * The theming contract (SPEC §2.6) + all component styles. A host restyles the softphone by
+ * overriding the `--cv-*` custom properties — which are INHERITED, so they cross the shadow boundary
+ * of `<coventia-softphone>` by design (the host's own CSS *selectors* do not, which is what stops a
+ * stray `button { width:100% }` from destroying the dialpad).
+ *
+ * Defaults match the Coventia product: light surface, emerald accent, soft rounded key cards.
+ *
+ * Reseller:  coventia-softphone { --cv-accent:#7c3aed; --cv-bg:#0b0b0f; }
+ * CRM (shadcn bridge, ~15 lines, dark mode included):
+ *   .cv-softphone { --cv-bg:hsl(var(--background)); --cv-text:hsl(var(--foreground)); … }
+ *
+ * TYPOGRAPHY NOTE: `--cv-font` is a system stack on purpose. An embedded widget should inherit its
+ * host's type, not force a webfont into someone else's app; hosts override the token if they want.
+ *
+ * Strings are Spanish-only (SPEC §2.4). No i18n.
+ */
+
+/*
+ * The custom element's own box.
+ *
+ * A custom element is `display: inline` by default and has NO size — and the widget inside now fills
+ * its host rather than asserting 340×520, so without this the element would render to ZERO. The
+ * drop-in promise is "one tag and it works", which means the TAG must carry a box.
+ *
+ * These are defaults, not decisions: they sit on `:host`, so any host stylesheet outranks them —
+ *
+ *   coventia-softphone { width: 100%; height: 100%; }   ← a sidebar
+ *   coventia-softphone { height: 600px; }               ← taller
+ *
+ * React consumers never see this: they import `/ui` and their own wrapper states the box (the CRM's
+ * PhoneDialer does exactly that).
+ */
+:host {
+  display: block;
+  width: 340px;
+  height: 520px;
+}
+
+/* React's container inside the shadow root — element path only; inert everywhere else.
+ *
+ * It must pass the host's height straight through. `.cv-softphone` below is `height: 100%`, and a
+ * percentage height resolves against the PARENT: leave this div at its default `auto` and that 100%
+ * silently becomes `auto` too, so the widget collapses to its content height and the host's `height`
+ * is ignored. What you see is a short card stranded in a taller box — which reads as a broken widget,
+ * not as a broken wrapper. */
+.cv-mount {
+  height: 100%;
+}
+
+:host,
+.cv-softphone {
+  /* Surface */
+  --cv-bg: #ffffff;
+  --cv-surface: #f9fafb;
+  --cv-surface-2: #f3f4f6;
+  --cv-border: #f3f4f6;
+  --cv-border-strong: #e5e7eb;
+
+  /* Text — three tiers, split by CONTRAST DUTY, not by taste:
+     `text`  informational primary        17.7:1
+     `muted` informational secondary       4.8:1  (AA — phone numbers, timestamps, tab labels)
+     `faint` DECORATIVE only               2.5:1  (keypad letters, placeholder — never information)
+     The legacy used gray-400 for all secondary text, which fails AA at 2.54:1. Splitting the tier
+     keeps the look while making the informational text legible. */
+  --cv-text: #111827;
+  --cv-muted: #6b7280;
+  --cv-faint: #9ca3af;
+
+  /* Intent — emerald. Split by CONTRAST DUTY, because one "brand green" cannot do all three jobs:
+     `accent`        FILL that carries a white glyph  → emerald-600, white 3.77:1 ✓
+                     (emerald-500 is the prettier brand green but white on it is 2.54:1 — the
+                      call button's phone icon would fail WCAG non-text contrast. Measured, not guessed.)
+     `accent-strong` emerald AS TEXT on a surface     → emerald-700, 5.48:1 ✓ for the 10px tab label
+     `accent-light`  DECORATIVE only (the ring halo)  — never carries text, so it stays vivid */
+  --cv-accent: #059669;
+  --cv-accent-strong: #047857;
+  --cv-accent-light: #10b981;
+  --cv-accent-soft: #a7f3d0;
+  --cv-accent-contrast: #ffffff;
+  --cv-danger: #ef4444;
+  /* `--cv-danger` ITSELF fails 3:1 non-text contrast against `--cv-danger-soft` (2.6:1, measured) —
+     the same AS-TEXT/on-a-tinted-surface split `accent` already has, `danger` was just missing until
+     the Historial tab's status badges needed it. Darker on light (mirrors `accent-strong`), LIGHTER on
+     dark (red-400) — same inversion `accent-strong` documents above, same reason: emphasis on a dark
+     surface means more light, not less.
+     red-700 (#b91c1c) was the first pick here and overshot both minimums (6.47:1 text, 4.47:1 badge)
+     enough to read as a dark, brownish red rather than red — red-600 clears both with real margin
+     still (4.83:1 / 3.34:1, measured) and looks like red. */
+  --cv-danger-strong: #dc2626;
+  --cv-danger-soft: #fecaca;
+  /* A third status hue, sky — for the Historial row status chip specifically: an outgoing call that
+     WAS answered gets its own colour rather than sharing `accent`, matching the legacy CRM's own
+     three-way split (emerald/sky/rose) that this file's earlier restrained accent-only-for-"fine"
+     version had collapsed away. Same strong/soft split, same inversion, as `accent`/`danger` above —
+     4.47:1 light / 4.42:1 dark against `-soft`, measured. */
+  --cv-info: #0284c7;
+  --cv-info-strong: #0369a1;
+  --cv-info-soft: #bae6fd;
+  --cv-hold: #6366f1;
+
+  /* Shape & type */
+  --cv-radius: 16px;
+  /* Strong ease-out. The built-in CSS easings are too weak to read as intentional. */
+  --cv-ease-out: cubic-bezier(0.23, 1, 0.32, 1);
+  --cv-radius-key: 16px;
+  --cv-font: system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif;
+  --cv-font-size: 14px;
+  --cv-shadow: 0 1px 2px rgb(0 0 0 / 0.04), 0 1px 3px rgb(0 0 0 / 0.06);
+
+  color: var(--cv-text);
+  font-family: var(--cv-font);
+  font-size: var(--cv-font-size);
+}
+
+/**
+ * Dark theme — matched to the Coventia product's own dark tokens, not invented.
+ *
+ * The CRM defines `--background: 240 10% 10%` (#17171c) with surfaces at 15.9% (#27272a) and borders
+ * at 25.9% (#404044) — the zinc/240-hue family. An earlier draft here used a near-black
+ * (#0f0f13, ~half the luminance of the product's background) with 2%-luminance borders that were
+ * effectively invisible. That is the "black tonality" that read wrong: right hue, wrong lightness.
+ *
+ * Note the accent INVERTS: on light, `accent-strong` is darker than `accent` (emerald-700); on dark
+ * it must be LIGHTER (emerald-400), because emphasis on a dark surface means more light, not less.
+ * Same token, opposite direction — miss this and the timer/active tab sink into the background.
+ *
+ * ── HOW THE THEME IS CHOSEN ──────────────────────────────────────────────────
+ * By default it follows the OS (`prefers-color-scheme`). But a host must be able to PIN it: the
+ * Coventia CRM toggles dark with a class (next-themes), not the OS setting — so a user with a dark
+ * OS but the CRM in light mode would otherwise get a dark widget inside a light app.
+ *
+ *   <SoftphoneWidget theme="light" />   → data-cv-theme="light"  — always light
+ *   <SoftphoneWidget theme="dark" />    → data-cv-theme="dark"   — always dark
+ *   <SoftphoneWidget />                 → follows the OS
+ *
+ * To follow the HOST's theme rather than the OS, pass the host's current theme through, e.g.
+ * next-themes: `const { resolvedTheme } = useTheme(); <SoftphoneWidget theme={resolvedTheme} />`.
+ *
+ * The dark block is duplicated below (OS-driven vs. pinned) on purpose: plain CSS has no way to
+ * share a declaration block across a media query and a selector, and the honest duplication beats a
+ * clever custom-property toggle nobody can debug.
+ */
+@media (prefers-color-scheme: dark) {
+  :host(:not([data-cv-theme='light'])),
+  .cv-softphone:not([data-cv-theme='light']) {
+    --cv-bg: #17171c;          /* CRM --background            240 10% 10%  */
+    --cv-surface: #202027;     /* between bg and secondary                 */
+    --cv-surface-2: #27272a;   /* CRM --secondary/--muted     240 3.7% 15.9% */
+    --cv-border: #2e2e33;
+    --cv-border-strong: #404044; /* CRM --border              240 3.7% 25.9% */
+    --cv-text: #fafafa;        /* CRM --foreground            0 0% 98%     */
+    --cv-muted: #a1a1aa;       /* CRM --muted-foreground      240 5% 64.9% → 6.97:1 AA */
+    --cv-faint: #71717a;       /* decorative only                          */
+    --cv-accent-strong: #34d399; /* emerald-400 — 9.29:1 on #17171c        */
+    --cv-accent-light: #34d399;  /* the halo reads brighter on dark          */
+    --cv-accent-soft: #065f46;   /* glows must darken on dark, not glare     */
+    --cv-danger-strong: #f87171; /* red-400 — LIGHTER than --cv-danger, same inversion as accent-strong */
+    --cv-danger-soft: #7f1d1d;
+    --cv-info-strong: #38bdf8;   /* sky-400 — same inversion, same reason */
+    --cv-info-soft: #0c4a6e;
+    --cv-shadow: 0 1px 2px rgb(0 0 0 / 0.4);
+  }
+}
+
+/* Pinned dark — wins regardless of the OS setting. */
+:host([data-cv-theme='dark']),
+.cv-softphone[data-cv-theme='dark'] {
+  --cv-bg: #17171c;
+  --cv-surface: #202027;
+  --cv-surface-2: #27272a;
+  --cv-border: #2e2e33;
+  --cv-border-strong: #404044;
+  --cv-text: #fafafa;
+  --cv-muted: #a1a1aa;
+  --cv-faint: #71717a;
+  --cv-accent-strong: #34d399;
+  --cv-accent-light: #34d399;
+  --cv-accent-soft: #065f46;
+  --cv-danger-strong: #f87171;
+  --cv-danger-soft: #7f1d1d;
+  --cv-info-strong: #38bdf8;
+  --cv-info-soft: #0c4a6e;
+  --cv-shadow: 0 1px 2px rgb(0 0 0 / 0.4);
+}
+
+.cv-softphone,
+.cv-softphone *,
+.cv-softphone *::before,
+.cv-softphone *::after {
+  box-sizing: border-box;
+}
+
+/* ── Shell ──────────────────────────────────────────────────────────────────── */
+.cv-softphone {
+  display: flex;
+  flex-direction: column;
+
+  /* FILL the box the host gives us; do not assert one.
+     This was `width: 340px; height: 520px`, which is a component telling its host how big its
+     layout is. The CRM's panel is 310 wide, so the third keypad column was simply cut off — and no
+     amount of theming could have fixed it, because the widget was not asking. A component in
+     someone else's layout accepts a size. */
+  width: 100%;
+  height: 100%;
+
+  /* …but a dialpad is not a spreadsheet. Given 900px it should not become a 900px dialpad with
+     300px keys; it should be itself, centred. Cap and centre rather than stretch. */
+  max-width: var(--cv-max-width, 420px);
+  margin-inline: auto;
+
+  /* Adapt to THIS box, not to the viewport. The widget can be 310px wide inside a 1920px screen —
+     a media query would ask the wrong question and get a confident wrong answer. Container queries
+     are the only ones that know the truth, and a shadow root is the ideal place for them. */
+  container-type: inline-size;
+  container-name: cv;
+
+  background: var(--cv-bg);
+  overflow: hidden;
+
+  /* The frame is the HOST's call. The CRM's panel already draws `border rounded-xl shadow-2xl`, so
+     drawing our own put a card inside a card — nested chrome, which is always wrong. Defaulting to
+     a frame still suits a bare drop-in on a blank page; a host that has its own sets these to
+     `none` / `0` and the double edge disappears. */
+  border: var(--cv-shell-border, 1px solid var(--cv-border-strong));
+  border-radius: var(--cv-shell-radius, var(--cv-radius));
+  box-shadow: var(--cv-shell-shadow, 0 4px 24px rgb(0 0 0 / 0.06));
+}
+
+/* Narrow hosts — a sidebar, a phone-width column. Reclaim the horizontal padding first: at 260px
+   the gutters cost more than they give, and a cramped keypad is worse than a tight one. */
+@container cv (max-width: 300px) {
+  .cv-keypad { padding: 0 0.6rem; gap: 6px; }
+  .cv-dial-prefix { padding: 0.7rem 0.6rem 0; }
+  .cv-dial-head { padding: 0.3rem 0.6rem 0.6rem; }
+  .cv-display { font-size: 1.5rem; }
+  .cv-controls-row { gap: 1.1rem; }
+
+}
+
+/* Short hosts. The flex chain already lets the keypad absorb what is left, but below this the keys
+   stop being tappable — so buy the height back from the chrome instead of from the keys. */
+@container cv (max-height: 440px) {
+  .cv-dial-prefix { padding-top: 0.5rem; }
+  .cv-dial-head { padding-top: 0.2rem; padding-bottom: 0.4rem; }
+  .cv-dial-foot { padding-bottom: 0.5rem; }
+  .cv-controls { gap: 0.4rem; padding-bottom: 0.6rem; }
+}
+
+/* The flex chain that makes the layout work: body flexes, views fill it, only the
+   keypad/list grows. Without `min-height:0` a grid child refuses to shrink and overflows. */
+.cv-body {
+  flex: 1;
+  min-height: 0;
+  display: flex;
+  flex-direction: column;
+}
+.cv-view {
+  flex: 1;
+  min-height: 0;
+  display: flex;
+  flex-direction: column;
+  /* Containing block for `.cv-detail` below — an absolute overlay must cover exactly THIS tab's
+     content, not escape to whatever the next positioned ancestor up the tree happens to be. */
+  position: relative;
+}
+
+/* ── Tab bar ─────────────────────────────────────────────────────────────────── */
+.cv-tabs {
+  display: flex;
+  border-top: 1px solid var(--cv-border);
+  background: var(--cv-bg);
+  flex-shrink: 0;
+}
+.cv-tab {
+  flex: 1;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  gap: 3px;
+  padding: 9px 0 8px;
+  background: none;
+  border: none;
+  color: var(--cv-muted);
+  cursor: pointer;
+  font: inherit;
+  transition: color 0.15s ease, background 0.15s ease;
+}
+.cv-tab:hover:not(:disabled) { background: var(--cv-surface); }
+.cv-tab[aria-selected='true'] { color: var(--cv-accent-strong); }
+.cv-tab:disabled { opacity: 0.35; cursor: not-allowed; }
+.cv-tab span { font-size: 10px; font-weight: 600; line-height: 1; letter-spacing: 0.01em; }
+
+/* ── Buttons ─────────────────────────────────────────────────────────────────── */
+.cv-btn {
+  font: 600 0.875rem var(--cv-font);
+  cursor: pointer;
+  padding: 0.5rem 0.9rem;
+  border-radius: 10px;
+  border: 1px solid var(--cv-border-strong);
+  background: var(--cv-bg);
+  color: var(--cv-text);
+  transition: background 0.15s ease, transform 0.06s ease;
+}
+.cv-btn:hover:not(:disabled) { background: var(--cv-surface); }
+.cv-btn:active:not(:disabled) { transform: scale(0.97); }
+.cv-btn:disabled { opacity: 0.45; cursor: not-allowed; }
+.cv-btn--accent {
+  background: var(--cv-accent);
+  border-color: var(--cv-accent);
+  color: var(--cv-accent-contrast);
+}
+.cv-btn--accent:hover:not(:disabled) { background: var(--cv-accent-strong); }
+
+/* Round action buttons (answer / hangup / call) */
+.cv-round {
+  width: 64px;
+  height: 64px;
+  border-radius: 999px;
+  border: none;
+  cursor: pointer;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  color: #fff;
+  transition: background 0.15s ease, transform 0.08s ease, box-shadow 0.15s ease;
+}
+.cv-round:active:not(:disabled) { transform: scale(0.94); }
+.cv-round--answer {
+  background: var(--cv-accent);
+  box-shadow: 0 8px 20px -4px var(--cv-accent-soft);
+}
+.cv-round--answer:hover:not(:disabled) { background: var(--cv-accent-strong); }
+.cv-round--answer:disabled {
+  background: var(--cv-surface-2);
+  color: var(--cv-faint);
+  box-shadow: none;
+  cursor: not-allowed;
+}
+.cv-round--hangup {
+  background: var(--cv-danger);
+  box-shadow: 0 8px 20px -4px var(--cv-danger-soft);
+}
+.cv-round--hangup:hover:not(:disabled) { filter: brightness(0.94); }
+
+/* ── Dialpad ─────────────────────────────────────────────────────────────────── */
+/* The prefix chip, on its own row above the number.
+   Sharing a line with the number starves it: chip + erase button eat the middle, and a formatted
+   international number needs every pixel. The number is the content; the prefix is a setting. */
+.cv-dial-prefix {
+  flex-shrink: 0;
+  display: flex;
+  justify-content: center;
+  padding: 1rem 1rem 0;
+}
+.cv-dial-head {
+  flex-shrink: 0;
+  display: flex;
+  align-items: center;
+  padding: 0.35rem 1rem 0.75rem;
+  gap: 0.25rem;
+}
+/*
+ * The outcome of the last attempt, under the number.
+ *
+ * ALWAYS in the layout, visible or not. The keypad is `flex: 1` and absorbs whatever height is left,
+ * so a line that appears and disappears would resize every key and shift the whole grid under the
+ * user's finger — mid-dial, which is exactly when this text arrives. Reserving the row costs one line
+ * of height and buys a keypad that never moves.
+ */
+.cv-dial-outcome {
+  flex-shrink: 0;
+  margin: 0;
+  min-height: 1.15rem;
+  padding: 0 1rem;
+  text-align: center;
+  font-size: 0.78rem;
+  line-height: 1.15rem;
+  color: var(--cv-muted);
+  /*
+    One line, always. `error-text.test.ts` caps every outcome at 48 characters so nothing should ever
+    reach this — but a cap depends on whoever writes the next string remembering it, and the failure
+    it prevents is not cosmetic: the keypad below is `flex: 1`, so a second line resizes all twelve
+    keys and shifts the grid under a finger that is already moving. Truncating is visibly wrong and
+    harmless; reflowing the dialpad mid-dial is invisibly wrong and makes the user misdial.
+  */
+  white-space: nowrap;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  /* Muted, not danger: the phone still works. A red line here would read as a broken phone. */
+  opacity: 0;
+  transition: opacity 150ms ease-out;
+}
+.cv-dial-outcome[data-shown='true'] {
+  opacity: 1;
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-dial-outcome {
+    transition: none;
+  }
+}
+
+.cv-display {
+  flex: 1;
+  min-width: 0;
+  font: 600 1.75rem var(--cv-font);
+  font-variant-numeric: tabular-nums;
+  letter-spacing: -0.02em;
+  text-align: center;
+  color: var(--cv-text);
+  border: none;
+  background: none;
+  padding: 0;
+  caret-color: var(--cv-accent);
+}
+.cv-display::placeholder { color: var(--cv-faint); font-weight: 400; }
+.cv-display:focus { outline: none; }
+
+/* The spacer/erase pair keeps the number optically centred. */
+.cv-dial-side {
+  width: 36px;
+  height: 36px;
+  flex-shrink: 0;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  border: none;
+  background: none;
+  color: var(--cv-muted);
+  cursor: pointer;
+  border-radius: 999px;
+  transition: color 0.15s ease, opacity 0.15s ease, transform 0.06s ease;
+}
+.cv-dial-side:hover { color: var(--cv-text); }
+.cv-dial-side:active { transform: scale(0.9); }
+.cv-dial-side[data-hidden='true'] { opacity: 0; pointer-events: none; }
+
+/* THE layout fix: the keypad flexes to fill, and its rows share the space equally.
+   Keys must NOT use aspect-ratio — that overflows the shell and shoves the call button
+   under the tab bar. */
+.cv-keypad {
+  flex: 1;
+  min-height: 0;
+  display: grid;
+  grid-template-columns: repeat(3, 1fr);
+  grid-template-rows: repeat(4, 1fr);
+  gap: 8px;
+  padding: 0 1rem;
+}
+.cv-key {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  gap: 1px;
+  border-radius: var(--cv-radius-key);
+  border: 1px solid var(--cv-border);
+  background: var(--cv-bg);
+  box-shadow: var(--cv-shadow);
+  color: var(--cv-text);
+  cursor: pointer;
+  user-select: none;
+  transition: background 0.12s ease, transform 0.06s ease;
+}
+.cv-key:hover { background: var(--cv-surface); }
+.cv-key:active { transform: scale(0.95); background: var(--cv-surface-2); }
+.cv-key b { font: 500 1.25rem/1 var(--cv-font); }
+.cv-key small {
+  font-size: 9px;
+  font-weight: 600;
+  letter-spacing: 0.14em;
+  /* Decorative: the letters carry no information the digit doesn't. `faint`, not `muted`. */
+  color: var(--cv-faint);
+  line-height: 1;
+}
+
+.cv-dial-foot {
+  flex-shrink: 0;
+  display: flex;
+  justify-content: center;
+  padding: 0.75rem 0 1rem;
+}
+
+/* ── Active call ─────────────────────────────────────────────────────────────── */
+.cv-call {
+  flex: 1;
+  min-height: 0;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  gap: 0.15rem;
+  text-align: center;
+  padding: 1rem;
+}
+
+.cv-avatar-wrap { position: relative; margin-bottom: 0.85rem; }
+.cv-avatar {
+  position: relative;
+  width: 68px;
+  height: 68px;
+  border-radius: 999px;
+  /* accent → accent-strong (emerald 600→700): white initials clear 3.77:1 at EVERY stop. Starting
+     the ramp at emerald-500 would look punchier but drop the light end to 2.54:1. */
+  background: linear-gradient(135deg, var(--cv-accent) 0%, var(--cv-accent-strong) 100%);
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  color: #fff;
+  font: 700 1.3rem var(--cv-font);
+  letter-spacing: -0.01em;
+  box-shadow: 0 8px 20px -6px var(--cv-accent-soft);
+}
+/* A soft halo while ringing — the one moment worth animating. */
+.cv-avatar-ping {
+  position: absolute;
+  inset: 0;
+  border-radius: 999px;
+  /* Decorative — nothing sits on it, so it uses the vivid emerald. */
+  background: var(--cv-accent-light);
+  opacity: 0.16;
+  animation: cv-ping 1.6s cubic-bezier(0, 0, 0.2, 1) infinite;
+  pointer-events: none;
+}
+@keyframes cv-ping {
+  0% { transform: scale(1); opacity: 0.22; }
+  80%, 100% { transform: scale(1.7); opacity: 0; }
+}
+.cv-avatar-dot {
+  position: absolute;
+  bottom: 1px;
+  right: 1px;
+  width: 14px;
+  height: 14px;
+  border-radius: 999px;
+  background: var(--cv-accent);
+  border: 2px solid var(--cv-bg);
+}
+
+.cv-call-name { font-size: 1rem; font-weight: 600; line-height: 1.2; }
+.cv-call-number { font-size: 0.75rem; color: var(--cv-muted); margin-top: 2px; }
+
+.cv-timer {
+  display: flex;
+  align-items: baseline;
+  justify-content: center;
+  gap: 1px;
+  margin-top: 0.75rem;
+  color: var(--cv-accent-strong);
+}
+.cv-timer b {
+  font: 700 2.25rem/1 var(--cv-font);
+  font-variant-numeric: tabular-nums;
+  letter-spacing: -0.03em;
+}
+.cv-timer i {
+  font: 300 1.75rem/1 var(--cv-font);
+  font-style: normal;
+  color: var(--cv-accent);
+  animation: cv-blink 1.6s ease-in-out infinite;
+  margin: 0 1px;
+}
+@keyframes cv-blink { 0%, 100% { opacity: 1; } 50% { opacity: 0.35; } }
+
+.cv-call-status {
+  margin-top: 0.6rem;
+  font-size: 0.78rem;
+  color: var(--cv-muted);
+  letter-spacing: 0.04em;
+}
+.cv-badge-hold { color: var(--cv-hold); font-weight: 600; }
+
+/* ── Pre-connect device check (ringing / dialing) ──────────────────────────────
+   Before a call connects there is only ONE other control on screen (Colgar, or
+   Rechazar/Contestar) — putting Dispositivos in that same neighbourhood, even
+   spaced out, keeps it a mis-tap away from hanging up or answering. The entry
+   chip lives beside the call status instead, removing it from that neighbourhood
+   rather than just adding distance within it — same resting-pill SHAPE as `.cv-cp`
+   (CountryPicker), reused rather than invented fresh.
+
+   Opening it does NOT pop a panel into that same tight space, though — this
+   SDK's real production embed (a 310×520 host panel with its own header eating
+   further into that) leaves too little free room around a trigger sitting in
+   vertically-centred content for a floating popover to open into without either
+   overlapping Colgar/Rechazar/Contestar or clamping itself down to something
+   cramped and scrolly for just two rows. `.cv-call-devices-inline` REPLACES the
+   avatar/name/status block in `.cv-call` instead (see that JSX's own comment) —
+   an inline swap, not an overlay, so it gets the full box, not a leftover sliver.
+   ───────────────────────────────────────────────────────────────────────────── */
+.cv-call-devices-chip {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.35rem;
+  height: 26px;
+  padding: 0 0.65rem;
+  border: 1px solid var(--cv-border-strong);
+  border-radius: 999px;
+  background: var(--cv-bg);
+  color: var(--cv-muted);
+  font: 600 0.7rem var(--cv-font);
+  cursor: pointer;
+  transition: background 0.15s ease, border-color 0.15s ease, color 0.15s ease;
+}
+.cv-call-devices-chip:hover { background: var(--cv-surface); }
+.cv-call-devices-chip:active { transform: scale(0.95); }
+
+/*
+  The entry-point row — ONE chip today (Dispositivos), up to two once a host configures
+  `incomingCallAction` (that one first: who is calling outranks a phone-utility setting). `width:
+  100%` + `flex-wrap` on purpose: a host's action label is arbitrary text this component cannot
+  assume is short, so two chips sit side by side when they fit and wrap onto their own centred line
+  when they do not, rather than overflowing `.cv-call`'s fixed width.
+*/
+.cv-call-chips {
+  width: 100%;
+  display: flex;
+  flex-wrap: wrap;
+  justify-content: center;
+  gap: 0.5rem;
+  margin-top: 0.65rem;
+}
+
+.cv-call-devices-inline {
+  width: 100%;
+  display: flex;
+  flex-direction: column;
+  gap: 0.9rem;
+  /* `.cv-call` centres and centre-aligns its normal (avatar) content — rows read left-aligned
+     everywhere else in the widget (Ajustes, the in-call popover), so this opts back out of both. */
+  text-align: left;
+  animation: cv-call-devices-in 0.18s cubic-bezier(0.2, 0, 0.2, 1);
+}
+@keyframes cv-call-devices-in {
+  from { opacity: 0; transform: translateY(6px); }
+  to   { opacity: 1; transform: none; }
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-call-devices-inline { animation: none; }
+}
+.cv-call-devices-header { display: flex; align-items: center; gap: 0.5rem; }
+.cv-call-devices-title { font-size: 0.95rem; font-weight: 600; color: var(--cv-text); }
+/* `--cv-muted` on `--cv-bg` — the same already-verified pairing `.cv-settings-note` uses
+   (4.83:1 light / 6.97:1 dark), not a new one. */
+.cv-call-devices-context {
+  margin: 0;
+  font-size: 0.78rem;
+  color: var(--cv-muted);
+}
+
+/* ── Call controls ───────────────────────────────────────────────────────────
+   TWO TIERS. Hang up is the one action that must never be hunted for, so it sits
+   alone, centred, and largest — the anchor. The secondaries flank above it. They
+   used to share a single row, where hang up was just the last button and carried
+   the same weight as "transfer"; mid-call, that is the wrong hierarchy.
+   ─────────────────────────────────────────────────────────────────────────── */
+.cv-controls {
+  flex-shrink: 0;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  gap: 0.7rem;
+  padding: 0.35rem 1rem 1.1rem;
+  /* The containing block for `.cv-device-popover` — see that rule's own comment for why it is
+     anchored here rather than to the trigger button. */
+  position: relative;
+}
+.cv-controls-row {
+  display: flex;
+  justify-content: center;
+  gap: 1.5rem;
+}
+.cv-controls-primary {
+  display: flex;
+  justify-content: center;
+  gap: 2.75rem;
+}
+/* Button + its word. The column keeps the label from widening the hit target. */
+.cv-ctrl-item {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  gap: 0.3rem;
+}
+/* 10px, muted: present when you look for it, silent when you don't. An icon-only
+   control is a quiz, and mid-call is the worst time to sit one. */
+.cv-ctrl-label {
+  font-size: 0.625rem;
+  line-height: 1;
+  color: var(--cv-muted);
+  white-space: nowrap;
+  user-select: none;
+}
+.cv-ctrl {
+  width: 48px;
+  height: 48px;
+  border-radius: 999px;
+  border: 1px solid var(--cv-border-strong);
+  background: var(--cv-bg);
+  color: var(--cv-text);
+  cursor: pointer;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  transition: background 0.15s ease, color 0.15s ease, transform 0.06s ease;
+}
+.cv-ctrl:hover { background: var(--cv-surface); }
+.cv-ctrl:active { transform: scale(0.94); }
+
+/* The ON states say what they MEAN, in the widget's own tokens: muted is danger,
+   held is hold, transfer-open is accent. Colour is the state, not decoration. */
+.cv-ctrl[data-tone='danger'] {
+  background: var(--cv-danger);
+  border-color: var(--cv-danger);
+  color: #fff;
+}
+.cv-ctrl[data-tone='hold'] {
+  background: var(--cv-hold);
+  border-color: var(--cv-hold);
+  color: #fff;
+}
+.cv-ctrl[data-tone='accent'] {
+  background: var(--cv-accent-soft);
+  border-color: transparent;
+  color: var(--cv-accent-strong);
+}
+.cv-ctrl[data-tone]:hover { filter: brightness(0.95); }
+
+/* Muted is the one state worth animating: it is invisible, it is easy to forget,
+   and the cost of forgetting is talking to nobody. Same halo the avatar rings
+   with — one language, not two. */
+.cv-ctrl[data-tone='danger'] {
+  position: relative;
+}
+.cv-ctrl[data-tone='danger']::after {
+  content: '';
+  position: absolute;
+  inset: 0;
+  border-radius: 999px;
+  background: var(--cv-danger);
+  animation: cv-ping 1.6s cubic-bezier(0, 0, 0.2, 1) infinite;
+  pointer-events: none;
+  z-index: -1;
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-ctrl[data-tone='danger']::after { animation: none; opacity: 0; }
+}
+.cv-ctrl[aria-pressed='true'] {
+  background: var(--cv-text);
+  color: var(--cv-bg);
+  border-color: var(--cv-text);
+}
+
+.cv-transfer {
+  display: flex;
+  gap: 0.5rem;
+  width: 100%;
+  padding: 0.85rem 0.25rem 0;
+}
+
+/*
+  The in-call device quick-switch (SPEC §7 Phase 2 — device management). Same rows as the Ajustes tab
+  (`.cv-settings-row`, via the shared `DevicePickers`), in a popover instead of a page — the call
+  screen already takes over the whole body, so there is no tab bar to reach Ajustes from mid-call.
+
+  Only the in-call state still uses a floating popover — before a call connects, Dispositivos is
+  inline content instead (`.cv-call-devices-inline`, above), not an overlay. Opens UPWARD (`bottom:
+  100%`): the trigger sits at the bottom of the call screen, and there is no room to open downward.
+  Anchored to `.cv-controls`'s own horizontal padding — a container whose width is bounded by ITS
+  parent, never the narrow trigger itself — the same fix CountryPicker's own popover needed (see its
+  comment).
+*/
+.cv-device-popover {
+  position: absolute;
+  z-index: 20;
+  display: flex;
+  flex-direction: column;
+  gap: 0.6rem;
+  padding: 0.7rem;
+  background: var(--cv-surface);
+  border: 1px solid var(--cv-border);
+  border-radius: var(--cv-radius);
+  box-shadow: var(--cv-shadow);
+}
+.cv-device-popover--above {
+  bottom: 100%;
+  left: 1rem;
+  right: 1rem;
+  margin-bottom: 0.6rem;
+  transform-origin: bottom center;
+  animation: cv-device-pop-in-up 0.14s cubic-bezier(0.2, 0, 0.2, 1);
+}
+@keyframes cv-device-pop-in-up {
+  from { opacity: 0; transform: translateY(4px) scale(0.97); }
+  to   { opacity: 1; transform: none; }
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-device-popover--above { animation: none; }
+}
+/* No per-row override needed here: `.cv-settings-row`/`.cv-settings-note` carry no border,
+   background or padding of their own (see the Settings tab block) — this popover's own `gap` and
+   `padding` are the only spacing in play, which is what keeps it lighter than the full Ajustes
+   page's bordered section for what is meant to be a quick, transient panel. */
+
+/* ── Lists (contacts / history) ──────────────────────────────────────────────── */
+.cv-list-head { flex-shrink: 0; padding: 0.85rem 1rem 0.5rem; }
+.cv-search {
+  width: 100%;
+  padding: 0.5rem 0.75rem;
+  border-radius: 10px;
+  border: 1px solid var(--cv-border-strong);
+  background: var(--cv-surface);
+  color: var(--cv-text);
+  font: inherit;
+  transition: border-color 0.15s ease, background 0.15s ease;
+}
+.cv-search::placeholder { color: var(--cv-muted); }
+.cv-search:focus { outline: none; border-color: var(--cv-accent); background: var(--cv-bg); }
+
+/*
+  A wrapper around `.cv-search`, not a change to it — that class is also the transfer-target input
+  in CallScreen, which wants neither an icon nor a clear button. `.cv-search--icon` is an ADDITIVE
+  modifier on the input itself (padding only), so the base class is byte-for-byte what it was for
+  every other consumer.
+*/
+.cv-search-field { position: relative; display: flex; align-items: center; }
+.cv-search--icon { padding-left: 2.15rem; padding-right: 1.85rem; }
+.cv-search-icon {
+  position: absolute;
+  left: 0.75rem;
+  color: var(--cv-muted);
+  pointer-events: none;
+}
+.cv-search-clear {
+  position: absolute;
+  right: 0.5rem;
+  width: 22px;
+  height: 22px;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  border: none;
+  border-radius: 999px;
+  background: none;
+  color: var(--cv-muted);
+  cursor: pointer;
+  transition: color 0.12s ease, transform 0.1s var(--cv-ease-out);
+}
+.cv-search-clear:hover { color: var(--cv-text); }
+.cv-search-clear:active { transform: scale(0.88); }
+
+/* ── Historial filters: status (Todas/Perdidas) + person ─────────────────────── */
+.cv-segmented {
+  display: flex;
+  gap: 2px;
+  padding: 2px;
+  border-radius: 10px;
+  background: var(--cv-surface-2);
+  margin-bottom: 0.4rem;
+}
+.cv-segmented-btn {
+  flex: 1;
+  padding: 0.35rem 0;
+  border: none;
+  border-radius: 8px;
+  background: none;
+  color: var(--cv-muted);
+  font: 600 0.75rem var(--cv-font);
+  cursor: pointer;
+  transition: background 0.15s ease, color 0.15s ease, box-shadow 0.15s ease;
+}
+/* The active segment is stated by its own fill + shadow, not colour alone — the same reasoning
+   `.cv-item-action[data-tone='accent']`'s own comment gives for resting-state colour: a state that
+   only differs by hue must still read on a screen that renders neither. */
+.cv-segmented-btn[aria-selected='true'] {
+  background: var(--cv-bg);
+  color: var(--cv-text);
+  box-shadow: var(--cv-shadow);
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-segmented-btn { transition: none; }
+}
+
+/* The person filter — same combobox SHAPE as `.cv-cp-*` (CountryPicker): a chip opening a positioned
+   popover list with a checkmark on the active row. Not the same CLASSES: the two pickers have nothing
+   to do with each other and sharing a namespace would make a future change to one silently reach the
+   other. */
+.cv-person-filter { position: relative; width: 100%; }
+.cv-person-filter-chip {
+  display: flex;
+  align-items: center;
+  gap: 0.4rem;
+  width: 100%;
+  padding: 0.4rem 0.65rem;
+  border: 1px solid var(--cv-border-strong);
+  border-radius: 10px;
+  background: var(--cv-surface);
+  color: var(--cv-muted);
+  font: 500 0.78rem var(--cv-font);
+  cursor: pointer;
+  transition: background 0.15s ease, border-color 0.15s ease;
+}
+.cv-person-filter-chip:hover { background: var(--cv-surface-2); }
+/*
+  Border only, no fill — the popover opening and the caret rotating already say "this is open";
+  painting the whole width of a wide text pill solid green on top of that was the same over-strong
+  green the selected row had (see its own comment below). A coloured border is the same restrained
+  signal `.cv-search:focus` already uses for "active" elsewhere in this file.
+*/
+.cv-person-filter-chip[aria-expanded='true'] {
+  border-color: var(--cv-accent);
+}
+.cv-person-filter-label {
+  flex: 1;
+  min-width: 0;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+  text-align: left;
+  color: var(--cv-text);
+}
+.cv-person-filter-caret {
+  flex-shrink: 0;
+  transition: transform 0.18s cubic-bezier(0.2, 0, 0.2, 1);
+}
+.cv-person-filter-caret[data-open='true'] { transform: rotate(180deg); }
+.cv-person-filter-pop {
+  position: absolute;
+  top: calc(100% + 6px);
+  left: 0;
+  right: 0;
+  z-index: 20;
+  max-height: 220px;
+  overflow-y: auto;
+  padding: 0.25rem;
+  background: var(--cv-surface);
+  border: 1px solid var(--cv-border);
+  border-radius: var(--cv-radius);
+  box-shadow: var(--cv-shadow);
+  transform-origin: top center;
+  animation: cv-cp-in 0.14s cubic-bezier(0.2, 0, 0.2, 1);
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-person-filter-pop { animation: none; }
+  .cv-person-filter-caret { transition: none; }
+}
+.cv-person-filter-item {
+  width: 100%;
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  padding: 0.45rem 0.5rem;
+  border: none;
+  border-radius: calc(var(--cv-radius) - 4px);
+  background: none;
+  color: var(--cv-text);
+  font: 400 0.8rem var(--cv-font);
+  text-align: left;
+  cursor: pointer;
+}
+.cv-person-filter-item:hover { background: var(--cv-surface-2); }
+/*
+  NOT a solid `--cv-accent-soft` fill — that read as a wall of saturated green across a wide row,
+  much louder than the legacy CRM's own treatment for this exact list (`bg-emerald-50` — a barely-
+  there wash — plus coloured text, never a strong fill). Coloured, bold text + the checkmark carry
+  "selected" instead; `--cv-accent-strong` is already verified elsewhere in this file as AA against
+  `--cv-surface`, which is what this popover sits on.
+*/
+.cv-person-filter-item[aria-selected='true'] .cv-person-filter-name {
+  font-weight: 600;
+  color: var(--cv-accent-strong);
+}
+.cv-person-filter-name {
+  flex: 1;
+  min-width: 0;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+.cv-person-filter-check { color: var(--cv-accent-strong); flex-shrink: 0; }
+.cv-person-filter-check[data-on='false'] { opacity: 0; }
+
+.cv-list {
+  flex: 1;
+  min-height: 0;
+  overflow-y: auto;
+  padding: 0 0.5rem 0.5rem;
+}
+/*
+  Historial's day group header. Sticky within `.cv-list` (its nearest scrolling ancestor — a plain
+  wrapper div between the two does not break that), OPAQUE `--cv-bg` rather than a translucent
+  `/85 + backdrop-blur` treatment: it still needs to fully occlude rows scrolling underneath it, and
+  a flat match to the list's own background does that with no new CSS feature this file doesn't
+  already use elsewhere.
+*/
+.cv-history-day {
+  position: sticky;
+  top: 0;
+  z-index: 1;
+  padding: 0.5rem 0.6rem 0.35rem;
+  background: var(--cv-bg);
+  color: var(--cv-muted);
+  font-size: 0.68rem;
+  font-weight: 600;
+  text-transform: uppercase;
+  letter-spacing: 0.04em;
+}
+.cv-item {
+  display: flex;
+  align-items: center;
+  gap: 0.7rem;
+  padding: 0.5rem;
+  border-radius: 12px;
+  /*
+    NOT `cursor: pointer` — this div has no click handler of its own; only its children
+    (`.cv-item-main`, `.cv-item-action`) do, and each already sets its own pointer cursor. Putting
+    it here too used to make the WHOLE row's box promise a click — its own padding, and the flex
+    `gap` between avatar/name/button — none of which does anything when clicked. Most noticeable
+    right where one row's padding meets the next, which reads as "there's something clickable
+    between these two contacts" when there is not.
+  */
+  transition: background 0.12s ease;
+  text-align: left;
+  width: 100%;
+  border: none;
+  background: none;
+  font: inherit;
+  color: inherit;
+}
+.cv-item:hover { background: var(--cv-surface); }
+.cv-item-avatar {
+  width: 40px;
+  height: 40px;
+  border-radius: 999px;
+  /*
+    RADIAL, not diagonal — deliberately. The initials sit centered, so a radial gradient puts them
+    at its lightest point (pure `--cv-surface`) no matter what, while the edges still darken toward
+    `--cv-surface-2` for the same cheap depth a diagonal gradient gave. A diagonal version measured
+    4.39:1 for `--cv-muted` text at its far corner — under the 4.5:1 text needs — because centered
+    text's exact position against a DIAGONAL gradient depends on glyph width, not just circle size.
+    Centering the gradient on the centered text removes that dependency entirely, structurally,
+    rather than nudging a token and hoping the margin holds. Both stops stay tokens, so this is
+    still theme-correct for free — a hardcoded gray gradient would not adapt to dark mode.
+  */
+  background: radial-gradient(circle, var(--cv-surface), var(--cv-surface-2));
+  /*
+    Without this, the circle's own boundary can vanish: `.cv-item:hover` sets the ROW background to
+    `--cv-surface` — the exact color the gradient above STARTS at (1.00 contrast ratio, i.e.
+    identical) in both themes. `--cv-border-strong` is the same token `.cv-search`'s border already
+    uses against this same surface a few rules up — a pairing already proven visible, not a new one.
+  */
+  border: 1px solid var(--cv-border-strong);
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  color: var(--cv-muted);
+  font-size: 0.78rem;
+  font-weight: 700;
+  flex-shrink: 0;
+}
+/*
+  The Historial row's status chip — WHY a call needs colour at all: direction is already the icon's
+  shape (an arrow in/out), but "did this connect" is not shape-able, and a flat grey circle made every
+  row look identical at a glance. Small badge, not a row-wide fill (that mistake already got made once
+  on the person filter — see its own comment): a 40px circle reads as a status glyph, the same way a
+  colored icon-badge does anywhere else; a wide fill reads as decoration competing with the text next
+  to it. `--danger-strong`/`--accent-strong` (not the plain base tokens) because the base tokens
+  measure BELOW 3:1 non-text contrast against their own `-soft` fill — `--cv-danger` on
+  `--cv-danger-soft` is 2.6:1; `--cv-danger-strong` is 4.47:1 light / 3.62:1 dark, measured.
+*/
+.cv-item-avatar[data-tone='accent'] { background: var(--cv-accent-soft); color: var(--cv-accent-strong); }
+.cv-item-avatar[data-tone='info'] { background: var(--cv-info-soft); color: var(--cv-info-strong); }
+.cv-item-avatar[data-tone='danger'] { background: var(--cv-danger-soft); color: var(--cv-danger-strong); }
+/* A button, reset to look like plain content — the row is a container, not a control. */
+.cv-item-main {
+  flex: 1;
+  min-width: 0;
+  display: block;
+  border: none;
+  background: none;
+  padding: 0;
+  font: inherit;
+  color: inherit;
+  text-align: left;
+  cursor: pointer;
+  transition: transform 0.1s var(--cv-ease-out);
+}
+.cv-item-main:disabled { cursor: default; }
+.cv-item-main:not(:disabled):active { transform: scale(0.985); }
+.cv-item-name {
+  display: block;
+  font-weight: 600;
+  font-size: 0.875rem;
+  white-space: nowrap;
+  overflow: hidden;
+  text-overflow: ellipsis;
+}
+/*
+  14px bold does not clear WCAG's large-text bar (18.66px bold) — this text needs the full 4.5:1, not
+  the 3:1 large-text minimum. `--cv-danger-strong`: 6.47:1 light / 6.46:1 dark against `--cv-bg`,
+  measured; the plain `--cv-danger` this used to be was only 3.76:1 light — a real (if marginal) fail.
+*/
+.cv-item-name[data-tone='danger'] { color: var(--cv-danger-strong); }
+.cv-item-sub {
+  display: block;
+  font-size: 0.72rem;
+  color: var(--cv-muted);
+  margin-top: 1px;
+  font-variant-numeric: tabular-nums;
+}
+.cv-item-sub-outcome { color: var(--cv-danger-strong); }
+/*
+  Decorative reinforcement, not the sole carrier — the row's own play button is what says "this call
+  has a recording" (it only renders when one exists); this is a small hint IN the metadata line that
+  the button is worth pressing, so `--cv-faint` (2.5:1, documented above as decorative-only) is the
+  right tier here, same reasoning `.cv-empty-icon`/`.cv-gate-mark` already use for icons next to real
+  text rather than standing alone.
+
+  `display: inline-flex` is load-bearing, not decoration — every OTHER inline icon in this file gets
+  an explicit `display` for the same reason: `/react` + `/ui` render straight into the host's light
+  DOM (no shadow root), so a host reset like Tailwind Preflight's `svg { display: block }` reaches
+  this element directly. Without an explicit override here, that reset knocks the icon onto its own
+  line instead of trailing the duration text it is meant to sit beside.
+*/
+.cv-item-sub-rec {
+  display: inline-flex;
+  color: var(--cv-faint);
+  margin-left: 0.3rem;
+  vertical-align: -1px;
+}
+.cv-item-action {
+  width: 34px;
+  height: 34px;
+  border-radius: 999px;
+  border: none;
+  background: none;
+  color: var(--cv-muted);
+  cursor: pointer;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  flex-shrink: 0;
+  transition: background 0.12s ease, color 0.12s ease, transform 0.1s var(--cv-ease-out);
+}
+.cv-item-action:hover { background: var(--cv-accent); color: #fff; }
+.cv-item-action:active { transform: scale(0.9); }
+/*
+  The call action specifically (ContactsTab) — NOT History's "play recording", which shares this
+  same class and must stay neutral; a play button has no reason to be accent-colored. Scoped with
+  `data-tone`, the same modifier convention `.cv-ctrl[data-tone]` already uses elsewhere in this file.
+
+  Coloured at REST, not just on hover: a hover-only reveal never fires on a touchscreen, so the one
+  affordance that most needs to read as "you can tap this" would be invisible on exactly the devices
+  a phone widget is likeliest to run on. `accent-strong` is already verified elsewhere in this file
+  as AA on a surface; `accent-soft` is the same hover tint `.cv-ctrl[data-tone='accent']` uses, just
+  transparent at rest so fifty rows of solid fill never turns the list into a wall of green.
+*/
+.cv-item-action[data-tone='accent'] { color: var(--cv-accent-strong); }
+.cv-item-action[data-tone='accent']:hover { background: var(--cv-accent-soft); color: var(--cv-accent-strong); }
+
+@media (prefers-reduced-motion: reduce) {
+  .cv-item-main, .cv-item-action, .cv-search-clear { transition: none; }
+}
+
+.cv-empty {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  height: 100%;
+  color: var(--cv-muted);
+  text-align: center;
+  padding: 2.5rem 1.25rem;
+  font-size: 0.82rem;
+}
+.cv-empty-icon {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  width: 48px;
+  height: 48px;
+  border-radius: 999px;
+  background: var(--cv-surface);
+  color: var(--cv-faint);
+  margin-bottom: 0.75rem;
+}
+.cv-empty-title { margin: 0; font-size: 0.85rem; font-weight: 600; color: var(--cv-muted); }
+/*
+  `--cv-muted`, NOT `--cv-faint` — this file documents faint as "decorative only... never
+  information" (2.5:1, below AA), and this line IS information: it is the reason the list is
+  empty, sometimes echoing the user's own search back to them. `--cv-faint` here measured 2.54:1
+  light / 3.70:1 dark against a 4.5:1 bar — a real failure, not a rounding difference.
+*/
+.cv-empty-sub { margin: 0.2rem 0 0; font-size: 0.75rem; color: var(--cv-muted); }
+.cv-empty-spinner {
+  margin-bottom: 0.75rem;
+  animation: cv-spin 0.8s linear infinite;
+  /* A loading spinner's rotation IS the information, with no static equivalent — unlike this
+     file's other motion, it stays exempt from reduced-motion rather than freezing into a shape
+     that would just look stuck. Colour comes from `.cv-empty`'s own `color: var(--cv-muted)` —
+     the spinner no longer sets its own, now that it sits next to real text instead of standing
+     alone: the icon is decorative reinforcement, same as `.cv-empty-icon`, not the sole carrier. */
+}
+@keyframes cv-spin {
+  to { transform: rotate(360deg); }
+}
+
+/* The scroll-triggered "load more" marker — see `useInfiniteList`. Never visible itself; a small
+   height so it has a real box for the `IntersectionObserver` to track. */
+.cv-list-sentinel {
+  height: 1px;
+}
+.cv-list-loading-more {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  padding: 0.75rem 0 0.25rem;
+  color: var(--cv-muted);
+}
+/* Exempt from reduced-motion for the same reason `.cv-empty-spinner` is — see its own comment. */
+.cv-list-loading-more-spinner {
+  animation: cv-spin 0.8s linear infinite;
+}
+
+/* ── Contact detail (overlays the list) ──────────────────────────────────────── */
+.cv-detail {
+  position: absolute;
+  inset: 0;
+  /* Above the list's own sticky day-group header (`.cv-history-day`, z-index: 1) — otherwise
+     that header's z-index wins the stacking fight wherever its unscrolled flow position happens
+     to land on top of this overlay, and it paints through despite both having an opaque bg. */
+  z-index: 2;
+  display: flex;
+  flex-direction: column;
+  background: var(--cv-bg);
+  animation: cv-detail-in 220ms var(--cv-ease-out) both;
+}
+@keyframes cv-detail-in {
+  from { opacity: 0; transform: translateX(10px); }
+  to   { opacity: 1; transform: none; }
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-detail { animation: none; }
+}
+
+.cv-detail-head { flex-shrink: 0; padding: 0.6rem 0.5rem 0; }
+.cv-detail-back {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.3rem;
+  padding: 0.4rem 0.5rem;
+  border: none;
+  border-radius: 8px;
+  background: none;
+  color: var(--cv-muted);
+  font: 600 0.82rem var(--cv-font);
+  cursor: pointer;
+  transition: color 0.12s ease, transform 0.1s var(--cv-ease-out);
+}
+.cv-detail-back:hover { color: var(--cv-text); }
+.cv-detail-back:active { transform: scale(0.97); }
+
+.cv-detail-body { flex: 1; min-height: 0; overflow-y: auto; padding: 0 1.25rem; }
+.cv-detail-identity {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  text-align: center;
+  padding: 0.75rem 0 1.5rem;
+}
+.cv-detail-avatar {
+  width: 72px;
+  height: 72px;
+  border-radius: 999px;
+  /* Same radial + border treatment as `.cv-item-avatar` (see its own comment), just larger. Neutral
+     by default — a contact has no "status" to colour. `HistoryDetail` overrides both with `[data-tone]`
+     below: a call DOES have one, the same one the list row already shows, so the hero avatar staying
+     grey there would be information the list already gave up on repeating here. */
+  background: radial-gradient(circle, var(--cv-surface), var(--cv-surface-2));
+  border: 1px solid var(--cv-border-strong);
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  color: var(--cv-muted);
+  font-size: 1.35rem;
+  font-weight: 700;
+  margin-bottom: 0.85rem;
+}
+/* Same token pairs already verified for `.cv-item-avatar[data-tone]` — size doesn't change a contrast
+   ratio, so no new numbers to measure here. */
+.cv-detail-avatar[data-tone='accent'] { background: var(--cv-accent-soft); color: var(--cv-accent-strong); border-color: transparent; }
+.cv-detail-avatar[data-tone='info'] { background: var(--cv-info-soft); color: var(--cv-info-strong); border-color: transparent; }
+.cv-detail-avatar[data-tone='danger'] { background: var(--cv-danger-soft); color: var(--cv-danger-strong); border-color: transparent; }
+.cv-detail-name {
+  margin: 0;
+  font-size: 1.1rem;
+  font-weight: 700;
+  color: var(--cv-text);
+  letter-spacing: -0.01em;
+}
+.cv-detail-name[data-tone='danger'] { color: var(--cv-danger-strong); }
+.cv-detail-meta {
+  margin: 0.2rem 0 0;
+  font-size: 0.78rem;
+  color: var(--cv-muted);
+}
+
+/* ── Call detail: recording ───────────────────────────────────────────────── */
+.cv-detail-recording { margin-bottom: 1rem; }
+.cv-detail-recording-label {
+  margin: 0 0 0.4rem;
+  padding: 0 0.15rem;
+  font-size: 0.68rem;
+  font-weight: 600;
+  text-transform: uppercase;
+  letter-spacing: 0.03em;
+  color: var(--cv-muted);
+}
+.cv-detail-audio { width: 100%; display: block; }
+.cv-detail-audio + .cv-detail-audio { margin-top: 0.5rem; }
+.cv-detail-recording-status {
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  margin: 0 0 1rem;
+  padding: 0.65rem 0.75rem;
+  border-radius: 12px;
+  background: var(--cv-surface);
+  color: var(--cv-muted);
+  font-size: 0.78rem;
+}
+/*
+  Text colour only, same neutral `--cv-surface` background the other states use — NOT a
+  `--cv-danger-soft` fill. Measured first, not assumed: `--cv-danger-strong` on `--cv-danger-soft`
+  is 3.34:1 light / 3.62:1 dark, well under the 4.5:1 this 0.78rem text needs (it only ever cleared
+  the SEPARATE 3:1 non-text bar this token was built for — an icon on that badge, not body text on
+  it). Same lesson the person-filter fix already paid for: a badge-strength pairing that works for an
+  icon is not automatically safe for text.
+*/
+.cv-detail-recording-status--warn { color: var(--cv-danger-strong); }
+.cv-detail-recording-spinner { animation: cv-spin 0.8s linear infinite; flex-shrink: 0; }
+
+/* ── Call detail: who handled it ──────────────────────────────────────────── */
+.cv-detail-handlers { display: flex; flex-wrap: wrap; align-items: center; gap: 0.3rem; }
+.cv-detail-handler-hop { display: inline-flex; align-items: center; gap: 0.3rem; }
+.cv-detail-handler-arrow { color: var(--cv-faint); flex-shrink: 0; }
+.cv-detail-handler-chip {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.3rem;
+  padding: 0.15rem 0.5rem;
+  border-radius: 999px;
+  background: var(--cv-surface-2);
+  color: var(--cv-text);
+  font-size: 0.75rem;
+  font-weight: 600;
+}
+/* The LAST hop — the one the call actually ended with — is the one worth a glance first. */
+.cv-detail-handler-chip[data-tone='accent'] { background: var(--cv-accent-soft); color: var(--cv-accent-strong); }
+.cv-detail-handler-ext {
+  font-weight: 400;
+  font-variant-numeric: tabular-nums;
+  opacity: 0.75;
+}
+
+.cv-detail-rows {
+  border: 1px solid var(--cv-border);
+  border-radius: 14px;
+  overflow: hidden;
+  background: var(--cv-bg);
+}
+.cv-detail-row {
+  display: flex;
+  align-items: center;
+  gap: 0.7rem;
+  width: 100%;
+  padding: 0.7rem 0.85rem;
+  border: none;
+  border-top: 1px solid var(--cv-border);
+  background: none;
+  font: inherit;
+  color: inherit;
+  text-align: left;
+}
+.cv-detail-row:first-child { border-top: none; }
+.cv-detail-row--action {
+  cursor: pointer;
+  transition: background 0.12s ease;
+}
+.cv-detail-row--action:hover { background: var(--cv-surface); }
+.cv-detail-row-icon {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  width: 32px;
+  height: 32px;
+  border-radius: 999px;
+  background: var(--cv-surface-2);
+  /*
+    Without this the circle nearly vanishes into its own row: `--cv-surface-2` measures only ~1.1:1
+    against the row's rest-state background and ~1.05:1 against `--cv-surface`, the color
+    `.cv-detail-row--action:hover` sets the ROW to — both far below a readable boundary, and worse
+    than `.cv-item-avatar`/`.cv-detail-avatar` above even manage WITH their border (1.18:1 light /
+    1.57:1 dark). Same token, same fix, same reason.
+  */
+  border: 1px solid var(--cv-border-strong);
+  color: var(--cv-muted);
+  flex-shrink: 0;
+}
+.cv-detail-row-text { flex: 1; min-width: 0; display: flex; flex-direction: column; }
+.cv-detail-row-eyebrow {
+  font-size: 0.68rem;
+  font-weight: 600;
+  text-transform: uppercase;
+  letter-spacing: 0.03em;
+  color: var(--cv-muted);
+}
+.cv-detail-row-value {
+  font-size: 0.85rem;
+  font-weight: 500;
+  color: var(--cv-text);
+  white-space: nowrap;
+  overflow: hidden;
+  text-overflow: ellipsis;
+}
+.cv-detail-row-chevron { color: var(--cv-faint); flex-shrink: 0; }
+
+.cv-detail-foot { flex-shrink: 0; padding: 0.85rem 1.25rem 1.1rem; }
+.cv-detail-call { width: 100%; display: flex; align-items: center; justify-content: center; gap: 0.4rem; }
+
+/* ── Settings tab (device selection, SPEC §7 Phase 2) ──────────────────────────── */
+.cv-settings-body {
+  flex: 1;
+  min-height: 0;
+  overflow-y: auto;
+  padding: 1rem;
+  display: flex;
+  flex-direction: column;
+  /* Generous separation BETWEEN sections, deliberately larger than any gap inside one — grouping
+     only reads as grouping if the space between groups is clearly bigger than the space within one
+     (see impeccable's layout guidance: "tight grouping, generous separation"). */
+  gap: 1.5rem;
+}
+
+/*
+  One labeled group (`SettingsSection`): a title, and a bordered body holding its rows. Ajustes
+  started as a flat list of two rows with nothing to say they were related — fine for exactly two
+  rows, unreadable the moment an unrelated third setting lands with nothing to tell it apart from
+  the device rows above it.
+
+  The body is ONE card, not a card per row: `.cv-settings-row`/`.cv-settings-note` below carry no
+  border or background of their own, only a divider between siblings — the same shape
+  `.cv-detail-rows`/`.cv-detail-row` already use elsewhere in this file, and deliberately not a
+  stack of individually-bordered cards (nested-card territory).
+*/
+.cv-settings-section { display: flex; flex-direction: column; gap: 0.5rem; }
+.cv-settings-section-title {
+  margin: 0;
+  padding: 0 0.2rem;
+  font-size: 0.7rem;
+  font-weight: 700;
+  text-transform: uppercase;
+  letter-spacing: 0.04em;
+  color: var(--cv-muted);
+}
+.cv-settings-section-body {
+  border: 1px solid var(--cv-border);
+  border-radius: 14px;
+  background: var(--cv-bg);
+  overflow: hidden;
+}
+.cv-settings-section-body > * { padding: 0.75rem 0.85rem; }
+.cv-settings-section-body > *:not(:first-child) { border-top: 1px solid var(--cv-border); }
+
+.cv-settings-row { display: flex; align-items: center; gap: 0.7rem; }
+/* Same treatment as `.cv-detail-row-icon`, same reason — see its own comment on why the border is
+   load-bearing: `--cv-surface-2` alone nearly vanishes into the section's own background. */
+.cv-settings-row-icon {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  width: 32px;
+  height: 32px;
+  border-radius: 999px;
+  background: var(--cv-surface-2);
+  border: 1px solid var(--cv-border-strong);
+  color: var(--cv-muted);
+  flex-shrink: 0;
+}
+.cv-settings-row-text { flex: 1; min-width: 0; display: flex; flex-direction: column; gap: 0.35rem; }
+/* Same pairing as `.cv-detail-row-eyebrow` (`--cv-muted` on `--cv-bg`), verified there already. */
+.cv-settings-row-label {
+  font-size: 0.68rem;
+  font-weight: 600;
+  text-transform: uppercase;
+  letter-spacing: 0.03em;
+  color: var(--cv-muted);
+}
+.cv-settings-select {
+  width: 100%;
+  padding: 0.45rem 0.6rem;
+  border-radius: 8px;
+  border: 1px solid var(--cv-border-strong);
+  background: var(--cv-surface);
+  color: var(--cv-text);
+  font: inherit;
+  font-size: 0.85rem;
+  transition: border-color 0.15s ease, background 0.15s ease;
+}
+.cv-settings-select:focus { outline: none; border-color: var(--cv-accent); background: var(--cv-bg); }
+.cv-settings-empty { font-size: 0.85rem; color: var(--cv-muted); }
+/* `--cv-muted` on `--cv-bg` — 4.83:1 light / 6.97:1 dark, computed fresh for THIS pairing (the note
+   used to sit on `--cv-surface` with its own card; now it sits directly on the section's `--cv-bg`,
+   a different background that earns its own check rather than inheriting the old one's number). */
+.cv-settings-note {
+  margin: 0;
+  color: var(--cv-muted);
+  font-size: 0.8rem;
+  line-height: 1.5;
+}
+/* Closing note for the tab as a whole, not any one section — sits directly on `.cv-settings-body`,
+   which shares the same `--cv-bg` as `.cv-settings-section-body` above, so the `--cv-muted`-on-
+   `--cv-bg` pairing already verified for `.cv-settings-note` carries over unchanged. Centred and
+   quieter than a row: this is a footnote about the tab, not a row's worth of content. */
+.cv-settings-more {
+  margin: 0;
+  padding: 0 0.5rem;
+  text-align: center;
+  color: var(--cv-muted);
+  font-size: 0.78rem;
+  line-height: 1.5;
+}
+
+/* ── Centred states (mic gate) ───────────────────────────────────────────────── */
+.cv-center {
+  flex: 1;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  gap: 0.85rem;
+  padding: 1.75rem;
+  text-align: center;
+}
+.cv-center p { color: var(--cv-muted); margin: 0; font-size: 0.85rem; line-height: 1.5; }
+
+
+/* "Cómo permitirlo" — a native <details> disclosure.
+   Collapsed by default: the people who already know where the padlock is should not have to read
+   past three steps to get there, and the people who don't get them without leaving the app. */
+.cv-help {
+  width: 100%;
+  margin-top: 0.15rem;
+  text-align: left;
+}
+.cv-help summary {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.3rem;
+  justify-content: center;
+  width: 100%;
+  padding: 0.3rem;
+  border-radius: 8px;
+  color: var(--cv-muted);
+  font: 500 0.75rem var(--cv-font);
+  cursor: pointer;
+  list-style: none; /* hide the default triangle; the icon is the affordance */
+  transition: color 0.15s ease, background 0.15s ease;
+}
+.cv-help summary::-webkit-details-marker { display: none; }
+.cv-help summary:hover { color: var(--cv-text); background: var(--cv-surface-2); }
+.cv-help[open] summary { color: var(--cv-text); margin-bottom: 0.35rem; }
+
+.cv-help ol {
+  margin: 0;
+  padding: 0.6rem 0.7rem 0.6rem 1.6rem;
+  background: var(--cv-surface);
+  border-radius: 10px;
+  color: var(--cv-muted);
+  font-size: 0.73rem;
+  line-height: 1.55;
+}
+.cv-help li + li { margin-top: 0.3rem; }
+.cv-help li::marker { color: var(--cv-faint); font-variant-numeric: tabular-nums; }
+
+.cv-help a {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.25rem;
+  margin-top: 0.45rem;
+  padding-left: 0.1rem;
+  color: var(--cv-accent-strong);
+  font-size: 0.73rem;
+  font-weight: 500;
+  text-decoration: none;
+}
+.cv-help a:hover { text-decoration: underline; }
+
+/* The panel is the only thing that moves, and only when opened by hand — so it animates. */
+.cv-help[open] ol {
+  animation: cv-gate-in 200ms var(--cv-ease-out) both;
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-help[open] ol { animation: none; }
+}
+
+/* ── The permission gate ─────────────────────────────────────────────────────
+   Four states, and only ONE of them deserves a designed screen.
+
+   `checking` resolves in ~100–400 ms. Rendering it immediately means the user
+   sees text appear and vanish inside a blink — a flash reads as jank, not as
+   information. So it is delayed 450 ms with `both` fill: invisible during the
+   delay, and if the check finishes first (the usual case, and always the case
+   when permission is already granted) it is never painted at all.
+
+   `prompting` is the one the user actually reads and acts on. It gets the
+   hierarchy: mark, title, reason, action.
+   ─────────────────────────────────────────────────────────────────────────── */
+.cv-gate {
+  flex: 1;
+  min-height: 0;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  justify-content: center;
+  gap: 0.6rem;
+  padding: 1.5rem 1.75rem;
+  text-align: center;
+}
+
+/* The disc echoes the call avatar — one visual language, not two. */
+.cv-gate-mark {
+  display: grid;
+  place-items: center;
+  width: 52px;
+  height: 52px;
+  border-radius: 999px;
+  background: var(--cv-accent-soft);
+  color: var(--cv-accent-strong);
+  margin-bottom: 0.15rem;
+}
+.cv-gate[data-tone='danger'] .cv-gate-mark {
+  background: var(--cv-danger-soft);
+  color: var(--cv-danger);
+}
+
+.cv-gate-title {
+  margin: 0;
+  font: 600 0.95rem var(--cv-font);
+  color: var(--cv-text);
+  letter-spacing: -0.01em;
+}
+.cv-gate p {
+  margin: 0;
+  color: var(--cv-muted);
+  font-size: 0.8rem;
+  line-height: 1.5;
+  max-width: 24ch; /* two comfortable lines, not one long one */
+}
+.cv-gate .cv-btn { margin-top: 0.5rem; }
+
+/* Entrance. Staggered 45 ms apart: the eye follows mark → title → reason →
+   action, which is the order it needs to read them in anyway. */
+.cv-gate > * {
+  animation: cv-gate-in 260ms var(--cv-ease-out) both;
+}
+.cv-gate > *:nth-child(2) { animation-delay: 45ms; }
+.cv-gate > *:nth-child(3) { animation-delay: 90ms; }
+.cv-gate > *:nth-child(4) { animation-delay: 135ms; }
+
+@keyframes cv-gate-in {
+  from { opacity: 0; transform: translateY(6px); }
+  to   { opacity: 1; transform: none; }
+}
+
+/* The checking state: held back, then a quiet fade. No stagger, no movement —
+   it is a status, not a screen, and it should barely register. */
+.cv-gate[data-state='checking'] > *,
+.cv-gate[data-state='warming'] > * {
+  animation: cv-gate-wait 200ms var(--cv-ease-out) 450ms both;
+}
+@keyframes cv-gate-wait {
+  from { opacity: 0; }
+  to   { opacity: 1; }
+}
+/* A slow breath rather than a spinner: a spinner promises a long wait, and this
+   is not one. */
+.cv-gate[data-state='checking'] .cv-gate-mark,
+.cv-gate[data-state='warming'] .cv-gate-mark {
+  background: var(--cv-surface-2);
+  color: var(--cv-muted);
+  animation: cv-gate-wait 200ms var(--cv-ease-out) 450ms both,
+             cv-breathe 1.8s ease-in-out 450ms infinite;
+}
+@keyframes cv-breathe {
+  0%, 100% { opacity: 1; }
+  50%      { opacity: 0.45; }
+}
+
+/* Reduced motion: keep the fade and — critically — keep the DELAY, which is
+   timing rather than motion and is the whole point. Drop the travel. */
+@media (prefers-reduced-motion: reduce) {
+  .cv-gate > * {
+    animation: cv-gate-wait 200ms var(--cv-ease-out) both;
+  }
+  .cv-gate[data-state='checking'] .cv-gate-mark,
+  .cv-gate[data-state='warming'] .cv-gate-mark {
+    animation: cv-gate-wait 200ms var(--cv-ease-out) 450ms both;
+  }
+}
+
+@media (prefers-reduced-motion: reduce) {
+  .cv-avatar-ping,
+  .cv-timer i { animation: none; }
+  .cv-softphone *,
+  .cv-softphone *::before { transition-duration: 0.01ms !important; }
+}
+
+/* `*` and `#` stay in the grid — a keypad without them is not a keypad — but they are not part of a
+   number (toE164 keeps digits only). Dimmed rather than `disabled` so the grid still reads as a
+   keypad and the glyphs stay legible; they become live DTMF on the in-call screen. */
+.cv-key[data-dialable='false'] {
+  cursor: default;
+}
+.cv-key[data-dialable='false'] b {
+  color: var(--cv-faint);
+}
+.cv-key[data-dialable='false']:hover {
+  background: none;
+}
+.cv-key[data-dialable='false']:active {
+  transform: none;
+}
+
+/* ── Country picker ──────────────────────────────────────────────────────────
+   The prefix chip + its list. Sits where the old left spacer was, so the number
+   stays optically centred against the 36px erase button on the right.
+
+   The popover is absolutely positioned inside the widget rather than portalled:
+   there is nowhere to portal TO inside a shadow root, and the widget already owns
+   its stacking context. That also means it cannot be clipped by a host's
+   `overflow:hidden` — the failure SPEC §2.6 lists for the CRM's Radix version.
+   ──────────────────────────────────────────────────────────────────────────── */
+/* The anchor spans the whole ROW, not just the chip.
+   With the chip centred, anchoring to the chip put the popover's left edge at ~120px and its right
+   edge past the widget — clipped by `.cv-softphone { overflow: hidden }`, which is the classic
+   absolute-inside-overflow bug. Anchoring to the full row makes overflowing arithmetically
+   impossible: `left:0; right:0` cannot be wider than the row that contains it. */
+.cv-cp {
+  position: relative;
+  display: flex;
+  justify-content: center;
+  width: 100%;
+}
+/* A PILL, with a resting surface and a border.
+   This was `border: none; background: none` — invisible until hover, so it read as a label rather
+   than a control. That was survivable when it sat inline beside the number; alone on its own row it
+   is just floating text, and nothing says "you can change this". A control that changes state has to
+   look like one at rest, not only under a cursor that may never arrive (touch has no hover at all). */
+.cv-cp-chip {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.3rem;
+  height: 30px;
+  padding: 0 0.5rem 0 0.4rem;
+  border: 1px solid var(--cv-border-strong);
+  border-radius: 999px;
+  background: var(--cv-surface);
+  color: var(--cv-text);
+  font: 600 0.8rem var(--cv-font);
+  cursor: pointer;
+  transition: background 0.15s, border-color 0.15s;
+}
+.cv-cp-chip:hover { background: var(--cv-surface-2); }
+.cv-cp-chip:active { transform: scale(0.95); }
+/* Open: the chip is the thing the list belongs to, so it stays visibly engaged while the list is up. */
+.cv-cp-chip[aria-expanded='true'] {
+  background: var(--cv-accent-soft);
+  border-color: var(--cv-accent);
+}
+.cv-cp-dial {
+  font-variant-numeric: tabular-nums;
+  letter-spacing: -0.02em;
+}
+.cv-cp-caret {
+  color: var(--cv-faint);
+  flex-shrink: 0;
+  transition: transform 0.18s cubic-bezier(0.2, 0, 0.2, 1);
+}
+.cv-cp-caret[data-open='true'] { transform: rotate(180deg); }
+
+/* The country mark. TWO designed states in ONE 20×14 box (a flag's own 3:2), so the chip and every
+   row keep their rhythm whichever is showing — nothing reflows when the flags land. The plate is the
+   LOADING state (flags are a lazy import) and the offline state, not a fallback: there is no flash of
+   something broken, only a designed plate becoming a designed flag, once per session.
+   `::part(country-mark)` lets a host restyle either. */
+.cv-mark {
+  width: 20px;
+  height: 14px;
+  flex-shrink: 0;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  font-size: 14px;
+  line-height: 1;
+  font-family: 'Apple Color Emoji', 'Segoe UI Emoji', 'Noto Color Emoji', var(--cv-font);
+}
+/* The SVG fills the slot exactly; 3x2 is the flag aspect, so nothing is letterboxed or cropped. */
+.cv-mark-svg {
+  width: 100%;
+  height: 100%;
+  display: block;
+  border-radius: 2px;
+  object-fit: cover;
+}
+.cv-mark[data-plate='true'] {
+  /* The ISO code set into the slot a flag will occupy. */
+  font-family: var(--cv-font);
+  font-size: 8.5px;
+  font-weight: 700;
+  letter-spacing: 0.04em;
+  color: var(--cv-text);
+  background: var(--cv-surface-2);
+  border: 1px solid var(--cv-border);
+  border-radius: 3px;
+  /* Cap-height letters sit optically high in a 14px box; nudge them back to centre. */
+  padding-top: 1px;
+}
+
+.cv-cp-pop {
+  position: absolute;
+  top: calc(100% + 6px);
+  /* Pinned to BOTH row edges, so it is bounded by the container by construction — no width guess,
+     no media query, nothing to clip. `max-width` keeps it from looking stretched on a wide host. */
+  left: 0;
+  right: 0;
+  margin-inline: auto;
+  max-width: 260px;
+  z-index: 20;
+  display: flex;
+  flex-direction: column;
+  background: var(--cv-surface);
+  border: 1px solid var(--cv-border);
+  border-radius: var(--cv-radius);
+  box-shadow: var(--cv-shadow);
+  overflow: hidden;
+  /* Grows from the chip it belongs to, rather than appearing on top of it. */
+  transform-origin: top center;
+  animation: cv-cp-in 0.14s cubic-bezier(0.2, 0, 0.2, 1);
+}
+@keyframes cv-cp-in {
+  from { opacity: 0; transform: translateY(-4px) scale(0.97); }
+  to   { opacity: 1; transform: none; }
+}
+@media (prefers-reduced-motion: reduce) {
+  .cv-cp-pop { animation: none; }
+  .cv-cp-caret { transition: none; }
+}
+.cv-cp-search {
+  flex-shrink: 0;
+  padding: 0.5rem 0.65rem;
+  border: none;
+  border-bottom: 1px solid var(--cv-border);
+  background: none;
+  color: var(--cv-text);
+  font: 400 0.8rem var(--cv-font);
+  outline: none;
+}
+.cv-cp-search::placeholder { color: var(--cv-faint); }
+/* Both states named explicitly. In the CRM the widget mounts via `/ui`, i.e. in the LIGHT DOM — none
+   of the shadow-DOM isolation the web-component playground proves applies there, so a host's focus
+   ring (or the browser's own) can land on our input. The accent underline IS the focus indicator. */
+.cv-cp-search:focus,
+.cv-cp-search:focus-visible {
+  outline: none;
+  border-bottom-color: var(--cv-accent);
+  border-bottom-width: 2px;
+  padding-bottom: calc(0.5rem - 1px);
+}
+.cv-cp-list {
+  overflow-y: auto;
+  max-height: 220px;
+  padding: 0.25rem;
+}
+.cv-cp-item {
+  width: 100%;
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  padding: 0.4rem 0.45rem;
+  border: none;
+  border-radius: calc(var(--cv-radius) - 4px);
+  background: none;
+  color: var(--cv-text);
+  font: 400 0.8rem var(--cv-font);
+  text-align: left;
+  cursor: pointer;
+}
+.cv-cp-item:hover { background: var(--cv-surface-2); }
+/* The current country is stated by the row, not only by a tick at the far right. */
+.cv-cp-item[aria-selected='true'] { background: var(--cv-accent-soft); }
+.cv-cp-item[aria-selected='true'] .cv-cp-name { font-weight: 600; }
+.cv-cp-name {
+  flex: 1;
+  min-width: 0;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+.cv-cp-item .cv-cp-dial {
+  color: var(--cv-muted);
+  font-weight: 400;
+}
+.cv-cp-check { color: var(--cv-accent-strong); flex-shrink: 0; }
+.cv-cp-check[data-on='false'] { opacity: 0; }
+.cv-cp-empty {
+  margin: 0;
+  padding: 1rem 0.5rem;
+  text-align: center;
+  color: var(--cv-muted);
+  font-size: 0.78rem;
+}