Floating mode leaves a late personal window floating
Pull request 16143, merged into quattro, refreshes floating-workspace exclusions when a personal window rule arrives after saved workspace modes. zihaomu wrote that the first matching window received the floating mode's size.
zihaomu wrote that a saved floating mode builds its opening rules from the float patterns already recorded, and that a later personal rule recorded a new pattern without refreshing those exclusions. He wrote that the first matching window received the mode's size, and that it became tiled when floating mode ended.
The pull request says the first matching window stays outside the floating mode's ownership, the same as later matching windows, and that ending floating mode leaves these windows floating.
zihaomu wrote that the comparison used an isolated configuration rather than a full installed Omarchy 4.5 session, and that confirmation in the reporter's complete configuration would be useful. He wrote that the patch does not establish a general fix for initial title-based size negotiation.