[Daanish2003]

Summary

Spec #1007, the Tasks view and whole-Bot pause/reset (build item 2 of 14 on #962), from the Wayfinder #974.

• Tasks view: a "Tasks N" header popover with In progress / Scheduled / Done tabs replaces the To-do and Routines · Check-ins popovers. It reads one RPC, bots.tasks, and refreshes live from change-log hints. (The Tasks view: a "Tasks N" popover with the existing controls #1009)
• Skip a waiting Routine, webhook or Check-in Trigger with triggers.skip. The Trigger never reaches a Turn, and Done shows it as skipped. (Skip a waiting Routine, webhook or Check-in Trigger #1010)
• User edits: routines.edit (the edit is its own Approval, the Routine keeps its state, and the edit applies from the next run) and checkIns.edit, in inline forms. (The user edits a Routine or a Check-in #1011)
• Bot pause: bots.pause and bots.resume, a "⋯" Bot menu, a Paused badge, a composer banner, a disabled composer. While the Bot is paused, everything that comes due is recorded as skipped (reason paused). User Messages and Approval yeses are refused, and a webhook still answers 202. (Bot pause and resume #1012)
• Bot reset: bots.reset behind a typed-name gate. It wipes the Bot's Routines, Check-ins, Helpers, pending Approvals and own Memory files, keeps everything else the spec lists, and appends a reset mark. The Bot sees nothing from before the mark. (Bot reset #1013)
• Schema (Schema for the Tasks view, Bot pause and Bot reset #1008): bot.paused_at, Trigger skipped_at + skip_reason, the reset message role, and a partial index for skipped Triggers. All in one migration.
• CONTEXT terms Tasks view, Bot pause and Bot reset (from docs/974-tasks-view).

Closes #1007

How it was tested

• New integration suites at the RPC seam: bot-tasks, bot-trigger-skip, bot-pause, bot-reset, bot-memory-reset, plus cases added to the bot-send, Routine-fire and Check-in suites. Each new test was seen red before its implementation or fix.
• New UI component tests: bot-tasks, bot-task-edits, bot-pause, bot-reset.
• A high-effort branch review found 10 issues, all fixed in db7c9e8 and 13ae493. They include: pause now takes back allowed-but-unstarted calls; a pre-reset call's result never reaches the reset Bot; Memory deletion is a durable runner job; and attachments are no longer lost on a pause/resume race.
• Full verify on 13ae493: VERIFY OK, 2564 tests passed (34 skipped). Full e2e: 58/58.

Decisions I made

• Public API (owner-approved on Bot reset #1013, 2026-10-30): an optional resetBot(botId, userId, context) hook on defineFeature, run by a durable bot.reset job enqueued in the reset transaction. Memory implements it. ADR 0029 is amended.
• Schema (owner-approved, 2026-10-30): the partial index bot_trigger_skipped_idx is folded into the spec's unreleased migration 20261029163647_tasks_view. A local database that applied the earlier version needs recreating.
• The reset mark is a third message_role value, reset.
• A user Message skipped by a pause stays visible but is left out of later Turns' input. Email to a paused Bot saves no Message.
• While paused, only tool-call Approval yeses and Choice answers are refused. Routine and rule approvals are unchanged.
• A new bot change kind carries Bot-row changes (text column, no migration). pausedAt is on the Bot type, bots.get/list and the user export.
• Reset's history cut uses a strict > on the mark's timestamp. A row in the mark's own millisecond is treated as before it.
• New public RPCs, all approved in the spec: bots.tasks, bots.pause, bots.resume, bots.reset, triggers.skip, routines.edit, checkIns.edit.

Risk

• Schema: one new migration (approved). Irreversible by design: bots.reset deletes a Bot's Routines, Check-ins, Helpers with their transcripts, and its Memory files. The lab repo is never deployed.
• Left as follow-ups: an approved call already started at pause time finishes, and its result is kept as skipped. The Tasks view's six reads are not snapshot-consistent; a change hint triggers a re-fetch.

🤖 Generated with Claude Code