docs(ui): capture Crew organizer coverage - #630
Conversation
|
Warning Review limit reached
Next review available in: 31 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 Run ID: ⛔ Files ignored due to path filters (12)
📒 Files selected for processing (102)
✨ 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Independent exact-head review receipt for Verdict: LGTM — no blocking findings. Verified independently:
Risk is low because the commit changes no executable symbols or runtime flows. GitNexus indexing of this exact worktree completed, but its MCP reader rejected the freshly built DB due a local storage-version mismatch; the exact raw diff and changed-record comparison independently confirm the docs/LAT-only scope. |
d6316c1
into
codex/ui-field-primitives
What changed
Why
This establishes reproducible organizer-flow evidence on top of the shared field primitives before broader UI extraction work. It also records three concrete mobile overflow findings without changing application behavior in this slice.
Validation
e7ba19fa32e0c95b49793e4afbfcf2cbe302fdd7pnpm check:page-coveragelat checkThe full Crew suite remains baseline-red at this exact head: 170/173 files and 3158/3160 tests pass. Existing failures are two missing component import suites and two stale event-import label assertions; the XLSX decompression-cap suite passes 21/21. None touch this documentation/evidence-only diff.
mainSummary by cubic
Adds reproducible evidence for the Crew organizer, admin, and token/series flows across desktop and mobile; all captures are clean. Introduces shared
@repo/ui/empty-stateand@repo/ui/metricpatterns to standardize organizer UIs and improve responsive behavior and semantics.New Features
crew-*-coverage-audit.md.@repo/ui/empty-stateand@repo/ui/metric, adopts them across Crew and Start, and adds Storybook stories for both.Bug Fixes
__rootand adds Playwright checks for responsive headers.Written for commit d6316c1. Summary will update on new commits.