I3382 — Every recorded benchmark run answers the same delivery-economics shape as a task

✕BLOCKED wave 1 · p1 · implementation profile · parallel safe

Part of delivery-economics-are-measured-over-declared-windows — Delivery economics are measured on corpus runs and on real work over a window registered before it opens, and published with their denominators and losses.

Objective

Add economics tasks --runs: per recorded benchmark run, wall time from started_at to finished_at and per session (duration_ms), scripted follow-up prompts apart from interventions (none by construction of the headless harness), ci_reruns not_applicable, spend as observed tokens with the projected cost labelled as a projection, and accepted as the hidden acceptance_tests check. Add an aggregate per suite and variant with medians beside their denominators, published nowhere until ADR 0082's rule is met.

Why

T3 of the owner's report of 2026-10-19 asks for the same figures on corpus runs, and T2 and T4 compare arms in this shape, so real work and benchmark runs are read alike.

Current state

apps/majordomus-cli/src/economics/model.rs:687 records duration_ms per session and :701 reported_cost_microusd; no reading combines them per run.

Desired state

economics tasks --runs returns one record per committed run in the task shape.

Scope

• apps/majordomus-cli/src/economics
• apps/majordomus-cli/tests/economics.rs
• docs/ECONOMICS.md

Out of scope

• Comparing arms (I3371)
• Publishing an aggregate

Dependencies

• I3376○READY One capability states each task's wall time and episodes from every checkout's ledger, and names every field it cannot yet fill as not observed

Acceptance criteria

• Every committed run under .ai/repo/benchmarks/economics/runs answers the shape
• Interventions read none by construction, ci_reruns not_applicable
• The projected cost is labelled as a projection
• The aggregate states its denominator

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test economics
• majordomus economics check

Evidence required

• test_run_records_answer_the_task_shape

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3382.yaml. Read it back with majordomus plan show I3382.