Align tasks and automations product model

[sentry-junior]

Track product and runtime alignment for scheduled tasks, event tasks, and resource subscriptions after UX work on task agent input (#1716).

Open questions and follow-ons:

• Product name: keep Task, rename family to Automation, or split notify vs automate jobs
• First-class delivery mode (notify vs silent) as stored data, not only prompt prose
• Agent input, dashboard, docs, tools, and destination footers should use one vocabulary
• How schedule, event, and subscription sources map under that model

Current framing lives in packages/junior/src/chat/task-input.ts, with the section outline in packages/junior/src/chat/README.md under Task agent input (one [task] header, optional source, explicit [[NO_REPLY]]).

Requested by David Cramer.

--

View Junior Session in Sentry

[dcramer]

Event terminology follow-up

Resource event is accurate, but it exposes an internal data-model term. The leading replacement is Event.

This gives the related terms a direct meaning:

• Event: one normalized change published by a plugin or core.
• Watch: a temporary Conversation association that receives matching Events.
• Event task: a saved instruction that runs for matching Events.

This also fits the current docs, which already use phrases such as “plugin event.” The main conflict is the stored Conversation event log. Use Agent history item for those records, as TERMINOLOGY.md already requires.

Decide this with the Task versus Automation product name. Then apply one complete rename across the Source kind, plugin contract, watches, dashboard, and docs. Do not add a partial alias.

Related: #1563 and #1730.