@dbx-tools/ui-branding 0.6.217 → 0.6.219

package/README.md

@@ -67,11 +67,13 @@ default AppKit renders untouched.
 </BrandProvider>
 ```
 
-The bridge is **identity-only** (primary/accent/ring/sidebar-primary + fonts). It
-intentionally does not remap neutrals (`--background`/`--foreground`/`--muted`/
-`--border`) because a `BrandContext` carries a single light palette — remapping
-neutrals would disable dark mode. Add new semantic tokens to re-skin in
-`brand-bridge.css`.
+The bridge is **identity-only** (primary/ring/sidebar-primary + fonts). Selected
+menus, rows, and tabs receive a subtle `primaryHover` tint rather than a brand
+accent, so default navigation stays cool blue instead of reading as coral/red or
+success green. It intentionally leaves neutrals (`--background`/`--foreground`/
+`--muted`/`--border`) and status tokens (`--success`/`--warning`/
+`--destructive`) to AppKit because those values must remain theme-aware. Add new
+semantic tokens to re-skin in `brand-bridge.css`.
 
 ## Assets
 

package/index.ts

@@ -3,7 +3,7 @@
 // Hand edits are overwritten on the next watch; this file is read-only.
 
 export const PACKAGE_IDENTIFIER = "@dbx-tools/ui-branding";
-export const PACKAGE_VERSION = "0.6.217";
+export const PACKAGE_VERSION = "0.6.219";
 export * as browser from "./src/browser.ts";
 export * as generatedAssets from "./src/generated/assets.ts";
 export * as reactBrand from "./src/react/brand.tsx";

package/package.json

@@ -31,13 +31,13 @@
     "react-dom": "~19.2.4"
   },
   "dependencies": {
-    "@dbx-tools/shared-core": "0.6.217"
+    "@dbx-tools/shared-core": "0.6.219"
   },
   "license": "Apache-2.0",
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.6.217",
+  "version": "0.6.219",
   "type": "module",
   "exports": {
     "./react": "./src/react/index.ts",

package/src/brand-bridge.css

@@ -35,15 +35,16 @@
    * in `ThreadSidebar`, which styles off `bg-accent text-accent-foreground`, was
    * the worst of it.
    *
-   * So tint rather than replace: a low percentage of the brand accent mixed into
-   * the CURRENT `--background`. Because `--background` is a neutral this bridge
-   * deliberately leaves to AppKit, the mix follows the active theme on its own -
-   * a pale wash in light mode, a deep one in dark - which keeps AppKit's own
-   * per-theme `--accent-foreground` (near-black / near-white) readable against
-   * it. That is also why `--accent-foreground` is NOT set here: pinning it would
-   * break whichever theme it was not chosen for.
+   * Menus, selected rows, and tabs are navigation, not success or identity
+   * signals. Tint them with the cooler primary-hover color rather than the
+   * identity accent so the default brand produces a quiet blue wash instead of
+   * coral/red or success green. Mixing into the CURRENT `--background` follows
+   * the active theme on its own - pale in light mode and deep in dark mode -
+   * while AppKit's per-theme `--accent-foreground` remains readable. That is
+   * also why `--accent-foreground` is NOT set here: pinning it would break
+   * whichever theme it was not chosen for.
    */
-  --accent: color-mix(in oklab, var(--brand-color-accent) 18%, var(--background));
+  --accent: color-mix(in oklab, var(--brand-color-primary-hover) 12%, var(--background));
   --sidebar-primary: var(--brand-color-primary);
   --sidebar-primary-foreground: var(--brand-color-background);
   --sidebar-ring: var(--brand-color-primary);

package/src/styles.css

@@ -1,6 +1,6 @@
 :root {
-  --brand-color-primary: #ff3621;
-  --brand-color-primary-hover: #98102a;
+  --brand-color-primary: #1b3139;
+  --brand-color-primary-hover: #0e538b;
   --brand-color-accent: #00a972;
   --brand-color-foreground: #1b3139;
   --brand-color-background: #ffffff;