## What happened

`omarchy debug` is unreachable through the dispatcher, even though `omarchy --help`
advertises it under "Common commands":

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

$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print

$ omarchy debug idle
Unknown Omarchy command: omarchy debug idle
```

The binaries themselves are present and work fine when called directly:

```
$ /usr/bin/omarchy-debug --no-sudo --print
Date: ...
Hostname: ...
Omarchy Package: omarchy 4.0.4-1
[full diagnostic output]
```

## What was expected

`omarchy debug --no-sudo --print` runs the diagnostics, as documented in
`omarchy --help` and in the binary's own metadata
(`# omarchy:examples=omarchy debug --print --no-sudo`).

This matters because `omarchy debug` is the command users are asked to run when
filing bug reports.

## Root cause pointer

No route for `debug` is registered at all:

```
$ omarchy commands --all | grep -cE '^\s+omarchy debug( |$)'
0
```

For comparison, `version` — which also has a parent binary plus children —
registers 4 routes and works. The difference appears to be that
`omarchy-debug-idle` declares `# omarchy:group=debug`, which opens a `debug`
group, while `omarchy-debug` itself declares neither `omarchy:group=` nor
`omarchy:name=`. Other parents in the same situation (`toggle`, `hook`, `menu`)
are not standalone commands, so the gap is invisible there; for `debug` the
parent *is* the primary command, so it becomes unreachable.

Sibling binaries that need an explicit route declare it via `# omarchy:name=`
(e.g. `omarchy-install-gaming-gpu-lib32` uses `name=gaming gpu-lib32`), which
suggests `omarchy-debug` may simply be missing such a declaration.

## Also worth noting

The built-in metadata check does not catch this:

```
$ omarchy commands --check
Command metadata check passed (440 commands)
```

An advertised command that cannot be dispatched arguably should fail that check.

## Steps to reproduce

On a stock Omarchy 4.0.4-1 install:

1. `omarchy --help` — observe `omarchy debug` listed under "Common commands"
2. `omarchy debug` — fails with "Unknown Omarchy command"
3. `/usr/bin/omarchy-debug --no-sudo --print` — works

## System details

- Omarchy 4.0.4-1
- Kernel: stock Arch `linux` 7.2.3.arch1-3