Per-bot task list + Kanban board (conversation-derived tasks, tree + group admin views) #1058

Owner urgency: ship now (filed by owner 2026-10-25).

Related but not duplicates: #349 (inbox list shipped), #471 (inbox board v2 / needs-human), #149 (task layer). This issue is the product surface: each Bot owns a task list the Bot itself maintains from conversation, with a Kanban to track progress for that Bot, its subordinates, and (for group admins) tasks received in a group.

Goal (one observable behavior)

Before: A user looking at a Bot (or a tree parent, or a group) cannot see a durable, Bot-owned list of what that Bot is working on, how far each item has gone, or what subordinates / group-mates are doing — only scattered chat and the personal Agent inbox from #349.

After:

1. Every Bot has its own task list. Tasks are created/updated when the Bot summarizes work from its own conversations (not only from GitHub issues).
2. A Kanban board (columns: Not started / In progress / Done, with optional swimlanes) shows what that Bot is doing and how far each card has progressed. UI should follow the attached reference mock (left Bot/iteration switcher, priority tags, assignee, progress, drag to start/complete).
3. A parent Bot (tree) can open a subordinate’s board and see each child’s task progress.
4. A group chat admin can open a group-scoped view of every Bot in that group and see tasks that Bot received / is tracking in that group.

Acceptance criteria

• Persisted per-Bot task records (id, title, status, progress or column, optional priority, assignee Bot/user, source conversation/group ids, updatedAt) with host APIs to list/create/update; Bots update the list from conversation summarization (prompt + host hook or tool — reuse Team mode via groups: task layer step 1 - responsible-owner authority, FLYBOT-TASK envelope, workBotId #149 / existing task envelope if present, do not invent a second parallel model).
• UI: Bot-scoped task list + Kanban matching the reference layout at a readable level (columns Not started / In progress / Done; cards with id, title, priority, status, progress; left rail to switch Bots / children). Drag or explicit actions move cards between columns.
• Tree parent can select a child Bot and see that child’s tasks and column progress.
• Group admin view: for a group the viewer admins, list member Bots and the tasks those Bots associated with that group; non-admins do not see other Bots’ group tasks.
• Tests cover task CRUD / status transitions and the group-admin visibility rule; npm run verify (or the repo’s equivalent verify gate) passes.
• Changelog fragment under changelog.d/ for the user-visible change.
• PR Fixes #<this> and does not expand into Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471’s unread inbox board redesign unless reusing shared board components is clearly cheaper.

Where it sits (likely)

• Host task storage / APIs near existing Agent inbox / task layer (#149, #349 leftovers).
• Desktop/web UI beside the Agent inbox sidebar entry; shared board primitives if Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471 v1 count-board left any.
• Tree plugin / group membership for subordinate and group-admin scopes.
• Prompt or turn-end summarization path so Bots keep the list current from dialogue.

Exact paths: investigate on tip of main; prefer extending shipped inbox/task types over a greenfield store.

Out of scope / do not touch

• Full Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471 team assigner/owner redesign and non-FlyBot runtime cards ([RFC] 跨运行时 Agent 对话与协作：以 OpenCode 为首个试点的目标、需求与两种方案 #198).
• Changing approval security / Bot Social grant model beyond read filters for group admins.
• Auto-approve rules, cross-team visibility beyond tree children and groups the viewer admins.
• Hand-editing CHANGELOG.md or version numbers.

Reference

Owner-attached Kanban mock (enterprise VI style board): Not started / In progress / Done columns, swimlanes, priority tags, drag "start task" / "complete task". Cloud agent will receive the image on launch.