* 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
* 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