Redesign the Automation UX and UI workflow

Problem and outcome

Redesign the Automation workflow so users understand how to configure, test, enable, monitor, and recover scheduled or conditional work.

Scope

• Map creation and editing from schedule or condition selection through Space selection, execution setup, testing, enabling, and reviewing the resulting Session.
• Clearly present runtime availability, readiness, timezone, and the next execution time.
• Use valid future scheduling defaults, explain first-run timing, and validate one-time selections.
• Add a Run now action with visible progress, results, and a link to the Session.
• Present configuration revision selection, fresh-versus-continuing Session behavior, and repeat/overlap policies clearly.
• Design setup required, ready, disabled, queued, running, waiting, completed, failed, and missed states with actionable explanations.
• Show missed-execution and automatic-deactivation reasons, plus recovery actions.
• Make execution history and one-time completion understandable.
• Define privacy-conscious UX events for discovery, setup, validation, editing, testing, and abandonment.

Design and validation

Follow docs/design-system/design.md and docs/product-terminology.md, use docs/design-system/index.html as the visual reference, and reuse existing UI primitives and semantic tokens. Preserve backend Trigger identifiers and contracts.

• Creation, editing, testing, monitoring, and recovery flows are designed and implemented.
• Users can understand readiness, timezone, first execution, Session behavior, and execution outcomes.
• Missing setup, missed executions, and deactivation have clear next actions.
• Light/dark themes, keyboard navigation, loading, empty, error, and long-content states are validated.
• Focused tests, type checking, design-system checks, locale parity when applicable, and git diff --check pass.

Related work

Runtime readiness, configuration pinning, Session routing, and execution policies belong to #1929.