[Fix] Disabled automations no longer launch from stale scheduler scans

[roomote-roomote]

​Opened on behalf of @daniel-lxs. View the task or mention @roomote-roomote for follow-up asks.

What changed

The scheduler's atomic launch claim now requires the persisted automation to still be enabled. A stale scheduler snapshot can no longer claim and launch an automation after a user disables it.

Database-backed regression coverage captures an enabled automation, disables it, and verifies the stale launch claim is rejected. Existing coverage continues to verify that enabled automations can be claimed.

Why this change was made

The scheduler lists enabled automations before processing them individually. Previously, the later atomic claim checked only launch fencing and lastRunAt, so a disable committed between the list and claim could still permit one unwanted run.

Impact

Disabling an automation now prevents pending scheduler snapshots from launching it. The targeted database suite passes all 9 tests, and the database package type-check, lint, and formatting checks pass.

Related PRs

• Artifact deletion retry safety: [Fix] Task deletion no longer leaks artifacts after storage failures #2186

[roomote-community]

No code issues found. See task

_{Reviewed 6c0f55b}