Scheduled-task detector

Run at 2026-09-18 04:30:00 · grace 6 h · 13 tasks checked

2MISSING
should have moved and didn't
2UNVERIFIABLE
nothing can prove it either way
2STALE
source machine unreachable
1QUIET-OK
quiet run, fallback moved
5OK
artifact moved on schedule
1NOT-DUE
nothing due yet

What to do

escalated-case-digest
expected an artifact newer than 2026-09-17 09:00:00; none found
SIG-02expansion-obfuscation — brace-next-to-quote in SKILL.md: '\'{"' (line 3)
weekly-fleet-review
expected an artifact newer than 2026-09-15 16:00:00; none found; the scheduler says it ran at 2026-09-15 16:16:00, but no session exists for it
SIG-10phantom-run — the scheduler recorded a run at 2026-09-15 16:16:00 but no session for this task exists, so nothing ever executed — a dispatch failure, not a blocked call inside the run

Every task

TaskVerdictDue byEvidenceWhy
escalated-case-digestMISSING2026-09-17 09:00:00~/Downloads/case-digest-2026-09-10.html
2026-09-10 09:04:00
SIG-02: expected an artifact newer than 2026-09-17 09:00:00; none found
weekly-fleet-reviewMISSING2026-09-15 16:00:00~/tasks/weekly-fleet-review/state.md
2026-09-08 22:54:00
SIG-10: expected an artifact newer than 2026-09-15 16:00:00; none found; the scheduler says it ran at 2026-09-15 16:16:00, but no session exists for it
filter-domain-pasteUNVERIFIABLE2026-09-13 08:00:00—quiet_ok with no fallback artifact — nothing can ever prove this ran
morning-stand-testUNVERIFIABLE2026-09-17 08:30:00~/Trackers/Health_Dashboard.html
2026-09-16 20:30:00
no artifact moved, but this task self-suppresses under a documented rule and leaves no receipt either way (SIG-09)
worker-nightly-export (worker)STALE——worker source stale; per-task verdict suppressed
worker-ticket-rollup (worker)STALE——worker source stale; per-task verdict suppressed
inbox-junk-sweepQUIET-OK2026-09-17 07:00:00~/tasks/inbox-junk-sweep/state.md
2026-09-17 07:10:00
primary absent (legitimate); fallback moved
daily-garden-checkOK2026-09-17 18:00:00~/Trackers/Garden_Log.xlsx
2026-09-17 18:05:00
primary artifact moved on schedule
daily-job-pipelineOK2026-09-17 03:00:00~/jobs/run_2026-09-18.json
2026-09-18 03:39:00
primary artifact moved on schedule
habit-naggerOK2026-09-16 22:30:00~/Trackers/habits-state.json
2026-09-17 20:30:00
primary artifact moved on schedule
morning-briefOK2026-09-17 11:00:00~/Downloads/morning-brief-2026-09-17.html
2026-09-17 11:18:00
primary artifact moved on schedule
weekly-podcast-digestOK2026-09-14 07:00:00~/Downloads/podcast-digest-2026-09-14.html
2026-09-14 11:30:00
primary artifact moved on schedule
manual-backfillNOT-DUE——no cron (one-time or manual)

What this report can't vouch for

Latent hazards

These tasks tell the agent to run something an unattended run can't get permission for (SIG-02/03). Today it's a prediction, not a failure: fix it here, or find out later from a MISSING row. Hits inside a warning (“do not use $(...)”) are already excluded.

TaskStatusPattern
escalated-case-digestwatchedSIG-02'{" line 3
old-rainfall-reportdisabledSIG-03python3 -c line 3
shelf-auditenabled, unwatchedSIG-03&& line 1