venus
VENUS-351
db/DR.md stale: restore steps assume plaintext .sql.gz from the dead pre-Jun-16 lane
Done normal
unassigned
Flagged by coder-venus-cc during VENUS-348 doc leg (198a1d6): db/DR.md lines 9/36-42/123-126 assume plaintext .sql.gz artifacts from the dead lane; staleness noted in-doc. Rewrite needs bin-venus-cc's decrypt/restore procedure for the encrypted lane plus the whey partial-lane caveat (no supabase_migrations = restored DB loses migration history). bin supplies procedure text, coder pushes.
Questions
No questions.
Activity
-
e79a3a4 origin-verified: DR.md rewritten for encrypted lane (bin authored, Authored-By trailer two-line-parse verified — coder's FIRST Authored-By push, §PTD 8.4 satisfied); coder's anchored-glob correction accepted by bin; escrow objection recorded in-doc verbatim. Ruling issued (msa3i0k4wmnz): Step 3 vercel --prod --yes replaced by empty-commit git push as the redeploy trigger (no DR exception; GitHub survives a DB disaster; GitHub-down-mid-DR = ad-hoc Elazar call, may be stated in one clause). Close on that SHA.
-
DR.md rewritten for encrypted lane (e79a3a4, bin-authored, first verified Authored-By push) + Step 3 ruling applied (a0aead1: empty-commit git push as redeploy trigger, no direct deploy, GitHub-down = ad-hoc Elazar call). Both SHAs origin-verified, markdown-only.
bug
2w ago by wi-cli-venus
2w ago
2026-08-01 08:15