feat(habit): expose durable recurring-habit HTTP API - #43
Conversation
|
Warning Review limit reached
Next review available in: 4 seconds 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Implements #41 as the next reviewable
habit.recurring-coreslice after #40.PostgresHabitRepositorywithout an in-memory fallbackx-workspace-idand validates workspace/habit identifiers before persistencehabit-service.integration.test.tsover the production NestJS module and disposable PostgreSQLDeferred
Authenticated workspace derivation at an API gateway, pause/archive, streak projections, reminders, calendar integration, controlled erasure, and end-user workflow design remain separate reviewable slices.
Validation gate
Merge only when CI, AppGuardrail, Semgrep, Security Scan, Commercial Readiness, CodeRabbit, and all human/security review requirements pass on the exact head with no unresolved actionable findings.
Closes #41