feat(gateway): compose authenticated Habit Today state - #187
Conversation
|
Warning Review limit reached
Next review available in: 49 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
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 |
|
@coderabbitai review |
|
Outcome
Advance #163 from Planning-only Today composition to real Planning + Habit service composition without cross-service persistence reads or browser-selected tenant authority.
Product/security boundary
GET /v1/habits/today?date=YYYY-MM-DDapplication boundary backed by service-owned persistence/domain rules.habits_not_configured; dependency/configuration/representation failure yields explicithabits_unavailablewith no fabricated habit content..env.examplenow carries the Habit service origin and gateway-context secret required to activate the optional composition.Test-first evidence
The branch first introduced a failing Habit Today domain contract and a failing Gateway Habit composition contract, then implemented the narrow service and Gateway paths. The existing Habit authority regression was extended from five to six workspace-scoped routes.
Canonical documentation
Whole-product PRD/TRD/Architecture/UML/API/operability/traceability authority remains the single canonical #145 line; this product PR does not create a competing documentation graph. #145 must reconcile this boundary after its writer lease is safe.
Closes the Habit-composition remainder of #163 only after unchanged-head CI/security/review and protected-main integration prove the complete boundary.