docs(xint): split policy persistence and activation - #241
Conversation
|
Warning Review limit reached
Next review available in: 28 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (16)
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. Comment |
|
AUTH is actively implementing the policy-mutation boundary. This planning PR is now draft and must not merge first. After AUTH merges, REV will pull exact current main, inspect the resulting routes/PREP/resource contexts/migrations, and refresh or replace this contract before any REV persistence implementation. |
|
Closing as superseded by merged WS-XINT-003-02A PR #242 and current main. This draft must not be conflict-merged: AUTH/ART and immutable policy-lineage contracts advanced after it was authored. REV will reconcile a fresh bounded lifecycle contract from current main after the remaining AUTH-owned policy mutation activation is merged. |
Summary
Evidence
The full suite and repository-wide coverage are delegated to GitHub Actions. No runtime code, migration, route, action availability, contribution behavior, workflow, dependency, or test configuration changes in this PR.
Human checkpoint
Confirm 02A is the only implementation-ready child, 02B remains deferred until post-02A refresh, and the PR activates no product behavior.