Freshness Check
scripts/check-freshness.tsis the live maintenance readout for overdue automations, stale syncs, and uncompiled material.
Run:
npx tsx scripts/check-freshness.ts
The script reads state.json, automation definitions, sync timestamps, source compile markers, and maintenance state. Kevin should never need to track dates manually. Source: AGENTS.md Session Startup; scripts/check-freshness.ts
Interpretation
| Output | Meaning | Response |
|---|---|---|
| Needs attention | Something configured to run is overdue, never run, stale, or blocked. | Name it and run/route it if in scope. |
| Notices | Informational gaps such as on-demand or cloud-only jobs. | Mention only when relevant. |
| Up to date | State is current for the configured cadence. | Usually omit from user-facing summary. |
2026-07-01 Snapshot
The current check reports 27 needs-attention items, 2 notices, and 5 up-to-date items. The important classes are never-run Slack/Gmail/Circleback/Calendar integrations, never-run daily and weekly automations, stale source-compile, stale Obsidian/AI-session syncs, and overdue self-heal. Source: npx tsx scripts/check-freshness.ts, 2026-07-01
This snapshot is evidence, not a standing table. Re-run the command for the actual current state.
Common Mistakes
- Treating cloud notices as local failures.
- Updating
automations.<slug>after a failed external collection and pretending sync succeeded. - Reporting stale state before doing an unrelated urgent task.
- Ignoring a never-run integration forever instead of routing setup, deletion, or explicit deferral.
Timeline
- 2026-07-01 | Added live-state semantics and the 2026-07-01 freshness snapshot while keeping the command output authoritative. Source: User request, 2026-07-01; scripts/check-freshness.ts
- 2026-05-31 | Freshness check documented in heartbeat category. Source: public wiki expansion, 2026-05-31