Cryptograss:Moods/usage/todo: Difference between revisions

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
Re (talk | contribs)
Quote a task: its unquoted "Prompts: OpenRouter" broke the list (via update-page on MediaWiki MCP Server)
DrivingThatTrain (talk | contribs)
m Merged, says GitHub: https://github.com/cryptograss/magenta/pull/303
 
(One intermediate revision by one other user not shown)
Line 15: Line 15:
   kind: review
   kind: review
   link: https://github.com/cryptograss/magenta/pull/303
   link: https://github.com/cryptograss/magenta/pull/303
  done: true
- task: Merge magenta#303, then redeploy maybelle
- task: Merge magenta#303, then redeploy maybelle
   who: justin
   who: justin
   kind: merge
   kind: merge
   link: https://github.com/cryptograss/magenta/pull/303
   link: https://github.com/cryptograss/magenta/pull/303
- task: Once #251 has real plan readings, turn headings show OpenRouter turns in billed dollars and Claude Code turns as the 5-hour window after them ("5h 44% (+2)"), not list-price dollars
  done: true
- task: "Once #251 has real plan readings, turn headings show OpenRouter turns in billed dollars and Claude Code turns as the 5-hour window after them (\"5h 44% (+2)\"), not list-price dollars"
   who: magent
   who: magent
   kind: code
   kind: code

Latest revision as of 22:09, 8 November 2026

  • ☐
    Once #251 has real plan readings, turn headings show OpenRouter turns in billed dollars and Claude Code turns as the 5-hour window after them ("5h 44% (+2)"), not list-price dollars
    code · magent
  • ☐
    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.
  • ☐
Done (4)