Capto is a dead-man's switch for cron jobs, workers, and containers that shows the last useful context when a background task goes quiet. It combines lightweight checks with incident breadcrumbs so teams can investigate the failure rather than search a dashboard from scratch.

What's included in this release:

• Heartbeat checks tell teams when a worker or daemon has stopped sending its expected ping.
• Cron checks compare activity with a schedule and timezone so jobs that never start can be noticed.
• HTTP checks wait for consecutive failures before paging, keeping a single transient blip quiet.
• Optional breadcrumbs preserve recent job context on an incident, including messages and useful data.
• Alerts can reach ntfy, Telegram, email, or a webhook, with queued delivery and retry handling.

Together, these checks and contextual alerts help teams detect quiet failures, understand what happened last, and route the incident to the channel they already use.