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

`rg` is an unchecked hard dependency of the test suite, and without it nine guards report `ok` instead of failing.

`base-test.sh` provides `require_command`, and 30+ files use it for `jq`, `python3` and `node`. Nothing in `test/` ever calls `require_command rg`:

```
$ grep -rn 'require_command rg' test/
(no matches)
```

Twelve files use `rg` anyway, and every one of these guards is written in negative form, where a failing `rg` reads as "clean":

```bash
if rg -q 'barMoveSettling|barMoveSettleTimer' "$ROOT/shell/plugins/bar/Bar.qml"; then
  fail "bar move outline must clear when the pointer is released"
fi
pass "bar move outline has no post-release settling state"
```

A command that fails inside `if` is exempt from `set -e`, so a missing `rg` (exit 127) takes the "no match" branch and prints `ok`. The same holds if a grepped file is ever renamed — `rg` exits 2 and the guard evaporates silently rather than failing.

`bin-style-test.sh:7-15` is the worst shape, because it swallows the error explicitly and both its assertions can only ever pass:

```bash
raw_command_checks=$(rg -l 'command -v' "$ROOT/bin" | rg -v '/omarchy-...' || true)
[[ -z $raw_command_checks ]] || fail "bin commands use command helpers"
pass "bin commands use command helpers"
```

Replacing `rg` with a stub that behaves like "command not found":

```
$ printf '#!/bin/bash\necho "rg: command not found" >&2\nexit 127\n' > "$mask/rg"
$ for t in bin-style idle nightlight windows-vm battery-status panel-command-path bar; do
    PATH="$mask:$PATH" bash test/shell.d/$t-test.sh; done

bin-style-test.sh          exit=0   rg: command not found | ok - bin commands use command helpers
                                    rg: command not found | ok - bin commands use the notification helper
idle-test.sh               exit=0   ok - Stay Awake toggle persists state without reentrant shell IPC
nightlight-test.sh         exit=0   ok - nightlight toggle leaves indicator refresh to the nightlight service
battery-status-test.sh     exit=0   rg: command not found | ok - battery status owns capacity and remaining calculations
panel-command-path-test.sh exit=0   rg: command not found | ok - panels avoid bar path resolution for omarchy helpers
bar-test.sh                exit=0   ok - bar move outline has no post-release settling state
windows-vm-test.sh         exit=1   rg: command not found | not ok - Windows VM uses manual startup by default
```

Six of seven go green. `panel-command-path-test.sh` has only that one assertion, so the whole file becomes a no-op.

`windows-vm-test.sh` is the only one written in positive form and the only one that fails loudly — which is the fix for the rest, alongside a `require_command rg` in `base-test.sh` and in `test/cli` (which has no `require_command` at all, and two `rg` guards at `:422` and `:445`).

Affected: `bin-style-test.sh`, `panel-command-path-test.sh`, `idle-test.sh:50`, `nightlight-test.sh:89`, `battery-status-test.sh:47`, `bar-test.sh:17`, `indicator-contract-test.sh:73`, `test/cli:422,445`.

---

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

Narrower than filed. A missing `rg` silently invalidates nine ordinary negative assertions plus one compositor-gated assertion across eight files -- but four other `rg`-using files fail loudly, so the complete shell suite does not pass green without ripgrep. Ripgrep is also in Omarchy's core package set, so the exposure is a nonstandard dev host, a deliberately masked `PATH`, or a broken install, rather than a routine machine.