Minor nits — clean change, nothing blocking.

Good calls: bidirectional fill is driven by the existing min/max props rather than a new bidirectional flag, so no public API surface is added. Tests, story, and docs all included, and the h-4/h-5 breaking change is flagged honestly in the description.

• src/components/Slider/Slider.vue:108-114 — the hasLabeling block got re-indented (operands dropped from 6 to 4 spaces) but isn't otherwise touched by this PR. Looks like a stray Prettier reversal; revert it to keep the diff focused on the slider fill.
• src/components/Slider/Slider.vue:151-157 — the bidirectional case hand-rolls a <div> with data-orientation/data-disabled to replace <SliderRange>. Fine, since reka's SliderRange can't fill from a midpoint, but worth a one-line comment saying why the plain div exists so a future reader doesn't 'fix' it back to SliderRange.

Logic checks out: isBidirectional correctly requires min<0 && max>0, single-thumb fills between zero-crossing and the thumb, two-thumb keeps standard between-thumbs behaviour, and the zero-width case is covered by a test.

_{barista · claude-opus-4-8 · 11k in / 4.2k out · 444k cached · 69s · $0.601}