IB-WP-0019-T02: usage rollup from run records

Every completed generate run now aggregates per-call adapter usage from
the workflow-engine run records into output/budget/usage.yaml. Per-call
data is bucketed by (workflow_id, stage_id, provider, model) with
running totals for calls, prompt_tokens, completion_tokens,
total_tokens, and cost_usd_known (sum of adapter-reported cost when the
provider returns it; usually zero today). A run-level entry captures
run_index, started_at, completed_at, duration_seconds, the executing
plan snapshot_id (resolved from the latest plans.yaml entry), and the
workflow-level run_id / stage_count summaries.

cost_usd_estimated is left as None for this task; T03 wires the
rate-table resolver so the same bucket gets a model-priced fallback
when the adapter does not return cost directly.

Fixture-mode runs are recorded with provider='fixture', zero tokens,
and cost_status='unknown' rather than silently skipped, so the rollup
honestly reflects which stages actually ran.

102 tests pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

This commit is contained in:

Bernd Worsch

2026-05-17 19:46:40 +02:00

parent 37bbaf9fab

commit 678508226a

4 changed files with 315 additions and 2 deletions

									
										2

workplans/IB-WP-0019-budget-and-usage-registry.md
									
												View File
												
				@@ -95,7 +95,7 @@ state_hub_task_id: "7f1a4e0a-c1ad-49f3-aad1-6946de9b1219"

				```task

				id: IB-WP-0019-T02

				status: todo

				status: done

				priority: high

				state_hub_task_id: "a612f8d4-f96d-4fae-9aa6-66a7946414f5"

				```

IB-WP-0019-T02: usage rollup from run records

2 workplans/IB-WP-0019-budget-and-usage-registry.md Unescape Escape View File

2

workplans/IB-WP-0019-budget-and-usage-registry.md

View File