Apply the SPEC-053 field renames to every concrete tint definition that ships with refrakt. Primary scope: Lumina's five tints (base, subtle, warm, cool, dark). Secondary scope: any plugin under plugins/ that defines its own tints. End state: every shipped tint uses the new vocabulary; everything renders identically to before.
Tracking started May 18 — check back for trends.
8df92a3packages/lumina/src/config.ts tint configs migrated: background → bg, primary → text, secondary → muted, accent → primary, mode: 'dark' → lockMode: 'dark', drop mode: 'auto' entriesbase, subtle, warm, cool, dark) updated; the dark tint specifically becomes { lockMode: 'dark', dark: { … } } with the renamed fields insideplugins/ audited via grep for tints: — any that ship tint definitions get migrated. Likely candidates: marketing, docs, design (worth verifying)tint="base", tint="warm", tint="cool", tint="subtle", tint="dark" renders identically pre and post migrationbackground:, primary: as a tint field, secondary:, accent:) inside tints: { … } blocks anywhere in the codebaseThis is the work item that depends on the previous three in the SPEC-053 chain (WORK-195, WORK-196, WORK-197) being merged. Once the types, merge, and CSS bridge speak the new vocabulary, the actual config files migrate.
For Lumina's config.ts, the migration is a careful find-and-replace within tints: { … } blocks — semantic, not regex-blind, because the same field names appear in other contexts (e.g., a CSS color token name might happen to contain "primary" too). Walk each tint definition explicitly.
Plugin audit: grep -rl "tints:" plugins/ to find candidates, then migrate each in the same way.
packages/lumina/src/config.ts — primary file to migrateplugins/*/src/ — secondary audit scope