## Summary

The contributing guide instructs bug reporters to run `omarchy debug`, but no `debug` command exists in the shipped CLI (verified on 4.0.3-1). Reporters following the guide hit a dead end before they can generate the diagnostics the template asks for.

## Environment

- Omarchy: 4.0.3-1 (Arch Linux package)
- Hyprland: 0.56.2-2
- CPU: AMD Ryzen 7 7735HS (Radeon 680M iGPU)
- RAM: 27 GiB

## What happened

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

```text
$ omarchy commands --all | grep -- -debug
(no output — the command is not registered)
```

`omarchy debug` alone (the interactive variant the guide also references, which it says uploads to logs.omarchy.org and prints a shareable URL) fails identically.

## What was expected

The contributing guide (and the omarchy.org docs) reference:

- `omarchy debug --no-sudo --print` — "also written to /tmp/omarchy-debug.log"
- `omarchy debug` — interactive variant that uploads the log to logs.omarchy.org (expires after 24h) and prints a shareable URL

Given the issue template asks for a diagnostics log, a working `omarchy debug` (or an updated guide) is needed so reporters can actually gather it.

## Suggested fix

Either ship the `debug` command, or update the contributing guide / docs to point at whatever the current supported way of generating diagnostics is (e.g. vendored `omarchy-system-info`-style output, journalctl excerpts, `hyprctl systeminfo`).