NotifyStepDefinition

Notify step — sends a notification (Slack, Teams, email) without dispatching a tool. Stuart 2026-05-19: 1 template on dev uses ``type='notify'`` (the FIC reconciliation step); same schema-gap fix as archie_query.

Field	Type	Description
`id`required	`string`	—
`name`required	`string`	—
`type`	`string`	—
`description`	`string \| null`	—
`depends_on`	`string \| object[]`	—
`stage`	`string \| null`	—
`timeout`	`string \| null`	—
`retry_policy`	`RetryPolicy \| null`	—
`error_handler`	`StepErrorHandler \| null`	—
`impact_level`	`"low" \| "medium" \| "high" \| "critical"`	Impact classification for steps. `lowmediumhighcritical`
`run_mode`	`"propose" \| "auto_run"`	Execution mode for steps. `proposeauto_run`
`requires_approval`	`boolean`	—
`metadata`	`object \| null`	—
`examples`	`StepExample[] \| null`	Attached example files for this step. Each entry pairs a platform.file_uploads.file_id with a role + tags + notes so the runtime can shape its instruction. Bounded at 20 to keep a reasonable upper limit on the prompt preamble.
`tags`	`string[] \| null`	Categorical labels on the step itself (e.g. 'pdf-read', 'coutts', 'fy25'). Free-form; recommended tag set is documented per workstream surface.
`channel`required	`string`	Notification channel slug (e.g. 'slack:#close-team', 'email:[email protected]').
`message`required	`string`	Message body — supports {{ outputs.* }} Jinja2 placeholders.
`inputs`	`object \| null`	Optional Jinja2 input bindings.