fix(guard-size): preview base branch ceilings (sc-1494) - #375
Conversation
## Summary - read the raw-line baseline from the exact ship base before creating a worktree - print current lines, effective ceiling, headroom, and working-tree/base drift - share authoritative size policy and mirror gate semantics for shipped baselines, skipped directories, and disabled caps - distinguish proven violations from unavailable preview reads, which defer to the authoritative gate - run the preview from the repository root for both new ships and PR reships - document the standalone command and add focused unit plus ship integration regressions - repair the pre-existing PR #370 test fixture encoding that made main fail Biome, without changing its value ## Root cause The authoritative guard runs in the ship worktree, where the baseline comes from the selected base. The shared checkout could expose a different size-lines baseline, so contributors could not see the real cap until after the expensive gate chain started. ## Validation - clean detached origin/main build: bun run build - Story #1494 focused regressions: 9 passed - diff-focus prerequisite regression: 30 passed - base-aware preflight against origin/main: all changed source/test files within their effective ceilings - duplication guard: PASS - GitNexus scoped Story #1494 change audit: LOW risk, zero affected processes Story: sc-1494 Autonomous report: 20dc0667-a65d-4cf8-9284-09080bc91ff7
|
Warning Review limit reached
Next review available in: 14 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 ignored due to path filters (7)
📒 Files selected for processing (10)
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 |
Summary
Root cause
The authoritative guard runs in the ship worktree, where the baseline comes from the selected base. The shared checkout could expose a different size-lines baseline, so contributors could not see the real cap until after the expensive gate chain started.
Validation
Story: sc-1494
Autonomous report: 20dc0667-a65d-4cf8-9284-09080bc91ff7