Skip to content

Refresh eval dashboard and align UI with updated product shell#6

Merged
0xaeres merged 3 commits into
mainfrom
feature/update-eval-dashboard-details
Jul 11, 2026
Merged

Refresh eval dashboard and align UI with updated product shell#6
0xaeres merged 3 commits into
mainfrom
feature/update-eval-dashboard-details

Conversation

@0xaeres

@0xaeres 0xaeres commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Updated the evals experience with grouped metric visualization and refreshed dashboard details
  • Aligned setup, landing, council, connector, and skill screens with the revised Anvay design system and shell structure
  • Added/updated API, event stream, and type plumbing to support the new UI flows
  • Reworked branding assets, icons, and global styling to match the updated visual identity

Testing

  • Not run (not requested)

@vercel

vercel Bot commented Jul 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
anvay-ui Ready Ready Preview, Comment Jul 11, 2026 3:57pm

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@0xaeres, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 9dab9554-f474-4288-8e95-09538ff92191

📥 Commits

Reviewing files that changed from the base of the PR and between 99125e0 and c24440f.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • components/evals/MetricGroupedBarChart.tsx
  • lib/api/index.ts
  • lib/evals.ts
  • package.json
📝 Walkthrough

Walkthrough

The landing page now uses reusable navigation, scrollspy, progress, back-to-top, and motion-fallback components with expanded styling. Supporting screens update missing-value placeholders and several status, description, and punctuation strings.

Changes

Landing experience

Layer / File(s) Summary
Landing layout and visual styling
app/globals.css
Landing anchor offsets, navigation states, chips, centered headers, and evaluation statistics styling are updated.
Scroll-driven motion behavior
app/globals.css
Scroll-driven animation styles, parallax keyframes, motion fallback states, and back-to-top styling are added.
Landing navigation and page composition
components/screens/LandingChrome.tsx, components/screens/LandingPage.tsx
Reusable landing navigation, scrollspy, scroll progress, motion fallback, and back-to-top components are wired into the page with updated copy and evaluation markup.

UI copy and missing-value normalization

Layer / File(s) Summary
Missing-value display updates
components/screens/ConnectorDetail.tsx, components/screens/EvalsScreen.tsx
Missing synchronization and diagnostic values now display N/A.
Status and descriptive wording
components/screens/ConnectorNew.tsx, components/screens/CouncilSession.tsx, components/screens/CouncilStage.tsx, components/screens/EvalsScreen.tsx, components/screens/SkillDetailPage.tsx
Connector, council, evaluation, and manual rerun text is updated for wording and punctuation consistency.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Visitor
  participant LandingNav
  participant LandingMotion
  participant ScrollTopButton
  participant LandingPage
  Visitor->>LandingPage: scroll landing page
  LandingNav->>LandingNav: update active section and progress
  LandingMotion->>LandingPage: reveal and transform motion elements
  ScrollTopButton->>Visitor: show after scroll threshold
  Visitor->>ScrollTopButton: click back to top
  ScrollTopButton->>LandingPage: smoothly scroll to page top
Loading

Possibly related PRs

  • 0xaeres/anvay-ui#2: Earlier landing-page structure and styling continued by this landing rework.
  • 0xaeres/anvay-ui#5: Related evaluation dashboard work connected to the updated evaluation screen text and fallbacks.

Poem

I hop through the nav as the page glides by,
With glowing sections and motion-lit sky.
“N/A” keeps blank data neat and clear,
Plain words make every status easier to hear.
Back to the top—away we go! 🐇

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main UI refresh across the eval dashboard and updated product shell.
Description check ✅ Passed The description is clearly related to the changeset and matches the eval, shell, styling, and UI updates.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 `@components/screens/LandingChrome.tsx`:
- Line 117: Update the onClick scroll handler in LandingChrome to respect
prefers-reduced-motion: use smooth scrolling only when the user prefers motion
and instant scrolling otherwise, while preserving the existing scroll-to-top
behavior.
🪄 Autofix (Beta)

✅ Autofix completed


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5b480757-18c2-465a-ae38-1680e18ae64d

📥 Commits

Reviewing files that changed from the base of the PR and between e80387f and 99125e0.

📒 Files selected for processing (9)
  • app/globals.css
  • components/screens/ConnectorDetail.tsx
  • components/screens/ConnectorNew.tsx
  • components/screens/CouncilSession.tsx
  • components/screens/CouncilStage.tsx
  • components/screens/EvalsScreen.tsx
  • components/screens/LandingChrome.tsx
  • components/screens/LandingPage.tsx
  • components/screens/SkillDetailPage.tsx

Comment thread components/screens/LandingChrome.tsx Outdated
Drops unused MetricGroupedBarChart component, getEvalRun/getEvalJob/toneFill
exports, and their now-orphaned dependents (modeHue, EvalJobStatus, recharts).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Fixes Applied Successfully

Fixed 1 file(s) based on 1 unresolved review comment.

Files modified:

  • components/screens/LandingChrome.tsx

Commit: 15cb58514784b5eebd1fcb2b59e838d63e3dc055

The changes have been pushed to the feature/update-eval-dashboard-details branch.

Time taken: 6m 29s

Fixed 1 file(s) based on 1 unresolved review comment.

Co-authored-by: CodeRabbit <noreply@coderabbit.ai>
@0xaeres
0xaeres merged commit 01744ca into main Jul 11, 2026
4 checks passed
@0xaeres
0xaeres deleted the feature/update-eval-dashboard-details branch July 11, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant