Part 1 of what #1917 asked (split after two red tries). One file, so a red check can only be this file or main.
Done looks like:
[ ] src/core/migrations/<UTC yyyymmddHHMMSS>-usage-count.ts, stamped later than the newest file in that directory on today's main (copy the shape of 20261016120000-kept-is-a-person-s.ts), creates usage_count(hour TEXT, pattern TEXT, method TEXT, status TEXT, role TEXT, surface TEXT, n INTEGER NOT NULL DEFAULT 0, PRIMARY KEY (hour, pattern, method, status, role, surface)) WITHOUT ROWID. status holds a class (2xx…5xx).
[ ] Nothing else changes: no module, no server wiring, no page. Do not hand-edit src/core/releases.json.
[ ] test/schema-migrations.test.ts, test/schema-additive.test.ts, test/sole-owner-suspend.test.ts and test/check-list.test.ts pass. If one of them fails on main too, say so in the pull with the main sha and its output, and do not change it here.
Files: the one migration. Run bun x tsc --noEmit and the four tests above before pushing.
Part 1 of what #1917 asked (split after two red tries). One file, so a red check can only be this file or main.
Done looks like:
src/core/migrations/<UTC yyyymmddHHMMSS>-usage-count.ts, stamped later than the newest file in that directory on today's main (copy the shape of20261016120000-kept-is-a-person-s.ts), createsusage_count(hour TEXT, pattern TEXT, method TEXT, status TEXT, role TEXT, surface TEXT, n INTEGER NOT NULL DEFAULT 0, PRIMARY KEY (hour, pattern, method, status, role, surface)) WITHOUT ROWID.statusholds a class (2xx…5xx).src/core/releases.json.test/schema-migrations.test.ts,test/schema-additive.test.ts,test/sole-owner-suspend.test.tsandtest/check-list.test.tspass. If one of them fails on main too, say so in the pull with the main sha and its output, and do not change it here.Files: the one migration. Run
bun x tsc --noEmitand the four tests above before pushing.