chore(theme): drop the unused --text-display token

[yigitdot]

Background

app/globals.css's @theme inline block defines --text-display: clamp(3.5rem, 14vw, 12.5rem) but nothing references it — grep for text-display / --text-display across app/, components/, lib/, content/ finds only the declaration. It's been dead since before #101 (it was --fs-display then; #101 just renamed it along with the rest of the scale for namespace coherence — see the review note). Tailwind v4 won't even emit a text-display utility because it's never used in a class.

Options

1. Delete it — one-line removal from the @theme inline block. Simplest; the scale loses one rung but no behaviour changes.
2. Wire it up — if there's an intended "display" headline size larger than --text-h1 that we want on the books, find/define the call site and use text-display. (No such call site exists today, and chore(theme): migrate footer to Tailwind theme utilities #76/feat(blog): redesign the index and post pages as a "field-log" table #99/fix(blog): capitalize post headings, center body, tighten heading rhythm #100's redesigns didn't introduce one, so this seems unlikely.)

Recommendation: option 1 unless someone has a near-term use for a display-size token.

Links

• Surfaced in the PR chore(theme): migrate inline layout/typography CSS-var styles to Tailwind #101 review (kept out of scope there since the token predates the PR).
• Related theme follow-up: chore(theme): promote --frame-* layout tokens to Tailwind namespaces #102

[github-actions]

🎯 Agentic Issue Triage

Summary: Remove the unused --text-display CSS custom property from app/globals.css's @theme inline block. The token has no call sites and Tailwind v4 never emits a utility for it — it's dead code.

Analysis

Type: Chore / dead-code cleanup
Scope: Single-line deletion in app/globals.css
Risk: None — no component, MDX file, or stylesheet references text-display or --text-display
Related: Sibling cleanup issue #102 (layout token promotion); both stem from the PR #101 rename pass

Suggested implementation

Option 1 (recommended): delete the declaration from @theme inline:

- --text-display: clamp(3.5rem, 14vw, 12.5rem);

That's the entire change. No import, no component, no test needs touching.

Verify with:

grep -r "text-display\|--text-display" app/ components/ lib/ content/
# should return no results after the deletion
pnpm lint && pnpm exec tsc --noEmit && pnpm build

Sub-tasks checklist

• Delete --text-display: clamp(3.5rem, 14vw, 12.5rem); from app/globals.css @theme inline
• Run grep -r "text-display" app/ components/ lib/ content/ to confirm zero remaining references
• Run pnpm lint && pnpm exec tsc --noEmit && pnpm build to confirm clean build
• Open PR referencing this issue (conventional commit: chore(theme): drop unused --text-display token)

Resources

• [Tailwind v4 @theme docs]((tailwindcss.com/redacted) — explains when tokens generate utilities (only if used in a class)
• PR chore(theme): migrate inline layout/typography CSS-var styles to Tailwind #101 — the rename pass that surfaced this token
• Issue chore(theme): promote --frame-* layout tokens to Tailwind namespaces #102 — related layout-token promotion follow-up

Generated by Agentic Triage for issue #103 · ● 1.3M · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@c7d030cd6d4607b90d9ac3ffc8b24aff4f251632