fix(mockups): keep soft-mark caution copy on shared UNGROUNDED

[BigSimmo]

Summary

• Follow-up for Devin on Design mockups: quieter VerificationNotice caution lockups #1605: the soft-mark caution sample was hand-typing the approved warning in two styled spans instead of reusing the shared UNGROUNDED constant.
• Split that constant into UNGROUNDED_LEAD / UNGROUNDED_TAIL, compose UNGROUNDED from them, and render soft-mark from the same pieces so wording cannot drift.

Verification

• Local Prettier on the touched mockup file
• Verification not run: mockup-only copy-source change; no production UI path. npm run verify:pr-local will run in CI.
• UI verification not run: design-scratch mockup only (*-mockups.tsx / mockups route), outside production UI gates.

Risk and rollout

• Risk: Low — design-scratch mockup only; no production VerificationNotice change.
• Rollback: Revert the squash commit.
• Provider or production effects: None

Notes

• Design mockups: quieter VerificationNotice caution lockups #1605 squash-merged with the CodeRabbit ReactNode import fix; this Devin finding landed after that tip and needs this follow-up.
• Ledger row appended for the babysit sweep.

[coderabbitai]

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:24 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: 8647e216-35f9-4a5e-88e7-6a2e12e6563a

📥 Commits

Reviewing files that changed from the base of the PR and between 909b34a and e7336f8.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• src/components/verification-notice-subtle-mockups.tsx

---

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

[supabase]

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 ↗︎.

[devin-ai-integration]

✅ 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.