feat: add MediaSupplyFavorite types and update task plan for generated-code drift diagnosis

task_plan.md

@@ -4,7 +4,7 @@
 Continue the desktop AI monitoring implementation by first adding a client-side local scheduler with durable queueing and adaptive execution policy, then adding a reusable hidden Playwright CDP execution layer that attaches to Electron Chromium and reuses existing account partitions.
 
 ## Current Phase
-Phase 68
+Phase 69
 
 ## Phases
 ### Phase 1: Progress Verification
@@ -455,6 +455,18 @@ Phase 68
 - [x] Record final behavior and any live-environment caveat
 - **Status:** complete
 
+### Phase 69: Generated-Code Drift Diagnosis
+- [ ] Identify the exact CI generation command and pinned sqlc version
+- [ ] Reproduce the generated-code diff locally
+- [ ] Determine whether source SQL/schema or generated output is stale
+- **Status:** in_progress
+
+### Phase 70: Generated-Code Repair And Verification
+- [ ] Regenerate only the affected committed artifacts
+- [ ] Re-run the same generation check until the worktree is stable
+- [ ] Run relevant Go tests and record the generated files
+- **Status:** pending
+
 ## Key Questions
 1. How should the desktop client defer and locally optimize monitor-task execution without violating one-task-per-platform serialism?
 2. What is the smallest durable local cache that allows same-day resume while safely dropping stale next-day monitor tasks?
@@ -517,6 +529,7 @@ Phase 68
 ## Errors Encountered
 | Error | Attempt | Resolution |
 |-------|---------|------------|
+| Root `.github/workflows/backend-ci.yml` not found | 1 | Locate the active Gitea/CI workflow with `rg --files` instead of relying on historical planning notes |
 | Runtime invalidation payload included unsupported `platform` field | 1 | Remove the redundant field; account ID and message already identify the health event |
 | Server regression still expected old literal skip reason and 10 SQL args | 1 | Update assertions to the new parameterized skip reason/cancellation payload and 11 args |
 | Authorization bulk-cancellation patch context did not match the existing SQL argument block | 1 | Split the server change into smaller exact-context patches |