perf(webapp): scope declarative schedule sync to the current environment

syncDeclarativeSchedules loaded every declarative schedule for the whole project across all environments, then re-fetched deletion candidates it already had in memory. Scope the load to the current environment, drop the redundant re-fetch, and select only the columns the reconcile uses.

Also push projectId onto the schedule-limit count joins so it uses a project-scoped index instead of scanning the full TaskSchedule and RuntimeEnvironment tables.

Follow-up to #4522, which batched the delete side.

Author: ericallam

.server-changes/scope-declarative-schedule-sync.md

@@ -0,0 +1,6 @@
+---
+area: webapp
+type: improvement
+---
+
+Make background worker registration cheaper for projects with many scheduled tasks by scoping declarative schedule reconciliation to the current environment and dropping redundant schedule lookups.

apps/webapp/app/v3/services/checkSchedule.server.ts

@@ -131,12 +131,14 @@ export class CheckScheduleService extends BaseService {
         projectId,
         active: true,
         environment: {
+          projectId,
           type: {
             not: "DEVELOPMENT",
           },
           archivedAt: null,
         },
         taskSchedule: {
+          projectId,
           active: true,
         },
       },

apps/webapp/app/v3/services/createBackgroundWorker.server.ts

@@ -655,9 +655,21 @@ export async function syncDeclarativeSchedules(
     where: {
       type: "DECLARATIVE",
       projectId: environment.projectId,
+      instances: {
+        some: {
+          environmentId: environment.id,
+        },
+      },
     },
-    include: {
-      instances: true,
+    select: {
+      id: true,
+      friendlyId: true,
+      taskIdentifier: true,
+      instances: {
+        select: {
+          environmentId: true,
+        },
+      },
     },
   });
 
@@ -764,16 +776,9 @@ export async function syncDeclarativeSchedules(
 
   //Delete instances for this environment
   //Delete schedules that have no instances left
-  const potentiallyDeletableSchedules = await prisma.taskSchedule.findMany({
-    where: {
-      id: {
-        in: boundedIn(Array.from(missingSchedules)),
-      },
-    },
-    include: {
-      instances: true,
-    },
-  });
+  const potentiallyDeletableSchedules = existingDeclarativeSchedules.filter((schedule) =>
+    missingSchedules.has(schedule.id)
+  );
 
   const scheduleIdsToDelete: string[] = [];
   const scheduleIdsToDetachFromEnvironment: string[] = [];