Skip to content

chore(recovery): retain the state after the AI training policy apply - #83

Merged
devantler merged 1 commit into
mainfrom
claude/zone-retain-ai-training
Nov 15, 2026
Merged

devantler merged 1 commit into
mainfrom
claude/zone-retain-ai-training

Conversation

@devantler

Copy link
Copy Markdown
Contributor

Why

The DNS workflow refuses every new run until the last apply's state is kept as the recovery copy. #82 has been applied.

What

Keeps the encrypted state from that apply (run 43702623125) in recovery/backend-source/. It decrypts with the independently held recovery key and matches the copy recovered on a fresh runner. Data only: no DNS, settings or code changes.

Part of #21

🤖 Generated with Claude Code

Run 43702623125 (source 23a0c22) set the zone's AI training crawler
policy to disabled, moving the state from serial 7 to 8 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 devantler left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Local review at b27af79. This is data only: recovery/backend-source/ is replaced by the after package of run 43702623125. It decrypts with the independent identity (VERIFIED scope=authenticated-files). Its state digest fa0ff89d equals the fresh-runner recovered copy. The lineage is unchanged, the serial goes 7 → 8, and the configuration digest is unchanged. check-recovery-package.sh passes. Clean.

🤖 Generated with Claude Code

@devantler
devantler marked this pull request as ready for review November 15, 2026 10:12
@devantler
devantler merged commit d06370d into main Nov 15, 2026
16 checks passed
@devantler
devantler deleted the claude/zone-retain-ai-training branch November 15, 2026 10:12
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