Task-driven Bot execution: unfinished board tasks wake the owning Bot #1109

Written-by: Dev

Goal

Make conversation Tasks drive Bot turns: when a Bot has unfinished work on the board, it wakes and executes that work on its own, instead of waiting for another human message.

Owner ask (2026-10-25, after #1099 / #1100): 「让Bot执行任务变成任务驱动，自主执行」.

Today (#1099 / merged #1100)

• track_tasks records overall + per-Bot subtasks, names the highest-priority unfinished task as Next:, and supports ask / answer when stuck.
• The prompt tells the Bot to continue that next task when it already has a turn.
• Idle default (Team prompts: a Bot stays idle until it is addressed or given a task (part B of #645) #699): a Bot does nothing until the user addresses it, it is @-mentioned in a group, or its parent hands it work via message_bot. Unfinished board cards therefore sit until someone chats again.

Expected behavior

1. Wake on unfinished work — when a Bot owns unfinished conversation tasks that are not waitingFor: input, the host starts a turn for that Bot (own chat, or the group Session that owns the subtask) with a clear continue cue naming the next task id/title/priority. No new user message required.
2. Auto-advance — after a turn updates progress/column and more unfinished own work remains (still not waiting), the Bot is woken again for the new Next (or finishes the chain in one turn when that is already natural). Done / cancelled / waiting tasks stop the drive.
3. Stuck stays escalate-once — a task waiting on input must ask the user or the group (existing ask path) and must not keep waking until answer clears it.
4. Priority — wake order matches track_tasks / compareForWork (urgent → high → normal → low; in-progress before not-started at the same priority).
5. Idle default preserved for inventing work — Bots still must not invent new jobs or status spam. Unfinished tasks the user or a group already handed them count as "given a task" under Team prompts: a Bot stays idle until it is addressed or given a task (part B of #645) #699; they do not authorize unsolicited new work.
6. Guards — no wake while that Session already has an open turn; coalesce duplicate wake requests; backoff if a wake made no board progress; do not open unbounded group rounds from the driver alone.

Scope (implementation sketch — agent should verify)

• Host path that notices unfinished conversation tasks and injects / schedules a continue turn (likely near tasks.js / delivery / follow-through; reuse existing schedule or inbox patterns if one already fits).
• Prompt: unfinished board work is an allowed wake reason; keep the "do not invent work" rule.
• track_tasks may expose or persist enough for the host to decide wake vs wait without a model call.
• Tests: host-level cases for wake, no-wake when waiting, no double-wake mid-turn, stop when done; extend prompt/tool tests if copy changes.
• Changelog fragment + docs/subsystems/core-host.md if behavior/docs change.

Out of scope

• RSI GitHub Issue→PR orchestrator ([RSI Baseline] Implement a persistent autonomous task orchestrator #787 / epic [RSI Baseline Epic] Build FlyBot as an Autonomous Software Engineering System #784).
• Replacing the per-Bot Kanban UI.
• Human project-management features beyond the current Tasks dialog.

Related

• Builds on Per-bot task list + Kanban board (conversation-derived tasks, tree + group admin views) #1058 / Add a per-Bot task board updated from conversation #1071 and Task board drives Bot planning: group overall tasks + per-Bot subtasks #1099 / Record a group's overall task and per-Bot subtasks #1100.
• Adjusts the practical reach of Team prompts: a Bot stays idle until it is addressed or given a task (part B of #645) #699 idle default for already recorded unfinished work only.

Acceptance

• A Bot with an unfinished own conversation task (not waiting) receives a continue turn without a new user message.
• After progress, remaining unfinished work continues (or a follow-up wake) until done or waiting.
• Waiting tasks ask once and do not wake-loop.
• Idle default still blocks inventing work and unsolicited status spam.
• Guards: no mid-turn double wake; backoff / coalesce as above.
• npm run verify green; docs/changelog as required.