Task board drives Bot planning: group overall tasks + per-Bot subtasks #1099

Written-by: Dev

Goal

Make the Tasks board a planning and execution aid, not only a status view.

Owner ask (after #1058 / #1071): the board should help Bots plan work and keep it moving. In a group there must be an overall group task plus subtasks per Bot. Also wanted: auto-advance from unfinished board work, escalate when stuck, and assign by priority in the group.

Today (#1058)

• Each Bot keeps its own list via track_tasks (conversation path).
• Board columns Not started / In progress / Done; tree parent and group-admin read of room-tagged tasks.
• No parent/child task link, no group-owned umbrella task, no prompt/tool loop that pulls unfinished board work into the next turn, no blocked→ask_user escalation from the board.

Expected behavior

1. Group overall task — a task scoped to the group (visible under Groups you admin / in group context) that represents the whole job.
2. Per-Bot subtasks — child tasks owned by member Bots, linked to that overall task; board shows the hierarchy (or clear parent id + nesting).
3. Planning — when the user (or group) gives work, the responsible Bot (or admin Bot) breaks it into the overall task + subtasks and records them with track_tasks / task APIs; prompt tells it to do this instead of only a flat list.
4. Execution loop — Bots treat unfinished own (sub)tasks as active work: update column/progress as they go; prefer continuing board work over inventing new work.
5. Stuck — when a task is blocked / waiting on input, the Bot asks the user (or group) instead of silently stalling.
6. Priority — high/urgent group work is preferred when choosing what to do next among open subtasks.

Scope (implementation sketch — agent should verify)

• Task model: parent/child (or equivalent) with group overall + Bot-owned children; origin.roomId stays for group tagging.
• track_tasks + prompt: create/link children; read unfinished and continue; blocked → ask.
• Board UI: show overall task and nested subtasks in group scope; keep group-admin read-only for others’ cards where that already applies.
• Tests: host + kanban client; extend group-admin smoke if practical.
• Changelog fragment + subsystem docs if behavior/docs change.

Out of scope

• Replacing the existing per-Bot board.
• Human-only project management UI beyond the current Tasks dialog.

Related

• Builds on Per-bot task list + Kanban board (conversation-derived tasks, tree + group admin views) #1058 / merged Add a per-Bot task board updated from conversation #1071.
• Smoke note: classic rooms without participants[] may need deriveParticipants for group task listing (local finding during group-admin E2E); fix if still broken on main.

Acceptance

• Group can have one overall task with per-Bot subtasks linked to it.
• Board (group scope) shows overall + children clearly.
• Bot prompt/tools drive create/update of that structure from conversation.
• Bot updates progress/column as it works; blocked path reaches the user.
• npm run verify green; docs/changelog as required.