### What is wrong?

Every command shipped by the `omarchy-settings` package is unreachable through
the `omarchy <group> <action>` dispatcher, even though the binaries are
installed, executable, and carry correct dispatcher metadata:

```
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.

$ omarchy-debug --no-sudo --print     # same binary, called directly
Date: Mon Aug 31 03:53:19 PM CEST 2026
Hostname: omarchy
...                                    # works, exit 0
```

They also do not appear in `omarchy commands --all`.

### Root cause

The dispatcher discovers commands by globbing its own bin directory
(`/usr/bin/omarchy:334`):

```bash
for file in "$OMARCHY_BIN_DIR/$binary"-*; do
```

Binaries from the `omarchy` package are symlinked into that directory; those
from `omarchy-settings` are not:

```
omarchy-pkg-add   (omarchy)           /usr/share/omarchy/bin/omarchy-pkg-add -> /usr/bin/omarchy-pkg-add
omarchy-debug     (omarchy-settings)  no entry in /usr/share/omarchy/bin
```

So the dispatcher never sees them. This is not a missing or corrupt file —
`pacman -Qkk omarchy` reports 1678 files, 0 altered, and the binaries are
present and annotated correctly, e.g. `/usr/bin/omarchy-debug` begins:

```bash
# omarchy:summary=Print debugging information
# omarchy:args=[--no-sudo] [--print]
# omarchy:requires-sudo=true
```

### Affected commands

All three binaries in `omarchy-settings`:

| Command | Summary (from its own metadata) |
| --- | --- |
| `omarchy-debug` | Print debugging information |
| `omarchy-debug-idle` | Show idle, screensaver, and lock diagnostics |
| `omarchy-upload-log` | Upload logs to logs.omarchy.org |

### Why this matters more than it looks

These are exactly the diagnostic commands the contributing docs instruct users
to run when filing a bug report, so the failure is self-concealing: the tooling
for reporting problems is the tooling that is broken. `omarchy-debug-idle`
("idle, screensaver, and lock diagnostics") is the specific tool for the
lock-screen focus bugs currently open (#9292, #9180), and users hitting those
cannot reach it by the documented name.

Triage on #9292 assumed an install missing the file. That is worth correcting:
the file is present, and the routing is what is broken.

### Steps to reproduce

1. `omarchy debug --no-sudo --print` -> `Unknown Omarchy command`
2. `omarchy commands --all | grep debug` -> no `omarchy debug` entry
3. `ls -l /usr/bin/omarchy-debug` -> exists, executable
4. `ls /usr/share/omarchy/bin/ | grep debug` -> nothing
5. `omarchy-debug --no-sudo --print` -> works

### Expected

`omarchy debug`, `omarchy debug idle` and `omarchy upload log` route to their
binaries and appear in `omarchy commands`.

### Workaround

Call them directly with a hyphen: `omarchy-debug`, `omarchy-debug-idle`,
`omarchy-upload-log`.

### System details

- Omarchy 4.0.2-1 (`omarchy-settings` 4.0.2-1)
- Kernel 7.1.9-arch1-2
- ASUSTeK X556UQ, Intel i5-6200U, Intel HD 520 + NVIDIA 940MX