* feat: Audit Resource ACL Changes and Fail Closed by Default
* fix: Keep Non-Reversible Admin Audit Handlers Fail-Open
* docs: Narrow AUDIT_LOG_FAIL_CLOSED Description
* fix: Audit and Restore ACL and Insights Changes in One Pass
* fix: Break Audit and Insights Permission Type Cycle
* test: Cover Resource ACL Audit Scenarios
* refactor: Audit Resource Permission Changes Before Writing
* test: Align Concurrent Revoke Audit Expectation
* fix: Skip Deleting ACL Entries That Were Not Audited
* fix: Read ACL Snapshots Through the Write Session
* fix: Never Block Revocations on Audit Outages and Normalize Principal Keys
* fix: Let an Explicit Public Disable Win Over a Public Update
* fix: Audit Duplicate ACL Rows as Combined Permissions
* fix: Audit Permission Changes Under One Target and Dedupe Revokes
* fix: Audit Capability Grants Before Writing Them
* feat: Serialize Resource Permission Updates With a Per-Resource Lease
* fix: Fence the Resource Lease Before Writes and Always Audit Grant Assignments
* fix: Renew the Resource Lease Before Each ACL Write Phase
* fix: Serialize System Grant Assignment and Revocation With a Per-Grant Lease
* fix: Keep Leases Alive During Audits, Bound Lock Index Wait, Canonicalize Audit Target IDs
* fix: Retry Deferred Revoke Audits Under the Lease and Audit Canonical Principal and Role IDs
* test: Expect Role IDs in Permission Audit Metadata
* fix: Read Mutation Snapshots From the Primary Outside Transactions
* fix: Flush Deferred Audits Before Cache Invalidation, Keep Renewals Monotonic, Keep Role Case in Grant Lease Keys
* refactor: Map the Busy Permission Error to Its Code in the API Package
* style: Sort Lease Imports and Type the Renewal Spec Read
* fix: Keep Success Audits After Commit, Report Downgrades as Revocations, Code Audit Outages
* refactor: Move the Audit Outage Code to Its Own Module
* fix: Translate Lock Failures, Lease Non-Transactional Sessions, and Code Grant Audit Outages
* fix: Sanitize Lease Renewal Failures at the Permission Boundary
* fix: Annotate the Unavailable Error Code for Isolated Declarations
* fix: Keep the Admin Route Fail-Closed Opt-In and Document Lease Clock Skew Safety
* fix: Translate Grant Lease Store Failures to a Retryable 503
* fix: Log Failed Grant Audit Writes With Safe Metadata Only
* test: Detect Raw Error Arguments in the Grant Audit Log Spec
* feat: Make Permission Lease Limits Configurable and Localize Retryable Sharing Failures
* fix: Bound Lock Index Readiness by the Lease Wait and Carry the Resource ID in Every Audit Entry
* test: Cover Lease Config Reaching the Leases and the Sharing Dialog Failure Messages
* fix: Load App Config on the Sharing and Grant Routes and Log Failed Lease Releases
* perf: Load App Config Only on the Grant Mutation Routes
* 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
* fix: Enforce Terms Acceptance on the Server When modalAcceptance Is On
* fix: Mark Backfilled Terms Acceptance Timestamps
* test: Cover Server-Enforced Terms Acceptance in the Mock Harness
* fix: Gate Management Routes and Skill Sync and Resolve Terms Policy Fail-Closed
* fix: Evict Cached Auth Documents When Terms Acceptance Is Reset
* fix: Guard Skill Sync Behind Terms Acceptance for Every Skill List Route
* fix: Move Terms Skill-Sync Guard Into the API Package and Evict All Users on Reset
* fix: Batch Terms Reset Cache Eviction and Sign the Spec User In Fresh
* fix: Let Stop Through the Terms Gate, Refresh Startup Config, and Wait Out Failed Eviction
* refactor: Narrow the Terms Exemptions and Share One Refusal Path Across Clients
* refactor: Compose the JWT Terms Gate Through an API Package Helper
* style: Sort Imports for the Shared Terms Refusal Helper
* test: Expose the Terms Gate Helper in the JWT Auth Spec Mock
* test: Cover the Terms Refusal Code on Pre-Stream Upload Errors
* feat: Paint the Operator Theme on a First-Ever Visit
The server embeds the deployment's base interface.theme in the HTML shell, with both modes the build resolved for a bundled name, so the boot script and the first commit of DeploymentTheme paint it before /api/config answers. A tab's owned cache still outranks it, shared links skip it, and a request scoped by a trusted X-Tenant-Id header gets the shell without it.
* test: Type the Inline Shell Theme Fixture as Raw JSON
* test: Tag the First-Visit Scenarios Literally
* fix: Ignore a Theme Boot File That Is Not an Object
* fix: Keep the Base Theme for a Tenant Header the Config Rejects
* fix: Report a Theme Boot File That Exists but Cannot Be Read
* fix: Embed the Base Config Theme in the Experimental Shell
* test: Stand In the Shell Theme for an Owned Copy Whose Session Ended
* fix: Boot-Paint a Cached Theme Only for the Tab's Signed-In Owner
The boot script and DeploymentTheme's first commit replayed the deployment-theme cache without checking its owner, so a browser that last held one identity's theme painted it for another until the config answered. The tab now records its signed-in owner in session storage and both paths replay the cache only when it matches.
* test: Assert Session Ends Forget the Tab Theme Owner
* test: Hold the First-Paint Config Answer Until the App Paints
* fix: Skip the Boot-Painted Theme Cache Once the Session Has Ended
* fix: Bind the Readable Session Hint to the Signed-In Owner
* test: End the Session for Real in the Expired-Hint Scenarios
* fix: Clear the Session Hint When a Local Refresh Finds No Session
* test: Give the Refresh Specs the Cookie Surface the Session Hint Uses
* test: Count the Signed-Out Config Answer in the No-Cached-Paint Scenarios
* fix: Retire the Session Hint on Every Rejected OpenID Refresh
* fix: Retire the Session Hint When a Refresh Carries No Token
* fix: Retire the Session Hint on Account Deletion and Password Reset
* refactor: Own the Session Hint Lifecycle in the Typed Auth Cookies
* fix: Hold Button Heights and the Dialog Close Button at the 24px Target
* fix: Write a Zero Button Height as a Length the Target Floor Can Compare
* test: Let the Delete Dialog Settle Before Measuring Its Close Glyph
* test: Pin the Theme Cache Digest the Rebased Resolver Emits
* feat: Add a Connected Account Setting for Pull Requests
* fix: Watch an Open Account Sign-In and Keep the Retry Button Named
* fix: Name the Disconnect Confirmation and Show the Provider the Server Reports
* feat: Tell the Client How Long a Pull Request Account Sign-In Lasts
* fix: Follow the Sign-In Lifetime and Keep Account Actions Settled Past Settings
* fix: Watch an Account Sign-In Until Its Window Closes, Even After Settings Closes
* fix: Refresh Pull Requests Once per Change of the Credential They Were Fetched With
* fix: Record Every Status the Sign-In Watch Reads
* fix: Keep Watching a Severed Sign-In Through Its Landing Page and End Watches With the Session
* fix: Drop a Sign-In Begun Before the Session Ended
* fix: Keep a Surviving Grant Removable and Tie a Sign-In Watch to Its Own Flow
* fix: Ask for the Pull Request Account Wherever Pull Requests Are On
* fix: Refresh Pull Requests on a Session's First Status and End a Failed Sign-In's Watch
* fix: Ignore an OAuth Failure That Names No Sign-In Flow
* fix: Start No Sign-In for a Window Closed Before the Server Answered
* fix: Keep a Known Grant Removable While the Status Check Fails
* fix: Name a Grant Without a Current App Only as an Account
* fix: Keep the Pull Request Account Row Readable on a Phone
* fix: Show a Grant Whose App Is Off as Not in Use
* fix: Apply a Sign-In Status Asked For Before the Flow Expired
* fix: Keep Focus When Removing the Last Pull Request Grant and Reuse Its Status
* fix: Resync Pull Request Credentials After Failed Sign-Ins and Disconnects
* fix: Ask for the Connection Status Afresh Once a Sign-In Settles
* fix: Resync Pull Requests From the Settings Visibility Status
* fix: Reconcile Pull Request Credentials Until a Status Read Succeeds
* fix: Keep Pull Request Sign-In State Accurate Across Failures and Account Switches
* fix: Drop Replaced Sign-In Answers and Reset Status When the Account Changes
* fix: Reset Unwatched Connection Status and Keep Focus When a Retry Hides the Row
* fix: Hear Late Sign-In Settlements and Explain Connect Failures After Settings Closes
* fix: Listen Until a Sign-In Settles and Keep Focus After a Dismissed Disconnect
* fix: Stop Cache Audit From Logging Cache Keys and Values
* fix: Keep Cache Audit Output to Counts and TTL
* fix: Log Cache Audit at Info So the Debug Toggle Still Emits
* test: Cover Cache Audit Redaction in the Mock Lane
* test: Run Cache Audit Scenario Against In-Memory Stores
* test: Parse Cache Audit Probe Output Before Asserting
* fix: Render Cache Audit Statistics in the Message and Move Formatting to packages/api
* fix: Encrypt User Plugin Credentials With Random-IV v3 Format
* test: Cover Credential Encryption Formats in Mock E2E Scenarios
* test: Round-Trip Real Credential Helpers in PluginService Spec
* 🙈 fix: Remove SharePoint Picker Payload Logging (#16997)
* fix: Add credentials.writeFormat to Gate v3 Credential Writes During Rollouts
* test: Expect 201 When the Legacy Write Format Override Is Created
* fix: Clear TTS Audio Cache On Session End and Hash Its Keys
* fix: Read Manual TTS Replays From the Hashed Cache Key
* fix: Purge Legacy TTS Cache Keys and Fence Writes Across Logout
* fix: Keep TTS Cache Writes Off the Playback Path
* test: Expect Hashed Keys in the StreamAudio Cache Lookup
* test: Use a Single-Token Reply Label in the TTS Cache Scenario
* fix: Settle TTS Cache Clear Before IdP Logout and Across Tabs
* test: Cover the TTS Cache Fence When Another Tab Logs Out
* test: Wait for the Second Tab Before Logging Out in the TTS Scenario
* fix: Latch TTS Cache Writes Shut Until the Tab Authenticates Again
* fix: Reopen TTS Cache Writes When Authentication Completes In Place
* fix: Leave for the IdP Even When TTS Cache Cleanup Fails
* fix: Retry a Failed Legacy TTS Purge and Fence Other Tabs on Manual Clear
* fix: Rerun the Legacy TTS Purge After Each Clear and Sign-In
* fix: Rerun the Legacy TTS Purge When Another Tab Clears
* fix: Fence Pre-Auth TTS Writes, Retry Failed Clears, and Fall Back to Storage Events
* fix: Version the Hashed TTS Cache Key Path
* fix: Move TTS Audio to a New Cache and Keep It Closed Until a Failed Clear Succeeds
* fix: Persist a Pending TTS Cache Delete Across Navigation
* fix: Reopen TTS Caching Only on Session Start and Fence Cache Reads
* fix: Keep the TTS Delete Fence in Cache Storage and Close Reads After Logout
* refactor: Keep Read-Aloud Audio in Tab Memory Instead of Cache Storage
* test: Return to the Conversation After Re-Login in the TTS Logout Scenario
* test: Close the Phone Sidebar Before Replaying in the TTS Logout Scenario
* fix: Bound the In-Memory TTS Cache by Size as Well as Count
* fix: Scope Cached TTS Audio to the Signed-In User
* fix: Keep the Settings Cache Delete Available While Legacy Audio Remains
* fix: Recheck Legacy TTS Audio After a Settings Clear and on Unowned Handoff
* fix: Fence TTS Writes Started Before an Account Signs In
* test: Opt the Fresh TTS Account Into Enter-to-Send
* fix: Load Google Tag Manager Only After Analytics Consent
Google Tag Manager initialized as soon as the chat footer or the chat route mounted whenever ANALYTICS_GTM_ID was set, for signed-in users and shared-link viewers alike, with no consent check. A single useAnalytics hook now owns initialization and loads the container only after the viewer grants consent, recorded in a persisted Jotai atom. A non-modal banner asks for that consent in the signed-in layout and on shared links, and a Data controls toggle changes it later; withdrawing consent pushes a consent mode update to a loaded container and completes on reload.
* fix: Restore Analytics Consent to a Container Still on the Page
* test: Cover Analytics Consent Scenarios
* test: Observe Missing Tag Manager Requests Over a Bounded Window
* fix: Recognize Only the Configured Tag Manager Container
* fix: Send Consent Withdrawal Only to the Configured Container
* fix: Describe the Consent Withdrawal Guard Accurately
* fix: Keep Advertising Consent Denied When Analytics Is Allowed
* fix: Let Shared-Link Viewers Change Analytics Consent
* fix: Retry a Tag Manager Container That Never Registered
* fix: Treat a Loading Container as Present and Drop It When It Fails
* fix: Drop a Failed Tag Manager Attempt's Start Event Before Retrying
* fix: Encrypt User Plugin Credentials With Random-IV v3 Format
* test: Cover Credential Encryption Formats in Mock E2E Scenarios
* test: Round-Trip Real Credential Helpers in PluginService Spec
* 🙈 fix: Remove SharePoint Picker Payload Logging (#16997)
* fix: Add credentials.writeFormat to Gate v3 Credential Writes During Rollouts
* test: Expect 201 When the Legacy Write Format Override Is Created
* 🔊 fix: Clear TTS Audio Cache On Session End and Hash Its Keys (#16998)
* fix: Clear TTS Audio Cache On Session End and Hash Its Keys
* fix: Read Manual TTS Replays From the Hashed Cache Key
* fix: Purge Legacy TTS Cache Keys and Fence Writes Across Logout
* fix: Keep TTS Cache Writes Off the Playback Path
* test: Expect Hashed Keys in the StreamAudio Cache Lookup
* test: Use a Single-Token Reply Label in the TTS Cache Scenario
* fix: Settle TTS Cache Clear Before IdP Logout and Across Tabs
* test: Cover the TTS Cache Fence When Another Tab Logs Out
* test: Wait for the Second Tab Before Logging Out in the TTS Scenario
* fix: Latch TTS Cache Writes Shut Until the Tab Authenticates Again
* fix: Reopen TTS Cache Writes When Authentication Completes In Place
* fix: Leave for the IdP Even When TTS Cache Cleanup Fails
* fix: Retry a Failed Legacy TTS Purge and Fence Other Tabs on Manual Clear
* fix: Rerun the Legacy TTS Purge After Each Clear and Sign-In
* fix: Rerun the Legacy TTS Purge When Another Tab Clears
* fix: Fence Pre-Auth TTS Writes, Retry Failed Clears, and Fall Back to Storage Events
* fix: Version the Hashed TTS Cache Key Path
* fix: Move TTS Audio to a New Cache and Keep It Closed Until a Failed Clear Succeeds
* fix: Persist a Pending TTS Cache Delete Across Navigation
* fix: Reopen TTS Caching Only on Session Start and Fence Cache Reads
* fix: Keep the TTS Delete Fence in Cache Storage and Close Reads After Logout
* refactor: Keep Read-Aloud Audio in Tab Memory Instead of Cache Storage
* test: Return to the Conversation After Re-Login in the TTS Logout Scenario
* test: Close the Phone Sidebar Before Replaying in the TTS Logout Scenario
* fix: Bound the In-Memory TTS Cache by Size as Well as Count
* fix: Scope Cached TTS Audio to the Signed-In User
* fix: Keep the Settings Cache Delete Available While Legacy Audio Remains
* fix: Recheck Legacy TTS Audio After a Settings Clear and on Unowned Handoff
* fix: Fence TTS Writes Started Before an Account Signs In
* test: Opt the Fresh TTS Account Into Enter-to-Send
* refactor: Lift the step handler branches into a core reduceStep
The stepHandler branches move to @librechat/chat as reduceStep(state, event, ctx), with the per-run maps in a StreamState and every write outside the message list returned as a StepEffect. useStepHandler keeps the frame coalescing and applies the effects to the Jotai and Recoil stores.
The equivalence spec runs a frozen copy of the previous hook against the new binding on each recorded sequence and compares every channel they write.
* test: Pin the step reducer equivalence digests and drop the frozen handler
* test: Load the step reducer from the built chat core
* test: Type the equivalence fixtures to the event unions
* ci: Type-Check Workspaces with bun check
Make every workspace tsconfig valid under TypeScript 7 semantics while
staying clean on the installed tsc 5.9: explicit types arrays (TS 7 no
longer auto-includes node_modules/@types), es2017 target for
data-provider, rootDir for api specs that import client contracts, and
noUncheckedSideEffectImports off for the CSS and matchMedia mock imports.
Fix the four client type errors newer DOM and Intl libs expose, and drop
the fetch.preconnect copy in useRum that only existed to satisfy the
leaked @types/bun globals.
Switch the client typecheck script and the CI type-check steps to
bun check (Bun 1.4.3); tsc --noEmit stays available as typecheck:tsc.
* chore: Fall Back to tsc When bun check Is Unavailable
Add scripts/typecheck.mts, which runs bun check when the installed Bun
provides it and the repository's tsc otherwise, so contributors without
Bun can still type-check. The client typecheck script and the
static-checks TypeScript gate both resolve their checker through it,
keeping local runs on the same checker CI uses whenever Bun is present.
* ci: Type-Check the Chat Package Through the Shared Checker
* ci: Run the Type Check When Only the Shared Checker Changes
A change to scripts/typecheck.mts alone started neither frontend review
nor the static-checks TypeScript gate, so a broken resolver could merge
unexercised. Add it to the frontend-review triggers and to every
typecheck project's paths.
The suppression-baseline scenarios copy static-checks.mts into synthetic
roots; copy its new typecheck.mts import alongside i18n.mts so the runner
loads there. Add scenarios for the checker choice and its fallback.
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
* 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
ChatView was the last chat reader of store.saveDrafts; it now takes the value from useChatSettings(), so a host that supplies its own chat settings drives ask-answer draft saving as it already drives the composer's. Inside the app both sources hold the same value.
* 🧯 feat: Recover Conversations Whose Attachments Keep Failing
Once a branch carries a problem attachment, every turn resends it and
fails the same way. A failed response whose branch carries files now
offers "Retry without files" (re-asks the failed turn with no files as a
new version) and, when earlier turns carry files, "Branch without files"
(a copy up to the last good answer with every upload and code output
left out, with the failed message restored to the composer). File-shaped
errors say so in the card.
The edit view shows a user message's files as removable chips; "Update &
rerun" sends only the kept files and Save is disabled after a removal.
Fork is offered on a failed turn and gains a "Leave out files" option,
backed by a new `excludeFiles` fork option that drops `files`,
`attachments` and the conversation's `files` from the copy.
Bedrock rejects a request whose documents share a name, and history
resends every earlier document, so repeated names are now numbered
before formatting.
* 🧯 fix: Cover Steered Files, Hand Off the Whole Failed Turn, Name Replayed Documents Once
- Excluding files from a fork also strips attachments steered into a
response (`content[].files` on steer parts), which replay like uploads,
and the decision lives in `forkFileScope` in packages/api.
- The recovery card counts steered attachments as files, and reads the
specific code inside a generic `error` envelope, so a rate limit is not
offered files as the fix.
- "Branch without files" hands the failed turn to the copy's composer the
way a message is put back for editing: text through the in-memory
handoff, quotes, manual skills and the reasoning override through their
compose-time atoms.
- Document names are deduplicated over the formatted payload after the
steer stamp, so replayed steer documents are numbered too.
- Fork stays withheld on a failed response, whose copy would carry the
error as an ordinary answer; the card's branch action copies up to the
turn before.
- Remove-file buttons are natively disabled while the editor is locked.
* 🧯 fix: Keep Search Sources, Scope Root Retries, Skip Legacy Rate Limits
- A fork without files keeps metadata-only attachments (search sources,
file search results) and drops only file-backed ones; the recovery card
likewise counts only file-backed attachments as files.
- A turn sent at the root takes none of the conversation's file refs: its
siblings' uploads (an edited first message, or one retried without its
files) no longer come back through the unanchored-continuation fallback.
- Rows that carry a legacy LangChain model, key or rate-limit code are not
offered files as the fix.
* 🧯 fix: Align File Exclusion With Replay's File Shapes, Skip Assistants, Verify the Copy
- Shared `messageCarriesFiles` (with `isFileContentPart`,
`hasContentPartFiles`, `isFileAttachment`) in data-provider names every
shape historical replay reads a file by: uploads, file-backed
attachments, attached `files` on any content part, and `image_file`,
`file` or direct `file_id` locators. The fork drops all of them and the
recovery card detects all of them.
- Assistants conversations get no recovery actions: their upstream thread
keeps every attachment, and those endpoints offer no fork either.
- "Branch without files" checks the returned copy; a server that ignored
`excludeFiles` gets an error toast instead of a false recovery.
* 🧯 fix: Type Replay's Provider-Native File Locators for the Part Predicates
The usage atom families, the breakdown preference and their helpers move from client/src/store/usage.ts to client/src/components/Chat/Input/TokenUsage/store.ts, beside the components that render them, and the store index stops re-exporting them. The SSE usage handler, the token-usage hook, the chat submission hook and their specs import the feature module. No behavior change.
* 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.
* 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