test: check shipped Earth/Loam CSS contrast in CI

[tuckcode]

Why

Shipped Earth/Loam contrast needs a gate on the CSS the app actually loads, not only the design token file.

Follow-up (this push)

• Unparseable colors (hsl(), oklch(), color-mix(), unresolved var(), …) now FAIL with theme, token, and raw value. They are not skipped. earthThemeTokens.test.ts proves an oklch() fixture exits 1.
• Rebased onto current main (includes Earth theme nits: leftover skins, Loam contrast, Earth dark default #147 and docs: stop PRs from conflicting in HANDOFF.md #150). docs/HANDOFF.md is not in this PR. The session note lives only in docs/plans/handoffs/2026-10-11-0715-cursor-grok-4-6-theme-contrast-check.md.
• pnpm handoff:check passes (900 lines, per-PR pointer from docs: stop PRs from conflicting in HANDOFF.md #150).

What landed earlier

• Real checker: scripts/contrast_check.py. Default reads src/index.css + src/themes.css.
• docs/design/earth-theme/contrast_check.py is a pointer; design-file mode still works.
• Blocking CI step in frontend-static-quality.
• WCAG AA: text 4.5:1, borders/focus/icons 3:1.

QA

• python3 scripts/contrast_check.py on current main CSS — exit 0, failing pairs none
• npx vitest run src/lib/earthThemeTokens.test.ts — 16 passed (includes unparseable fail)
• pnpm handoff:check — pass
• bash .husky/pre-push — all lanes OK in 7m 48s; hook on push OK in 7m 57s

Completion

• Localization: none — English only (C18)
• PostHog: no event needed because this is a checker, not a user action
• ADRs: none
• Demo vault dirt checked: empty

Ready for review. Do not merge from this agent. knispo merges.

  

[repowise-bot]

🔍 1 thing to check

1. This PR introduces 8 new findings (1 critical) across 1 file: 3× complex method, 2× nested complexity, 1× bumpy road (+2 more kinds). The worst are marked on the diff (see all)

⚠️ 1 new critical finding · Health of changed files: 9.7 → 8.2 (-1.5)

Check	Result
Coverage	Not set up · add one CI step
Tests	0 of 2 changed code files reached by a test · 1 reached by no test · 1 with no test signal
Security	No new findings on changed lines
Doc drift	No drift in docs this PR edits · 10 documents name changed files

Security

Scanned the changed lines at fa67ac2. 2 findings below med severity hidden (settings).

Pattern matches from a fixed regex registry: a floor, not a scanner. A clean result means no pattern matched a changed line, not that the change is safe.

Doc drift

• .github/SETUP.md names .github/workflows/ci.yml and is not in this PR
• docs/HANDOFF.md names package.json and is not in this PR
• docs/NEXT.md names package.json and is not in this PR
• +7 more on the PR page

---

📊 See the full report for this PR
_{Blast radius, every caller of the contracts it changes, and health before and after. No sign-in.
Plain markdown for agents}

_{Settings and updates}

_{Updated 2026-10-11 08:34 UTC, since the last push: health 8.3 to 8.2, 1 new finding
Silence one PR with [skip repowise] in the title · Bot settings
⭐ Star Repowise · 📥 Install on another repo}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics -29 complexity · -2 duplication

Metric	Results
Complexity	-29
Duplication	-2

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The CI checker does not enforce the 3:1 input-border threshold for several surfaces it enumerates, so CI can pass despite an invalid border contrast pair. This should be fixed before merging. Codacy reports the changes as up to standards; no uncovered complex files were identified.

About this PR

• Add fixture-based tests covering deliberately failing pairs, non-zero exits, missing or unparseable tokens, and the custom design-file mode.

Test suggestions

• Default invocation loads both shipped CSS files and reports Earth dark, Earth light, and Loam.
• Design-file invocation through docs/design/earth-theme/contrast_check.py remains compatible.
• Text, hover, selected, border, and focus-ring contrast pairs are evaluated and reported.
• A deliberately failing contrast pair produces a FAIL line and a non-zero exit status.
• Missing or unparseable required theme tokens cause a clear failure rather than silently passing.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. A deliberately failing contrast pair produces a FAIL line and a non-zero exit status.
2. Missing or unparseable required theme tokens cause a clear failure rather than silently passing.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🟡 MEDIUM RISK}

Apply the non-text threshold to every enumerated surface, or explicitly remove these surfaces from SURF_ROLES; do not print unchecked pairs as if they were enforced.