codeburn/scripts/upgrade-path
iamtoruk aeaa11f73f ci(upgrade-path): guard durable history across a bump on an extant source
The corpus had no durable SQLite provider, so the one never-lose direction it
could not reach was the one this change breaks: a source that keeps its file
while the provider prunes rows out of it. gen-corpus now writes copilot's OTel
span store at its real default path (80 spans over 40 days), and the run caches
it with the published CLI, deletes half the spans from a DB that stays present,
valid and populated, then upgrades through the parse-version bump.

Copilot cost must not shrink across that, and must still not shrink on the
warm run that reads the rewritten cache — a carry-forward that only survived
in memory fails the second check. Verified to bite: with the carry-forward
reverted the step reports LOST $0.361746 (10.0%) and fails.

Also: the expected daily-cache filename moves to v21.
2026-08-19 12:46:01 -07:00
..
compare.mjs ci: verify the 0.9.20 upgrade path on every platform 2026-08-18 12:14:55 -07:00
gen-corpus.mjs ci(upgrade-path): guard durable history across a bump on an extant source 2026-08-19 12:46:01 -07:00
run.mjs ci(upgrade-path): guard durable history across a bump on an extant source 2026-08-19 12:46:01 -07:00