Steam's beta overlay crashed Vulkan games, and Valve's own note records the fix
Valve's Steam client beta changelog of October 1 carries a single line about Vulkan: "Fixed crash when Vulkan games recreate their swapchain". Reports of games dying within seconds of launch had been arriving on Valve's own Linux tracker since 08:54 UTC on September 30.

Phasmophobia is one of the titles named in the reports filed on Valve's Linux tracker. Image: Kinetic Games
Valve posted that note on October 2 at 02:06 UTC and dated it October 1. The previous beta note is dated September 29 and went up on September 30 at 00:04 UTC, and the reports sit between the two.
The issue on Valve's own steam-for-linux tracker was closed on October 2. Its title is "Overlay Vulkan layer stack-overflows in VulkanSteamOverlayPresent and kills DELTARUNE (publicbeta 20260929221822)", and the opening report names the client build as 1790721607.
Valve names the fix but not the cause
Valve's note does not name a game, does not say which build introduced the crash and does not call it a regression. The only component it names is the Game Overlay, and that is the whole of Valve's account.
A swapchain is the set of image buffers a Vulkan game hands to the screen, and it is rebuilt whenever the window changes size or the game moves between windowed and full screen. Valve's wording puts the crash at that moment of rebuilding, and the opening report traces it to a stack overflow inside the overlay's renderer library on a frame presentation call.
The connection between the two builds comes from the people filing the reports, not from Valve. Two of them wrote that the problem was gone on build 1790904859, which is the one the October 1 note describes, and the issue was closed on that basis.
The reports name DELTARUNE, Cemu and Phasmophobia
The opening report describes DELTARUNE exiting a few seconds after its window appears, with or without the per-game overlay setting switched on. Another account reports the same behaviour from the Cemu 2.6 AppImage "as soon as Cemu tries to render the first frame".
Another account thinks Phasmophobia is hitting the same thing, crashing "100% of the time, on several different compat tools", and one more writes of "the same issue on every single game that uses proton". None of this is Valve's wording, and only Linux reports were filed, so there is nothing on the record about Windows clients.
What the reports agree on is that stopping the overlay's Vulkan layer from loading avoided the crash, one account doing it through the Vulkan loader's layer-disable variable and another with DISABLE_VK_LAYER_VALVE_steam_overlay_1. Switching the overlay off for the individual game was not enough: the opening report describes the crash happening whether or not that setting is on.
The same build carried a Steam Controller firmware fix
The October 1 note also lists a Steam Controller firmware change for Bluetooth BLE connections that "could disconnect repeatedly, especially on Steam Deck", a shorter connection time in Steam, and a fix for pairing failing over a puck connection.
Remote Play got the larger share of that build, including the change that raised Pyrowave's manual bitrate ceiling to 1 Gbit/s and reset everyone's manual figure. The overlay fix is one of the 16 lines in that note.
Valve's Vulkan housekeeping has not been confined to the client. On October 3 it told a Linux bug report that it had dropped the Vulkan extension requirement that was stopping Steam Link VR from starting. Both of the client builds here are beta-channel builds, which players have to opt into.