@kolkrabbi/kol-component 0.186.0 → 0.187.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolkrabbi/kol-component",
-  "version": "0.186.0",
+  "version": "0.187.0",
   "description": "KOL design-system components — atoms through organisms, emitting canonical kol-* classes. Pairs with @kolkrabbi/kol-theme for styling.",
   "license": "MIT",
   "type": "module",

package/src/hooks/colorMath.js

@@ -104,6 +104,37 @@ export function harmonyColors(hue, harmony, { saturation = 100, lightness = 50 }
   return roleOffsets.map((off) => hslToHex(normHue(hue + off), saturation, lightness))
 }
 
+/**
+ * Re-hue an EXISTING palette to a harmony, preserving each slot's own
+ * saturation and lightness.
+ *
+ * `harmonyColors` builds every role at ONE flat S/L, which is right when a
+ * caller has no palette yet and wrong the moment it does: a Light slot and a
+ * Dark slot both come back at 50% lightness, so the palette flattens on the
+ * first drag of the wheel (kol-fxr, `editor-set-is-behind-its-source`
+ * 2026-09-03 — its own wheel emits a hue and re-hues slot by slot, so the
+ * package's `colors` payload was half-ignorable).
+ *
+ * A slot that is `locked`, empty, or has no hex is passed through untouched —
+ * locking a colour is the one instruction a re-hue must not overrule.
+ *
+ * @param {number} hue base hue, 0–360
+ * @param {string|object} harmony harmony id or object
+ * @param {Array<{hex?: string, locked?: boolean}|string|null>} slots the current palette, in role order
+ * @returns {Array} the same shape back, re-hued — strings stay strings, objects keep every other key
+ */
+export function reHueSlots(hue, harmony, slots = []) {
+  const { roleOffsets } = harmonyById(harmony)
+  return slots.map((slot, i) => {
+    const off = roleOffsets[i % roleOffsets.length]
+    const hex = typeof slot === 'string' ? slot : slot?.hex
+    if (!hex || (typeof slot === 'object' && slot?.locked)) return slot
+    const { s, l } = hexToHsl(hex)
+    const next = hslToHex(normHue(hue + off), s, l)
+    return typeof slot === 'string' ? next : { ...slot, hex: next }
+  })
+}
+
 /**
  * Deterministic role colors derived from a base hex (S/L taken from the hex).
  * Convenience wrapper over `harmonyColors` for callers holding a color, not

package/src/molecules/Dropdown.jsx

@@ -3,7 +3,7 @@ import { toneClass, TONE_VARS } from '../utilities/tone.js'
 import { Icon } from '@kolkrabbi/kol-icons'
 import { MenuDropdownItem } from './MenuItem.jsx'
 import { PopoverPanel, usePopover } from '../utilities/Popover.jsx'
-import { indicatorSize } from '../hooks/glyphLadders.js'
+import { glyphSize, indicatorSize } from '../hooks/glyphLadders.js'
 
 /**
  * Dropdown — trigger IS button chrome (2026-07-08 chrome law).
@@ -77,6 +77,18 @@ const Dropdown = ({
    * while a row is hovered would otherwise leave the consumer previewing
    * forever. It never fires while closed — a closed dropdown has no rows. */
   onOptionHover,
