31802856015
88%

Ran 14 Aug 2026 01:05PM UTC

Jobs 1

Files 71

Run time 1min

Badge

Embed ▾

Committed 14 Aug 2026 01:01PM UTC coverage: 88.126%. Remained the same

Build # 31802856015

Build Type

push

github

Committed by

andgineer

Commit Message

one --prod flag for every task, restores included

--remote meant "read prod" on six commands and nothing else could reach prod
except restore-litestream, whose name looked exactly like the three restore
tasks that write locally. That naming is what let a mistyped command overwrite
production. The flag now names the environment and the confirmation names the
risk: restore-yadisk/-replica take --prod, ask for the literal word "prod"
(which --yes cannot suppress), and print how many expenses the snapshot drops
before doing anything.

--prod restores run entirely from the operator machine: stop services, preserve
the current DB under a timestamped name, swap, resync both LTX trees, restart,
report. No inv on the server, so a restore no longer depends on the revision
deployed there — which also removes local_replica_resync and, with it, the only
non-sftp use of VM1's replica key.

sql --write --prod stays refused: that path reads a /tmp snapshot torn down on
exit, so a mutation would be discarded rather than applied.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Coverage Stats

4802 of 5449 relevant lines covered (88.13%)

0.88 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	31802856015.1	14 Aug 2026 01:05PM UTC	71	88.13	GitHub Action Run

andgineer / dinary / 31802856015
88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 31802856015

andgineer / dinary / 31802856015 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 31802856015

andgineer / dinary / 31802856015
88%

README BADGES
x