fix(framework): parse space-separated hsl() color values

[shuvamk]

Summary

Color tokens authored with CSS Color-4 space syntax — hsl(0 0% 80%) and hsl(0 0% 80% / 50%) — silently lose every derived variant (transparent steps, shades, tints). Only the bare --<slug> base is emitted, verbatim.

HSLA_RE in src/core/framework/colors.ts only matched the legacy comma form with a number-only alpha:

const HSLA_RE = /^hsla?\(\s*([-+]?\d*\.?\d+)(?:deg)?\s*,\s*([-+]?\d*\.?\d+)%\s*,\s*([-+]?\d*\.?\d+)%(?:\s*,\s*([-+]?\d*\.?\d+))?\s*\)$/i

Space-separated hsl() therefore failed parseColor, fell through to the verbatim base fallback, and produced no channels to derive from. Its sibling RGBA_RE — one line below — already documents and supports "both comma and space syntax, alpha as number or percentage", so the two were asymmetric.

This matters in practice: modern CSS and common import sources (Tailwind) emit space-separated hsl(), and src/core/siteImport/colorTokens.ts even uses hsl(0 0% 80%) as a canonical example of an imported palette entry that becomes a framework color token.

Before → after

Input token lightValue	Before	After
hsl(0 0% 80%)	1 var (--c verbatim, no variants)	base hsla(0, 0%, 80%, 1) + 10 transparent + 2 shades + 2 tints
hsl(0 0% 80% / 50%)	dropped	base hsla(0, 0%, 80%, 0.5) + variants
hsl(0, 0%, 80%) (comma)	worked	unchanged

Fix

• Widen HSLA_RE to the same comma-or-space separator and number-or-percentage / slash-delimited alpha shape RGBA_RE already uses.
• Extract parseAlpha and share it between the hsl and rgb branches instead of duplicating the number/percentage coercion.

No new behavior for values that already parsed; comma-syntax hsl()/hsla() output is byte-identical.

Verification

• bun run build
• bun test (6332 pass, 0 fail; the new test fails on main and passes with the fix)
• bun run lint

Checklist

• Tests cover behavior changes — added an hsl(0 0% 80%) + hsl(... / 50%) case alongside the existing rgb(5 5 5 / 78%) space-syntax test.
• Docs were updated when behavior, config, deployment, or public surfaces changed — n/a (internal parser; no documented surface changes).
• No compatibility shim was added for old pre-release behavior.
• No secrets, local databases, uploads, or generated artifacts are included.