refactor(date-range-picker): drop segment rules that duplicate date-field.css

The range picker's segments are composed DateField segments (they carry
data-date-field-segment + the shared data-field-segment marker and read their
tokens from each endpoint's own [data-date-field]). The per-picker copy only
duplicated the Field base and re-added a focus font-weight the shared
field-segment-state layer deliberately drops (bold widens the ch-based segment,
jittering it on every increment). Removing it defers to date-field.css +
field-segment-state.css. Verified: segment box / padding / min-width / highlight
unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

src/uix/eidos/components/date-range-picker/date-range-picker.css

@@ -259,58 +259,13 @@
 	opacity: var(--date-field-disabled-opacity);
 }
 
-[data-date-range-picker] [data-date-field-segment] {
-	display: inline-flex;
-	align-items: center;
-	justify-content: center;
-	/* Fixed 2-digit width (font-relative) + tabular figures (shared layer) so the
-	   segment never reflows on 1 → 2 digit / glyph changes. border-box: 2ch + padding. */
-	min-inline-size: calc(2ch + 2 * var(--_date-field-segment-padding-inline));
-	padding-inline: var(--_date-field-segment-padding-inline);
-	border-radius: var(--date-field-segment-radius);
-	color: var(--date-field-segment-color);
-	font: inherit;
-	outline: none;
-	white-space: nowrap;
-	transition:
-		background var(--date-field-transition-duration) var(--date-field-transition-ease),
-		color var(--date-field-transition-duration) var(--date-field-transition-ease),
-		box-shadow var(--date-field-transition-duration) var(--date-field-transition-ease);
-}
-
-[data-date-range-picker] [data-date-field-segment][data-segment='literal'] {
-	min-inline-size: auto;
-	padding-inline: 0;
-	color: var(--date-field-literal-color);
-}
-
-[data-date-range-picker] [data-date-field-segment][data-placeholder] {
-	color: var(--date-field-placeholder-color);
-}
-
-[data-date-range-picker] [data-date-field-segment]:focus-visible {
-	/* Active highlight: shared `--field-segment-active-*` foundation tokens. */
-	background: var(--field-segment-active-bg);
-	color: var(--field-segment-active-text);
-	font-weight: var(--font-weight-semibold);
-}
-
-[data-date-range-picker] [data-date-field-segment][data-invalid] {
-	color: var(--date-field-segment-invalid-color);
-}
-
-[data-date-range-picker] [data-date-field-segment][data-readonly] {
-	background: var(--date-field-segment-readonly-bg);
-	color: var(--date-field-segment-readonly-color);
-	text-decoration: var(--date-field-segment-readonly-decoration);
-	text-underline-offset: 2px;
-	cursor: default;
-}
-
-[data-date-range-picker] [data-date-field-segment][data-disabled] {
-	cursor: not-allowed;
-	opacity: var(--date-field-disabled-opacity);
-}
+/* Segment box + states (literal / placeholder / focus highlight / invalid /
+   readonly / disabled) are owned by `date-field.css [data-date-field-segment]` +
+   the shared `field-segment-state.css [data-field-segment]` — the picker's segments
+   ARE composed DateField segments, reading their tokens from the endpoint's own
+   `[data-date-field]`. Re-declaring them here only duplicated the Field base (and
+   re-added a focus `font-weight` the shared layer deliberately drops to avoid the
+   ch-width jitter). */
 
 [data-date-range-picker-trigger] {
 	display: inline-flex;