The Color Trigger chip always showed a mid-gray swatch (#808080) in its unset/default state, indistinguishable from a disabled or error state.
ColorChip passed Color(it.midpointArgb().toInt()) unconditionally to the swatch Box. When all RGB channels are at their full-range defaults (0–255), midpointArgb() returns 0xFF808080, a flat mid-gray with no semantic meaning in the current theme.
Added an isColorSet check in ColorChip (EditColorTrigger.kt): when all six channel bounds are still at their defaults (rMin==0, rMax==255 etc.), the swatch uses MaterialTheme.colorScheme.outlineVariant to signal “not yet configured.” Once the user narrows any axis, the computed midpoint renders as before.
Any chip that derives a display color from user-configured bounds should guard the zero-configuration path — the all-defaults midpoint is almost always an unintended visual. Use a theme token (outlineVariant, surfaceVariant) as the placeholder instead of letting the computation produce an accidental literal.