* 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
* feat: Derive the Theme Cache Version and Close the Color Token Drift
* feat: Add a Button Padding Role for the Default Size
* test: Run the Boot Script Through the Version Injection
* fix: Retain Signed-Out Provenance and Tighten Token Declarations
* 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
* refactor: Clear Raw-Color, Unknown-Class and Arbitrary-Value Suppressions in Auth, Nav and Endpoints
* refactor: Use the Registry Type Steps in the Nav Shortcut Chrome
* refactor: Prune Recorded Suppressions the Registry Type Steps Clear
* fix: Polish the Pull Request Chip and Card Header
Shrink the GitHub link icon and keep its hover on the icon only, drop the agent avatar from the chip so only the pull request icon remains, and open the hover card below the chip.
* fix: Scale the GitHub Icon With a viewBox and Rebase the Card Placement onto the Shared Panel
* refactor: Route Stylesheet Colours Through Theme Variables and Gate CSS Literals
* fix: Run the Colour Check Through Its Own Script
* fix: Read Numeric Fallbacks Inside Colour Function var() in the Colour Literal Check
* 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 the Conversation Pull Request in the Sidebar List
Add a batch lookup route and a sidebar row mark: the state icon with the CI dot, opening the same card beside the row on hover. The row keeps the conversation's own title.
* fix: Address Review Findings on the Sidebar Pull Request Batch and Row Mark
Cap the whole batch with a configurable deadline, make the row mark a keyboard-reachable button that opens the card on focus, refresh rows when the window regains focus through the shared batch, and show a retryable failure state instead of treating a failed first lookup as no pull request.
* fix: Send Sidebar Pull Request Batches One at a Time
Queue every batch request behind the one before it, so an oversized list or an overlapping flush cannot multiply the server's configured lookup concurrency, and bound how long one request may hold the queue so a request that never answers cannot stop the rest.
* fix: Keep the Batch Request Timeout Above the Server Deadline
Default the client's request timeout to just past the longest batchTimeoutSeconds a deployment may configure, so a queued request never starts while the previous request's server-side lookups are still running.
* fix: Keep Batch Lookups Inside the Concurrency Limit and Per-Entry Failures Per Entry
Share one lookup limiter across every batch request so lookups that outlive a request's deadline keep their slot, answer a missing token only for the conversations that needed it, and point the row at its pull request description only while that text is in the page.
* fix: Bound Batch Reads, Scope Concurrency Per Credential, and Gate the Sidebar on the Batch Version
Start the batch deadline when the request arrives and bound the config and lane reads, count lookup slots per credential, advertise a batch route version and ask only a server that has it, take no row space for an absent mark, show a failed refresh over a cached empty answer, keep a malformed response from stalling the request queue, and repair the lane recording tests that still used a mock removed on dev.
* fix: Move Capability Resolution Into the Package and Harden the Batch Route and Queue
Resolve the pull request startup capabilities in packages/api so the route stays wiring only, bound the config and lane reads by the configured deadline, merge identical lanes before taking limiter slots, fall back to the single route when a replica has no batch route, and dispose the batch queue when the signed-in user changes.
* fix: Abort the Batch Fallback With Its Request So the Queue Never Overlaps It
Give the batch fetcher the request's abort signal and pass it to every single-route call, abort a request that times out or is disposed, and stop the fallback workers from starting more calls once it has.
* fix: Forward the Abort Signal to the Batch POST
Pass the request's abort signal through the batch fetcher, the data-provider call and Axios, so a batch request that times out or is disposed is cancelled instead of continuing beside the next one, and settle a request promptly when it is aborted.
* fix: Close the Pull Request Lookup Follow-Ups and Cancel Abandoned Sidebar Rows
* 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: Clear the Raw-Color and Unknown-Class Design Suppressions
* fix: Keep the Prose Classes style.css Still Reads
* fix: Keep the split-parent Marker the Screenshot Spec Waits On
* chore: Prune the Recorded Suppressions the Rebase Cleared
* 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
* feat: Show the Conversation Pull Request in the Chat Header
A header chip shows the pull request a code conversation opened: the agent picture with a CI status dot, the pull request icon and a truncated title. It opens a card with the number, added and removed lines, a link to GitHub, and state and checks badges. The chip renders nothing while loading, when there is no pull request, or when the first lookup fails.
* feat: Place the Pull Request Chip Beside the Model Controls and Move It to the Overflow Menu on Small Screens
On desktop the chip sits with the left header controls and its card opens to the right as an Ariakit hovercard that slides in from the left, on hover or keyboard focus. Small screens offer the same card from the header overflow menu through a dialog, following the dialog-item contract.
* fix: Address Review Findings on Pull Request Polling, Badges and Tooltip Layering
Advertise pullRequestsEnabled in the startup config and skip the lookup without it, keep polling a finished pull request while its checks run, render the card badges with the shared Chip, and portal the GitHub tooltip into the card's own layer.
* fix: Address Second Round Review Findings on the Pull Request Dialog and Chip
Scope the mobile dialog to the conversation it opened for and expose dialog semantics on its menu entry, only use the chat agent's avatar for the routed conversation, and make the hover tests move the pointer the way a browser does so they pass under NODE_ENV=development as CI runs them.
* 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>
* 🏝️ fix: Apply the No-Workspace Decision Wherever an Agent's Code Route Resolves
A conversation set to run without attached workspaces failed mid-turn with
"Choose an attached workspace before using this agent." when its agent's
default machine was attached and the turn loaded a skill or another tool at
execution time. Request-start initialization honoured the decision, but the
execution-time tool loader re-resolved the agent's attached default and then
demanded a workspace selection the conversation intentionally never made.
The per-agent code rule now lives in one typed function,
resolveAgentCodeExecution (packages/api/src/code/agent.ts): it applies the
conversation's no-workspace opt-out, the run-code grant, the stateful
capability and the stateful environment policy, then resolves the base route.
Request-start initialization, lazy subagent metadata and graph members, the
execution-time and definition tool loaders, and the legacy execute_code
loader all go through it, so an opted-out agent lands on the managed default
route with no code tools at every site. Per-call subagent machine choices
offer and accept no attached machine in such a conversation, and a source
invariant test keeps new resolver call sites on the shared rule.
* fix: Pass the Implicit Stateful Route Rollout Into the Shared Code Rule
The per-agent code rule read the implicit stateful route rollout from the environment itself. It now takes it as a parameter, and the request boundaries (initializeAgent and withRequestCodeInputs) resolve it from the deployment configuration, so the rule stays a pure function of its inputs.
* fix: Carry the Initializer's Code Opt-Out Into Tool Definition Loading
initializeAgent hands the tool loaders a partial agent record (id, tools, provider, model) together with the code route it already resolved. Without the agent's route fields the definition loaders could not see a no-workspace opt-out and recomputed code execution as enabled, so tool classification could advertise the programmatic bash tool that execution then refuses. initializeAgent now passes attachedEnvironmentOptOut through every tool loader, and the shared rule keeps an opt-out its caller already decided.
* feat: Quiet Prompt Editor Boxes, Table Columns and Destructive Buttons for a Theme
* fix: Outrank the Cell Border Color With the Column Rule Share
* fix: Keep the First Table Cell's Outer Edge Under the Inset Share
* fix: Keep the Batched Edit Divider on the Light Border
* fix: Keep Web Search Source Row Separators on the Light Border
* fix: Quiet the Result Switcher Divider and Keep the RTL Table Edge
* fix: Resolve Table Edges by Cell Direction and Keep the Variables Card Opaque in Details
* fix: Draw Table Frame Edges in Logical Terms So Direction Needs No Selector
* fix: Keep Soft Destructive Hover and Pressed Tints Above 4.5:1
* feat: Record Lane Git State and Serve Conversation Pull Requests
A conversation now stores the branch, head and repository its code lane last reported, written only by the server after a finished bash command and excluded from ordinary reads, generic saves, unset fields and imports. GET /api/convos/:conversationId/pull-request finds the pull request for that branch through an injected GitHub source with a bounded cache, answers null for an absence, and maps failures to stable codes without upstream text. The feature is off unless endpoints.agents.pullRequests is enabled with a token reference.
* fix: Address Review Findings on Pull Request Lookup and Lane Writes
Scope the lookup cache, shared in-flight request and rate limit cooldown to the credential, so one tenant's token never serves another. Ask for open pull requests on their own before falling back to the newest closed one, read every page of check runs up to a bound and never report an incomplete rollup as passing, order lane writes per conversation so an older write cannot land last, and name both required token permissions in the example config.
* fix: Address Second Round Review Findings on Pull Request Lookup
Clear the stored lane when the conversation moves to another workspace or leaves attached execution, so the previous workspace's pull request is never served. Fence the lane write on the time it was reported, so an older report from another replica cannot replace a newer one. Honor GitHub's reset window up to an hour instead of ten minutes, and expose the request timeout, whole lookup timeout and check run page limit as endpoints.agents.pullRequests settings with the previous values as defaults.
* fix: Authorize Pull Request Repositories and Fence Lane Writes
Require an administrator allowlist of repositories before the server token is used, since a worker reports its own repository. Match a pull request to the commit the conversation last ran at, so a reused branch name does not return another pull request. Fence the lane write on the workspace the command ran in, so a write queued before a move cannot bring the old lane back, and record a subagent thread's lane on the visible root conversation. Key the lookup cache and shared request by the recorded commit and the lookup policy, and document the worker flag in the example config.
* fix: Order Lane Reports by a Database Sequence and Tighten Head Matching
Replace wall clock ordering of lane reports with a per conversation counter reserved in the database when the command settles, so replica clock skew cannot reject a newer report. Treat a pull request whose head is behind the recorded commit as no match, and expose the candidate and comparison bounds of the history search as settings. Read the app config and the owner scoped lane together, inject the HTTP transport from the route instead of falling back to a global, skip a report identical to the last one written, and name the Contents permission that commit comparison needs.
* fix: Queue Lane Reports by the Visible Conversation and Read Checks for the Current Head
Order lane report reservations by the conversation the write lands on, so two subagent threads of one conversation share a chain, and write every report instead of skipping a repeat, since another recorder may have changed the lane in between. Read a pull request's detail before its check runs and use the head it reports, so line counts, mergeability and checks describe one commit. Treat an expired temporary chat as gone when reserving, writing and reading the lane, and make the shared cache capacity a setting.
* fix: Fence Lane Reports by Attachment Epoch and Place Recorders Before Reporting
Strip dotted descendants of lane fields from saves and imports, partition the pull request cache per credential, resolve the lane write target when the tool is created, and fence reports with a codeAttachmentEpoch that advances only on an owner move or detach.
* fix: Fence Subagent Lane Reports by the Root Epoch and Cover Forks and Moved Heads
Read the visible root's attachment epoch for a subagent report, gate lane recording on pullRequests.enabled, make the credential partition bound a config field, revalidate the detail head against the recorded commit, and find fork pull requests through the recorded commit.
* fix: Keep the Credential Cache Bound Deployment Wide and Budget Head Revalidation
Apply the largest configured credential bound to the shared cache, count cache hits as use, spend the comparison budget on a moved head, and fix the data-provider config default test.
* fix: Cool Down Headerless Secondary Rate Limits
A 403 whose message names a secondary rate limit now starts the credential cooldown for at least a minute instead of being cached as a ten second failure.
Code workers can report the branch and head commit of the lane a command ran in. LibreChat now accepts an optional laneGit key on execute_command results, bounded to a 256 character branch without control characters and a 40 or 64 character lowercase hex head, and rejects anything else. The data-provider gains the pull request types, endpoint, query key and service method, and an endpoints.agents.pullRequests config block that is off by default and takes the token only as an environment variable reference.
* 🔁 fix: Recover Concurrent First SAML, LDAP and Social Logins
SAML, LDAP and social logins looked the user up and then inserted it
with nothing in between, so two first logins for one new identity both
inserted and the unique index failed the second with E11000.
Every strategy now provisions first-login users in packages/api:
createUserOnce inserts through createUserIfAbsent and, on user_exists,
repeats the strategy's own lookup and resolves to the account that won,
once its creator finished provisioning it (its start balance exists when
one is configured), admitted exactly as a found account (a tenant
account resolves its tenant config and that config's email-domain policy
applies). provisionSamlUser, provisionLdapUser and provisionSocialUser
own the create / recover / refresh decision, so a recovered account gets
the same refresh as any account the login finds (claimSamlIdentity, the
LDAP directory overwrite, handleExistingUser), and the CJS strategies
only pass their models and services and map the result to passport.
The lookups take a plain FindUserByFields and the contracts carry
UserRecord and NewUserData. createOpenIDUser now goes through
createUserOnce.
Related to #16766
* ⚡ perf: Read a Recovered Account's Config and Balance Together
After losing the insert race, createUserOnce resolved the tenant config
and only then read the start balance, although the balance check now
depends only on the creation config. Both reads start together.
* 🚪 fix: Let Concurrent First OpenID Logins Continue as the New User
Two requests for the same not-yet-created OpenID identity both missed
findOpenIDUser and both called createUser; the unique email and OpenID
indexes rejected the second insert, and that login failed with E11000.
createUserIfAbsent (data-schemas) inserts a first-login user and reports
a lost race as { ok: false, error: { code: 'user_exists' } }. It
initializes the start balance under the new user's id before inserting
the user, so the account is never visible without it, and removes that
balance when the write fails or a unique index rejects the insert.
createUser shares the insert-only credit (creditStartBalance).
createOpenIDUser (packages/api) creates through it and, on user_exists,
repeats findOpenIDUser with its provider and issuer checks and continues
as the account that won, admitted and refreshed exactly as if the first
lookup had found it: the account's own config (tenant config for a
tenant account) and its email-domain policy apply, and applyOpenIDProfile
writes this callback's claims. It continues only once the winner
finished provisioning the account: when that config sets a start
balance, the balance must exist, which a previous-release creator
credits only after its insert. UserRecord and NewUserData are the plain,
storage-neutral contracts.
Related to #16766
* ↩️ fix: Hold a Recovered Login on the Creation Config's Start Balance
The provisioning barrier read the recovered account's tenant config.
With a tenant start balance the base config does not set, every
concurrent first login in that tenant failed again, because the winner
creates the user under the base config and login balance sync only
initializes the tenant balance afterwards.
The barrier guards against a previous-release creator's $inc landing on
a balance login balance sync already initialized, and that creator only
credits the base config's start balance. createOpenIDUser now holds the
recovered login only when the config new users are created under sets a
start balance; a tenant-only start balance is initialized insert-only by
login balance sync and cannot be added twice.
* fix: Keep Reasoning Out of Every Read Aloud Path
Read aloud spoke the Thoughts section along with the answer. The hover
button flattened think parts into the string it handed to TTS, browser
autoplay and the hooks parsed content without skipping reasoning, and
server streaming spoke the stored text field, which an aborted turn
persists with its reasoning included.
Add getSpeechText to data-provider as the single source for spoken text:
text parts only for structured content, and the legacy :::thinking block
stripped from plain text, treating a still-open block as reasoning so
streamed speech only ever grows. Route the hover button, browser
autoplay and server streaming through it, and skip reasoning in the TTS
hooks' own content parsing.
* fix: Speak String Message Content Without Its Reasoning
Imported or client-built messages can carry their answer as string
content rather than parts; read it like plain text instead of falling
back to an empty text field.
* fix: Keep Answers Between Repeated Legacy Thinking Blocks
Strip every closed :::thinking block before treating an unterminated one
as reasoning, so a second closed block no longer swallows the answer
that follows it.
* fix: Skip Read Aloud and Autoplay When Only Reasoning Remains
A turn stopped mid-reasoning has no answer to speak once reasoning is
filtered. Gate autoplay on the same speech text it will play, so the
external engine never opens a stream that can only time out, and hide
the Read aloud action when there is nothing to read. Every speech path
reads a finalized message, so speak an unmatched :::thinking marker as
the answer text the UI shows instead of dropping the rest.
* refactor: Move Speech Chunk Polling Into packages/api
The decision of what text to stream as speech lived in the legacy CJS
service. Move the chunk processor to packages/api as
createSpeechChunkProcessor, taking the message cache and lookup from the
caller, and leave streamAudio.js wiring them in. Its tests move with it
onto an in-memory cache instead of module mocks.
* fix: Speak Exactly the Answer the Message View Shows
Share the legacy :::thinking parser between the message view and speech,
so Read Aloud strips the same block the view collapses instead of a
separate pattern drifting from it. Trim structured speech text so a
whitespace-only answer is not speakable, and key autoplay's audio cache
by the spoken text, as manual playback already is, so audio cached with
reasoning before this change is never replayed.
* fix: Fall Back to Text When String Content Is Empty
* feat: Let a Theme Quiet Decorative Borders
* test: Cover the Chrome and Inset Border Roles in the Mock Harness
* fix: Draw the Selected Category Tab Edge at the Chrome Share
* fix: Route Chips, Subtle Icon Buttons and Hover Rings Through the Chrome Share
* fix: Draw the Remaining Inner Card Dividers at the Inset Share
* feat: Add a Focus Role for Rows Inside Content
* test: Cover the Subtle Focus Role in the Mock Harness
* test: Probe the Subtle Focus Role Through Its Theme Variable
* test: Focus the Probe to Read the Subtle Focus Utility
* test: Read the Subtle Focus Ring From Its Utility Property
* fix: Ring the Subagent Progress Disclosure in the Subtle Focus Role
* 📴 fix: Finalize Compaction Snapshots and Move Abort Policy Into packages/api
* 🔕 fix: Inspect Every Part When Finalizing and Reuse the Loaded Row
* 📴 fix: Settle Finalized Compaction Rows and Verify Their Anchor
* 📴 fix: Withhold the Unanchored Abort Final and Settle Marked Snapshots
* 📴 fix: Consolidate the Compaction Abort Policy Into One Injected Operation
* 📴 fix: Settle the Live Compaction Row Past an Anchor-Shaped Collision
* 📴 fix: Lift the Failed-Turn Settlement Into the Compaction Module
* 📴 fix: Keep a Removed Round's Failure and Guard Settled Jobs From Snapshots
* ⚡ perf: Read Only the Anchor Id in the Abort Existence Check
* 📴 fix: Withhold the Abort Final Only When a Row Needed Writing
* test: Cover Stopped Compaction Finalization and the Missing Anchor in E2E
* fix: Withhold a Stopped Compaction That Carries No Anchor Id
* fix: Settle Stopped Compactions, Announce Finalized Rows, and Own the Abort Read in packages/api
* test: Accept the Model Spec Query on the Stopped Reply Conversation URL
* fix: Report the Anchor Read Failure Beside a Withheld Compaction Abort
* fix: Synthesize a Compaction Failure Only for a Round After the Latest Outcome
* fix: Skip the Anchor Read When a Stopped Turn Writes No Row
* fix: Decide the Disconnect Snapshot Gate in packages/api
The last-subscriber partial save now asks resolveDisconnectSnapshotMode for
the settled-job decision instead of branching on the job record in the CJS
controller.
* fix: Leave an Already Settled Compaction Row to the Path That Settled It
* 📴 fix: Persist Cancelled Compactions With Their Identity
* 🧪 test: Build the Cancelled-Compaction Leaf on a Real Conversation
* 🧪 test: Assert the Withheld Controls on the Live Cancelled Compaction
* 📴 fix: Keep Live Disconnect Compaction Rows Free of a Synthesized Failure
* 🧪 test: Cover the Compaction Flag in the Redis Job Round Trip
* 📴 fix: Keep a Stopped Compaction Honest and Its Anchor Untouched
* feat: Move Chat Actions Into a Header Options Menu
The header's export/share button becomes a chat options menu with Share, Export, Rename, Pin, Change project, Remove from project, Duplicate, Archive and Delete for the open chat. The sidebar row menu keeps Pin, Mark unread, Rename, Archive and Delete.
* fix: Address Review Findings on the Header Chat Options Menu
Limit read-only subagent threads to share and export, apply the sidebar's rename gate for running chats, let an unchanged title claim ownership, keep later navigation after a late archive, hide history-only actions for temporary chats, expose dialog semantics on the dialog items, and fix import sorting.
* fix: Scope Header Chat Option Dialogs to the Conversation They Opened For
ChatView stays mounted across a route change, so dialog flags now carry the conversation id they were opened for and reset when the open chat or the read-only state changes.
* fix: Settle Header Delete and Rename Dialogs Against the Open Chat
Read the open route when a delete settles, give the delete dialog the id its menu item controls, return focus to the menu item when a rename saves, and only let a close clear the dialog it belongs to.
* fix: Ignore a Late Rename Result After the Dialog Is Gone
A rename that settles after its dialog unmounted no longer closes the parent state or moves focus to the reused menu item.
* fix: Dismiss Header Chat Options When the Route Leaves Their Chat
The route moves before the chat state does and the menu and dialogs are portaled outside the hidden pane, so they are now dismissed on a route change and gated on it. A delete that settles after another chat opened no longer closes that chat's menu, and the options read the freshest cached copy of the chat instead of an older point entry.
* feat: Layered Surface Roles for the ClickHouse Theme
Adds purpose-named roles for the chat canvas, user message, cards, sidebar rows, settings tabs, menu panels, composer and search pill. Each follows the surface it painted before, so the default theme is unchanged; ClickHouse steps them apart with Click UI tokens.
* fix: Align Sticky Phase Headers, Boot Routes, and Row Fades With the Layer Roles
* fix: Cover Trailing Slash and Bare Dashboard Paths in the Boot Canvas Route
* fix: Match Boot Canvas Routes Case-Insensitively
* test: Expect the User Message Role on Other-Author Turns
* test: Expect the User Message Role on the Subagent Briefing