Skip to content

docs: record the alpha.6 drift-guidance fix - #7

Merged
StarsailsClover merged 1 commit into
mainfrom
docs/alpha6-drift-guidance
Oct 5, 2026
Merged

StarsailsClover merged 1 commit into
mainfrom
docs/alpha6-drift-guidance

Conversation

@StarsailsClover

Copy link
Copy Markdown
Member

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, and
the 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) → name
    capture first, offer repair only as the deliberate revert.
  • doctor: reports the same distinction instead of a bare "no clobber fingerprint".

repair merges unconditionally, so the previous wording invited reverting a change the
user meant to keep. Covered by status_guides_capture_for_a_benign_edit and the extended
status_reports_clobber_then_health.

Verification

cargo fmt --all -- --check                         -> pass
cargo clippy --workspace --all-targets -D warnings -> pass
cargo test --workspace                             -> 37 passed / 0 failed

Docs only; no behaviour change in this PR.

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).
@StarsailsClover
StarsailsClover merged commit 5458e5f into main Oct 5, 2026
2 checks passed
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