🧱 refactor: Harden Composer Design System

[danny-avila]

I hardened the redesigned Composer so it composes the shared UI modules and semantic theme tokens introduced by #14670 before #14473 lands.

• Merge the latest dev changes, including 🧩 refactor: Shared UI Design System Tokens #14670, into the Composer redesign branch.
• Extend the shared Chip with a theme-aware surface tone and IconButton with a semantic primary-action variant.
• Replace Composer-specific chip and icon-button implementations with shared Chip, IconButton, and Button composition.
• Remove direct Tailwind palette colors and raw color values from Composer modules and the palette-entry data interface.
• Use semantic accent, fixed-surface, inverted-action, and destructive text tokens for theme-safe UI states.
• Prefix the necessary virtualized-list and motion CSS to the Composer implementation.
• Add semantic-color guardrails for the Composer seam and strengthen shared-component raw-color detection.
• Preserve specialized Composer interactions, dynamic layout styles, reduced-motion behavior, and listbox keyboard semantics.

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

• Ran the complete client Jest suite: 320 suites and 4,037 tests passed.
• Ran the complete @librechat/client Jest suite: 18 suites and 171 tests passed.
• Ran Composer and supporting targeted suites: 7 suites and 109 tests passed.
• Ran client and package TypeScript checks.
• Ran ESLint on every changed TypeScript module.
• Ran Prettier checks and git diff --check.
• Ran the client Vite CI build successfully.
• Scanned the combined 💬 refactor: ChatForm UI redesign with unified palette #14473 diff for direct Tailwind palette utilities and raw colors.

Test Configuration:

• macOS
• Node.js 24
• Jest in band with coverage disabled
• Vite CI mode

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes
• Any changes dependent on mine have been merged and published in downstream modules.

Stacked on #14473.

[danny-avila]

@codex review

[danny-avila]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 08c5322dc5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".