feat: Refactor template handling, improve scheduler functions, and add timezone utilities

- Moved Jinja2 template setup to a shared configuration file (templates_config.py) for consistent usage across routers.
- Introduced timezone utilities in a new module (timezone.py) to handle UTC to local time conversions and formatting.
- Updated all relevant routers to use the new shared template configuration and timezone filters.
- Enhanced templates to utilize local time formatting for various datetime fields, improving user experience with timezone awareness.

backend/routers/recurring_schedules.py

@@ -5,7 +5,6 @@ API endpoints for managing recurring monitoring schedules.
 """
 
 from fastapi import APIRouter, Request, Depends, HTTPException, Query
-from fastapi.templating import Jinja2Templates
 from fastapi.responses import HTMLResponse, JSONResponse
 from sqlalchemy.orm import Session
 from typing import Optional
@@ -15,9 +14,9 @@ import json
 from backend.database import get_db
 from backend.models import RecurringSchedule, MonitoringLocation, Project, RosterUnit
 from backend.services.recurring_schedule_service import get_recurring_schedule_service
+from backend.templates_config import templates
 
 router = APIRouter(prefix="/api/projects/{project_id}/recurring-schedules", tags=["recurring-schedules"])
-templates = Jinja2Templates(directory="templates")
 
 
 # ============================================================================
@@ -209,17 +208,25 @@ async def create_recurring_schedule(
             auto_increment_index=data.get("auto_increment_index", True),
             timezone=data.get("timezone", "America/New_York"),
         )
+
+        # Generate actions immediately so they appear right away
+        generated_actions = service.generate_actions_for_schedule(schedule, horizon_days=7)
+
         created_schedules.append({
             "schedule_id": schedule.id,
             "location_id": location.id,
             "location_name": location.name,
+            "actions_generated": len(generated_actions),
         })
 
+    total_actions = sum(s.get("actions_generated", 0) for s in created_schedules)
+
     return JSONResponse({
         "success": True,
         "schedules": created_schedules,
         "count": len(created_schedules),
-        "message": f"Created {len(created_schedules)} recurring schedule(s)",
+        "actions_generated": total_actions,
+        "message": f"Created {len(created_schedules)} recurring schedule(s) with {total_actions} upcoming actions",
     })