cosmic-files is the file manager. cosmic-files-applet is the desktop that shows your ~/Desktop. They're one
cargo workspace, and the applet depends on the app crate with a desktop-applet feature. The host build compiled
the component with cargo build --release --workspace, which feature-unifies desktop-applet onto the app
binary as well. So the file manager also ran the applet's output-event handler and created its own full-screen,
all-edges-anchored layer surface showing the Desktop folder: opening Files put a second, interactive copy of the
file view on the wallpaper, over the real window and behind everything else, and it followed the app across
workspaces.
Reported from a live machine on 26.10.11, reproduced in QEMU on 26.10.12 with a GL-enabled virtual GPU and
injected input, and root-caused by building the two halves together versus separately. They are two cargo
invocations now, -p cosmic-files then -p cosmic-files-applet, and the build fails if the app binary carries
applet code. A gate test keeps the component table honest.
It's a good example of why the Desktop components are built by our own script rather than "cargo build the workspace": cargo's feature resolution is a sensible default for a library and a wrong default for shipping two different programs out of one tree.