issues: retain preserved UI follow-ups#1116
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Warning Review limit reached
Next review available in: 50 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
#064#065Validation
npm run docs:check-links: passed (1,140 references)npm run docs:check-index: passednpm run check:skills: passedgit diff --check: passedRisk
One documentation file only. The accordion remains paused until explicit user return. No application code, tests, builds, providers, secrets, production data, or deployment behavior changed.
RAG impact: no retrieval behaviour change — task-ledger documentation only.
Note
Low Risk
Single documentation file only; no runtime, tests, or deployment behavior changes.
Overview
Updates
docs/outstanding-issues.mdso two in-flight UI efforts stay on the universal ledger without changing application code.Adds #64 (reconcile the isolated formulation disabled/contrast patch from
agent/formulation-disabled-contrast) at queue order 16, ahead of the release UI gate #55, with Playwright andverify:uicalled out. Adds #65 (finish the paused compact document source-text accordion oncodex/chat-document-text-accordion-7cb4) at order 35, explicitly paused until the user resumes. Matching Open items rows document outcomes, gates, and stop conditions for both.Existing queue entries after #64 are renumbered (prior orders 16–33 → 17–34);
<!-- issues:next-id=066 -->advances the allocator from 64.Reviewed by Cursor Bugbot for commit 1b5f709. Configure here.