TenantAtlas/specs/032-backup-scheduling-mvp/tasks.md

Tasks: Backup Scheduling MVP (032)

Date: 2026-01-05 Input: spec.md, plan.md

Phase 1: Spec & Setup

• T001 Create specs/032-backup-scheduling-mvp (spec/plan/tasks + checklist).

Phase 2: Data Model

• T002 Add migrations: backup_schedules + backup_schedule_runs (tenant-scoped, indexes, unique slot).
• T003 Add models + relationships (Tenant->schedules, Schedule->runs, Run->backupSet).

Phase 3: Scheduling + Dispatch

• T004 Add command tenantpilot:schedules:dispatch.
• T005 Register scheduler to run every minute.
• T006 Implement due-calculation (timezone, daily/weekly) + next_run_at computation.
• T007 Implement idempotent run creation (unique slot) + cache lock.

Phase 4: Jobs

• T008 Implement RunBackupScheduleJob (sync -> select policy IDs -> create backup set -> update run + schedule).
• T009 Implement ApplyBackupScheduleRetentionJob (keep last N, soft-delete backup sets).
• T010 Add error mapping to error_code (TOKEN_EXPIRED, PERMISSION_MISSING, GRAPH_THROTTLE, UNKNOWN).

Phase 5: Filament UI

• T011 Add BackupScheduleResource (tenant-scoped): CRUD + enable/disable.
• T012 Add Runs UI (relation manager or resource) with details + link to BackupSet.
• T013 Add actions: Run now + Retry (permission-gated); notifications persisted to DB.

Phase 6: Tests

• T014 Unit: due-calculation + next_run_at.
• T015 Feature: dispatcher idempotency (unique slot); lock behavior.
• T016 Job-level: successful run creates backup set, updates run/schedule (Graph mocked).
• T017 Job-level: token/permission/throttle errors map to error_code and status.
• T018 Retention: keeps last N and deletes older backup sets.

Phase 7: Verification

• T019 Run targeted tests (Pest).
• T020 Run Pint (./vendor/bin/pint --dirty).