Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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.
Contracted exit codes lost when the usage/diagnostic write fails: unknown verb exits 1, help exits 1
Low-severity issue, currently open.
Description
The issue as recorded.
Under set -e, the unknown-verb diagnostic (bin/omarchy-menu:50-52) and the help heredoc (34-35) abort the script when their write fails. With fd 2 closed an unknown verb exits 1 without reaching the canonical exit 2. With fd 1 closed help exits 1 and never reaches exit 0. Callers that distinguish usage errors (2) from generic failure (1) misclassify, and help loses its promised success.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
- CVE surface
- None
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
./pocs/crs-260930-3vzg-menu.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-3vzg-menu.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
only manifests on a closed or full stdout/stderr
The fix
Guard the writes (echo ... >&2 || true; exit 2; and cat >&1 || true; exit 0) so the contracted exit status survives a failed write
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
No authoredcode links reach these requirements in this historical reconstruction. Automatically derived code links aren't reconstructible for past runs, so implementing code may have existed without an authored trace.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- proof/evidence/ki-menu-cli-exit-code-write-races.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.