In my previous post, Monitoring Claude Code hook watchdogs with launchd, I set up liveness monitoring for hooks — and immediately ran into the next question: a healthy hook means nothing if the product behind it is down. What I really wanted was a single page I could skim in five minutes every morning and know that everything is fine.
That page is daily-brief.sh. launchd runs it three times a day (8:00, 10:30, and at login), and it compiles production HTTP probes, hook latency p95, launchd exit codes, 7-day API costs broken down by model, and per-project git status into one Markdown file appended to Obsidian.
The problem: checking five places by hand every morning
The more you automate, the higher the risk that something breaks silently. I used to open all of these manually every morning:
The Vercel dashboard (production liveness)
