Group kanban: one task lead assigns, and that Bot starts the card without a nudge #1182

Written-by: Dev

Environment

FlyBot main at 2521aab (after #1109 task-drive and #1099 group tasks). Ordinary group rooms, not face-to-face.

Steps to reproduce

1. In a group that has an admin and at least one other Main Bot, give the group a job.
2. Watch who calls track_tasks with overall: true and assignee.
3. Leave the assigned cards on the board and do not send another message.

Actual

• plansRoom in core/src/host/tasks.js is true for the group admin and every Main Bot in the room, so more than one Bot can record the overall task and assign subtasks. There is no selectable task lead, so when the Chief is not the one who should divide the work, the room cannot name a single planner.
• A member can record a new room task that is not a subtask of the overall task, which is a second plan.
• An assigned subtask stays open until someone moves the column. Nothing claims it.
• core/src/host/task-drive.js does wake the owner after a board write, but the wake is a private [Continue task] follow-up (role: 'task'). The turn's reply is not posted to the group. The prompt tells the Bot to use ask_user in its own chat when it is not in a group reply, so a question leaves the room. The card looks idle unless a person nudges.

Expected

• One selectable task lead (总负责人) per ordinary room divides the board. When none is picked, the group admin does, and only that Bot. Another Main Bot does not plan. Chief may be absent: the picked lead still assigns.
• A member does not open a second, unparented group plan. They update the card they were given, or link their own subtask to the overall task.
• Assigning a subtask claims it. The assignee starts the work and does not wait for a confirmation.
• That wake is a turn in the assignee's group session (role: 'room'). The reply is posted into the group, so a question stays there. A late post does not call the whole room. A live round still waits until it ends.

Where it sits

• core/src/host/tasks.js plansRoom (admin or any Main member).
• core/src/host/task-drive.js cueFor / deliver (role: 'task', reply not a room post).
• core/src/host/prompt.js and track_tasks: "the admin (or a Main Bot)".
• core/src/host/groups.js adminNote: every admin is told to record the overall task.

Suggested direction

One room.taskLead, set from group settings or update_group. plansRoom is that lead, else the admin. Claim on assign. Drive a group subtask as a room turn whose reply posts late into the group.