chore: Upgrade Tailwind CSS from v3 to v4 (partial - dependencies only)

[Copilot]

Description

Upgrades Tailwind CSS dependencies from v3.4.17 to v4.1.17. Build is non-functional - v4's CSS-first architecture is incompatible with the project's JavaScript theme configuration using CSS variables.

Changes

• Dependencies: tailwindcss v3.4.17 → v4.1.17, removed @tailwindcss/nesting (built-in), added @tailwindcss/postcss
• PostCSS: Updated plugin from tailwindcss to @tailwindcss/postcss
• CSS imports: Migrated from @tailwind directives to @import "tailwindcss"

Why Build Fails

V4 doesn't auto-generate utilities from theme.extend.colors with CSS variables. Custom utilities like border-border, text-primary-hover don't exist, breaking @apply directives throughout the codebase.

Next Steps

See TAILWIND_V4_MIGRATION_NOTES.md for migration options:

1. Rewrite theme using @theme directive (~2-3 days) - recommended
2. Manually create utilities (~3-4 days)
3. Replace @apply with CSS properties (~4-5 days)
4. Hybrid approach (~2-3 days)

Do not merge until migration strategy is chosen and build is functional.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test. (Build fails - migration incomplete)
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings (Build currently fails)
• I have added tests that prove my fix is effective or that my feature works (Migration incomplete)
• New and existing unit tests pass locally with my changes (Build currently fails)
• Any dependent changes have been merged and published in downstream modules

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• registry.npmmirror.com
  • Triggering command: node /usr/local/bin/pnpm install (dns block)
  • Triggering command: npm view tailwindcss versions (dns block)
  • Triggering command: npm view tailwindcss version (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Upgrading Tailwind CSS from v3 to v4</issue_title>
<issue_description>Upgrading Tailwind CSS from v3 to v4.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Upgrading Tailwind CSS from v3 to v4 #6883

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9a20c28

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[likui628]

先关了，暂时没时间处理，我怕你不小心合了