Skip to content

Continue verified home backup purges on their provider deadline - #382

Merged
Chris Eckert (ceckert) merged 1 commit into
mainfrom
codex/continue-restored-backup-purge
Nov 21, 2026
Merged

Chris Eckert (ceckert) merged 1 commit into
mainfrom
codex/continue-restored-backup-purge

Conversation

@ceckert

Copy link
Copy Markdown
Member

A normal TEST restore activated cleanly with the original home and enabled schedule. After authorizing backup deletion, the successful provider progress response was classified as a third transient failure and delayed the next confirmation by 480 seconds.

Use the durable operation watch timer to resume the authenticated backup release after 30 seconds when the provider reports that deletion is still converging. Keep the same snapshot custody until both the live and recoverable copies are absent. Readiness checks, ownership proof, and error handling keep their existing policy.

The regression proves repeated live and recoverable deletion progress does not spend failure attempts or extend the wait. Fake-clock coverage proves the exact due wake after a watch resync. Local typecheck, scoped lint, and 219 focused tests passed.

Signed-off-by: Chris Eckert <christopher.k.eckert@gmail.com>
@ceckert
Chris Eckert (ceckert) merged commit 465a020 into main Nov 21, 2026
16 checks passed
@ceckert
Chris Eckert (ceckert) deleted the codex/continue-restored-backup-purge branch November 21, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant