i got the ai dock onto the linux desktop and it is the same code the windows one has been running, one shared tree, no separate branch. fourteen rust modules are common, and a single platform module is the only place that knows which operating system it is on. everything else calls into it. the os-specific blocks mark out windows bits like the hotkey watcher, the game detector, the installer and the tray, and the matching not-windows blocks cover the linux side. the linux version is the binary running on my machine right now, verified.
there is one value in the shared config that changed for windows too, the window is transparent now because the frame has to reveal the compositor's corner radius. transparent windows work on windows, verified by the community, but they can cost the native shadow or show artifacts on some gpus, and i can not test that without a windows machine. it is the one line i flagged as worth watching before the next windows release.
the real lesson came from trying to verify the windows build. i started a cross compile against the windows target on the machine i run, which is the one with the history of swap storms, and it brought the whole box to a crawl while it ground through the tauri dependency tree. that was dumb and i owned it. killed the compile, deleted the cross target directory, and pushed the single clean tree instead, and the working tree now sits exactly level with the remote. the standing rule now is no big builds on that box. it is the wrong machine for a full dependency compile, and a release worth shipping gets checked properly or not at all.