Skip to content

chore: migrate Tailwind v4 while preserving dashboard design - #203

Open
atulmgupta wants to merge 20 commits into
mainfrom
chore/tailwind-v4
Open

atulmgupta wants to merge 20 commits into
mainfrom
chore/tailwind-v4

Conversation

@atulmgupta

Copy link
Copy Markdown
Collaborator

Description

Separate Tailwind v4 migration requested after the post-merge follow-ups.

Depends on #202: this branch starts from its unmerged, fully verified head f84aad0. Main is the PR target so the full existing workflow matrix runs. Merge #202 first; do not merge this draft automatically.

The initial commit records completed A/B verification and migration references. Tailwind implementation is in progress using the official4.3.3 upgrade tool, CSS-first configuration and native container queries. Preserve all tokens, accent behavior, themes and widget geometry; compare against the saved49 v3 Windows baselines before any intended baseline update. No tolerance, workflow, coverage or test relaxation.

Type of Change

  • Infrastructure / dependency change
  • Documentation update

Checklist

  • A/B source head is fully green:199 successful checks, one existing conditional skip
  • Complete inherited-source local CI replica passed, including Windows visuals and zero proxy escapes
  • Tailwind v4 migration and complete verification finished

Screenshots (if applicable)

Eight375/768/1280/1920 light/dark v3 dashboard captures and all49 current Windows baselines were saved outside Git for comparison. Migration screenshots/results will be recorded here.

@atulmgupta
atulmgupta marked this pull request as ready for review October 26, 2026 21:25

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant