docs: confirm workspace capacity boundary

[brylie]

Summary

• updates the architecture diagram to distinguish the shipped Phase 0 global Y.Doc from future shards
• records the merged test: benchmark CRDT workspace capacity #116 capacity evidence as a bounded architecture decision rather than an open-ended assumption
• adds the snapshot-size and event-loop escalation boundary to the persistence specification

Refs #112

Verification

• npm run lint

This does not claim catalog routing or document/Collection shards are implemented; #112/#113 remain the design and implementation path.

Summary by CodeRabbit

• Documentation
  • Updated architecture documentation to describe the current global in-memory data storage model and its capacity limits.
  • Added guidance on future scaling boundaries, including document- and collection-level sharding.
  • Documented persistence capacity indicators, including snapshot size and event-loop performance thresholds.
  • Clarified that these thresholds are planning signals and do not represent implemented scaling features.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f6856f1e-78fb-40cf-90b5-807dda5e2193

📥 Commits

Reviewing files that changed from the base of the PR and between b130ea4 and 628a0f1.

📒 Files selected for processing (2)

• docs/specifications/architecture.md
• docs/specifications/persistence.md

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

---

📝 Walkthrough

Walkthrough

The architecture and persistence specifications now document a global Phase 0 Y.Doc, its capacity boundary, future sharding direction, and thresholds for prioritizing sharding or compaction.

Changes

Phase 0 capacity

Layer / File(s)	Summary
Global shard capacity model docs/specifications/architecture.md	The Phase 0 architecture uses one global in-memory Y.Doc. The specification documents its capacity boundary, future document- and Collection-level sharding, and the absence of shard-aware routing.
Snapshot capacity thresholds docs/specifications/persistence.md	The persistence specification records 2 MiB snapshot-size and 100 ms event-loop-p99 thresholds for prioritizing sharding or compaction.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 628a0

This documentation-only change records the workspace capacity boundary and persistence limits without altering runtime behavior. No actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the documentation change that records the workspace capacity boundary. It is concise and related to the main changes in the architecture and persistence specifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/confirm-workspace-capacity-boundary

---

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