KeepMyConfig v26.0-Alpha.4

KeepMyConfig v26.0-Alpha.4

Fixes the failure that followed the Codex 0.147 update and makes protection survive future updates and reboots.

Root causes found

1. No persistence. The manually started watch process did not survive the update/reboot; neither the Startup folder nor Task Scheduler had a KeepMyConfig entry, so the 03:09 rewrite of config.toml went unnoticed.
2. Detection blind spot. The Codex updater preserved model/model_provider, so the diff scored 3 against the balanced threshold of 4 (12 protected paths removed, one new app key added) and would have been treated as a user edit.

Added

• autostart install|status|uninstall (Windows): registers KeepMyConfig-Watch (logon daemon) and KeepMyConfig-Check (periodic one-shot repair, 5-minute default) with the current-user Task Scheduler and starts both immediately.
• doctor now reports autostart state.
• Codex-update-aware detection: a changed BROWSER_USE_CODEX_APP_VERSION plus protected removals forces a clobber; removing 3+ complete mcp_servers/plugins/marketplaces/projects entries adds clobber weight.

Verified

• Real incident replay with the actual damaged backup: Clobber score 6 with 7 complete entries removed and app version 26.930.31428 -> 26.930.31730; watch --once restored all 12 paths and kept the new app build.
• 33 tests passing (18 core unit + 11 workflow + 3 CLI + 1 autostart); clippy -D warnings and fmt --check clean.
• CI green on Windows and Linux for commit 98782b6.

Build

• Commit: 98782b6
• Target: x86_64-pc-windows-msvc, Rust stable
• Crate version: 0.1.0-alpha.4
• Asset: keepmyconfig-x86_64-pc-windows-msvc.zip

Upgrade

Replace keepmyconfig.exe, then run:

keepmyconfig status
keepmyconfig autostart install

Alpha notice: CLI flags and policy defaults may change before v26.0. CC Switch database writes remain opt-in (--apply), dry-run by default, and always preceded by a backup.