cos daily and cos retro answer “what happened?” in-session. The recurring ask from leads is the push version: a weekly digest — tasks done per swimlane, WIP that’s aging, newly learned patterns, and any gate bypasses — delivered without opening a session.
The data already exists (board history, learning records, the bypass log), so this is an output-channel feature, not a data feature. Two design questions before it’s buildable:
- Delivery: email means SMTP config per install; a generated markdown report (cron-friendly, pipe it anywhere) might be the 80% version.
- Scope: per-project, or across every registered project (the hub already knows them all)?
Vote if you want this, and comment with which delivery/scope combination you’d actually use.