docs(plan): record publish management research and phase plan

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

task_plan.md

@@ -329,6 +329,18 @@ Phase 47
 - [x] Record residual test caveats
 - **Status:** complete
 
+### Phase 48: Admin-Web Publish Management
+- [ ] Expose tenant-authenticated publish task listing and retry APIs
+- [ ] Add admin-web publish-management API client, route, nav entry, and i18n labels
+- [ ] Build the content-management publish management page with title, account/platform, status, task info, time, and action controls
+- **Status:** in_progress
+
+### Phase 49: Publish Management Verification
+- [ ] Run targeted backend and frontend checks
+- [ ] Record changed files, test results, and remaining desktop deep-link caveats
+- [ ] Deliver the completed scope to the user
+- **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?