ref(chat)!: add task, Plugin dispatch, and Agent invocation Sources

[dcramer]

Scheduled tasks, Event tasks, Plugin dispatches, and Agent invocations now set
the Source that caused each Turn. They no longer copy a Slack Source or the
parent Run's Source. Plugin background tasks use the Source saved on the Turn.

Slack tools use the Conversation Location and visibility. Actions on the
current Slack message still require a Slack Source. Slack reply instructions
require Delivery and a Slack Location. This lets scheduled Slack work reply to
Slack while an Agent invocation can use Slack tools without sending its result
to Slack.

Plugin dispatch callers must stop passing source; Junior now sets Plugin
dispatch Source. Legacy session Source and Destination reads remain only for
deployed data. TODOs state when to remove them. Scheduled task and Event task
tools still require Slack when users manage them. TODOs state that these tools
should later work from web and other Conversations.

Refs #1563

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
junior-docs	Ready	Preview	Aug 29, 2026 10:26pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2873322. Configure here.}

[cursor]

Plugin tasks drop Slack context

Medium Severity

Prior public Slack thread evidence is now skipped whenever the Turn source is scheduled_task, event_task, plugin_dispatch, or agent_invocation. That decision uses the trigger Source, but conversation context is a Conversation Location and visibility concern. Plugin session.completed tasks for scheduled Slack work and Agent invocations therefore lose the public thread messages a completed run may have acted on.

 

^{Reviewed by Cursor Bugbot for commit 2873322. Configure here.}