refactor(bookings): add round-robin host effective-limits foundation

[deepshekhardas]

Fixes #28715

Summary

Foundation implementation for per-member round-robin booking limits. This PR establishes the service structure without changing current booking behavior.

Changes

• Added RoundRobinHostLimitsService class
• Implemented getEffectiveLimits() to calculate host booking counts within time windows
• Implemented ilterHostsByLimits() structure (currently allows all hosts)
• Implemented getHostLimitStatus() for UI indicators

Time Windows Supported

• Day
• Week
• Month

Structure

• Host limit configuration with userId, eventTypeId, limit, and window
• Booking count queries within time windows
• Remaining slots calculation

Next Steps

Future PR will:

• Add UI for configuring host limits
• Enable actual limit enforcement
• Add limit exceeded notifications

Testing

• Service methods are unit testable
• Foundation structure ready for limit enforcement

[cubic-dev-ai]

2 issues found across 5 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/features/ee/round-robin/RoundRobinHostLimitsService.ts">

<violation number="1" location="packages/features/ee/round-robin/RoundRobinHostLimitsService.ts:49">
P2: Falsely treating `limit = 0` as "no limit" due to a falsy check allows unlimited capacity when a zero limit should mean no bookings allowed.</violation>
</file>

<file name="apps/web/modules/bookings/columns/filterColumns.ts">

<violation number="1" location="apps/web/modules/bookings/columns/filterColumns.ts:138">
P2: Newly added UTM header translation keys are referenced but missing in locale resources, causing fallback/raw key rendering in the UI.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.}

[cubic-dev-ai]

P2: Falsely treating limit = 0 as "no limit" due to a falsy check allows unlimited capacity when a zero limit should mean no bookings allowed.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/features/ee/round-robin/RoundRobinHostLimitsService.ts, line 49:

<comment>Falsely treating `limit = 0` as "no limit" due to a falsy check allows unlimited capacity when a zero limit should mean no bookings allowed.</comment>

<file context>
@@ -0,0 +1,225 @@
+      const window = config?.window ?? null;
+
+      // If no limit is set, host has unlimited capacity
+      if (!limit || !window) {
+        results.push({
+          userId,
</file context>

Suggested change

	if (!limit || !window) {
	if (limit == null || window == null) {

[cubic-dev-ai]

P2: Newly added UTM header translation keys are referenced but missing in locale resources, causing fallback/raw key rendering in the UI.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/web/modules/bookings/columns/filterColumns.ts, line 138:

<comment>Newly added UTM header translation keys are referenced but missing in locale resources, causing fallback/raw key rendering in the UI.</comment>

<file context>
@@ -128,5 +133,64 @@ export function buildFilterColumns({ t, permissions, status }: BuildFilterColumn
     }),
+    columnHelper.accessor((row) => (row.type === "data" ? row.booking.utmSource : null), {
+      id: "utmSource",
+      header: t("utm_source"),
+      enableColumnFilter: true,
+      enableSorting: false,
</file context>