feat: show whether an automation is ready before it is enabled #144

Summary

Please provide a clear readiness report for an automation before a user enables it.

Problem or workflow

Self-hosters and small teams need to know whether a recurring task is ready to run reliably. A configured schedule alone does not tell them whether required tools, settings, permissions, or recovery arrangements are in place.

Affected area

Automation setup, scheduling, and health reporting.

Proposed behavior

Extend the existing scheduling and health workflows with an easy-to-read summary showing what is ready, what is blocked, what has not been checked, and what the user needs to do next. Let users review the result without enabling the automation or changing their system. Keep readiness separate from whether a task is currently enabled or has run successfully before.

For example, someone preparing a nightly maintenance task should be able to understand why it is not ready and resolve the missing requirements before scheduling it.

Related: #61. This request focuses on readiness before activation rather than outcomes after a scheduled run.