Cryptograss:Moods/usage/todo

• ☐
  Review magenta#235 (Pi on OpenRouter records the model that ran and what OpenRouter billed)

  review · re
• ☐
  Merge magenta#235, then redeploy hunter and maybelle

  merge · justin
• ☐
  Review magenta#237 (usage section on the prompts page)

  review · re
• ☐
  Merge magenta#237 after

  merge · justin
• ☐
  End-to-end tests of the cost path (Pi event to stored row to page), including routers

  code · re
• ☐
  Daily check of the page's OpenRouter total against OpenRouter's billed total (/api/v1/key usage_daily)

  code · re
• ☐
  Decide whether to backfill OpenRouter's billed cost onto past routed Pi calls (writes to the record)

  decision · justin

  Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly.