Add north star release readiness gate#340
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 33 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 Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis PR adds documentation defining a North Star Completion Tracker (epics A–J, progress vocabulary, executive snapshot) and a Release Readiness Gate process, cross-links them with existing docs, adds a Completion Gate checklist to runtime-authority-dead-paths.md, and introduces a verification script plus two npm scripts to enforce their consistency. ChangesNorth Star Tracker and Verification
Estimated code review effort: 2 (Simple) | ~15 minutes Sequence Diagram(s)sequenceDiagram
participant Developer
participant Yarn as "yarn release:readiness"
participant VerifyScript as "verify-north-star-tracker.mjs"
participant Docs as "Tracker/Gate/Ownership docs"
Developer->>Yarn: run release:readiness
Yarn->>Yarn: run yarn verify
Yarn->>VerifyScript: run verify:north-star
VerifyScript->>Docs: read and assert markers
Docs-->>VerifyScript: content
VerifyScript-->>Yarn: exit 0 or exit 1 with errors
Yarn-->>Developer: pass/fail result
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/runtime-authority-dead-paths.md`:
- Around line 11-17: The file contains two conflicting “Completion Gate”
sections, which makes the release-gate contract ambiguous. Merge this new gate
text into the existing Completion Gate section, or rename one heading so only
one authoritative target remains. Use the existing Completion Gate heading in
docs/runtime-authority-dead-paths.md as the single place for the consolidated
rules.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e9f3bda8-1658-46a7-96ba-75238687f8b8
📒 Files selected for processing (6)
docs/core-sidecar-north-star.mddocs/north-star-completion-tracker.mddocs/release-readiness-gate.mddocs/runtime-authority-dead-paths.mdpackage.jsonscripts/verify-north-star-tracker.mjs
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
yarn verify:north-starandyarn release:readinessso the tracker/gate is enforcedVerification
Summary by CodeRabbit
Documentation
Chores