Skip to content

chore(deps): bump @mind-studio/ui to 0.7.0 (brand-refresh typography) - #20

Closed
rep0x wants to merge 1 commit into
mainfrom
chore/ui-0.7.0-brand-refresh
Closed

chore(deps): bump @mind-studio/ui to 0.7.0 (brand-refresh typography)#20
rep0x wants to merge 1 commit into
mainfrom
chore/ui-0.7.0-brand-refresh

Conversation

@rep0x

Copy link
Copy Markdown
Member

What this delivers

Bumps @mind-studio/ui from ^0.5.0^0.7.0, picking up the design-system brand refresh:

  • Serif heading typography — h1–h3 now resolve to Fraunces via the var(--font-serif)var(--mind-font-serif)var(--font-fraunces) chain.
  • kbd monospace styling.
  • Semantic state tokens (success / warning / error / info).

Typography QA (Tier 2)

✅ Chain verified end-to-end. The ui package's dist/styles.css maps h1–h3 → var(--font-serif)var(--mind-font-serif)var(--font-fraunces), and shell's src/app/layout.tsx already exposes --font-fraunces (via next/font/googleFraunces, applied on <html>). globals.css imports the ui stylesheet, so the chain reaches Fraunces with no alias needed.

Verification

  • npm run typecheck — ✅ green
  • npm run build (Next web build) — ✅ green (16/16 routes)
  • Tauri native bundle not run (host app; web build + typecheck only, per scope).

Scope

Tier 1+2 of #29 — dependency bump + typography verification only. The logo lockup (shell wordmark stays "Mind") and Tauri desktop icons are a deferred Tier 3/4 wave; no logo/favicon/asset/icon code touched here.

Refs #29

🤖 Generated with Claude Code

Picks up the serif heading typography (Fraunces h1–h3), kbd mono, and
the semantic state tokens from the design-system brand refresh.
Refs #29
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rep0x

Copy link
Copy Markdown
MemberAuthor

Superseded by #21, which was branched from this bump branch (so it already contains the 0.7.0 bump) and has been squash-merged to main. Closing as redundant.

@rep0xrep0x closed this Jun 21, 2026
@rep0x
rep0x deleted the chore/ui-0.7.0-brand-refresh branch June 21, 2026 16:13
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@rep0x