docs(plan): update planning artifacts for adapter and account-pool work

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

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 47
+Phase 60
 
 ## Phases
 ### Phase 1: Progress Verification
@@ -341,6 +341,84 @@ Phase 47
 - [ ] Deliver the completed scope to the user
 - **Status:** pending
 
+### Phase 50: Hunyuan Collection And Markdown Diagnosis
+- [x] Build deterministic tests for API-SSE-primary and page-RPA-fallback behavior
+- [x] Use Electron CDP to inspect the real Hunyuan search toggle and streaming endpoint
+- [x] Reproduce the malformed Markdown display at the storage/rendering boundary
+- **Status:** complete
+
+### Phase 51: Hunyuan SSE/Search And Markdown Implementation
+- [x] Enable web search before submitting Hunyuan monitoring questions
+- [x] Parse official API SSE data first and fall back to page RPA only when unavailable
+- [x] Normalize collected Markdown without corrupting citations or source extraction
+- [x] Fix the admin answer renderer if display corruption is frontend-side
+- **Status:** complete
+
+### Phase 52: Hunyuan End-To-End Verification
+- [x] Run targeted adapter and Markdown regression tests
+- [x] Verify the live Hunyuan flow over Electron CDP
+- [x] Run desktop/admin typecheck, tests, build, and diff cleanup
+- **Status:** complete
+
+### Phase 53: Multi-Account Model And Runtime Audit
+- [x] Confirm whether server account storage already permits multiple accounts per desktop client and AI platform
+- [x] Trace desktop binding, account projection, task leasing, and monitor execution account selection
+- [x] Define failover-eligible versus terminal task/account errors and cooldown behavior
+- **Status:** complete
+
+### Phase 54: Multi-Account Binding And UI
+- [x] Preserve multiple bound AI accounts for the same platform instead of replacing the current account
+- [x] Render per-platform account lists with add, open, refresh, and unbind controls
+- [x] Keep existing single-account installations backward compatible
+- **Status:** complete
+
+### Phase 55: Same-Platform Monitor Failover
+- [x] Select a healthy local account pool for each monitoring platform
+- [x] Retry the same question with another account on risk control, challenge, empty/unknown, or recoverable collection failure
+- [x] Cool down failed accounts and record attempted/selected account diagnostics without duplicate server completion
+- **Status:** complete
+
+### Phase 56: Multi-Account Verification
+- [x] Add focused server/desktop tests for multi-account binding and selection
+- [x] Run desktop/server typecheck, tests, build, and diff cleanup
+- [x] Verify account-pool UI and failover state through the running desktop client
+- **Status:** complete
+
+### Phase 57: AI And Media Account UI Alignment
+- [x] Replace the AI-only compact platform selectors with the media-account card structure
+- [x] Match media-account spacing, card dimensions, status treatment, buttons, filters, and table shell
+- [x] Preserve AI multi-account actions and per-account risk-control warnings
+- **Status:** complete
+
+### Phase 58: AI Account UI Visual Verification
+- [x] Run desktop typecheck, tests, build, formatting, and diff checks
+- [x] Inspect the live AI page over Electron CDP at desktop and narrow viewports
+- [x] Remove temporary screenshots and record the final visual result
+- **Status:** complete
+
+### Phase 59: Missing-Citation Account Failover
+- [x] Add regression coverage for answers with and without structured citation sources
+- [x] Rotate to another same-platform account when a successful answer has no citations or search results
+- [x] Keep the last non-empty answer when every bound account lacks sources and avoid account-health cooldown
+- **Status:** complete
+
+### Phase 60: Admin AI Account Management Extraction
+- [ ] Add an AI Account Management route and tracking menu item after External Article Marks
+- [ ] Build an account-level multi-account page from tenant desktop account data
+- [ ] Match the bound media account card, filter, status, node, and unbind interactions
+- **Status:** in_progress
+
+### Phase 61: Tracking Dashboard Cleanup
+- [ ] Remove the embedded AI platform status query, projection, template, and styles from Data Details
+- [ ] Preserve unrelated platform analytics and collection controls
+- **Status:** pending
+
+### Phase 62: Admin AI Account Verification
+- [ ] Run admin typecheck, build, formatting, and diff checks
+- [ ] Verify navigation order, multi-account cards, filters, and responsive layout in a real browser
+- [ ] Remove temporary visual artifacts and record results
+- **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?