Settings → Sync: 'recent days' number field rides the shared TextField face

[th3-br41n]

What

The selective-sync "keep the last N days" field was a hand-rolled <input type="number"> with its own 5rem width + border + radius + surface — so its box drifted from every other control in Settings (the exact thing the control-face ratchet exists to stop).

Now that <TextField> forwards min/max/step (#154 — the reason this field couldn't use the primitive before), route it through <TextField size=Sm min={1} max={3650}>. The .sync-section__number host keeps only the 5rem width + right-aligned digits; the box (height / border / surface) comes from .bs-input.

Why it's the clean one to migrate first

This closes the loop I built over the last three PRs end-to-end:

primitive gap found (#152 ratchet) → primitive fixed (#154 min/max) → consumer migrated → baseline shrinks (10 → 9).

The control-face ratchet's stale-baseline check requires the file be dropped from control-faces-baseline.json in the same PR, so the two can't drift.

Verified: control-faces green (9 baselined, sync no longer offends), css-tokens green, typecheck:packages clean, sync-section suite 7/7.

Scope note: the other baselined Settings offenders are either plain-text inputs (pure migration — I'm holding those for a live-shell pass so I can eyeball the polish) or type="time" inputs that should route through the shared date/time cell, not a raw input. This one is safe to do blind: it's a number field on an obscure advanced setting, and the standard face can't look worse than a bespoke 5rem box.

🤖 Generated with Claude Code