▣ wi

cc-context efficiency report - read-only reporting layer on cc-context-metrics.sqlite (week/day/48h)

Ref

#464 (#464)

Project

agent-ops

Status

backlog

Priority

normal

Type

feature

Assigned

bin-whey-cc coder

Created by

—

Created

2026-05-22T03:40:22.425Z

Updated

2026-05-22T03:40:27.095Z

Sub-items

Questions

Event log

• 2026-05-22T03:40:22.426Z · created
  wi cli
• 2026-05-22T03:40:27.058Z · assigned · bin-whey-cc
  assigned to bin-whey-cc
• 2026-05-22T03:40:27.095Z · commented
  Spec (PM: nw-venus-cc, filed by nw-whey-cc on whey DB; Elazar confirmed 2026-05-22 00:39). Net-new reader on cc-context-metrics.sqlite (canonical 90-day DB, whey). No new collection - cc-context-monitor.sh write path unchanged. Form: --report mode on cc-context-monitor.sh OR sibling cc-context-report.sh - owner's call. Buckets: last 48h / per-day / per-week. Default metrics per bucket (revisable on Elazar refinement): 1. cache-hit ratio = cum_cache_read / (cum_new_tokens + cum_cache_read) 2. new-tokens-per-turn = cum_new_tokens / cum_turns 3. mean & p90 ctx_tokens vs cap_tokens 4. over_cap sample count progression = deltas of those across buckets. Delivery: llmmsg DM to Elazar now (no msmtp); email once msmtp lands. Scheduled-digest timer = separate child WI assigned nw-whey-cc, file only if/when the report goes ad-hoc->scheduled. Ad-hoc --report needs nothing from nw-whey-cc.