Skip to content
Search PyroSoft

Bourbon 26 development journal · Part 9 of 10

The audit that put saves and reset safety first

Protecting newer environments before broadening the feature work.

By Mike Rodriguez2 min readDevelopment work: Oct 19, 2026Updated New

Adding a new launch route also means teaching the rest of the app how to preserve it. The October 19 audit found an example we needed to address immediately: Complete Reset's existing retention rules didn't fully cover the newer SteamOS and native Steam environments.

With the default keep-games and keep-saves choices, the audited version could still remove a guest disk or private-prefix saves from those newer routes. The response was to put their full environments into the preservation contract and add activity checks before teardown. If an integration was running, changed or couldn't be verified safely, reset needed to stop before destructive work.

The remediation kept disks, authentication, providers and recovery records in place. The reset screen explained that choice, and unsafe relocation combinations were contained while the complete transaction path was developed. The updated audit records those reset fixes as released in 26.10.19.1.

Ownership verification was another priority. Different purchase methods needed consistent decisions, and a provider outage couldn't be treated as proof that someone didn't own Bourbon. The following changes bounded requests, handled incomplete responses as retryable failures and preserved the existing state during outages. The audit records that batch as released in 26.10.19.2.

There were updater and focus fixes in the same day's work, but I wanted the safety story to have its own chapter. We found a real gap after earlier tests had passed, added cases that exercised that gap, and kept the broader audit open.

That is useful progress even though it isn't a flashy new feature. Your installed games and saves should be the starting point for recovery. A reset or repair needs to earn the right to touch them through explicit ownership and preservation checks.

Bourbon 26 development journal

View the journal

Live10 entries so farUpdated New (10 entries updated in the last 14 days)

  1. Part 1Bourbon 26: choosing the right way to playDevelopment work: Jul 31, 2026Updated , new
  2. Part 2When the menus work but the game world is blackDevelopment work: Aug 17, 2026Updated , new
  3. Part 3Making setup and repair less disruptiveDevelopment work: Aug 30 – Sep 6, 2026Updated , new
  4. Part 4Smart Play starts figuring out unfamiliar gamesDevelopment work: Sep 29 – 30, 2026Updated , new
  5. Part 5Activation, installers and knowing which program we launchedDevelopment work: Oct 2 – 8, 2026Updated , new
  6. Part 6Giving SteamOS its own place in BourbonDevelopment work: Oct 9 – 12, 2026Updated , new
  7. Part 7Keeping older tools and newer Steam clients in their own lanesDevelopment work: Oct 13 – 16, 2026Updated , new
  8. Part 8Native Steam integration and a library you can use from the couchDevelopment work: Oct 17 – 18, 2026Updated , new
  9. Part 9The audit that put saves and reset safety firstDevelopment work: Oct 19, 2026Updated , new
  10. Part 10Moving Bourbon safely, then making the verification fasterDevelopment work: Oct 19 – 20, 2026New

Arrow keys move through the results, Enter opens one, Command or Control with Enter opens it in a new tab. Tab and Shift+Tab change which kind of results are shown.