docs(plan): update planning artifacts for AI accounts and adapter work

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

findings.md

@@ -358,3 +358,6 @@
 - `/api/tenant/accounts` already returns account-level client, health, runtime authorization, verification, heartbeat, deletion, and session data. No new storage schema or list endpoint is required.
 - `tenantAccountsApi.remove(id)` and `requestDelete(id)` already support the same node-scoped unbind lifecycle used by Media Account Management.
 - The new management page should list only real bound AI accounts, one card per account. Platform coverage and health totals can preserve the former overview without rendering fake account cards for unbound platforms.
+- The live tenant account response already contains real avatar URLs for Yuanbao, Qwen, and Kimi, and all three remote images load successfully in Chromium. The admin page can render `avatar_url` directly and only fall back to an initial when the field is absent.
+- The desktop AI authorized-account table ignored `RuntimeAccount.avatarUrl` and always rendered the display-name initial. This renderer-only omission was the root cause of the placeholder avatars shown in the client despite successful avatar collection and synchronization.
+- The initial admin AI card was 21px taller than the media card because the long session UID wrapped the identity subtitle. Giving the UID the remaining flex width with single-line ellipsis and adopting the media card's exact typography/padding restores the shared 270px geometry.

progress.md

@@ -981,3 +981,16 @@
 - Added Phases 60-62 for a new tracking-side “AI 账号管理” menu after “外部文章标记”.
 - Confirmed the existing tracking status panel collapses multiple accounts to the first account per platform even though the API returns every account.
 - Confirmed account removal and delete-request APIs can be reused from Media Account Management; implementation needs no server migration.
+- Browser verification fallback note: the first isolated Playwright mock command failed because `run-code` expects one callback expression rather than consecutive top-level statements. No page state or backend data was changed; the retry wraps the setup in one async callback.
+- The callback retry reached API interception but the CLI sandbox did not expose the global `URL` constructor. Replaced URL parsing with deterministic request-string normalization before rerunning the isolated fixture.
+- The first successful fixture execution remained on login because the SPA auth store had initialized before test local storage was written. Moved the isolated session seed to `page.addInitScript` so it runs before the next document and Pinia bootstrap.
+
+## 2026-07-12T16:40:00+08:00 - Admin AI account management extraction complete
+
+- Added “AI 账号管理” immediately after “外部文章标记” and moved account status out of Data Details.
+- The new admin page renders one card per AI account, preserves same-platform accounts independently, and reuses the tenant account health, node, delete-request, and unbind lifecycle.
+- Matched `/media` live geometry: toolbar 74.78px and standard account card 270.09px at desktop width; mobile verification showed no horizontal overflow.
+- Browser network interception added a second Qwen account temporarily; both Qwen cards rendered independently and total card count increased from three to four.
+- Confirmed all three live AI account avatars load as real remote images in the admin browser.
+- Fixed the desktop AI authorized-account table to render `record.avatarUrl`; initials now appear only when an account has no avatar.
+- Verification passed: admin production build, desktop-client Vue typecheck, targeted Prettier formatting, browser desktop/mobile inspection, and `git diff --check`.

task_plan.md

@@ -403,21 +403,21 @@ Phase 60
 - **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
+- [x] Add an AI Account Management route and tracking menu item after External Article Marks
+- [x] Build an account-level multi-account page from tenant desktop account data
+- [x] Match the bound media account card, filter, status, node, and unbind interactions
+- **Status:** complete
 
 ### 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
+- [x] Remove the embedded AI platform status query, projection, template, and styles from Data Details
+- [x] Preserve unrelated platform analytics and collection controls
+- **Status:** complete
 
 ### 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
+- [x] Run admin typecheck, build, formatting, and diff checks
+- [x] Verify navigation order, multi-account cards, filters, and responsive layout in a real browser
+- [x] Remove temporary visual artifacts and record results
+- **Status:** complete
 
 ## Key Questions
 1. How should the desktop client defer and locally optimize monitor-task execution without violating one-task-per-platform serialism?