Repository navigation
docs: record the alpha.6 drift-guidance fix - #7
Merged
Merged
Conversation
The guidance change landed inside 143f8c9 ("feat: recover from CC Switch configs and track asset snapshots") without a changelog entry. Record it: `status` now names `capture` for drift that carries no clobber fingerprint and offers `repair` only as the deliberate revert, and `doctor` reports the same distinction instead of a bare "no clobber fingerprint". Verified: cargo fmt --all -- --check, cargo clippy --workspace --all-targets -D warnings, cargo test --workspace (37 tests).
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.
What
Adds the missing changelog entry for the drift-guidance change that shipped inside
143f8c9(CC Switch recovery + asset coverage) as part of the v26.0-Alpha.6 line.Why
The project rule is that documents stay consistent with the code. That commit changed the
user-facing guidance but only described
ccswitch recover, asset-coverage tracking, andthe WMI launcher.
The behaviour being recorded
status: drift with a clobber fingerprint →run keepmyconfig repair.status: drift without a clobber fingerprint (a user or Codex edit) → namecapturefirst, offerrepaironly as the deliberate revert.doctor: reports the same distinction instead of a bare "no clobber fingerprint".repairmerges unconditionally, so the previous wording invited reverting a change theuser meant to keep. Covered by
status_guides_capture_for_a_benign_editand the extendedstatus_reports_clobber_then_health.Verification
Docs only; no behaviour change in this PR.