**System details:** Omarchy `quattro` @ 7488eade (post-4.0.0), QEMU/KVM VM, Hyprland session. Found by an automated QA pass; reproduced on a disposable worker VM.

`omarchy plugin clone` builds the new plugin id from `$USER`, with no check that the result avoids the reserved `omarchy.` namespace:

```bash
new_id="${USER:-$(id -un)}.${source_id#omarchy.}"
```

(`bin/omarchy-plugin-clone:131`)

The default user on the Omarchy ISO is literally `omarchy` — the name Omarchy's own docs use — so for that user every clone produces an id like `omarchy.clock`, which `PluginRegistry` then rejects:

```js
for (var tk in thirdParty) {
  if (firstParty[tk] || String(tk).indexOf("omarchy.") === 0) {
    console.warn("PluginRegistry: plugin " + tk
      + " rejected: id is reserved for first-party Omarchy plugins")
    continue
  }
```

(`shell/services/PluginRegistry.qml:602-608`)

The CLI reports success, the built-in keeps rendering, and every edit the user makes to their clone is ignored forever:

```
$ whoami
omarchy
$ omarchy-plugin-clone omarchy.clock
Cloned omarchy.clock to /home/omarchy/.config/omarchy/plugins/omarchy.clock and switched to omarchy.clock

$ qs log -p $OMARCHY_PATH/shell | grep reserved
WARN qml: PluginRegistry: plugin omarchy.clock rejected: id is reserved for first-party Omarchy plugins

$ omarchy-shell shell listPlugins | grep clock
{'id': 'omarchy.clock', 'name': 'Clock', 'firstParty': True, 'clonedFrom': ''}   # still the built-in

$ grep '"name"' ~/.config/omarchy/plugins/omarchy.clock/manifest.json
  "name": "My Clock",                 # the clone exists on disk and is never loaded
```

Rejecting or re-prefixing an id that starts with `omarchy.` in `omarchy-plugin-clone` closes it.

---

**Correction, after an independent review of this report:**

Narrower than filed. This needs the effective `$USER` to be exactly `omarchy`, which is an explicitly configured account name rather than the default population of ISO installations -- the worker this was found on had that username set by its own provisioning, not by Omarchy. Where it does apply, the clone is silently ignored forever and the CLI still reports success.