# Moving Bourbon safely, then making the verification faster

> Qualified candidate work and a later storage improvement that still needs its own gate.

Canonical page: https://pyrosoft.pro/blog/moving-bourbon-safely-then-making-the-verification-faster

Live development journal; no publication date.
Work period: 2026-10-19 to 2026-10-20
Updated: 2026-10-20

Moving a game library sounds simple until the app also owns a guest disk, private runtime, saved credentials and paths another application has stored. The next Bourbon pass connected those pieces to shared storage and lifecycle rules, with recovery copies and verification built into the move.

The October 20 audit update records Candidate05 completing 351 required groups with no failed groups. Four individual opt-in or platform subtests were skipped. Its exact private upgrade test started from production 26.10.19.2, and the M2 acceptance included native Steam focus, input, relaunch, Stop and restore. The moved SteamOS environment rendered, accepted input, suspended, resumed and powered off cleanly.

Those are useful results for that candidate. Physical controller testing and the original affected M5 Max/macOS 27 report remained separate gaps. The work record doesn't turn an M2 success into a universal fix or describe this private candidate as a new public release.

A later cleanup exposed another practical issue: checking extended attributes could launch an external process for every file. The newest source added a native macOS reader, keeping the same digest representation and conservative error handling. On the recorded 7,477-entry archival corpus, it produced the same manifest as the prior command path in 9.5 seconds.

That last change came after Candidate05's qualification. It needs a fresh full candidate and gate, so I'm leaving it clearly marked as development work in this entry.

The direction is encouraging: safer moves, more dependable session focus and less overhead during verification. The next step is to qualify the exact newer artifact and close the remaining hardware and input gaps, while preserving the recovery behavior that made these moves reviewable in the first place.