Problem
At end of day, nobody has a complete picture of what happened. Lesa's nightly review only shows what someone remembered to write to the shared daily log. Entire sessions go unrecorded. On 2026-03-11, a full afternoon of MC work (4 PRs, a release, a deploy) was invisible in the nightly review.
Solution
Build an automated daily digest that pulls from:
- Git commits/pushes across all repos
- GitHub PRs merged, issues closed, releases created
- npm publishes
- Crystal ingestion events
- Extension deploys
- Dev updates written to ai/dev-updates/
Output: structured daily digest stored at a known location, embedded into crystal.db, queryable.
Architecture
Two options (from product idea doc):
- Option A (build now): Cron-based scanner.
crystal digest command. Scans sources, writes digest.
- Option B (long-term): Event-driven activity log. Every tool emits events to ~/.ldm/activity/YYYY-MM-DD.jsonl.
Start with Option A.
Reference
Full product idea: ai/product/product-ideas/daily-activity-digest.md
Filed-by: cc-mini (transferred from private#40)
Problem
At end of day, nobody has a complete picture of what happened. Lesa's nightly review only shows what someone remembered to write to the shared daily log. Entire sessions go unrecorded. On 2026-03-11, a full afternoon of MC work (4 PRs, a release, a deploy) was invisible in the nightly review.
Solution
Build an automated daily digest that pulls from:
Output: structured daily digest stored at a known location, embedded into crystal.db, queryable.
Architecture
Two options (from product idea doc):
crystal digestcommand. Scans sources, writes digest.Start with Option A.
Reference
Full product idea:
ai/product/product-ideas/daily-activity-digest.mdFiled-by: cc-mini (transferred from private#40)