Skip to content

Bring the docs in line with 3.4.0 - #20

Merged
BiosSystem merged 1 commit into
masterfrom
feature/docs-3.4.0
Sep 6, 2026
Merged

Bring the docs in line with 3.4.0#20
BiosSystem merged 1 commit into
masterfrom
feature/docs-3.4.0

Conversation

@BiosSystem

Copy link
Copy Markdown
Owner

Two documented things did not exist.

docs/Execution-Architecture.md told users to restore with:

reg import "%TEMP%\WinSwift_Backup_<timestamp>.reg"

Backups are JSON, written to Backups\WinSwift-RegistryBackup-<timestamp>.json. Nothing in the codebase has ever written to that %TEMP% path. The same doc, the README comparison table, and the UPSTREAM capability matrix all advertised a -Revert parameter that has never been declared in WinSwift.ps1.

Replaced with what the code actually does: automatic rollback, manual restore through Load-RegistryBackupFromFile + Restore-RegistryBackupState, and -Undo for individual features.

Other corrections:

  • README had a section titled "State Snapshot, Verification and Rollback Architecture" that described backup and verification but no rollback. Added the rollback stage, including the app-removal exclusion and the -SkipRegistryBackup interaction.
  • Added an exit code table covering 3 (rolled back) and 4 (rollback failed). Both were undocumented outside the changelog.
  • Flow diagram now shows the failure branch rather than a straight line to the summary.
  • -Undo and -NoAutoRollback documented in the README and wiki.
  • WIKI execution flow gained the rollback step, and its "revert scripts" claim now points at -Undo.
  • SECURITY.md moves the supported line to 3.4.x, marks 3.3.x unsupported with the reason, and adds sections for elevation enforcement and automatic rollback.

Docs only. Static validation passes (110 files).

Two documented things did not exist. The architecture doc told users to
restore with reg import from %TEMP%\WinSwift_Backup_<timestamp>.reg, but
backups are JSON under Backups\WinSwift-RegistryBackup-<timestamp>.json.
It also documented a -Revert parameter that has never been declared, and
the README and upstream matrix both advertised it.

Replaced with what the code does: the automatic rollback path, the
manual restore through Load-RegistryBackupFromFile and
Restore-RegistryBackupState, and -Undo for individual features.

Also documents the rollback stage in the README, which had a section
titled "Rollback Architecture" describing only backup and verification,
adds the exit code table covering 3 and 4, updates the flow diagram to
show the failure branch, and records -Undo and -NoAutoRollback.

SECURITY.md moves the supported line to 3.4.x and marks 3.3.x
unsupported, noting the elevation guard that printed its warning and
then continued into the apply pipeline.
@BiosSystem
BiosSystem merged commit 22662d5 into master Sep 6, 2026
1 check passed
@BiosSystem
BiosSystem deleted the feature/docs-3.4.0 branch September 6, 2026 19:48
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