Simplify WeChat binding cards and guided setup

.project-docs/30-worklog/tasks/20261012-wechat-channel-cards-a76f390d.md

@@ -0,0 +1,77 @@
+# Task: Simplify WeChat channel binding and update combined trial
+
+## Identity
+
+- Task ID: 20261012-wechat-channel-cards-a76f390d
+- Mode: Feature
+- Branch: codex/20261012-wechat-channel-cards-a76f390d-wechat-channel-cards
+- Worktree: /Users/chillishark/Makelore 麦洛/.codex-worktrees/makelore/20261012-wechat-channel-cards-a76f390d
+- Base commit: ad1d2f261d5810ec79a5e88da58209673a1e7b8d
+- Owner: codex
+- Status: Planning
+
+## Scope
+
+- Simplify the WeChat channel page into account cards and an explicit choose-Agent → scan → confirmed binding flow. Remove channel chat/activity panels from this configuration surface. Combine all prior approved Agent refinements in the current temporary application.
+
+## Intent And Constraints
+
+- Product-language communication; user approved implementation and the combined temporary-app update. Preserve one current Agent target per account, many accounts per Agent, account isolation, Main-owned authentication/operations, creator billing and cloud history. No real WeChat binding/model calls for verification. Cloud changes remain with the user's teammate; do not invent physical-WeChat identity or duplicate detection absent from the current contract.
+- Latest base includes prior simplified creation/configuration, cards-first entry, chat polish and manual-only sidebar. Preserve all of them. Keep other local tasks/read-only source, installed app and user profile intact; runtime replacement is restricted to the known temporary app/artifacts. User's new update instruction supersedes earlier code-only constraints.
+
+## Project Context Loaded
+
+Task context:
+- ID: 20261012-wechat-channel-cards-a76f390d; Feature; owner codex.
+- Worktree: /Users/chillishark/Makelore 麦洛/.codex-worktrees/makelore/20261012-wechat-channel-cards-a76f390d.
+- Branch: codex/20261012-wechat-channel-cards-a76f390d-wechat-channel-cards.
+- Base commit: ad1d2f261d5810ec79a5e88da58209673a1e7b8d.
+- Bundled check/start/status passed, owner/reservation and HEAD match. 38 peers read only: 37 concrete scopes, one old undefined child-language record; no blocking conflict. Prior Agent changes form a single ancestry chain.
+
+Read:
+- AGENTS.md, startup order/memory index/planning gate, own record, positioning and integrated current state, decision index, system overview/community collaboration.
+- Business rules/success criteria, evidence/reflection/commitments indexes and personal-cloud-agents ADR; each peer's scope, constraints and promotion candidates.
+- ChannelAccounts, typed channel contract, current channel checks, CloudAvatar/QR/dialog components; read-only Yuxi channel/identity/lifecycle contract. Existing temporary app runtime evidence and current CUA accessibility state.
+- Design skill database search; adapt progressive disclosure, contrast/focus and soft cards to existing cream/pastel/orange style, without new fonts/themes.
+
+Relevant understanding:
+- Project is an AI creation client for students/creators, excludes courses; Main/WS/Yuxi retain auth, billing, resources and run authority.
+- User confirms one WeChat → one current Agent, many WeChats → one Agent, no WeChat transcript in channels. Existing scalar account target supports this relationship; only own published/enabled Agents are eligible.
+- Old integrated UI descriptions include channel history tabs; this user-approved configuration simplification takes precedence. Feature task proposes canonical updates only.
+- Pause preserves login/target but stops ongoing channel work; switch/clear stops old work and delivery. Clear target disables while retaining login. Disconnect also signs out but retains target/history. Present unlink as cancelling the Agent association, with an explicit confirmation; do not conflate it with logout.
+- The current client/cloud projection has no verified real WeChat identity or repeated-scan lookup. Preserve recovery/conflict/error feedback and reuse existing account records for management; true duplicate-scan enforcement requires the cloud owner, not guessed names.
+- Runtime currently uses Entry Trial PID 63739 / Host 62867, with formal app separately running. CUA confirms channels open and saved settings. Only renderer changed since that live source; compare final Main artifact hashes before choosing a renderer-only refresh that preserves login. Otherwise build/probe an isolated shell with rollback and manual login.
+- Files: ChannelAccounts, focused channel tests, README, own task record, task-specific ignored runtime artifacts. No canonical or sibling source writes.
+- Gates passed; no unresolved product conflict. Real WeChat and paid model behavior remain outside fixture evidence.
+
+Gate result:
+- Passed.
+
+## Plan
+
+1. Implement pastel account cards and accessible add/manage dialogs with explicit confirmed connection and activation, safe switch/pause/unlink, loading/empty/error/recovery states. Remove channel transcript/activity UI from the configuration page.
+2. Verify cardinality, existing/new account flows, QR completion, failures/recovery, keyboard/compact layouts and inherited Agent pages; run typecheck/scoped lint/build/Electron checks.
+3. Save the reviewed result, bind a verified runtime update, preserve live login when identical Main artifacts allow it, and display the updated channel page. Record actual runtime evidence and limits.
+
+## Outcome
+
+- Implemented account cards, optional account remark, choose-Agent → scan → explicit activation and binding receipt. Management supports target replacement, pause/resume, confirmed unlink and separate disconnect. One scalar target per account and multiple accounts per Agent are retained. Channel configuration no longer renders or requests chat/activity panels.
+- Uses authoritative account refresh after QR confirmation and before activation; checks current target/revision/blockers and activation receipts. Failed route keeps the created account identity; pending recovery blocks conflicting actions; successful mutations followed by read failures are not replayed. Initial loading/read failure is distinct from an empty account list.
+- README and focused checks match the final page. Current ancestry includes all earlier approved Agent creation/configuration, direct-use, cards-first entry, chat polish and manual-only sidebar/icon changes. Renderer deployment is pending actual application verification; no cloud mutations performed.
+
+## Verification
+
+- Focused channel unit checks: 27 passed, including no false completion/success when enable returns enabled=false; creation/route failure identity; connection confirmation, recovery, stale target/revision, switch/pause/unlink/disconnect and no history requests.
+- Final production build passed. Production Electron fixture: both channel binding and combined Agent scenarios passed (2 tests, 10.3s). Final screenshots reviewed: readable pastel cards, compact management dialog and correctly placed Select arrow; inherited creation/configuration/sidebar/chat checks remain passing. Fixtures use isolated synthetic data, not the real user's cloud state.
+- Final post-review typecheck, scoped ESLint and whitespace checks passed. Independent final code review found no remaining necessary fixes.
+- Live temporary app inspected through CUA: logged in, saved Agent settings, empty message composer. Formal installed app remains separate and untouched. Runtime update will verify identical Main/preload/utility bytes and preserve its process before reloading the page; visible result will be recorded after confirmation.
+
+## Follow-ups
+
+- Cloud owner must confirm real WeChat identity/repeated-scan behavior. Current account DTO does not expose a verified identity, so this client never guesses duplicates from account remarks. Real WeChat/paid model behavior is not established by fixture checks.
+- Complete combined temporary-app refresh and record visible UI evidence before declaring this task ready.
+
+## Promotion Candidates
+
+- Target: integrated current state and personal-cloud-agents channel UI description. Proposal: channel configuration consists of account cards and choose-Agent/scan/explicit-enable management; no chat/activity surface. Evidence: user's explicit approval, focused fixture checks and reviewed screenshots. Future impact: prevents reintroducing conversation management into configuration. Semantic conflict: older integrated descriptions include channel history tabs; this approved UI simplification supersedes that presentation while preserving cloud history/billing. Human confirmation: already obtained for product direction; canonical promotion still requires a separate integration task.
+- Target: channel contract/commitments. Proposal: confirm stable real-WeChat identity and repeated-scan resolution with the cloud owner before claiming physical-account uniqueness. Evidence: current scalar target gives one Agent per account record but DTO lacks physical identity. Future impact: prevents misleading duplicate detection. Human confirmation/cloud contract required; no client-side guessed identity.