docs(architecture): two-repo topology + distribution model

[mmorerasanchez]

Summary

• Molecules tree fix — adds the relocated ThemeToggle.tsx to the molecules/ block in alphabetical position (after TabNav.tsx, before TokenCounter.tsx), bringing the tree count to 18 and matching the prose header.
• Distribution & Repo Topology section — new ## Distribution & Repo Topology section inserted immediately before ## Further Reading, covering:
  • app-democrito (public product/registry) vs democrito-site (private showcase/submodule) vs democrito-archive
  • The copy-product-public.mjs build seam and why public/r/ must never be hand-edited in the site repo
  • Step-by-step registry update workflow
  • Submodule checkout requirements for both GitHub Actions and Vercel
  • Why generated artifacts (public/r/*.json, tokens/design-tokens.json) are committed and CI drift-checked
• Cross-links — adds [Theming Guide](./theming.md) to ## Further Reading (was missing) and a See also line in the new section linking tokens, theming, and getting-started.

Test plan

• grep -n "ThemeToggle" docs/reference/architecture.md → line 59, between TabNav and TokenCounter
• grep -n "## Distribution" docs/reference/architecture.md → appears after ### Why this matters, before ## Further Reading
• grep -n "Theming Guide" docs/reference/architecture.md → appears in both the new section (See also) and Further Reading
• Cross-link targets all resolve: docs/reference/tokens.md, docs/reference/theming.md, docs/guides/getting-started.md

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@mmorerasanchez, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 14 minutes and 5 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 22a36780-5528-44b4-9d61-365bdd7c3563

📥 Commits

Reviewing files that changed from the base of the PR and between e9ffc20 and 83d73ca.

📒 Files selected for processing (1)

• docs/reference/architecture.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/architecture-two-repo-topology

---

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 and usage tips.}