Acceptance Criteria
- A "Palette and typography" section exists in the v0.14.0 migration guide (same destination page as WORK-199 — coordinate locations during implementation)
- The section opens with the user-facing change: "Lumina ships with a new neutral default palette in v0.14.0. The previous cream-and-navy palette is preserved as the
tideline preset." - The one-line config snippet for restoring the old colour appearance is shown verbatim
- The font change is documented: tideline switches
font.sans to IBM Plex Sans (from Outfit). The escape hatch for pinning Outfit is shown:{
"theme": {
"presets": ["@refrakt-md/lumina/presets/tideline"],
"tokens": {
"font": { "sans": "'Outfit', system-ui, sans-serif" }
}
}
}
- A note explaining the rationale (one or two sentences linking to SPEC-051 for the full story)
- Cross-references to WORK-199 (tint shape migration) — both pieces are part of the same v0.14.0 upgrade story
Approach
Single docs PR. The destination page is whatever the v0.14.0 migration guide lives in — coordinate with WORK-199 so they end up in the same place.
The voice is matter-of-fact, not alarmed — most users won't notice the default change because they haven't been hand-customising Lumina anyway. For the small set of users who have hand-tuned around the cream palette, the one-line opt-in restores everything.
Dependencies
- WORK-200, WORK-204, WORK-203 — the changes being documented must be merged and shipping.
References
- SPEC-051 — full rationale and the implementation step explicitly calling for this migration note
- WORK-199 — sibling migration note for tint shape changes