feat: Add automatic webhook setup and Connect Calendar UI for Meeting Scheduler

.cursor/rules/cursor-rules.mdc

@@ -1,7 +1,7 @@
 ---
 description: How to add or edit Cursor rules in our project
-globs: 
-alwaysApply: false
+globs: .cursor/rules/**/*
+alwaysApply: true
 ---
 # Cursor Rules Location
 
@@ -63,4 +63,3 @@ function badExample() {
   // Implementation not following guidelines
 }
 ```
-````

.cursor/rules/data-fetching.mdc

@@ -1,6 +1,9 @@
 ---
 description: Fetching data from the API using SWR
 globs: 
+  - apps/web/hooks/**/*
+  - apps/web/app/**/*.tsx
+  - apps/web/components/**/*
 alwaysApply: false
 ---
 # Data Fetching
@@ -44,4 +47,4 @@ const onSubmit: SubmitHandler<TestRulesInputs> = useCallback(async (data) => {
     toastSuccess({ description: "Saved!" });
   }
 }, []);
-``` 
+```

.cursor/rules/environment-variables.mdc

@@ -1,6 +1,9 @@
 ---
 description: Add environment variable
 globs: 
+  - apps/web/env.ts
+  - apps/web/.env.example
+  - turbo.json
 alwaysApply: false
 ---
 # Environment Variables
@@ -83,4 +86,4 @@ examples:
 references:
   - apps/web/env.ts
   - apps/web/.env.example
-  - turbo.json
+  - turbo.json

.cursor/rules/features/cleaner.mdc

@@ -1,6 +1,11 @@
 ---
-description: 
+description: Inbox Cleaner feature documentation
 globs: 
+  - apps/web/utils/actions/clean.ts
+  - apps/web/app/api/clean/**/*
+  - apps/web/app/(app)/*/clean/**/*
+  - apps/web/prisma/schema.prisma
+  - apps/web/utils/redis/clean.ts
 alwaysApply: false
 ---
 ## Inbox Cleaner

.cursor/rules/features/delayed-actions.mdc

@@ -1,3 +1,8 @@
+---
+description: Delayed Actions feature documentation
+globs:
+alwaysApply: false
+---
 # Delayed Actions Feature
 
 ## Overview

.cursor/rules/features/digest.mdc

@@ -1,5 +1,5 @@
 ---
-description: 
+description: Digest feature documentation
 globs: 
 alwaysApply: false
 ---
@@ -288,4 +288,3 @@ const isDigestEnabled = useFeatureFlagEnabled("digest-emails");
   coldEmailDigest: boolean,     // Include cold emails in digest
   digestSchedule: Schedule // When to send digests
 }
-```

.cursor/rules/features/knowledge.mdc

@@ -1,5 +1,5 @@
 ---
-description: 
+description: Knowledge Base feature documentation
 globs: 
 alwaysApply: false
 ---

.cursor/rules/features/schedule.mdc

@@ -1,5 +1,5 @@
 ---
-description: 
+description: Schedule feature documentation
 globs: 
 alwaysApply: false
 ---
@@ -311,158 +311,6 @@ const userTime = new Date().toLocaleString("en-US", {
 
 ---
 
-## Testing & Development
-
-### Testing Schedule Calculations
-
-```typescript
-import { calculateNextScheduleDate } from '@/utils/schedule';
-
-describe('Schedule', () => {
-  it('calculates daily schedule correctly', () => {
-    const next = calculateNextScheduleDate({
-      intervalDays: 1,
-      occurrences: 1,
-      timeOfDay: new Date('2023-01-01T11:00:00')
-    }, new Date('2023-01-01T10:00:00'));
-
-    expect(next).toEqual(new Date('2023-01-01T11:00:00'));
-  });
-
-  it('handles multiple occurrences per week', () => {
-    const next = calculateNextScheduleDate({
-      intervalDays: 7,
-      occurrences: 3,
-      timeOfDay: new Date('2023-01-01T09:00:00')
-    }, new Date('2023-01-01T08:00:00'));
-
-    // Should return first slot of the week
-    expect(next.getHours()).toBe(9);
-  });
-});
-```
-
-### Development Workflow
-
-1. **Design the schedule pattern** - What schedule do you need?
-2. **Test with calculateNextScheduleDate** - Verify the logic works
-3. **Add UI with SchedulePicker** - Let users configure it
-4. **Implement the recurring job** - Use the calculated dates
-5. **Test edge cases** - Timezone changes, DST, month boundaries
-
----
-
-## Common Patterns & Best Practices
-
-### Updating Schedule Settings
-
-```typescript
-// Always recalculate next occurrence when settings change
-const updateSchedule = async (newSchedule: Schedule) => {
-  const nextOccurrence = calculateNextScheduleDate(newSchedule);
-
-  await prisma.schedule.update({
-    where: { emailAccountId },
-    data: {
-      ...newSchedule,
-      nextOccurrenceAt: nextOccurrence
-    }
-  });
-};
-```
-
-### Processing Due Events
-
-```typescript
-// Standard pattern for processing scheduled events
-const processDueEvents = async () => {
-  const dueItems = await prisma.feature.findMany({
-    where: {
-      nextOccurrenceAt: { lte: new Date() }
-    },
-    include: { frequency: true }
-  });
-
-  for (const item of dueItems) {
-    // Process the event
-    await processEvent(item);
-
-    // Calculate and update next occurrence
-    const nextDate = calculateNextScheduleDate(item.schedule);
-    await prisma.feature.update({
-      where: { id: item.id },
-      data: {
-        lastOccurrenceAt: new Date(),
-        nextOccurrenceAt: nextDate
-      }
-    });
-  }
-};
-```
-
-### Form Integration
-
-```typescript
-// Standard form setup with SchedulePicker
-const ScheduleSettingsForm = () => {
-  const form = useForm({
-    defaultValues: getInitialScheduleProps(currentSchedule)
-  });
-
-  const onSubmit = async (data) => {
-      const schedule = mapToSchedule(data);
-  await updateScheduleAction(schedule);
-  };
-
-  return (
-    <form onSubmit={form.handleSubmit(onSubmit)}>
-      <SchedulePicker
-        value={form.watch()}
-        onChange={(value) => form.reset(value)}
-      />
-    </form>
-  );
-};
-```
-
----
-
-## Troubleshooting
-
-### Common Issues
-
-**Next occurrence not updating:**
-- Ensure you're calling `calculateNextScheduleDate` after each event
-- Check that `lastOccurrenceAt` is being updated
-- Verify timezone handling is consistent
-
-**FrequencyPicker not saving correctly:**
-- Use `mapToSchedule` to convert form data
-- Check that all required fields are present
-- Validate bitmask values for `daysOfWeek`
-
-**Unexpected scheduling behavior:**
-- Test with fixed dates instead of `new Date()`
-- Check for DST transitions affecting time calculations
-- Verify `intervalDays` and `occurrences` are positive integers
-
-### Debug Tools
-
-```typescript
-// Debug schedule calculation
-const debugSchedule = (schedule: Schedule, fromDate: Date) => {
-  console.log('Input:', { schedule, fromDate });
-
-  const next = calculateNextScheduleDate(schedule, fromDate);
-  console.log('Next occurrence:', next);
-
-  const timeDiff = next.getTime() - fromDate.getTime();
-  console.log('Time until next:', timeDiff / (1000 * 60 * 60), 'hours');
-};
-```
-
----
-
 ## File Reference
 
 ### Core Implementation
@@ -481,11 +329,3 @@ const debugSchedule = (schedule: Schedule, fromDate: Date) => {
 ### Validation & Types
 - `apps/web/app/api/ai/digest/validation.ts` - API validation schemas
 - `apps/web/types/schedule.ts` - TypeScript type definitions
-
----
-
-## Related Documentation
-
-- **[Digest Feature](mdc:digest.mdc)** - Primary use case for Schedule
-- **[Prisma Documentation](mdc:https:/prisma.io/docs)** - Database schema patterns
-- **[date-fns Documentation](mdc:https:/date-fns.org)** - Date manipulation utilities used internally

.cursor/rules/form-handling.mdc

@@ -1,6 +1,8 @@
 ---
 description: Form handling
 globs: 
+  - apps/web/app/**/*.tsx
+  - apps/web/components/**/*
 alwaysApply: false
 ---
 # Form Handling

.cursor/rules/fullstack-workflow.mdc

@@ -1,5 +1,6 @@
 ---
 description: Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.
+globs:
 alwaysApply: false
 ---
 # Fullstack Workflow
@@ -275,4 +276,3 @@ apps/web/
 - [Data Fetching with SWR](mdc:.cursor/rules/data-fetching.mdc)
 - [Form Handling](mdc:.cursor/rules/form-handling.mdc)
 - [Server Actions](mdc:.cursor/rules/server-actions.mdc)
-

.cursor/rules/get-api-route.mdc

@@ -1,6 +1,6 @@
 ---
 description: Guidelines for implementing GET API routes in Next.js
-globs: 
+globs: apps/web/app/api/**/route.ts
 alwaysApply: false
 ---
 # GET API Route Guidelines

.cursor/rules/gmail-api.mdc

@@ -1,6 +1,10 @@
 ---
 description: Guidelines for working with Gmail API
 globs: 
+  - apps/web/utils/gmail/**/*
+  - apps/web/utils/outlook/**/*
+  - apps/web/app/api/google/**/*
+  - apps/web/app/api/microsoft/**/*
 alwaysApply: false
 ---
 # Gmail API Usage

.cursor/rules/hooks.mdc

@@ -1,6 +1,9 @@
 ---
 description: React hooks
 globs: 
+  - apps/web/hooks/**/*
+  - apps/web/app/**/*.tsx
+  - apps/web/components/**/*
 alwaysApply: false
 ---
 # Custom Hook Guidelines

.cursor/rules/installing-packages.mdc

@@ -1,7 +1,7 @@
 ---
 description: How to install packages
-globs: 
-alwaysApply: false
+globs: null
+alwaysApply: true
 ---
 - Use `pnpm`.
 - Don't install in root. Install in `apps/web`:

.cursor/rules/llm-test.mdc

@@ -1,6 +1,6 @@
 ---
 description: Guidelines for writing tests for LLM-related functionality
-globs: 
+globs: apps/web/__tests__/**/*
 alwaysApply: false
 ---
 # LLM Testing Guidelines

.cursor/rules/llm.mdc

@@ -1,6 +1,9 @@
 ---
 description: Guidelines for implementing LLM (Language Model) functionality in the application
 globs: 
+  - apps/web/utils/ai/**/*
+  - apps/web/utils/llms/**/*
+  - apps/web/__tests__/**/*
 alwaysApply: false
 ---
 # LLM Implementation Guidelines

.cursor/rules/logging.mdc

@@ -1,6 +1,8 @@
 ---
 description: How to do backend logging
 globs: 
+  - apps/web/utils/**/*
+  - apps/web/app/api/**/*
 alwaysApply: false
 ---
 # Logging
@@ -25,4 +27,4 @@ const logger = createScopedLogger("action/rules").with({ userId: user.id });
 logger.log("Created rule");
 ```
 
-Don't use `.with()` for a global logger. Only use within a specific function.
+Don't use `.with()` for a global logger. Only use within a specific function.

.cursor/rules/notes.mdc

@@ -1,6 +1,6 @@
 ---
-description: 
+description: General development notes
 globs: 
 alwaysApply: true
 ---
-Do not try and run the project via `dev` or `build` command unless I explicitly ask you to.
+Do not try and run the project via `dev` or `build` command unless I explicitly ask you to.

.cursor/rules/page-structure.mdc

@@ -1,6 +1,6 @@
 ---
 description: Page structure
-globs: 
+globs: apps/web/app/(app)/**/*
 alwaysApply: false
 ---
 # Page Structure
@@ -9,4 +9,4 @@ alwaysApply: false
 - Components for the page are either put in `page.tsx`, or in the `apps/web/app/(app)/PAGE_NAME` folder
 - Pages are Server components so you can load data into them directly
 - If we're in a deeply nested component we will use `swr` to fetch via API
-- If you need to use `onClick` in a component, that component is a client component and file must start with `use client` 
+- If you need to use `onClick` in a component, that component is a client component and file must start with `use client`