* 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
* 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
* feat: Let Users Connect Their Own Account for Pull Request Lookups
* fix: Refuse Cross-Tenant Pull Request Callbacks and Surface Key Failures
* fix: Keep Pull Request Grants Through Outages and Remove Them on Disconnect
A token endpoint server error is an outage even with an OAuth error body, so
it no longer deletes the grant, and a refresh outage reaches the lookup as
unavailable instead of falling back to no token. Disconnect removes every
pr_oauth row of the user, whatever app or host is configured now. A grant that
never expires extends its retention when used, and the flow, request and
retention limits are configurable. The connection routes are built in
packages/api, mounted behind the pre-auth tenant middleware in both servers,
and answer failures with stable codes.
* fix: Keep the Pull Request OAuth App Out of Overrides
A role, group, user or tenant override can no longer change or remove pullRequests.oauth, so the connect capability and the callback see the operator's app.
* fix: Read a User's Pull Request Token Only With the Feature On
* fix: Report a Malformed Stored Pull Request Grant as a Failure
* fix: Remove a User's Stored Tokens When an Administrator Deletes the User
* fix: Answer No Pull Request for a Conversation Without a Lane When the User Token Fails
* fix: Share One Grant Read Between Concurrent Callers and Report an Expired Grant Disconnected
* fix: Remove a Pull Request Grant Only on a Definite Refusal and Past Its Retention
* fix: Version Pull Request Grants and Coordinate Refresh, Refusal and Retention Through Them
* fix: Invalidate a Refused User Token and Read It Only for a Lane That Needs It
* fix: Finish a Pull Request Connection Under the User's Effective Config Behind the Login Limiter
* fix: Type the Pull Request User Token for Isolated Declarations and Settle Retention Before Answering
* fix: Bind a Pull Request Connection Flow to the Generation a Disconnect Replaces
* fix: Start a Batch's User Token Read Only Within Its Deadline
* fix: Fence Pull Request Token Reads Against a Disconnect and Report a Failed Retention Cleanup
* fix: Fence Connection Status Like Token Reads and Keep a Newer Read Joinable
* fix: Report a Pull Request Grant Without Its App and Name the Sign-In That Made It
* fix: Read a User's Unexpired Pull Request Grants Newest First
* fix: Mark the Connection Callback as an OAuth Navigation and Report a Failed Extension
* fix: Name the Pull Request Sign-In Flow on Its Landing Page
* fix: Remove a Pull Request Grant of a Replaced App When It Is Read
* fix: Keep a Replaced App's Grant Untouched and Extend Retention From Each Day's Use
* fix: Accept a Pull Request Grant Only Under the User's Current Connection Generation
* fix: Renew the Connection Generation With a Grant Still in Use
* fix: Restore the Previous Connection When a Sign-In Cannot Store Its Grant
* fix: Decide a Sign-In by What Was Stored When a Write Does Not Answer
* fix: Roll Back a Sign-In's Generation Along With a Grant It Must Remove
* fix: Refresh an Access Token a Lookup Was Refused With Before Ending the Connection
* fix: Undo a Sign-In Only for a Confirmed Fence, Not a Failed Check
* fix: Read a User Token Again When the Connection Changes Under the Read
* fix: Apply the Current Retention Again When Another Replica Changed the Grant First
* test: Answer Each Concurrent Sign-In by Its Own Code
* fix: Skip Retention Rewrites for Grants That Expire Without a Refresh Token
* fix: Retry a Token Rejection That Loses to a Concurrent Grant Write
* fix: Skip User Token Reads for Lanes Without a Commit and Reread Status After a Reconnect
* 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.
* feat: Share Pull Request Lookups Across Replicas Through Redis
* fix: Bound the Shared Pull Request Cache and Drop Commands at Their Deadline
* fix: Pass the Cache Config to the Pull Request Store and Check It Before a Local Cooldown
* fix: Keep Batch Lookups Apart by Cache and Sharing Policy
* fix: Share Only Found Pull Requests and Rate Limits, Never Moving Them Backwards
* feat: Look Up Bitbucket Cloud Pull Requests
* fix: Keep the Pull Request Host Out of Overrides and Per-Host Keys
A role, group, user or tenant override can no longer change or remove pullRequests.host, so feature gating and link recording see the operator's host. Links are recorded only from the configured host, and the batch share key and the rate limit cooldown are scoped by host.
* fix: Compare Pull Request Link Hosts Through the Host Resolver
* test: Add Pull Request Scenarios Against a Fake GitHub Enterprise Host
* fix: Keep the Pull Request Provider Out of Overrides and the Batch Share Key
A role, group, user or tenant override can no longer change pullRequests.provider, so feature gating and link recording agree with the lookup, and a batch lookup for one provider is never joined by a request for another.
* fix: Read GitLab History Apart From Open Merge Requests
Merged and closed merge requests are listed on their own, so open fork merge requests on the branch name cannot crowd them out. Rate limit cooldowns are scoped by provider, and a workspace repository with a dot segment is rejected.
* fix: Revalidate Bitbucket Pull Requests and Skip Ones Without a Source Commit
Read a full closed page so a newer closed fork cannot hide an older pull request from the repository, recheck the source branch and fork status on the detail, and treat a pull request without a source commit as unmatchable instead of failing the lookup.
* fix: Follow Bitbucket's Next Link When Listing Pull Requests
* fix: Record the Lane Pull Request Without an Aggregation Pipeline Update
* fix: Match an Empty Lane Repository as Unknown
* fix: List Locked GitLab Merge Requests With the Open Ones
* fix: Replace an Expiring Fake Git Host Certificate
A conversation's pull request was found only by searching its branch for a PR whose head
contains the recorded commit, so a single unpushed local commit hid an existing PR.
The attached bash tool now hands its output to the lane recorder, which records a
github.com pull request link to the lane's repository with the lane state. The link is kept
across later reports on the same branch and repository and dropped when either changes. The
GitHub source reads a linked PR directly and accepts it when its head is the lane branch in
the lane repository; a fork's PR must carry the recorded commit. The single and batch routes
both pass the link, and the batch route keys lanes by it.
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: 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
* 🧯 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
* 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
* 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
* 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
* 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: 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
* feat: Filter OpenRouter Reasoning Efforts by the Selected Model
* fix: Address Review Findings on OpenRouter Per-Model Reasoning Efforts
* fix: Report Catalog Failures, Share Lookups and Honor Direct Endpoints for Reasoning Efforts
* fix: Move Capabilities Handler Into packages/api and Harden Catalog Lookups
* fix: Scope Reasoning Capabilities to One Endpoint and Gate Editors Until They Load
* fix: Skip Catalog Reads for Explicit Definitions and Keep Staged Efforts While Loading
* fix: Retry the Reasoning Capabilities Query on Focus and Reconnect After a Failure
* fix: Remember Failed Catalog Lookups, Reject Locked Overrides Early and Keep Restored Efforts
* fix: Hide Efforts Until the Catalog Is Known, Keep Unlisted Models Unknown and Accept Auto
* fix: Mark OpenRouter Endpoints by Their Resolved Host so the Client Fetches Capabilities
* fix: Share One OpenRouter Catalog Rule, Build the Catalog URL Safely and Make the Lifetime Configurable
* fix: Forward Static Catalog Headers, Resolve Relative Next Links and Align Client Freshness
* fix: Limit Capabilities to Exposed Models and Revalidate Against the Server Entry Expiry
* fix: Hide Efforts After a Failed Refresh, Reject Malformed Pagination and Skip User-Scoped Catalogs
* fix: Use Own-Property Lookups, Skip the Catalog for Auto and Revalidate From the Remaining Lifetime
* fix: Treat Request Metadata Headers as Shared, Store Catalogs as Own Entries and Hide Efforts During Refresh
* fix: Keep Configured Query Parameters Across Catalog Pages and Treat Expired Idle Data as Unknown
* fix: Expose Only Configured Variants, Skip Identity Headers on Fixed Lists and Keep Staged Efforts
* feat: Infer Reasoning Effort Support From Known Custom Endpoint Hosts
* fix: Gate Inferred Reasoning on Provider Support and dropParams
* fix: Infer Reasoning for the OpenRouter Params Endpoint Set by the Loader
* 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
* 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
* 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