feat(ui): publish document navigation mockups and review packets - #1278
Conversation
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reached
Next review available in:27 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 (7)
📝 WalkthroughWalkthroughThe change adds six Codex review orchestrator prompts, durable-artifact documentation locations, and branch-cleanup ledger records. It also adds a responsive document navigation mockup route with three concepts, route-aware layout behavior, sitemap registration, and Playwright coverage. ChangesReview documentation
Document navigation mockup
Estimated code review effort: 3 (Moderate) | ~25 minutes Sequence Diagram(s)sequenceDiagram
participant Browser
participant MockupsLayoutClient
participant DocumentTopNavigationMockupPage
participant DocumentTopNavigationMockups
Browser->>MockupsLayoutClient: Open /mockups/document-top-navigation
MockupsLayoutClient->>DocumentTopNavigationMockupPage: Select documents mode and hide composer
DocumentTopNavigationMockupPage->>DocumentTopNavigationMockups: Render navigation study
Browser->>DocumentTopNavigationMockups: Select Evidence section
DocumentTopNavigationMockups-->>Browser: Update active state and section content
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:543e4bbbae
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Uh oh!
There was an error while loading. Please reload this page.
BigSimmo
commented
Jul 27, 2026
@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. After fixing or dispositioning a thread, reply in that thread with as the first line, followed by a concise summary; that marker authorizes the workflow to close that exact thread. If human input or new authorization is required, do not use the marker and leave the thread open with the blocker. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation. |
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/prompts/codex-architecture-maintainability-ultra-review.md`:
- Around line 498-500: Update the second-agent verification waves in
docs/prompts/codex-architecture-maintainability-ultra-review.md:498-500,
docs/prompts/codex-data-database-safety-ultra-review.md:484-486, and
docs/prompts/codex-documentation-ownership-ultra-review.md:474-476 to provide
equivalent sequential fallback guidance when parallel subagents are unavailable.
Require each workflow to report that limitation so final classifications do not
imply independent verification that was not performed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 370ca2b0-a143-44f2-a3f9-becaf1bc4b3e
📒 Files selected for processing (18)
docs/branch-review-ledger.mddocs/codex/architecture-maintainability/README.mddocs/codex/data-database-safety/README.mddocs/codex/documentation-ownership/README.mddocs/codex/functional-correctness/README.mddocs/codex/performance-reliability/README.mddocs/codex/tests-quality-gates/README.mddocs/prompts/codex-architecture-maintainability-ultra-review.mddocs/prompts/codex-data-database-safety-ultra-review.mddocs/prompts/codex-documentation-ownership-ultra-review.mddocs/prompts/codex-functional-correctness-ultra-review.mddocs/prompts/codex-performance-reliability-ultra-review.mddocs/prompts/codex-tests-quality-gates-ultra-review.mddocs/site-map.mdsrc/app/mockups/document-top-navigation/page.tsxsrc/app/mockups/mockups-layout-client.tsxsrc/components/document-top-navigation-mockups.tsxtests/ui-document-top-navigation-mockup.spec.ts
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:71d442e792
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Uh oh!
There was an error while loading. Please reload this page.
Summary
Verification
npm run workflow:flightplan -- --write-evidence— PASSnpm run check:branch-review-ledger— PASSnpm run sitemap:check— PASSnpm run docs:check-index— PASSnpm run docs:check-scripts— PASSnpm run docs:check-links— PASS after adding the six tracked packet directoriesgit diff --check— PASSnpm run verify:cheap,npm run ensure, focused mockup Playwright,npm run verify:ui, andnpm run verify:pr-local— pending the repository's legitimate shared heavy-test ownerRisk and rollback
Risk is limited to design-scratch mockups and documentation. Mockups remain production-excluded by the existing mockup route contract. Roll back by reverting the three commits.
No live OpenAI, Supabase, Railway, ingestion, answer-generation, or clinical provider workflow was run.
RAG impact: no retrieval behaviour change — documentation and design-scratch mockups only.
Summary by CodeRabbit
New Features
Documentation
Tests