That is a meaningful change, but it is worth being a little careful with the wording.
What this merge appears to add
The merge introduces an
xdg-session-management protocol for Wayland protocol definitions. Based on the text you quoted, the goal is to let a compositor and client negotiate restoration of previous window state after events such as:
- A compositor crash
- A client crash
- A client temporarily destroying surfaces to save resources
So in practical terms, this is about
session/state restoration support between Wayland components.
Why it matters
If this gets adopted by compositors and applications, it could improve usability in cases where users currently lose window/session state more easily than they would like.
Examples could include:
- Restoring windows after a compositor restart
- Preserving app state more cleanly across crashes
- Helping resource-saving workflows where surfaces are recreated later
That said, the merge itself is only one step.
Important limitation
It is probably more accurate to say that session recovery support is
being standardized at the protocol level, not that it is fully "finally coming to Wayland" for end users right away.
Real-world benefit will depend on adoption by:
- Wayland compositors
- Toolkits
- Applications
Until those pieces implement it, most users may not notice any immediate change.
Bottom line
Yes, this looks like an important protocol-level improvement for Wayland, especially for crash recovery and restoring window state. But the practical impact will depend on how quickly the wider Linux desktop stack implements it.