@vegastack/design-tokens 0.7.45 → 0.7.49

package/dist/base.css

@@ -6,6 +6,9 @@
 
      FOC-1   one global :focus-visible cue; components restate nothing
      FOC-13  no focus rings anywhere, Tabs included: the cue is a background tint (MK 2026-09-25)
+     FOC-14  a border never changes colour on focus or while active (MK 2026-09-26), EXCEPT text
+             entry, which darkens its border subtly with an ease (MK 2026-09-27); invalid keeps its
+             destructive border in every state
      FOC-7   the forced-colours fallback for text entry
      MOT-5   the reduced-motion reset (and the one sanctioned !important)
      INT-1   the hand cursor, on a wider selector list than shadcn's --pointer rule
@@ -60,14 +63,22 @@
     @apply font-sans;
   }
 
-  /* FOC-1 + FOC-13 — the SINGLE focus affordance in the system, and it is NOT a ring.
-     No focus ring anywhere, Tabs included (MK 2026-09-25): a keyboard user sees a subtle background
+  /* FOC-1 + FOC-13 + FOC-14 — the SINGLE focus affordance in the system, and it is NOT a ring.
+     No focus ring anywhere, Tabs included (MK 2026-09-25). A keyboard user sees a subtle background
      TINT — `accent` at 50%, laid over whatever fill the control already has as a background IMAGE,
-     so a primary button, a chip, a row and a menu item all show it without any component
-     restating it. Text entry (text inputs, textarea, contenteditable) keeps its border tint
-     (FOC-3) and takes no fill. Tab triggers and panels take the same tint as everything else. Components carry no focus ring of their
-     own (FOC-6), and `design-lint`'s `no-focus-ring-glow` rule rejects any focus ring or outline
-     class, so one cannot creep back through a later upstream pull.
+     so a primary button, a chip, a row, a tab and a menu item all show it without any component
+     restating it. A border never changes colour on focus or while a control is active (MK
+     2026-09-26) — with ONE exception, text entry (MK 2026-09-27).
+
+     Text entry (FOC-3) — text inputs, textarea, and the bordered field GROUPS that frame one
+     (InputGroup, NumberField, ChipInput, the combobox chips, the panel search row) — takes NO fill
+     at all: it is excluded below, and its focus cue is a subtle darker border (`border-ring/40`)
+     that eases in over 150ms, written on the component that draws the border (the group, not the
+     control inside it, which has no border and no fill). An invalid field keeps its destructive
+     border in every state; focus never replaces it. The one caret-only surface is a contenteditable
+     document editor (TextEdit, `data-focus-cue="caret"`): no border, no fill, the caret is the cue.
+     Components carry no focus ring of their own (FOC-6); `design-lint`'s `no-focus-ring-glow` and
+     `no-focus-border` rules reject a ring anywhere and a focus border outside the text-entry set.
 
      Programmatic focus targets (`tabindex="-1"`) take no tint: AppShell's skip-link `<main>`, Base UI
      popups, a step heading focus is moved to. They are not tab stops, and each is a whole region.
@@ -136,9 +147,9 @@
     outline-offset: 1px;
   }
 
-  /* Text-entry focus (FOC-3). Every text-entry control signals focus with a border TINT and strips
-     the outline, because a raw text field cannot tell mouse from keyboard. Forced colours replaces
-     `border-color` outright, so the tint vanishes and `outline-style: none` stays in force — a
+  /* Text-entry focus (FOC-3). Every text-entry control signals focus with a subtle border change
+     and strips the outline, because a raw text field cannot tell mouse from keyboard. Forced colours
+     replaces `border-color` outright, so the cue vanishes and `outline-style: none` stays in force — a
      Windows High Contrast user had no caret location at all. This block is UNLAYERED on purpose:
      it beats the component's `outline-none` (a layered utility) regardless of specificity, so the
      fallback is written ONCE here, never per component.
@@ -160,8 +171,9 @@
      so its addons follow the rounded corner. The inner input's own outline is offset outward INTO
      that clip, so it was drawn and then cut, which is how an addon field ended up with no visible
      focus at all under the forced palette. The group carries the outline (it is the element whose
-     border the tint would have moved); the control inside it stands down, so the two never paint a
-     double ring. */
+     border darkens on focus); the control inside it stands down, so the two never paint a double
+     ring. The stand-down is (0,2,1) and beats both `input:focus` (0,1,1) and the `:focus-visible`
+     outline above (0,1,0). */
   [data-field-group] input:focus,
   [data-field-group] textarea:focus {
     outline: none;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vegastack/design-tokens",
-  "version": "0.7.45",
+  "version": "0.7.49",
   "description": "VegaStack design tokens (DTCG → Tailwind v4 theme + TS)",
   "license": "MIT",
   "repository": {