## Summary

After upgrading Omarchy from **4.0.2-1** to **4.0.3-1**, popups/panels opened from
**third-party/user-installed bar plugins** become stuck overlays. Once a plugin popup is
open it cannot be dismissed: Escape does nothing, clicking outside does nothing, and
clicking the trigger icon again does nothing. The overlay stays visible above normal
windows until logout/reboot. Restarting the Omarchy shell clears it because the overlay is
owned by the Quickshell `omarchy-shell` process.

Built-in first-party panels (network/audio/power/etc.) do **not** appear to be affected.

## Steps to reproduce

1. Upgrade from Omarchy 4.0.2-1 to 4.0.3-1.
2. Have a third-party/user-installed bar plugin that opens a popup/panel enabled, for
   example the calendar-clock clone `matteodevenuto.clock`.
3. Start a fresh session, or run `omarchy restart shell` after the upgrade.
4. Click the plugin's bar icon to open its popup.
5. Try dismissing it with Escape, by clicking outside, and by clicking the icon again.

## Expected behavior

The popup dismisses normally with Escape / outside click / re-clicking the trigger, like
first-party panels.

## Actual behavior

The popup opens and remains mapped above normal windows. Escape, outside clicks, and
re-clicking the trigger do not close it. The only reliable way found to clear it is logging
out/rebooting. This did not happen on 4.0.2-1.

## Suspected cause

4.0.3 changed `shell/plugins/bar/Bar.qml` `injectProps()` so third-party bar widgets
receive a new scoped `PluginBarApi` instead of the real `Bar` root. The popup/panel
plumbing and third-party host widgets were written against the old bar surface; APIs the
facade does not expose are silently missing, which can leave a `KeyboardPanel`/`Panel`
open with broken dismissal/coordination.

A fresh 4.0.3-1 session already logs QML compatibility errors from installed
third-party widgets:

```text
Sep 09 19:12:11 omarchy-shell[1085]: WARN scene: @plugins/bar/Bar.qml[2004:-1]: TypeError: Cannot assign to read-only property "moduleName"
Sep 09 19:12:18 omarchy-shell[1085]: WARN scene: QML Connections at file:///home/lone_wolf/.config/omarchy/plugins/lone_wolf.plugin-hider/PluginHider.qml[72:9]: Detected function "onBarConfigChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
Sep 09 19:12:20 omarchy-shell[1085]: WARN scene: file:///home/lone_wolf/.config/omarchy/plugins/jrmmhm.pocket/BarWidget.qml[89:-1]: TypeError: Cannot read property 'length' of undefined
Sep 09 19:12:20 omarchy-shell[1085]: WARN scene: file:///home/lone_wolf/.config/omarchy/plugins/jrmmhm.pocket/BarWidget.qml[126:-1]: TypeError: Cannot read property 'length' of undefined
```

## Related issues

This looks like part of the 4.0.2 → 4.0.3 third-party plugin API regression cluster:

- #10863 — `publicPluginManifest()` strips `__sourceDir`, breaking third-party plugins that locate their own files
- #10888 — no way for a third-party plugin to enumerate plugins
- #10907 — third-party plugins lost read access to their own shell.json entry
- #10908 — third-party menu clones get null `appLibrary`
- #10929 — `PluginBarApi` drops the bar drag API
- #10941 — bar widget popups leave a stale ghost frame on screen after closing (different symptom, same 4.0.3 popup area)

## Workaround

```bash
omarchy restart shell
```

clears the stuck overlay without logging out (not yet tested by the reporter while stuck;
logging out was used previously).

## System

| | |
|---|---|
| Omarchy | 4.0.3-1 (broken; 4.0.2-1 worked) |
| Quickshell | 0.3.1-1 |
| Hyprland | 0.56.2 |
| Kernel | 7.2.3-arch1-3 |
| GPU | Intel UHD Graphics (Tiger Lake), i915 |
| Hardware | ASUS P1412CEA laptop |
| Display | Single monitor, eDP-1 |