feat(light): add semantic shadow and accent-focus tokens for DIAL UI Kit

[PolinaGurinovich97]

Problem

@epam/ai-dial-ui-kit reads six colour tokens that the light theme never defined:

Kit reads	Where in the kit	Light theme had
--shadow-xs-1	boxShadow.xs	only shadow-blue-500-alpha-20
--shadow-xs-2	boxShadow.xs	only shadow-grey-1000
--shadow-sm	boxShadow.sm	only shadow-blue-500-alpha-8
--shadow-md	boxShadow.md	nothing exact (shadow-blue-500-alpha-4 is 4%, kit wants 6%)
--shadow-lg	boxShadow.lg	only shadow-blue-500-alpha-8
--stroke-accent-focus	borderColors	only stroke-focus-blue

The theme exposed the values under palette-style names, which the kit never looks up. Result: every shadow step and the accent focus ring in the light theme silently fell back to the hardcoded defaults compiled into the kit — a host could not retheme them.

Found by diffing themes[id=light].colors against the CSS variables referenced by the kit's tailwind.config.js, excluding the deprecated *ColorsToRemove sets.

Change

Six keys added to themes[id=light].colors:

"stroke-accent-focus": "#6785FB",

"shadow-xs-1": "#2764D933",
"shadow-xs-2": "#161B2D08",
"shadow-sm": "#2764D914",
"shadow-md": "#2764D90F",
"shadow-lg": "#2764D914"

Values are taken from the kit's own fallbacks, so rendering is unchanged — this only moves the shadow scale and accent focus ring from hardcoded to themable. shadow-md is the one value with no exact existing alias (6% vs the 4% of shadow-blue-500-alpha-4); it follows the kit.

Compatibility

Purely additive — no key renamed or removed. Consumers still reading shadow-blue-500-alpha-*, shadow-grey-1000 or stroke-focus-blue are unaffected.

Not included

Five kit variables remain undefined in the light theme, all deliberately — each is a second-level fallback whose primary name is already present:

• --bg-control-accent-gradient-from / -to / -hover-from / -active-to → primaries --bg-gradient-1 / -2 (+ hover/active) are defined.
• --bg-control-neutral-hover → primary --bg-control-neutral-hover-muted is defined, and development removed this alias on purpose in the 0.14.0 alignment.

The dark theme is out of scope here: it is missing the whole 2.0 token layer (69 keys vs 142), which is a separate piece of work.

Verification

• JSON.parse on the full file passes.
• Re-ran the token diff: the six gaps are closed, only the five intentional fallbacks above remain.

🤖 Generated with Claude Code