Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Costs & margin: one total for who g1t paid, own spend explained, rates and replaced rises said plainly | 1 | -- A proposal the guardrail applied as a rise waits for its notice as a |
| 2 | -- price version; a newer measurement before that date replaces the | |
| 3 | -- version (src/pricing.rs, schedule_version). The proposal behind the | |
| 4 | -- replaced version never took effect, but stayed "applied" with no date it | |
| 5 | -- is in force from: sandbox_second and build_second's rises of 2026-10-07 | |
| 6 | -- (v2, due 2026-10-21) were replaced by v3 (due 2026-10-22) on 2026-10-08. | |
| 7 | -- Nothing was charged at v2. From now on the replacement marks them | |
| 8 | -- superseded; these are the ones from before. | |
| 9 | UPDATE price_proposals SET status = 'superseded' | |
| 10 | WHERE status = 'applied' AND version_id IS NOT NULL | |
| 11 | AND version_id NOT IN (SELECT id FROM price_versions); |
