mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-16 05:41:16 +01:00
Section 22.1 of core-model.md: KDE and macOS refuse every message before the router's match while the focused window is not managed (handle_unmanaged_window_behaviour); Windows gates inside 18 functions. CommandHost gets a defaulted gate_message(&mut self, &SocketMessage) that lets everything through (the Windows form, its impl is untouched); the KDE and macOS impls call handle_unmanaged_window_behaviour and their routers call the hook where they called the method, so behaviour is identical per daemon. komorebi-core now depends on komorebi-protocol (for SocketMessage; Cargo.lock gains that one edge). This is the groundwork only: the router itself is still per daemon, because a shared router needs WindowManager<P> in core (see the struct-move analysis in core-model.md). No BEHAVIOUR change. Verified: KDE cargo test -p komorebi-linux 670 passed, 0 failed; fake-CC clippy -D warnings for the four macOS packages passes; cargo clippy -p komorebi-windows -p komorebi-core --all-targets -D warnings passes; tools/format-all --check clean. Not verified: KDE VM, macOS hand check (no behaviour change expected).