## Summary

If a bar-widget panel's `close()` throws, the shell is left with a full-screen layer-shell overlay that is still mapped and still owns a full-screen input region. Every click on the desktop lands on that surface and does nothing, the keyboard dismissal path is wedged the same way, and no IPC call can recover it. The only way out is restarting the shell — which a user whose desktop just stopped responding to clicks has no obvious way to discover.

A bug anywhere in one plugin's `close()` therefore escalates into a desktop-wide input lockout.

## Why

`Ui/KeyboardPanel.qml:69`:

```qml
function close() {
  if (owner && "close" in owner) owner.close()
  else root.open = false
}
```

The delegation is unguarded. If `owner.close()` throws, `root.open` is never set to `false`, and `root.open` is what everything else keys off:

- `Ui/KeyboardPanel.qml:81` — `visible: open || card.opacity > 0 || popoutSwitching`, so the window stays mapped.
- `Ui/KeyboardPanel.qml:124` — `mask: Region { width: root.screenW; height: root.screenH }`, so the mapped surface keeps hit-testing the whole output. Input is captured by the compositor-side region regardless of whether the QML `MouseArea` is enabled, so there is no click-through.
- `Ui/KeyboardPanel.qml:331` — the outside-click handler calls `root.close()`, which re-enters the same throwing path on every subsequent click.

Every other dismissal route funnels into the same function:

- Esc / key handling: the panel's `PanelKeyCatcher.onCloseRequested` calls the same owner `close()`.
- `omarchy-shell <target> close` and `omarchy-shell shell hide <id>`: `shell.qml:1192` `hide()` calls `bar.hideBarWidget(id)`, which calls the widget's `close()`.

So the surface that is blocking input can only be unmapped by code that is already broken.

## Steps to reproduce

1. `omarchy plugin clone omarchy.clock`
2. In the clone's `Panel.qml`, make `close()` throw on its first line:
   ```qml
   function close() {
     throw new Error("boom")
     ...
   }
   ```
3. `omarchy restart shell`
4. Click the clock in the bar to open the calendar.
5. Click anywhere else on the desktop.

Observed: nothing is clickable anywhere on any output. `hyprctl layers` shows the overlay still mapped at full size:

```
Layer level 3 (overlay):
    Layer 6553f5a77ab0: xywh: 0 0 3840 1080, a: 1, namespace: omarchy-keyboard-panel
```

`omarchy-shell omarchy.clock close` returns successfully and the layer stays mapped. Only `omarchy restart shell` clears it.

Expected: a throwing plugin degrades to "this panel misbehaves", not "the desktop stops accepting input".

## How I hit this for real

Not hypothetical — this is how I found it. A plugin cloned from `omarchy.clock` before an update kept the old line

```qml
root.bar.centerHoverRevealSuppressed = value
```

which the bar has since turned into a read-only property with a setter function. The clone's `close()` calls that helper on its first line, so every close threw before reaching `controller.hide()`:

```
WARN scene: file:///home/<user>/.config/omarchy/plugins/<id>.clock/Panel.qml[119:-1]:
TypeError: Cannot assign to read-only property "centerHoverRevealSuppressed"
```

Nothing on screen indicated a plugin error; the desktop simply stopped responding to clicks whenever the calendar was opened. Since `omarchy plugin clone` and `omarchy plugin add <git-url>` are both supported user-facing workflows, plugin code drifting out of sync with the shell API is an expected condition rather than an edge case.

## Suggested fix

Guard the delegation so a throwing owner cannot hold the surface open:

```qml
function close() {
  try {
    if (owner && "close" in owner) {
      owner.close()
      return
    }
  } catch (e) {
    console.warn("KeyboardPanel: owner close() threw, forcing close:", e)
  }
  root.open = false
}
```

Worth considering more broadly, since the same shape appears elsewhere: any unguarded call into plugin code from a path that owns compositor-level input (`open()`, `closeForPopoutSwitch()`, the popout coordinator) can wedge the shell the same way. A plugin exception should never be able to leave an input-grabbing surface mapped.

## System

| | |
|---|---|
| Omarchy | 4.0.4-1 |
| Kernel | 7.2.5-3-omarchy |
| CPU | Intel Core i7-6820HQ |
| GPU | Intel HD Graphics 530 (Skylake-H GT2) |
| Hyprland | 0.56.2 |
| Quickshell | 0.3.1 (Arch) |
| Display | 3840x1080 @ 60Hz, scale 1 |

Related: #13381 (also in the clock panel, unrelated cause).