* chore: Add framer-motion and react-dnd as @librechat/chat Peers
* refactor: Move the Composer Queue Rail Into the Chat Package
* fix: Keep Store Atoms Out of the Queue Rail's Module Load
splitMarkdown and editableParts move to packages/chat/src/core/parts and are
exported from the package root, so hasEditablePart is available to package
components. The micromark and mdast packages the splitter parses with become
peer and dev dependencies of @librechat/chat at the client's ranges, kept
external by the build, and the package jest config transforms them like the
client's does.
* refactor: Move Subagent Progress State and Content Folding Into @librechat/chat
* refactor: Attach the Subagent Activity Feed Through the Chat Transport
* test: Tag the Subagent Activity Panel E2E Specs With Scenarios
* test: Pin Replay, Ready and Live Steer Ordering Across an Activity Reconnect
* fix: Stop the Subagent Activity Feed on Refusals and Bound Idle Reconnects
* fix: Keep Attaching the Subagent Feed While the Child Thread Is Still Reserved
* test: Read Steer Order the Same While the Child Turn Streams and Once It Settles
* feat: Add a Minimal Consumer Example for @librechat/chat
A Vite React page under packages/chat/example renders a themed chat from the package's public entries and the @librechat/client theme, with an in-memory transport standing in for the server. Its jsdom smoke test runs in the package's jest suite, the package typecheck covers it, and ESLint keeps it to public imports and semantic theme roles.
* fix: Let Enter Confirm an IME Composition in the Example Composer
* fix: Report a Failed Turn in the Example and Restore Its Text
* fix: Localize the Example Copy and Guard the Safari IME Enter
* fix: Drop a Rejected Turn, Load the Component CSS, and Keep the i18n Instance in the Example Build
* refactor: Replace the Example App With a Public-Entry Consumer Spec
The owner does not want an example app in the repository. packages/chat/test/consumer.spec.tsx keeps what it proved: a chat built only from @librechat/chat, /react, /components and @librechat/client, over an in-memory transport, streams a reply into the message list under the ClickHouse theme. It sits outside src because chat/boundary rejects self-imports there; jest maps the entry names to the sources and the package typecheck covers it. The example app, its Vite, Tailwind and PostCSS config, its lint block, script and dependency lines are removed.
* chore: Declare the Consumer Spec's i18next Dev Dependencies
* chore: Retest Against Current Dev
* refactor: Move text-like message parts into @librechat/chat
Text, EmptyText, CollapsibleText, Summary and AgentUpdate move into the package's components entry with their unit specs and read the app only through MessagePartsHost, which gains renderMarkdown, useSmoothStreaming, useAgent and renderAgentIcon. The app's markdown and agent-icon renderers register from the Parts barrel, so the host module keeps its import graph.
The design-suppression runner compares a moved file's diagnostics by their first sentence: the remedy that follows names app-only compositions for client paths, so the same violation read as new after a move.
* test: Cover text-like parts rendered from @librechat/chat in the browser
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.
* 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.