Demo seed: the dollar-cost usage example sits inside Admin's 30-day window #1137

Merged
claude-bot merged 1 commit from fix/demo-usage-cost-in-window into main 2026-10-12 17:00:21 +00:00
Collaborator

From the owner's review (item rc9-l9-usage, marked "Needs a change", 2026-10-12): "Only The Amberwake Accord and The Amberwake Accord (GM Copy) have any AI usage associated with them right now."

Admin → AI usage & speed shows the last 30 days (SessionUsage.started_at). The demo seed wrote its one costed row ($0.41 transcription, $0.09 summary) on The Salt Crown's last successful session, months before the seed's "now", so the page could never show it, and the review page's direction to look there was wrong.

The row moves, unchanged, to The Tuesday Tide's latest played session (session 3, seeded 6 days before "now"). The Salt Crown keeps its failed-after-two-tries row, which is outside the window like the rest of that abandoned campaign. --reset clears the old row with its campaign. The seed's README is corrected (it also wrongly said Brinewatch carried the dollar row).

Demo data only; no app code changes.

Checks

  • tests/test_demo_seed.py on the dev server against a throwaway Postgres: 8 passed; it now asserts a costed row exists within 30 days of the seed's "now" and none on the admin campaigns.
  • Ruff: clean. scripts/changelog.py check: OK.

🤖 Generated with Claude Code

From the owner's review (item `rc9-l9-usage`, marked "Needs a change", 2026-10-12): "Only The Amberwake Accord and The Amberwake Accord (GM Copy) have any AI usage associated with them right now." Admin → AI usage & speed shows the last 30 days (`SessionUsage.started_at`). The demo seed wrote its one costed row ($0.41 transcription, $0.09 summary) on The Salt Crown's last successful session, months before the seed's "now", so the page could never show it, and the review page's direction to look there was wrong. The row moves, unchanged, to The Tuesday Tide's latest played session (session 3, seeded 6 days before "now"). The Salt Crown keeps its failed-after-two-tries row, which is outside the window like the rest of that abandoned campaign. `--reset` clears the old row with its campaign. The seed's README is corrected (it also wrongly said Brinewatch carried the dollar row). Demo data only; no app code changes. ## Checks - `tests/test_demo_seed.py` on the dev server against a throwaway Postgres: 8 passed; it now asserts a costed row exists within 30 days of the seed's "now" and none on the admin campaigns. - Ruff: clean. `scripts/changelog.py check`: OK. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(demo): move the hosted-rate usage row into the 30-day window
All checks were successful
CI / Does this change touch the recording path? (pull_request) Successful in 32s
CI / Synthetic session harness (no GPU, no LLM) (pull_request) Has been skipped
CI / Bot/backend version sync (pull_request) Successful in 35s
CI / Backend lint (ruff) (pull_request) Successful in 36s
CI / Docker image build (pull_request) Successful in 39s
CI / Feedback site tests (pull_request) Successful in 48s
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m6s
CI / Bot tests and audit (pull_request) Successful in 2m8s
CI / Frontend (shard 2/2) (pull_request) Successful in 7m42s
CI / Frontend (shard 1/2) (pull_request) Successful in 22m18s
CI / End-to-end journeys (phone) (pull_request) Successful in 21m36s
CI / End-to-end journeys (keyboard) (pull_request) Successful in 23m26s
CI / End-to-end journeys (desktop) (pull_request) Successful in 23m40s
CI / Backend migration, tests, and audit (pull_request) Successful in 35m15s
eb2a252af1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-bot scheduled this pull request to auto merge when all checks succeed 2026-10-12 16:25:01 +00:00
Sign in to join this conversation.
No description provided.