[Birfy]

Fixes #473

What. Each row in Settings → Scheduled tasks (and a Bot's card) shows its last run: "Running since …", "Last run …", "Last run … · Stopped", or in red "Last run … · Failed: ". A failed run of a task that is not paused gets Retry, which runs the task once now with the same prompt.

Why / how (Owner decision 2026-10-20, option a):

• A run fails only when DSH could not deliver it or the Bot's turn errored; a finished turn without an answer has run. FlyBot records each task's last run in state.scheduleRuns from the turn that took in the reminder (turns.js → schedules.js); a group task fails when a member's turn in that round failed.
• "Not delivered": DSH only logs a refused delivery and leaves the task due, so a task still due 2 minutes after FlyBot first saw it due (while the app runs) is a failed run, once per missed time.
• Retry sends a schedule-source message in DSH's reminder framing to the Bot's current part (or the group), so the turn is that task's run and keeps the scheduled connector verdict. DSH's own times are untouched: no backfill.
• Needs you: a failed scheduled turn is already in work.ended (Proactive reminders 1/3: event reminders (approval waiting, failed, finished) in app and desktop #353 notifications); a reminder DSH did not deliver is added there too (rt.noteRunFailure), the same list Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471 turns into Agent inbox cards. No second event path.
• Limits ([Team] Bound agent loops and resource consumption #56) are not in this step.

Test. ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify passes (core 1081, social 296, tree 80, timeline 83, scripts 93, interop 37, live-e2e 16; 0 failures). New tests: core/test/schedules.test.js (run results, Retry, not delivered), core/test/schedules-client.test.js (row line + Retry), authz.test.js (schedule-retry ownership). Not run: live DSH with the Automation tasks bundle, smoke test.

Risk tier: T2 (estimate; the controller sets the label)

[Birfy]

Self-review: PASS
Tip SHA: 561d0e3
Ran:

• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify at the tip: 0 failures (core lint + arch-docs OK, plugin lint, build-client --check, ds-bot-patches check, core 1081, social 296, tree 80, timeline 83, scripts 93, interop 37, live-e2e 16)
• CI at the tip: tests-ok, test, plugins (social/tree/timeline), package all green; risk tier T3 (authz.js, channel.js)
• Diff reviewed against the Owner decision (option a): failed = DSH did not deliver or the turn errored; a finished turn without an answer is a run; Retry = same prompt once now, no backfill; failures go into the Proactive reminders 1/3: event reminders (approval waiting, failed, finished) in app and desktop #353 ended-turn list (no second event path); limits ([Team] Bound agent loops and resource consumption #56) left out
• Design rules: Retry is an owner UI button behind the same session-ownership check as Pause (authz.js); no approval by chat reply; English UI copy with zh strings; no DSH patch (only createUserMessage with DSH's schedule source and its public catalog)
  Not run:
• Live DSH with the Automation tasks bundle (a real refused delivery, a real scheduled turn), the smoke test, the user's Mac instances
• Agent inbox card for a failed scheduled run: comes from Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471 (reads the same work.ended list), not in this PR

[Birfy]

Self-review: PASS
Tip SHA: 0c2f52a
Ran:

• Merged origin/main (303c0d6, includes Fit chat approvals and the Agent inbox to a phone-width screen #481/Keep live shares in People with access using Bot Social's reply_only #501/Show a friend's first line and its approval card live: read friends' inboxes fast while a window is on screen #505) into feat/473-schedule-last-run-retry; only conflict was generated 0008-client-bundle.patch (regenerated) (2026-10-20 15:02 Asia/Shanghai).
• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify: passed (core lint + arch-docs OK, plugin lint OK, build-client --check OK, ds-bot-patches check OK; core/social/tree/timeline/scripts/interop/live-e2e all green).
  Not run:
• Live Mac instances or the production Bot Social server (not touched).

[Birfy]

Self-review: PASS
Tip SHA: d3ad708
Ran:

• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify (pass)
• reviewed diff at tip vs owner design rules
  Not run:
• live Mac instances / production Bot Social

[Birfy]

Self-review: PASS
Tip SHA: 877927e
Ran:

• git merge origin/main (eb91742, after Remind about approvals waiting 15 min, switch each notification kind, one notification per chat #492 and Social: neutral 'You already have …' on a re-accepted invite; clearer Remove confirm #503) into the branch, no rebase or force-push; only conflict was the generated patches/ds-bot/0008-client-bundle.patch
• generated files regenerated, not hand-merged: took main's patches/ds-bot, then (cd core && npm run build), node scripts/ds-bot-patches.mjs generate, then check: ok (10 patches apply cleanly; core/ = ds-bot/ + patches)
• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify (core lint + arch-docs, plugin lint, build-client --check, ds-bot-patches check, all suites): pass, 0 failures (core 1102, social 309, tree 80, timeline 92, .github scripts 93, interop 37, live-e2e 16; a first run had 1 failure in connectors.test.js 'an address saved by an older version…' under parallel load, which passed 3/3 alone and in the full file; the rerun of the full verify passed)
• CI on this tip: all checks pass (tests-ok, Node 24 · DSH 0.2.0-rc.2, plugins social/timeline/tree, package, risk tier, reviewed tip); mergeable MERGEABLE, mergeStateStatus CLEAN
• re-read the diff against main at this tip: changelog.d fragment kept, no CHANGELOG.md or ds-bot/ edits, owner design rules kept (approvals only via UI buttons, English UI, no separate Friends' Bots section, no turn limit or Extend in friend chats, connector tokens only at /mcp)
  Not run:
• live Mac instances / production Bot Social

[Birfy]

Self-review: PASS (merge-main conflict fix; no feature change)

Tip SHA: 67ddae5
Ran:

• git merge origin/main (107aa82, after Timeline: an on-demand export endpoint #524 timeline export, Polish invites and friend chats: friend Bot placeholder, one invite control, Add friend auto-close, Sharing hint #504 invites polish, Show a tree coordinator its children's runtime load #508 tree coordinator load, Add an opt-in state journal and a dev replay script #527 state journal) into the branch; no rebase, no force-push
• conflicts: docs/subsystems/core-host.md (this PR's "Scheduled tasks: last run and Retry (Scheduled tasks: last run result, failed runs with retry, and limits (#354 follow-up) #473)" section and main's new "State journal (RFC: durable Bot state journal and time-travel replay (reliability) #511)" section at the same spot; kept both, unchanged) and the generated patches/ds-bot/0008-client-bundle.patch
• generated files regenerated, not hand-merged: git checkout origin/main -- patches/ds-bot, (cd core && npm run build), node scripts/ds-bot-patches.mjs generate, then check → pass (10 patches apply cleanly; core/ = ds-bot/ + patches); build-client --check → pass
• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify (core lint + arch-docs, plugin lint, build-client --check, ds-bot-patches check, all suites) → pass, 0 failures (core 1112, social 312, tree 83, timeline 93, .github scripts 93, interop 37, live-e2e 16; arch-docs OK, 24 changed files)
• smoke (PR touches core/src/host/): CONTEXT_WINDOW=100000 CHECK_RATIO=0.45 dev/bench.sh smoke494 3196 8896 reset && node dev/smoke.mjs smoke494 3196 against DSH 0.2.0-rc.2 → pass, all 42 steps; bench stopped afterwards
• CI on this tip: all checks pass (tests-ok, ubuntu-latest · Node 24 · DSH 0.2.0-rc.2, plugins social/timeline/tree, package, risk tier, reviewed tip); mergeable MERGEABLE, mergeStateStatus CLEAN
• re-checked the diff against main at this tip: still the same 24 files as the PR before the merge; one changelog.d fragment (473-schedule-last-run-retry.added.md); no CHANGELOG.md or ds-bot/ edits
  Not run:
• live Mac instances / DSH Desktop / real-model live-e2e (no key; mock model only)
• production Bot Social (not in scope)

Verdict: PASS

Not merge authority: risk:T3, waits for the maintainer's approval (merge queue).