+  /* ICON-ONLY TRIGGER — an icon name, or a pre-rendered node dropped in where
+   * the glyph goes. The trigger becomes the pinned square (`kol-btn-icon`) at
+   * the current size, with no label, no ghost widths and no caret; the panel
+   * still sizes to its own rows rather than the trigger. This is what a tool
+   * rail needs, and its absence is why kol-fxr's ToolPalette hand-rolls a
+   * trigger out of `PopoverPanel` + `usePopover` at a bespoke 36/22 instead of
+   * importing anything (`editor-set-is-behind-its-source`, 2026-09-03). */
+  iconOnly,
+  /* A mark drawn INSIDE the trigger box, over the glyph — the tool-palette
+   * corner fold is the case. Kept a slot rather than a boolean so the square
+   * has one implementation and the drawing stays the caller's. */
+  triggerAdornment,
   defaultOpen = false,
   className = ''
 }) => {
@@ -163,6 +175,12 @@ const Dropdown = ({
     `kol-btn-${resolvedSize}`,
     SIZE_TYPE[resolvedSize],
     'kol-dd-trigger',
+    /* ICON-ONLY: the pinned square from Button's own class, so a tool-rail
+     * dropdown is the same box as the icon button beside it at every rung
+     * (editor-set-is-behind-its-source, kol-fxr 2026-09-03 — its ToolPalette
+     * hand-rolls a trigger out of PopoverPanel + usePopover precisely because
+     * this mode did not exist). No label, no ghost widths, no caret. */
+    iconOnly && 'kol-btn-icon kol-dd-trigger--icon',
     isOpen && 'kol-dd-trigger--open',
     /* the dark chip on a washed plane; the panel continues it (ControlToneInverse, 2026-08-27) */
     toneClass(tone),
@@ -179,20 +197,33 @@ const Dropdown = ({
         aria-expanded={isOpen}
         data-state={isOpen ? 'open' : 'closed'}
       >
-        {/* every option's label rides along hidden so the trigger is as wide
-          * as its widest value — the panel matches the trigger's width, so
-          * trigger and list stay one piece at every selection */}
-        <span className="kol-dd-label">
-          <span>{currentOption?.label}</span>
-          {options.map((option) => (
-            <span key={option.value} className="kol-dd-ghost" aria-hidden="true">
-              {option.label}
+        {iconOnly ? (
+          /* the glyph comes from the SOLO ladder — an icon alone in a pinned
+           * square — never from a call-site number */
+          typeof iconOnly === 'string'
+            ? <Icon name={iconOnly} size={glyphSize(resolvedSize, true)} />
+            : iconOnly
+        ) : (
+          <>
+            {/* every option's label rides along hidden so the trigger is as wide
+              * as its widest value — the panel matches the trigger's width, so
+              * trigger and list stay one piece at every selection */}
+            <span className="kol-dd-label">
+              <span>{currentOption?.label}</span>
+              {options.map((option) => (
+                <span key={option.value} className="kol-dd-ghost" aria-hidden="true">
+                  {option.label}
+                </span>
+              ))}
             </span>
-          ))}
-        </span>
-        {/* chrome lives in .kol-dd-caret (trailing edge + open-state flip) —
-          * keyed off the trigger's data-state, no inline styles */}
-        <Icon name="chevron-down" size={indicatorSize(resolvedSize)} className="kol-dd-caret" />
+            {/* chrome lives in .kol-dd-caret (trailing edge + open-state flip) —
+              * keyed off the trigger's data-state, no inline styles */}
+            <Icon name="chevron-down" size={indicatorSize(resolvedSize)} className="kol-dd-caret" />
+          </>
+        )}
+        {/* a consumer's own trigger mark — the tool-palette corner fold rides
+            here so the square keeps ONE implementation */}
+        {triggerAdornment}
       </button>
 
       <PopoverPanel

package/src/molecules/PaletteHarmonyWheel.jsx

@@ -1,5 +1,5 @@
 import { useEffect, useRef } from 'react'
-import { HARMONIES, harmonyById, harmonyColors, normHue } from '../hooks/colorMath.js'
+import { HARMONIES, harmonyById, harmonyColors, normHue, reHueSlots } from '../hooks/colorMath.js'
 
 /* taxonomy-ok: a pure-canvas hue + harmony picker in the SpectrumControls
  * color-picker family. It nests no KOL component — its only import is the
@@ -20,6 +20,16 @@ import { HARMONIES, harmonyById, harmonyColors, normHue } from '../hooks/colorMa
  * arrow keys. `colors` is one hex per role offset of the active harmony
  * (see colorMath.harmonyColors), matching the satellite markers 1:1.
  *
+ * PASS `slots` IF YOU ALREADY HAVE A PALETTE (2026-09-03,
+ * `editor-set-is-behind-its-source`). Without it, `colors` is built at ONE
+ * flat `saturation`/`lightness`, so a Light role and a Dark role both come
+ * back at 50% — the palette flattens on the first drag, and kol-fxr's editor
+ * had to ignore half the payload because its own wheel re-hues slot by slot.
+ * With `slots`, every entry keeps its own S/L and only its hue moves, and a
+ * `locked` or empty slot is passed through untouched. `onHueChange(hue)` is
+ * the same seam with no payload at all, for a caller that owns the derivation
+ * outright — which is what fxr's wheel emits.
+ *
  * The ring hues, marker outlines and handle halo are literal color math
  * (hsl / #FFFFFF / rgba) on purpose — a spectrum is not themeable, and the
  * markers sit on fully-saturated ring hues, not on the surface (same
@@ -31,7 +41,9 @@ import { HARMONIES, harmonyById, harmonyColors, normHue } from '../hooks/colorMa
  * @param {number}        saturation  base saturation for emitted colors, 0–100 (default 100)
  * @param {number}        lightness   base lightness for emitted colors, 0–100 (default 50)
  * @param {Array}         harmonies   injectable scheme table (default HARMONIES)
+ * @param {Array}         slots       the CURRENT palette in role order (`{hex, locked}` objects or plain hex strings). Given, `colors` re-hues these — each slot keeps its own S/L, locked and empty entries pass through — instead of generating flat ones
  * @param {Function}      onChange    ({ hue, colors }) => void
+ * @param {Function}      onHueChange (hue) => void — the payload-free seam, for a caller that derives its own colours
  */
 
 /* Marker outline — white for contrast against the fully-saturated ring hues
@@ -44,8 +56,10 @@ export default function PaletteHarmonyWheel({
   harmony = 'analogous',
   saturation = 100,
   lightness = 50,
+  slots,
   harmonies = HARMONIES,
   onChange,
+  onHueChange,
 }) {
   const canvasRef   = useRef(null)
   const draggingRef = useRef(false)
@@ -58,10 +72,18 @@ export default function PaletteHarmonyWheel({
   )
 
   /* Emit next hue + its harmony colors. Held in a ref so the pointer/key
-   * handlers stay stable while always seeing the latest props. */
+   * handlers stay stable while always seeing the latest props.
+   *
+   * With `slots`, the colours are the CALLER'S palette re-hued — each slot
+   * keeping its own saturation and lightness — rather than a fresh flat set.
+   * Both fire, so a caller can take the hue and ignore the colours. */
   emitRef.current = (nextHue) => {
     const h = normHue(nextHue)
-    onChange?.({ hue: h, colors: harmonyColors(h, active, { saturation, lightness }) })
+    const colors = slots?.length
+      ? reHueSlots(h, active, slots)
+      : harmonyColors(h, active, { saturation, lightness })
+    onChange?.({ hue: h, colors })
+    onHueChange?.(h)
   }
 
   const outerR = size / 2 - 8