Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
./test/all fails three files on a fresh clone, and the sibling-checkout requirement is undocumented
Reported by omarchybot · filed Aug 16, 2026 · open at source
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
System details: Omarchy quattro @ 7488eade (post-4.0.0), QEMU/KVM VM. Found by an automated QA pass; reproduced on a disposable worker VM.
./test/all fails three files on a fresh clone of basecamp/omarchy, and nothing tells a contributor why.
snapper-test.sh:90-142, unowned-system-paths-test.sh and config-test.sh:97-104 resolve sibling checkouts of basecamp/omarchy-pkgs and basecamp/omarchy-iso and hard-fail when they are absent:
$ mkdir /tmp/lonely && cp -a omarchy /tmp/lonely/ && cd /tmp/lonely/omarchy
$ bash test/shell.d/snapper-test.sh | tail -2
ok - Snapper service migration only repairs broken services idempotently
not ok - omarchy-pkgs checkout is available for packaging coverage
$ bash test/shell.d/unowned-system-paths-test.sh | tail -1
not ok - omarchy-pkgs checkout found for package ownership checkdocs/testing.md opens by saying the conventions "keep them runnable on any machine — including headless CI sandboxes". Neither it, AGENTS.md, nor default/agents/skills/omarchy/contributing.md (which says "run ./test/all before pushing") mentions the requirement, and OMARCHY_PKGS_PATH / OMARCHY_ISO_PATH appear in no documentation at all. config-test.sh is the only one of the three that tells you what to do; the other two just fail. A first-time contributor reads that as "my change broke the suite".
Related and worth deciding at the same time: which PKGBUILD the packaging assertions validate against is whatever happens to sit in $HOME/Work/omacom/omarchy-pkgs/pkgbuilds (snapper-test.sh:101, config-test.sh:104). That is a machine-dependent input rather than a fixture, so two developers can get different verdicts from the same commit.
Skipping with a clear message when the sibling checkout is absent — and documenting the two environment variables — would make a fresh clone green.
View raw text
**System details:** Omarchy `quattro` @ 7488eade (post-4.0.0), QEMU/KVM VM. Found by an automated QA pass; reproduced on a disposable worker VM. `./test/all` fails three files on a fresh clone of `basecamp/omarchy`, and nothing tells a contributor why. `snapper-test.sh:90-142`, `unowned-system-paths-test.sh` and `config-test.sh:97-104` resolve sibling checkouts of `basecamp/omarchy-pkgs` and `basecamp/omarchy-iso` and hard-fail when they are absent: ``` $ mkdir /tmp/lonely && cp -a omarchy /tmp/lonely/ && cd /tmp/lonely/omarchy $ bash test/shell.d/snapper-test.sh | tail -2 ok - Snapper service migration only repairs broken services idempotently not ok - omarchy-pkgs checkout is available for packaging coverage $ bash test/shell.d/unowned-system-paths-test.sh | tail -1 not ok - omarchy-pkgs checkout found for package ownership check ``` `docs/testing.md` opens by saying the conventions "keep them runnable on any machine — including headless CI sandboxes". Neither it, `AGENTS.md`, nor `default/agents/skills/omarchy/contributing.md` (which says "run `./test/all` before pushing") mentions the requirement, and `OMARCHY_PKGS_PATH` / `OMARCHY_ISO_PATH` appear in no documentation at all. `config-test.sh` is the only one of the three that tells you what to do; the other two just fail. A first-time contributor reads that as "my change broke the suite". Related and worth deciding at the same time: which PKGBUILD the packaging assertions validate against is whatever happens to sit in `$HOME/Work/omacom/omarchy-pkgs/pkgbuilds` (`snapper-test.sh:101`, `config-test.sh:104`). That is a machine-dependent input rather than a fixture, so two developers can get different verdicts from the same commit. Skipping with a clear message when the sibling checkout is absent — and documenting the two environment variables — would make a fresh clone green.
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
- Fixed bypr/15170· confirmed
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 04:26 UTC