## What happens

A newly added plugin never gets instantiated in the bar, and its IPC handler is never registered —
the pre-edit (or pre-clone) instance keeps serving the target. Only a full shell restart picks the
plugin up.

Observed with `omarchy plugin clone omarchy.bluetooth` (which rewrites `bar.layout.right` from
`omarchy.bluetooth` to `eelco.bluetooth`), then editing the clone's `Panel.qml`:

- `omarchy-plugin-list` / `omarchy-shell shell listPlugins` both report the clone **enabled**, and
  the bar knows the entry, but
  `omarchy-shell shell debugBarGeometry` reports the slot as
  `{'id': 'eelco.bluetooth', 'width': 0, 'height': 0, 'visible': False, 'itemVisible': False}` —
  the widget paints nothing at all.
- `omarchy-shell shell call eelco.bluetooth toggleBluetooth ""` → `unknown` (not loaded).
- The `omarchy.bluetooth` IPC target still exists, but it is served by the **pre-edit** instance:
  * a function I added to the clone's `IpcHandler` never appeared (`Function not found.` for the old
    target, `Target not found.` for a renamed probe target),
  * a `console.log()` I added to the clone's `toggleBluetooth()` never fired,
  * the old code's behaviour is what still ran.
- Neither `omarchy-shell shell rescanPlugins` nor touching the files helps, although the shell does
  log `Local plugin changed, reloading: eelco.bluetooth` each time.
- `omarchy restart shell` fixes it immediately: the slot becomes
  `width: 23, visible: True, itemVisible: True` and the edited handler is the live one.

Possibly related: right at clone time the shell logs duplicate-handler warnings for several other
targets, i.e. the reload path does create new panel instances while the previous ones keep their IPC
registrations:

```
WARN scene: QML IpcHandler at .../hass/Panel.qml[173:3]: Handler was registered but will not be used because another handler is registered for target hass
WARN scene: QML IpcHandler at .../agents/Panel.qml[327:3]: ... target omarchy.agents
WARN scene: QML IpcHandler at .../panels/network/Panel.qml[210:3]: ... target omarchy.network
WARN scene: QML IpcHandler at @Ui/Panel.qml[48:3]: ... target omarchy.audio
WARN scene: QML IpcHandler at .../panels/monitor/Panel.qml[220:3]: ... target omarchy.monitor
WARN scene: QML IpcHandler at .../panels/power/Panel.qml[177:3]: ... target omarchy.power
```

(There was no such warning for `omarchy.bluetooth`, which is consistent with the new instance never
being created at all.)

## Expected

Adding a plugin with `omarchy plugin clone` (which enables it) instantiates its bar widget and
registers its IPC handler — or, failing that, `shell rescanPlugins` / a file change does.

## Steps to reproduce

1. `omarchy plugin clone omarchy.bluetooth`
2. Add something identifiable to the clone's `IpcHandler`, e.g.
   `function ping(): string { return "clone" }`, to
   `~/.config/omarchy/plugins/<user>.bluetooth/Panel.qml`.
3. `omarchy-shell shell rescanPlugins && sleep 2`
4. `omarchy-shell shell debugBarGeometry` → the clone's slot has `width: 0`, `visible: false`.
5. `omarchy-shell <user>.bluetooth ping` → `Target not found.` (handler never registered), while the
   old target still answers with the old function list.
6. `omarchy restart shell` → the slot becomes visible with a real width and the new handler works.

## System

- Omarchy 4.0.3-1, Omarchy (Arch), kernel 7.1.8-arch1-3
- quickshell 0.3.0 (quickshell-git 0.3.0.r20.g28771c7-3, AUR)
- Hyprland 0.56.2, qt6-base 6.11.2-3
- Intel i3-4030U / Haswell-ULT
- Shell env (from `omarchy-launch-shell`): `QS_DISABLE_FILE_WATCHER=1 QS_NO_RELOAD_POPUP=1`