Automations and cron editor: stuck runs and schedules

Goal: an operator can see at a glance what a schedule will do and whether it is stuck, and can clear it safely from wherever they meet it. Stuck automations 1. Release asks once ("Release? The stuck run may still finish."), as Delete does. 2. A stuck schedule's Run now is disabled with "Release it first". Stuck/Release shows even when the schedule is paused. 3. The Automations list row menu (⋯) offers Release for a stuck schedule. 4. The Runs tab folds consecutive `already_running` skips into one "Skipped N runs since …" row. Cron editor (automation When section) 5. One schedule gets one description: the summary row and the card must not word it differently, or the saved one is labelled. 6. The "Builder spells it … ; saved … is unchanged" note sits next to the expression field, not in small text below the card. The header expression field is clearly the builder's reading, not the saved value. 7. Close/Done is reachable at the open editor's own edge, not only at the far right of the summary row. Out of scope: lock/timeout mechanics (Task 7781); the mount handshake and parse window (Task 7773). Done means: - Each item shipped or declined with a reason in the PR; web unit tests for the confirm/disabled states. - Desktop and 390px screenshots of the touched surfaces. Required checks: ./dc check full Consolidates drafts 7826 (items 1–4, 6), 7848.

All 7 items shipped in PR #6215; it is merged (951c29513) and Jaah Deploy succeeded. Every full-gate stage passed except Vale, which fails on develop's people.md from Task 7866, not this diff (draft #7908). The 1440/390 screenshots are in report 6404.