Skip to content

Design mockups: quieter VerificationNotice caution lockups - #1605

Merged
BigSimmo merged 8 commits into
mainfrom
cursor/verification-notice-subtle-lockups-51e0
Aug 5, 2026
Merged

Design mockups: quieter VerificationNotice caution lockups#1605
BigSimmo merged 8 commits into
mainfrom
cursor/verification-notice-subtle-lockups-51e0

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds a design-scratch mockup at /mockups/verification-notice-subtle comparing seven quieter lockups for the live ungrounded / caution VerificationNotice (today: full amber body + TriangleAlert).
  • Options: A baseline · B icon-only caution (recommended) · C quiet amber rule · D words only · E “Review source match” label + muted prose · F hairline footnote · G soft mark + weight hierarchy.
  • Approved clinician wording is unchanged; this is presentation exploration only. Production VerificationNotice is not modified.

Verification

  • Live mockup route checked at http://localhost:4461/mockups/verification-notice-subtle (project identity confirmed via /api/local-project-id)
  • npm run sitemap:check / pre-commit docs sync
  • ESLint on new mockup files (clean after removing unused import)
  • Verification not run: npm run verify:pr-local — mockup-only design scratch; dry-run selected the full executable plan. Prefer focused review of the mockup page before adopting into ui/verification-notice.tsx.
  • UI verification not run: no production UI change yet; mockups are gate-exempt design scratch.

Risk and rollout

  • Risk: None to production behaviour — mockup route only (src/app/mockups/**).
  • Rollback: Delete the mockup route/component or close the PR.
  • Provider or production effects: None

Notes

  • COMPONENTS §1 still requires caution states to wear the warning role; B/C/E/F/G keep a warning channel, D does not.
  • If adopting B (icon-only), update tests/ui-v2-answer-safety.dom.test.tsx which currently expects caution body colour on --warning.
Open in Web Open in Cursor 

Summary by CodeRabbit

  • New Features
    • Added a mockups page showcasing seven subtle verification notices, a neutral reference state, and a sample answer.
    • Included varied visual treatments such as warning icons, muted text, borders, labels, and emphasis.
    • Added guidance on appropriate warning usage and preserving clinician wording.
  • Documentation
    • Added the new mockups page to the site map.

Add a design-scratch study comparing quieter presentations for the
ungrounded caution notice — icon-only warning, quiet rule, words-only,
label+prose, hairline, and soft-weight — without changing approved wording.
@supabase

supabase Bot commented Aug 4, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 19 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1d25f197-a5bb-47cd-b4c8-66547f3ae766

📥 Commits

Reviewing files that changed from the base of the PR and between e64297f and a9bbed8.

📒 Files selected for processing (1)
  • src/components/verification-notice-subtle-mockups.tsx
📝 Walkthrough

Walkthrough

Added a client-side mockup page for seven subtle VerificationNotice caution lockups, a neutral ready reference, sample answers, and adoption notes. Added a route component and sitemap entry for /mockups/verification-notice-subtle.

Changes

Verification notice mockups

Layer / File(s) Summary
Notice concepts and shared content
src/components/verification-notice-subtle-mockups.tsx
Defines approved notice strings, seven concept variants, sample answers, and a neutral ready reference.
Lockup rendering and mockup layout
src/components/verification-notice-subtle-mockups.tsx
Renders the seven caution presentations in reusable bordered mockup panels and includes adoption notes.
Route and sitemap registration
src/app/mockups/verification-notice-subtle/page.tsx, docs/site-map.md
Exposes the mockup page at /mockups/verification-notice-subtle and adds the route to the sitemap.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Title check ✅ Passed The title clearly identifies the design mockups and the quieter VerificationNotice caution lockups added by the pull request.
Description check ✅ Passed The description covers the summary, verification results, risk, rollback, production effects, and the reason required production checks were not run.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch

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

@BigSimmo
BigSimmo marked this pull request as ready for review August 5, 2026 09:39

@devin-ai-integration devin-ai-integration 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.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

coderabbitai[bot]

This comment was marked as resolved.

@BigSimmo
BigSimmo enabled auto-merge (squash) August 5, 2026 18:05

@devin-ai-integration devin-ai-integration 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.

Devin Review found 1 new potential issue.

View 2 additional findings in Devin Review.

Open in Devin Review

Comment thread src/components/verification-notice-subtle-mockups.tsx
@BigSimmo
BigSimmo merged commit 1675b47 into main Aug 5, 2026
42 checks passed
@BigSimmo
BigSimmo deleted the cursor/verification-notice-subtle-lockups-51e0 branch August 5, 2026 18:22
BigSimmo added a commit that referenced this pull request Aug 5, 2026
* fix(mockups): derive soft-mark caution copy from shared UNGROUNDED

Follow-up for Devin on #1605 — soft-mark was hand-typing the approved
warning in two spans; lead/tail now come from the same constants every
other sample uses.

* chore(ledger): record soft-mark UNGROUNDED follow-up

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
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.

2 participants