The step appliers, frame normalizer and SSE transport move from client/src/hooks/SSE into packages/chat/src/core with their specs, and the client imports them from @librechat/chat. The ask-user-question predicates the content applier reads move with them, and the client's approval module re-exports them so its consumers are unchanged.
* fix: Use Dropdown for Code Execution Settings So Menus Stay Open
* fix: Describe the Workspace Dropdown and Move Select Scenarios to the Code Tool Picker
* fix: Keep a Disallowed Saved Workspace Disabled in the Dropdown
* refactor: Judge chat imports on the resolved target with one boundary rule
scripts/eslint/chat.mjs replaces the import patterns and load selectors: every
specifier is normalized (extension, trailing slash, /index, package name)
before it is judged, across static imports, re-exports, import(), require(),
import-equals and import types, so any spelling of the /react or /components
entry or a UI package is rejected from core. A RuleTester table and a
table-driven scenario cover the spellings.
* fix: Anchor the chat boundary root to the config directory
* fix: Keep bare app paths and bare core entries behind the chat boundary
* fix: Treat aliased react paths in core as the /react entry
* feat: Scaffold the @librechat/chat package
Adds packages/chat with core, react and components entries, a tsdown build,
a node-environment jest config, turbo and root build wiring, import boundary
rules, design-lint scope, and core types for the chat transport, stream,
host and status. No code moves yet.
* test: Cover the @librechat/chat boundaries as scenarios
* fix: Run the chat suite in test:turbo and build it for the mock lane
test:turbo now selects @librechat/chat, the mock e2e job builds the package the
chat-package scenarios load, and the synthetic repository in the suppression
scenarios carries the packages/chat/src root lint:design:record names.
* chore: Build the chat package in frontend:ci too
* chore: Run the chat suite in test:all
* fix: Hold core TSX to the chat boundary and scan the package for cycles
* fix: Apply the chat import boundary to JavaScript sources
* fix: Keep nested core files off the components entry
* fix: Close the remaining chat package gates and fence aborts by generation
Blocks imports through the @librechat/frontend workspace name, adds the chat
sources to the i18n scan, the CSS color gate and the client Tailwind content,
and lets ChatAbortRequest carry the generation it means to stop.
* fix: Keep JSX out of the chat core and carry abort and reconnect outcomes
Rejects JSX under the core, copies the chat manifest before the Docker
install, keys the client app build caches on the chat sources, fences
reconnects by generation, and types the abort result the transport returns.
* test: Give the CSS gate's scratch tree the chat root it now scans
* fix: Close the remaining @librechat/chat gates and wiring
Rejects import() and require() across the package boundaries, holds chat
components to the literal-copy rule, compiles TSX in the package's jest
transform, builds the package in Frontend Unit Tests, requires its test job for
main promotion, adds it to the unused-dependency scan, and lists it wherever a
sibling workspace is listed: Dockerfile.multi, the docker smoke paths, the
remaining node_modules caches, the reinstall helper, the bun build chain and
AGENTS.md.
* fix: Tighten the chat boundaries and carry steering and Assistants aborts
Template-literal import() and require() and self-imports through the package
name are rejected, user-facing JSX attributes need localized text, the cycle
scan resolves self-imports, Dockerfile.multi builds the package for the client
stage, and the transport carries steer, cancelSteer, armSteer and the
Assistants abort key.
* feat: Match the chat transport and host contracts to the client's
The transport now reports settled and replaced starts, the stream's protocol
version and resumed flag, reconnect replay, generation status, paused-run
resume with approvals or answers, abort and steer protocol versions, and the
request error shape. The host config and auth carry what the client's
ChatSettings now supplies: rename-while-running, model specs, retention mode
and the user.
* fix: Keep lazy React-entry loads out of the core and type the Assistants stop
Relative import() and require() of the /react entry from core are rejected,
and an abortKey stop resolves to the terminal conversation and run messages the
Assistants route returns.
* fix: Fence start controls by protocol and close extension-bearing entry loads
Settled and replaced start results carry the protocol version, core loads of
the /react or /components entry with a file extension are rejected, and
test:packages:chat builds data-provider first.
* feat: Give the Checkbox Theme Roles for Its Fill and Corner
The shared checkbox painted no fill when unchecked and drew the rounded-sm
corner every small control shares, so the ClickHouse theme could not reach
Click UI's checkbox.color.background.default fill or its 0.125rem
checkbox.radii.all corner.
A checkboxRadius appearance role sets the corner and follows radiusSm, the
corner it drew before, when a theme names that and not this. A
checkbox-fill color role paints an unchecked box only when the new
checkboxFillStyle role is fill; the default transparent style keeps every
default theme pixel-identical, and the fill follows surface-primary when a
theme omits it. Checkbox and CheckboxGlyph read both roles.
The ClickHouse theme sets Click UI's fill and corner, and both entries
leave the drift guard's not-expressible list with their probes pinned to
match.
* test: Spell Each Checkbox Scenario Tag Literally
* test: Pin the Theme Cache Digest Built From the New Resolver
* test: Drive useChat Through a Substitute Transport for Send, Stop, Steer, Queue and Errors
* test: Tag the useChat Transport Specs as Acceptance Scenarios
* test: Fail the useChat Specs When a Turn Has No Response Placeholder
* test: Bound the Nested Jest Run and Fail the Scenarios on a Nonzero Exit
* test: Settle a Stopped useChat Turn Only on Its Aborted Final Frame
* feat: Lint Disabled Dims That Compose No Disabled Recipe
* fix: Catch Bracketed Disabled Variants and Read Recipes From References
* fix: Skip Enabled-State Branches and False-Valued Disabled States
* fix: Read Full-Opacity Recipes, Primitive Recipes and Compound Conditions
* fix: Keep the Suppression Error Wording the Baseline Spec Reads
* test: Add a lint scenario for the disabled-recipe rule
* fix: Leave negated disabled selectors and conditions alone in the disabled-recipe rule
* feat: Judge disabled recipes per branch, by import and by the element they restore
* fix: Trust recipes only from the theme module and only through defaulted cva variants
* fix: Resolve namespaced recipes through their import
* fix: Read cva disabled variants, guarded recipes and trailing important in the disabled-recipe rule
* fix: Read variant dims a disabled condition picks and recipes behind the same ternary
* fix: Follow nested disabled guards and real cva defaults in the disabled-recipe rule
* fix: Trust recipes only through class helpers and string concatenation
* fix: Read cva compound variants only under compoundVariants and guard key lookups
* fix: Require the recipe that can win for the faded element in the disabled-recipe rule
* fix: Judge stacked disabled variants by their most distant element
* fix: Match recipe markers, read || polarity, compound arrays, constant class strings and helper bindings
* fix: Accept spelled recipes, default-imported primitives, inverted props and disabled-guarded recipes
* fix: Check every chosen dim, trusted helper sources, data-disabled, recipe markers and guard identity
* chore: Re-record the disabled-recipe backlog after rebasing onto dev
* perf: Mount a sidebar row's menu actions only once its menu is used
ConvoOptions now keeps only its trigger and menu store on a row the pointer has reached; the mutations, route and chat-context subscriptions move into a controller that mounts when the menu opens, the shift quick actions show, or the delete dialog opens, and stays from then on so a request lands in the handlers that made it. A pointer sweeping the un-virtualized Pinned section leaves one trigger per row instead of one full menu.
* test: Watch every menu mutation hook in the mount-cost test
* refactor: Normalize Artifact Type Spellings in One Place
* test: Keep Backticks Out of the Short React Artifact Source
* test: Retry a Timed-Out Sandpack Boot in the Short React Scenario
* fix: Case-Fold Canonical Artifact Types as Well as Their Aliases
* refactor: Define the code highlight cadence default once
The interface schema, the config defaults and the client's normalizer read DEFAULT_CODE_HIGHLIGHT_THROTTLE_MS and MAX_CODE_HIGHLIGHT_THROTTLE_MS from data-provider, and normalizeCodeHighlightThrottleMs moves beside them so its bounds cannot drift from the schema's. A spec pins the schema, config defaults, normalizer and librechat.example.yaml to the same default.
* test: Read the cadence from the signed-in config payload
* fix: Let Field and Focus Call Sites Use the Control Roles
Drop the border-heavy focus rings on the memory value fields, the tool
output details link and the Mermaid dialog controls, so each takes its
primitive's focus-control ring or the global outline. Give
TextareaAutosize a field variant and move the bookmark description onto
it. Drop the quiet border overrides on form controls so they keep the
border-control outline, move defaultTextProps and InputNumber onto it,
and prune the no-restyle counts these call sites no longer carry.
* test: Expect the Edge Focus Treatment on ClickHouse Bookmark Fields
The detail dialog remembers the last control focused inside it and, after each commit, moves focus to the unavailable notice or the dialog title when that control is gone and nothing else took focus. This covers a refresh that drops a conversation starter as well as the existing 403/404 case, without depending on a blur that browsers do not fire consistently for removed elements. Starters are keyed by text and occurrence so the ones that survive a refresh keep their focus.
* fix: Keep Hover-Revealed Row Actions Visible Wherever a Finger Can Reach
* fix: Apply the Coarse-Pointer Reveal to the Composer Palette and Model Menu
* test: Assert the Reveal on an Earlier Reply, Not the Always-Visible Latest One
* test: Read the Timestamp From the Hovered Reply's Own Row
* fix: Hide Until Hover Only Where Hover Exists and No Pointer Is Coarse
* feat: Let a theme reshape the sign-in field and button
The sign-in floating-label field, the submit button and their shared corner read the new authFieldHeight, authButtonHeight and authControlRadius appearance roles, whose defaults reproduce the 44px field, 48px button and 16px corner. The corner follows radius2xl when a theme names only that. The ClickHouse theme draws them at Click UI's single field and button size with the button's square corner.
* fix: Size the sign-in button by its height role alone
A fixed height with vertical padding left a short theme height less room than the label. Specs now expect the role classes on the sign-in field.
* fix: Keep the reset label and password controls inside a themed field height
The reset request label rests in the middle of the field instead of 12px from its top, and the password field's reveal and copy buttons size from the sign-in field height, 4px off its edges and never under 24px. Both keep their stock positions and sizes.
* fix: Hold the password field controls inside the padding it reserves
The reveal and copy buttons stop growing at the stock 2.25rem, so a taller sign-in field keeps them clear of the typed value.
* feat: Let a theme reshape the second-factor and reset-success actions
The 2FA verify and reset-success continue buttons read authActionHeight and authActionRadius, which follow the sign-in button's height and corner when a theme names those and otherwise the Button height and radiusLg they drew, so the stock screens are unchanged and ClickHouse draws them at 32px with its 4px corner.
* test: Reach the second-factor screen through a pending sign-in
* fix: Rest the reset label inside a minimum-height field and keep the action corner on radiusLg
The reset request label rests from an inset that centers it 2px low as before but never past the field's bottom edge, and the other sign-in actions resolve their corner before the sign-in corner is derived from radius2xl, so a theme that names only radius2xl keeps radiusLg on them.
* fix: Show the Focused State of the InputNumber Option Variant
* test: Probe the InputNumber root rather than its input wrap
* fix: Keep the InputNumber Option Focus Fill Above Its Hover Fill
* feat: Adopt the continue icon, artifact timing, avatar border and dropdown intents Tailwind 3 never rendered
Sizes the continue action's glyph to the 19px of the actions beside it, times the artifact sheet's close to the 250ms its unmount waits for and the docked panel's open to 350ms, frames agent avatars with the 1px border they asked for, and lets the dropdown menu primitive cap its height, grow from its trigger and tint a destructive item's icon.
* fix: Cap the dropdown submenu at the space Radix measures
* test: Stop pinning the adopted artifact durations as inert
The sidebar toggle and the Agent Marketplace link use the nav Button variant and the new chat link hovers in surface-nav-hover, so every control in the desktop rail shares the navigation hover the panel buttons and sidebar rows use.
* feat: Route Every Prompt Category Icon Through a Per-Slot Role
* test: Retry Category Icon Reads While the Prompt List Settles
* fix: Carry the Renamed Category Icon Role to Its Slot 4 Name
* fix: Carry the Renamed Category Icon Role Through Every Color Reader
* fix: Keep Renamed Color Roles Out of the Unknown Token Warnings
* refactor: Paint the desktop icon rail with the nav Button variant
The rail's panel buttons now use the shared nav variant, so their hover and selected fills come from surface-nav-hover and surface-nav-selected like the sidebar rows, and the selected state stays on aria-pressed.
* test: Run the rail nav scenarios on a pointer device
* feat: Give Prompt Category Icons a Purpose Color Role
* fix: Keep Token Formatting and Skip Hover on Touch in the Category Icon Scenario
* test: Refresh the Theme Resolver Pin After Rebasing on the Avatar Ink Change
* fix: Read Math Function Channels in CSS Custom Property Triplets
* fix: Collapse Nested Numeric Math Before the Triplet Check
* fix: Read Exponents and Math Constants in Triplet Channels
* fix: Read round() Strategies in Triplet Math Channels
* 📴 fix: Stamp Legacy Failure Parts When Settling a Compaction Row
* 📴 fix: Redirect the Collision Error Row to the Live Response Id
* 📴 fix: Withhold the Anchor-Colliding Error Row and Keep Pending Rows Fallbacks
* 📴 fix: Scope the Settled-Job Guard to Compactions and Copy Stamped Parts
* test: Cover the Underscore-Leaf Compaction Failure and Abandoned Replies in E2E
* test: Fail the Underscore-Leaf Compaction Through the Blank Summarizer
* refactor: Return the Final Error Row Id From the Settlement
* refactor: Use Spinner Tones, Label Variants and Shared Button Props in Remaining Components
Replaces text colour, round shape and size overrides with the primitives' own tone, variant, shape and size props where the merged classes are identical, drops redundant field overrides, and removes the prose and arbitrary transition classes that generated no CSS or have a token form.
* test: Cover the Quiet Ink of the Marketplace Search Clear Button
* test: Assert the Clear Button Hover Ink Only Where Hover Exists
* refactor: Replace Inline Styles With Classes Outside Chat and the Side Panel
Moves display, overflow, user-select, outline, will-change, backdrop and mask styling onto utility classes and CSS custom properties across Agents, Artifacts, Audio, Bookmarks, Plugins, Projects, Share, routes and the shared client components, and drops the recorded no-inline-styles suppressions they cleared.
* test: Cover Marketplace Grid Columns Driven by the Columns Variable
* test: Pick a Single-File Directory for the Moved-File Prune Fixture
* refactor: Give InputNumber an Option Variant for Setting Values
* fix: Ship the Option InputNumber Reset With the Package Stylesheet
* refactor: Prune the Setting Value Suppressions After Rebase
* refactor: Use Existing Variants and Drop Redundant Overrides in Nav, Skills, Prompts and Endpoints
* test: Cover the Header Menu Trigger in the Default Theme
* chore: Prune Design Suppressions After the Rebase
* a11y: Ring Tabs, Table, Dropdown and Menu Items in the Focus Control Role
* test: Tag the Focus Primitives Scenarios Literally
* test: Match the Dark Focus Rule That Yields to Outline Utilities
* refactor: Keep Menu Items and Table Rows on Their Existing Focus Treatment
* refactor: Leave Tabs and Dropdown on the Global Focus Outline
* test: Assert Both Outline Utility Exclusions in the Dark Focus Rule
* refactor: Clear Chat Input Design Suppressions Through Existing Variants
* test: Cover the Chat Composer Send Path After the Suppression Cleanup
* refactor: Keep the FileUpload Action on Its Ghost Pressed Fill
* feat: Add 10, 11, 13 and 15px Steps to the Theme Type Scale
* test: Prove the Off-Scale Type Steps in the Mock Harness
* style: Sort cn Imports
* refactor: Name the 13 and 15px Steps 1xs and 1sm
* test: Probe the Type Step Roles Instead of Unused Utilities
* fix: Keep Chrome Surfaces and Destructive Confirms Legible in a Quiet-Chrome Theme
* fix: Soften Remaining Inline Destructive Triggers and Canonicalize Zero Chrome Alpha
* fix: Keep Pressed Feedback on the Quiet-Chrome Floating Control and Cover the Quiet Surfaces
* test: Scope the Quiet Surface Scenarios to the Header
* fix: Keep the Two-Factor Disable Trigger on the Soft Destructive Variant
* feat: Show Lia on the Welcome Screen
Adds the opt-in Show Lia setting (off by default) and the interface.mascot deployment flag (allowed by default). Lia mounts only on the landing page, loads lazily after first paint, stands on the composer's top edge clear of the greeting, reacts to typing, files and theme changes, and speaks through localized bubbles. She is decorative and hidden from assistive technology.
* fix: Keep Lia's Long-Message Reaction Re-Armed and Pointer Reads Per Frame
Deleting a message back under 280 characters now re-arms the long-message reaction, pointer handling reads layout at most once per animation frame, and the ChatView specs stub Lia like their other children.
* test: Open Settings from the Phone Drawer in the Lia Scenarios
The opt-in scenario no longer resets the stored preference on reload, and both Settings scenarios open the account menu from the mobile drawer on phones.
* fix: Measure Lia's Caret Like the Composer and Label Her When Idle
The caret mirror copies direction, alignment, indentation, wrapping and box sizing, so right-to-left and wrapped text measure like the composer. Hovering Lia between activities now says she is hanging out instead of showing nothing.
* fix: Wave Off Assistants Sends and Keep Lia's Canvas and Bubble Off Welcome Content
* fix: Keep Lia's Speech Bubble Inside Her Stage
* fix: Wrap Long Translations in Lia's Speech Bubble
* fix: Keep Lia's Long-Message Reaction Until It Plays and Pin the Scenario Greeting
* fix: Make Only Lia's Body Clickable So She Fits Beside Long Greetings
* fix: Let Lia Stand Beside the Composer When the Greeting Fills Its Top
* feat: Let Users Drag Lia Around and Keep Her Near the Composer
* test: Cover Picking Lia Up and Setting Her Down on the Composer
* refactor: Keep Lia's Preference Inside Her Feature
* fix: Let Keyboard Users Pet Lia and Move Her With the Arrow Keys
* test: Shift Only the Wall Clock for Lia's Morning Greeting
* test: Measure Lia's Keyboard Walk Both Ways So the Greeting's Width Cannot Pin Her
* fix: Bring Lia Back When a New Chat Opens During Her Farewell
* fix: Start Lia's Reactions on Her Own Clock After a Pause Without Room
* fix: Load Lia Through Stale-Asset Recovery and Skip the Farewell Before She Appears
* feat: Mark the Lia Settings Toggle as Beta
* refactor: Give Sign-In Controls Button, Input and Alert Variants
* fix: Load the Field Stylesheet From SecretInput
* fix: Default the Floating Fields to the Placeholder Sentinel
* test: Cover the Sign-In Control Roles in the Default Theme
* test: Wait for the Floating Label Transition Before Reading It
* test: Read the Floating Label Scale Property
* fix: Keep Button Heights on Theme Roles and Honor Reduced Motion in Floating Fields
* refactor: Mark Message Text Containers With a Data Attribute
* test: Tag the Private Text Spec as a Scenario
* test: Cover Message Text Containers in a Mobile-Safe Scenario
* fix: Dim a Disabled InputNumber Through Its Nested Input
* test: Cover the Disabled InputNumber Wrapper in the Browser
* test: Tag the InputNumber Scenarios Literally
* fix: Make DataTable Row Estimates Breakpoint- and Leaf-Column-Aware
* test: Cover the Compact Row Estimate Against the Rendered Cell
* test: Tag the Row Estimate Scenarios Literally
* fix: Reconcile stopped generations before detaching the stream
* test: Cover immediate Stop and delayed terminal reconciliation
* test: Accept both terminal outcomes of an immediate Stop
---------
Co-authored-by: Lia <lia@librechat.ai>