docs(decrating): add §6.A binding process discipline rules#72
Conversation
Adds 5 binding rules learned from real incidents during execution: - R-PR-1: Always pass --base main explicitly to gh pr create. Real incident: PR #56 merged to feature/decrating-phase1-scaffold instead of main. Content never reached main. Cargo + execution-core absorptions silently broke against the stale main. Recovery required PR #70 (replay of #56 onto main). - R-PR-2: Verify branch state at session start (worktree HEAD switching). - R-PR-3: Use forward-slash absolute paths in Edit/Write on Windows (backslash paths silently fail to persist). - R-PR-4: Pre-flight grep for cross-crate deps before absorbing. - R-PR-5: Type-promotion fallback when cascade is too tangled for global reorder (per PR #56's pattern). These rules are now binding for all remaining agent prompts.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 43 minutes and 15 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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
Adds binding process rules to `docs/decrating-plan.md` (§6.A) capturing operational lessons from real incidents during the absorption execution.
The five rules:
Test plan