### What happened

`shell/README.md` documents two ways for plugin code under
`~/.config/omarchy/plugins/` to take effect in the running shell:

> Saving a file anywhere under `~/.config/omarchy/plugins/` reloads plugin code
> automatically; `omarchy-shell shell rescanPlugins` remains available to force a reload.

Neither works here. The panel keeps rendering the previous code until
`omarchy restart shell`.

The file watcher itself is fine — saving the file logs the reload:

```
DEBUG qml: Local plugin changed, reloading: <user>.monitor
```

…and the plugin registry rescans afterwards (the usual `service-ready` and
handler-registration lines follow). The QML that is actually rendered does not
change.

### Steps to reproduce

1. `omarchy plugin clone omarchy.monitor`
2. In `~/.config/omarchy/plugins/<user>.monitor/Panel.qml`, change the panel
   heading (line 611) from `text: "Display"` to `text: "Display MARKER-A"` and save.
3. Open the panel (`SUPER + CTRL + D`) — heading still reads **Display**.
4. `omarchy-shell shell rescanPlugins`, reopen — still **Display**.
5. `omarchy restart shell`, reopen — now reads **Display MARKER-A**.

Steps 3 and 4 are the bug; step 5 is the workaround.

### Why this one bites harder than a stale heading

The same staleness applies to `omarchy plugin clone` itself. After cloning,
every tool reports the clone as the active plugin:

```
$ omarchy plugin list
omarchy.monitor      disabled  first-party  bar-widget  Display
<user>.monitor       enabled   third-party  bar-widget  My Display
```

…while the shell goes on executing the built-in component. Editing the clone
appears to have no effect, and there is nothing in the UI or the CLI output
pointing at a restart. I spent a while re-checking a patch that had been
correct all along before a marker string showed me which copy was live.

### Possible cause

Worth checking rather than a diagnosis — `finishPluginReload()` in
`shell/shell.qml:752` clears the component cache behind a feature test:

```qml
if (typeof Qt.clearComponentCache === "function") Qt.clearComponentCache()
```

If `Qt.clearComponentCache` is not exposed in Quickshell's QML environment,
that test fails silently and `pluginRegistry.rescan()` re-instantiates the
components from cache — which matches the symptom exactly: the reload runs
end to end, and the old code survives it. `~/.cache/quickshell/qmlcache/` may
be worth a look in the same breath.

### System

- Omarchy 4.0.2-1
- Hyprland 0.56.2
- Intel Core i7-12700H / NVIDIA RTX 3070 Ti Laptop GPU

### Related

Found while patching the display panel locally for #10086.