**System details:** Intel Core Ultra 5 225U, Intel Arrow Lake-U graphics (ThinkPad E14 Gen 7), omarchy-dev 4.0.0.r6720.g8e02fc8, Hyprland 0.56.2, Ghostty

> **How this report was produced.** I investigated this with Claude Code, using `hyprctl` state captured while the screensaver was running and the upstream commit history. I reviewed it before filing.

## What's wrong

The status bar stays visible above the screensaver. A single fullscreen monitor and no open bar panel are enough to see it. Screenshot attached (my bar is set to `transparent: true`, so the effect shows through it; with the default opaque bar the bar just sits on top).

## Steps to reproduce

1. With no bar panel open, run `omarchy-launch-screensaver force` (or wait for the idle timeout).
2. The bar is still visible along the top edge, drawn over the screensaver.

State captured while the screensaver was running:

```
$ hyprctl clients -j | jq -c '.[] | select(.class=="org.omarchy.screensaver") | {workspace: .workspace.name, fullscreen, floating}'
{"workspace":"special:screensaver-eDP-1","fullscreen":2,"floating":true}

$ hyprctl layers -j | jq -c '.["eDP-1"].levels | to_entries[] | {level: .key, ns: [.value[].namespace]}'
{"level":"0","ns":["omarchy-background"]}
{"level":"1","ns":[...]}
{"level":"2","ns":["omarchy-bar"]}
{"level":"3","ns":[...]}
```

The screensaver window is fullscreen, and the bar is still on the `top` layer (level 2) above it.

## Cause

#3284 (bf44355a9, merged 2026-09-27) moved the screensaver from the active workspace to its own special workspace, `special:screensaver-<monitor>`, so it would stop taking fullscreen away from the user's window. The cause is that fullscreen behaves differently on special workspaces:

- A fullscreen window on a regular workspace covers the `top` layer, which is why Super+F hides the bar, and why the screensaver used to cover it.
- A special workspace is drawn below the `top` layer even when its window is fullscreen (so a bar stays visible over the scratchpad). The fullscreen screensaver therefore no longer covers the bar.

#3284 doesn't mention the bar, so this looks like a side effect rather than something intended.

## Related

- #14326 and #14226 cover an open bar *panel* drawn over the screensaver. #14226 notes that "the open panel still draws above the screensaver… a separate layer-order question". This report is the general case: no panel needs to be open, so every screensaver run is affected.

## Possible direction

The bar could hide itself, or drop below windows, while an `org.omarchy.screensaver` window is mapped. That shouldn't go through the persistent `bar-off` toggle, which belongs to the user. Moving the screensaver back to the regular workspace would bring back #3218.