content: publish legal docs overhaul to production (tos-v1)

[0xkkonrad]

What ships

Bumps src/content to peanut-content latest. One signed commit, one file. The delta going live is the tos-v1 legal overhaul (mono 2e24455 + link-style fix 83166e9):

• New Terms of Service (/en/terms) — full rewrite: Squirrel Labs Ltd (company no. 14558823), self-custody framing with the card-collateral carve-out, all providers named, Points/Rewards split with the 3-month pending-reward expiry, E&W law, GBP 100 cap. Effective 2026-07-15.
• New Privacy Policy (/en/privacy) — replaces the 2022 Notion-era template (wrong entity, DAO audience). UK GDPR framing, full processor table, honest analytics disclosure.
• Card terms fixes (/en/card-terms-us, /en/card-terms-international) — 17 surgical edits: typos, a dropped "NEITHER" that inverted the US class-action waiver, the dangling "Section 12.3" reference, privacy-link repoint. Review sheet: mono/inbox/tos-v1/drafts/a3-CHANGES.md.

Decision log: mono/inbox/tos-v1/drafts/RULINGS.md. All docs passed a 3-agent review sweep before landing on mono main. Aleksandar's card-contact hotfix (#2423) is already live and included in this pointer.

Supersedes #2420 (pointer moved under it) and #2424 (format check correctly rejected locale-prefixed internal links; fixed in mono 83166e9).

Note: eslint is red on pre-existing app-source issues unrelated to this bump — it is not part of the required ci-success set.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
peanut-wallet	Ready	Preview, Comment	Jul 15, 2026 4:56pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 47 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: CHILL

Plan: Pro

Run ID: d633fac9-8eb9-4666-9413-66ed14b27d96

📥 Commits

Reviewing files that changed from the base of the PR and between 7258f72 and d64a2a4.

📒 Files selected for processing (1)

• src/content

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Code-analysis diff

Painscore total: 6122.01 → 6122.01 (0)
Findings: 0 net (+0 new, -0 resolved)

[github-actions]

🧪 UI test report — ✅ all green

Suites

• ✅ unit: 1836 ran, 0 failed, 0 skipped, 29.6s

📊 Coverage (unit)

metric	%
statements	58.2%
branches	42.2%
functions	47.0%
lines	58.3%

⏱ 10 slowest test cases

time	test
3.7s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › never places two stickers in heavy overlap (broad seed sweep)
0.5s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › every sticker stays within canvas at any count
0.4s	src/app/actions/__tests__/api-headers-extended.test.ts › should not include apiKey in updateUserById body
0.3s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › keeps stickers off the username pill (final pass respects the keep-out)
0.3s	src/app/actions/__tests__/api-headers.test.ts › should include Content-Type in updateUserById
0.1s	src/components/Global/GeneralRecipientInput/__tests__/GeneralRecipientInput.test.tsx › should handle valid 9-digit US account
0.1s	src/components/Global/GeneralRecipientInput/__tests__/GeneralRecipientInput.test.tsx › should handle valid ETH address
0.1s	src/components/Global/GeneralRecipientInput/__tests__/GeneralRecipientInput.test.tsx › should handle invalid ETH address (too short)
0.1s	src/components/Global/GeneralRecipientInput/__tests__/GeneralRecipientInput.test.tsx › should handle valid Italian IBAN
0.1s	src/components/Global/GeneralRecipientInput/__tests__/GeneralRecipientInput.test.tsx › should handle valid ENS name

_{📍 Inline annotations are in the **Unit test report** check above. Coverage artifact: `coverage-unit`. Generated by `.github/workflows/tests.yml`.}