[FlamurMaliqi]

Summary

• add a target repository that reads profiles only through the active immutable publication pointer
• parse stored JSON through the strict public profile trust boundary from VAY-1060: Strictly parse stored public Booking profiles #864
• preserve canonical/redirect slug resolution while making custom-domain routing require current verified Catalog ownership
• fail closed for revoked/reassigned domains, inactive revisions, malformed content, non-bookable profiles, and stale profiles

Stack

• Based on VAY-1060: Strictly parse stored public Booking profiles #864
• Does not activate the repository; runtime source selection follows separately

Verification

• API typecheck
• focused unit tests: 3 passed
• fresh migrations 0001–0078 + PostgreSQL integration: 2 passed
  • revoke/reassign custom domain
  • redirect resolves active pointer; inactive revision cannot resolve
• independent adversarial review: approved, no P1/P2 findings

Scope

Target TypeScript stack only. No legacy changes, mutable-profile fallback, or runtime activation.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 53570da0-8127-4af1-9ad8-5f78bddfedf5

📥 Commits

Reviewing files that changed from the base of the PR and between cece699 and 475b01b.

📒 Files selected for processing (3)

• apps/api/src/activeBookingPublicationProfile.integration.test.ts
• apps/api/src/activeBookingPublicationProfile.test.ts
• apps/api/src/routes/activeBookingPublicationProfile.ts

---

_{Comment @coderabbitai help to get the list of available commands.}