Task: Record the date a run priced at
Table of Contents
This page documents a task in the Prove the report grid run end to end — the remaining work story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
A run records the date it priced at, and why it moved when it did.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Prove the report grid run end to end — the remaining work |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-25 |
3. Acceptance
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
6. Notes
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
8. PRs
| PR | Title |
|---|---|
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Result
A run says which date it priced at, and why it moved.
The report instance gained priced_at and price_note, both nullable, with
their SQL, repository, domain and TypeScript regenerated. A record_run_pricing
operation carries the two from the package handler to the reporting service,
which writes them on the instance. The package handler sends it with the run's
own token, so the write is the run's and row-level security scopes it, and it
does not touch the database itself. A moved date says the run asked for one date
and the gathered data ends at the other. A date that did not move says nothing.
The page shows one line on the Run tab when the date is there.
Proven on instance c09ebaf1: priced_at 2026-05-05 and price_note "The run
asked for 2026-10-23 and the gathered market data ends at 2026-05-05, so the run
priced at the data's date.", read back both from SQL and from
report_instances get. The run completed, because it was a package run, whose
last step is packaging.
The reporting and shell suites pass, the web typecheck is clean, and the new service and page tests cover the write and the line.
=