Phase 1: extended category colour roles (quaternary/quinary/senary) + fixed-colour picker

[mapgie]

Phase 1 of the logging & category-system redesign (build guide). Fully additive: no DB migration (colorToken is free-form), no screen removed, DB stays at v23.

Now merged with main's theme palette reconciliation (#176) and re-verified against the reconciled palettes.

What's in here

• Color.kt: ExtendedRoles holder + deriveExtendedRoles(scheme), HSL house style (no HCT/TonalPalette dependency). Each extra role hue-rotates one of the scheme's own accents (primary +30, secondary -30, tertiary +45 degrees), keeping its saturation/lightness so the result sits in the scheme's accent band.
• Theme.kt: LocalExtendedRoles static CompositionLocal provided by GoFloTheme around MaterialTheme, derived once per theme. Runs on the CUSTOM (buildCustomColorScheme) path too. colorSchemeFor's signature untouched.
• CategoryAppearance.kt: QUATERNARY/QUINARY/SENARY added to CategoryColor; branches in both resolvers. The local is read only inside the new branches, so primary/secondary/tertiary/hex tokens resolve exactly as before, including outside GoFloTheme.
• ManageCategoriesScreen.kt: colour picker reworked to the row-6 mock: "In-theme roles" is six pill chips (unselected = hairline + colour dot + label; selected = tonal fill + check + bold label), and the hex section is reframed as "Fixed colour / Stays put on theme change".
• wcag_check_roles.py (new): mirrors the derivation in Python over every palette's accent trio in wcag_check.py's THEMES table (all 27 themes after themes: reconcile 12 palettes + WCAG mirror to the finalised colour spec #176) and asserts derived on-colour contrast >= 3:1.
• wcag_check.py restored to plain text: it had been committed as a single base64-encoded line in 84624bc and was unrunnable by its canonical name; themes: reconcile 12 palettes + WCAG mirror to the finalised colour spec #176 re-encoded its update the same way, resolved in the merge by decoding main's updated content. The byte-identical plain-text workaround copy wcag_check_real.py is removed now that the canonical file runs. LESSONS.md entry added; consider wiring the checkers into CI so this can't recur.
• Changelog fragment (minor), PLAN.md §7 progress log updated, subsystem map 03 drift note added.

Deviations from the phase guide's sketch (documented in PLAN.md §7)

1. Greyscale fallback: hue-rotating a grey is a no-op, so both High Contrast themes would have produced three roles identical to the base accents. Accents with saturation < 0.10 instead shift lightness toward mid-tone with distinct magnitudes (0.25/0.45/0.65), giving three clearly distinct greys per High Contrast theme.
2. On-colour selection: the sketch's fixed 0.35 luminance threshold has a band (luminance 0.30 to 0.35) where it picks white and white fails 3:1. On-colours instead pick near-black vs white by whichever contrasts more, which guarantees at least ~4.1:1 on any background.

Acceptance criteria (phase-1-color-roles.md)

• A category set to each of quaternary/quinary/senary renders that colour and re-themes when the palette changes — tokens resolve from LocalExtendedRoles, which is rebuilt from the active scheme on every theme change (verified by inspection; spot-check script exercises all light + dark palettes)
• A category set to a Fixed colour does not change on theme switch — hex path untouched
• Derived on-colours pass contrast in all 12 palettes — wcag_check_roles.py green: 81 roles across all 27 themes (12 families light+dark, High Contrast x2, Blue & Orange), worst ratio 4.21:1 on the reconciled palettes
• wcag_check.py and a11y_check.py both green (405 pairs / 27 themes post-themes: reconcile 12 palettes + WCAG mirror to the finalised colour spec #176; 95 files clean)
• Picker chips carry Role.RadioButton, are >= 48dp tall, and selection is not colour-only (tonal fill + check mark + bold label)

Feature-preservation checklist

• Existing primary/secondary/tertiary/hex tokens resolve exactly as before — old branches and the hex fallback are unchanged; isCustomColorToken's length-8 guard already excludes the new 7-10 char keys
• Calendar dots, DayLogSheet bubbles, Stats colour usage unchanged — calendar reads MaterialTheme.colorScheme directly; the other 7 consumers of toCategoryColor only gain new branches; widgets never call the Compose resolvers
• CUSTOM theme path still works — deriveExtendedRoles runs on whatever scheme GoFloTheme resolved, including buildCustomColorScheme output

CI is the build check for this environment; both Python checkers were run locally and pass.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01TCyUnDhCFcXP9yr3FuywuV