Repository navigation
chore(recovery): retain the state after the apex apply - #80
Merged
Merged
Conversation
Run 43679002478 (source 34cd9c5) edited the apex CNAME in place to www.devantler.tech and dropped the one-time www handover record that external-dns had already removed. The state moved from serial 5 to 6 on the same lineage with the configuration unchanged. The `after` and fresh-runner `recovered` packages authenticate with the independent identity and carry the same state digest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
devantler
commented
Nov 15, 2026
devantler
left a comment
Contributor
Author
There was a problem hiding this comment.
Local review at d1c4097. This is data only: recovery/backend-source/ is replaced by the after package of run 43679002478. It decrypts with the independent identity (VERIFIED scope=authenticated-files). Its state digest 677c495d equals the fresh-runner recovered package. The lineage is unchanged, the serial goes 5 → 6, and the configuration digest is unchanged. check-recovery-package.sh and scripts/test.sh pass (21 suites). Clean.
🤖 Generated with Claude Code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The DNS workflow refuses every new run until the state from the last apply has been kept as the recovery copy. The apex move (#79) has been applied.
What
Keeps the encrypted state from that apply (run 43679002478) in
recovery/backend-source/. It decrypts with the independently held recovery key and matches the copy recovered on a fresh runner. The configuration is unchanged, so no secret changes. Data only: no DNS or code changes.Part of #21
🤖 Generated with Claude Code