feat: Enhance provider components with detailed documentation and comments

- Added comprehensive comments and JSDoc-style documentation to NotificationProvider, ThemeProvider, UserProvider, and WebsiteThemeProvider for better clarity and maintainability.
- Improved type definitions in index.ts for better code understanding and usage.
- Introduced Docker support with Dockerfiles for various services including AI server, signaling server, and browser-use service.
- Created a docker-compose.yml file to orchestrate multiple services including PostgreSQL, AI, scraper, and frontend.
- Added a startup guide (startup.txt) for setting up the CRM environment on Ubuntu with Docker.
- Included a .dockerignore file to exclude unnecessary files from Docker builds.

Web_Calendar/types.ts

@@ -1,6 +1,14 @@
+// ── Web Calendar Types ──────────────────────────────────────────────
+// Core calendar event types used across the CRM system, including
+// event classification, status tracking, and participant metadata.
+
+/** Possible types of calendar events — triggered by different CRM workflows. */
 export type EventType = "call" | "follow_up" | "website_creation"
+
+/** Lifecycle state of a calendar event. */
 export type EventStatus = "scheduled" | "completed" | "cancelled" | "rescheduled"
 
+/** A single calendar entry linking a user, participant, developer, and optional lead/conversation. */
 export interface CalendarEvent {
   id: string
   userId: string
@@ -16,6 +24,7 @@ export interface CalendarEvent {
   endTime: string | null
   durationMinutes: number | null
   status: EventStatus
+  // Denormalized user references for display (avoid extra joins in list views)
   creator: { id: string; name: string; email?: string; role?: string; avatar?: string } | null
   participant: { id: string; name: string; email?: string; role?: string; avatar?: string } | null
   developer: { id: string; name: string; email?: string; role?: string; avatar?: string } | null