Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-628GitHub issuePublicDecided· Out of scope

Add contributor tooling to catch config conflicts, missing dependencies, and plugin collisions before merge

Reported by andyholst · filed Sep 12, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Add contributor tooling to catch config conflicts, missing dependencies, and plugin collisions before mergerevision 1 · captured 2026-09-28 21:23 UTC via poll

What's Missing

Omarchy has partial solutions to config and plugin conflicts, but no automated validation at PR time.

Already exists

  • omarchy-plugin-enable prevents two bar widgets from owning the same surface
  • o.rebind lets plugins replace Hyprland keybindings (PR #10537, merged)
  • install/helpers/ has logging and browser-policy helpers
  • bin/omarchy-hw-* scripts detect specific hardware

What's missing

  1. Config collision scanner — No tool checks if a new keybinding shadows an existing one, or if two .conf files set the same flag. Multiple PRs try to fix the keybindings scanner hanging (PR #11027, #11095, #10388, #10562), but none validate uniqueness.
  1. Install script dependency validator — install/hardware/all.sh runs scripts sequentially but doesn't check that every systemctl enable X has a matching package install. No automated gap detection.
  1. Hardware compatibility lookup — omarchy-hw-msi exists, omarchy-hw-nvidia-without-gsp exists, but there's no unified queryable database. Triage still requires manual searching.
  1. Plugin service conflict extension — Issue #10213 asks for replaces declarations in plugin manifests. Bar widgets already have this; services don't.

Proposal

Add CI checks that run on every PR:

  • Config scanner — reads all keybinding and .conf files, reports duplicates or shadows
  • Install validator — parses install scripts, cross-references systemctl enable against package installs
  • Hardware compat DB — unified queryable table of hardware IDs → drivers → conflicts

None of this requires new infrastructure — bash or Lua scripts outputting pass/fail. Existing test/shell.d/ is the natural home.

Effect on Contributors

PR adds keybinding → CI says "already bound by fcitx5 plugin" → fix immediately.
PR adds install script → CI says "service enabled but package not installed" → fix before merge.

Bugs move from "user discovers in production" to "contributor fixes on PR."

View raw text
## What's Missing

Omarchy has partial solutions to config and plugin conflicts, but no automated validation at PR time.

### Already exists

- `omarchy-plugin-enable` prevents two bar widgets from owning the same surface
- `o.rebind` lets plugins replace Hyprland keybindings (PR #10537, merged)
- `install/helpers/` has logging and browser-policy helpers
- `bin/omarchy-hw-*` scripts detect specific hardware

### What's missing

1. **Config collision scanner** — No tool checks if a new keybinding shadows an existing one, or if two `.conf` files set the same flag. Multiple PRs try to fix the keybindings scanner hanging (PR #11027, #11095, #10388, #10562), but none validate uniqueness.

2. **Install script dependency validator** — `install/hardware/all.sh` runs scripts sequentially but doesn't check that every `systemctl enable X` has a matching package install. No automated gap detection.

3. **Hardware compatibility lookup** — `omarchy-hw-msi` exists, `omarchy-hw-nvidia-without-gsp` exists, but there's no unified queryable database. Triage still requires manual searching.

4. **Plugin service conflict extension** — Issue #10213 asks for `replaces` declarations in plugin manifests. Bar widgets already have this; services don't.

## Proposal

Add CI checks that run on every PR:

- **Config scanner** — reads all keybinding and `.conf` files, reports duplicates or shadows
- **Install validator** — parses install scripts, cross-references `systemctl enable` against package installs
- **Hardware compat DB** — unified queryable table of hardware IDs → drivers → conflicts

None of this requires new infrastructure — bash or Lua scripts outputting pass/fail. Existing `test/shell.d/` is the natural home.

## Effect on Contributors

PR adds keybinding → CI says "already bound by fcitx5 plugin" → fix immediately.
PR adds install script → CI says "service enabled but package not installed" → fix before merge.

Bugs move from "user discovers in production" to "contributor fixes on PR."

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 12:21 UTC