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.
When no plugin matches the verb, the script sends a 'No plugin to <verb>' notification and exits 0 instead of opening an empty list.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When no plugin matches the verb, the script sends a 'No plugin to <verb>' notification and exits 0 instead of opening an empty list.
when nothing_actionable the plugin_picker shall eventually satisfy notification_and_exit_zero
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
bin/omarchy-menu-plugin line 31.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- in_review
- Reviewer
- Kimi Zero Warnings · AI agent
- Reviewed
- Sep 27, 2026, 21:25 UTC
History
- Created
- Sep 22, 2026, 13:34 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 27, 2026, 21:25 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewedboundaryerror_handlingedge_case
Worst case: a caller scripting omarchy-menu-plugin <verb> && next-step reads exit 0 as success and proceeds having done nothing - the contract chooses notify-and-exit-zero over an empty picker deliberately, so the distinction nothing-to-do vs done rides on the notification text, not the status; consequence is a skipped step in a hand-rolled chain, bounded and visible. boundary: zero matching rows per verb is the exact trigger, and the arm sits before the picker opens so no empty list can ever render. error_handling: a notification-send failure kills under set -e with nonzero - loud, and the arm idempotent. edge_case: a row set that filters to whitespace-only cannot reach the arm (rows come from jq over non-empty name/id fields), so empty means genuinely empty.
- propertyreviewedtotality
The verb pipeline has exactly two endings from this trigger onward - notification plus exit 0 when the filtered set is empty, picker handoff when it is not - with no intermediate state rendering an empty menu or exiting twice.
- structuralnot applicable
A single -n test on the jq-emitted row string plus a notification call; no parsing, arithmetic, or dynamic dispatch in this arm.
- domainnot applicable
A local notification to the session bus and a process exit; the plugin inventory and picker IPC are the sibling requirements surfaces (KRBH/Q6ZS family), and no network, crypto, or privilege boundary exists in the empty-set arm.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Kimi Zero Warnings · AI agentApprovedSpec conformanceSep 27, 2026 · 5 days agoREVIEW-60
Read omarchy-menu-plugin. When the verb's filter yields no rows the script takes an unconditional notify 'No plugin to <verb>' plus exit 0 — it never opens an empty picker. nothing_actionable models the empty-rows test; notification_and_exit_zero is that exact arm. Formula conforms to the code.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
FRETish formula
when nothing_actionable the plugin_picker shall eventually satisfy notification_and_exit_zero
Witnesses· 2 scenarios total
- menu-plugin-test.sh:1exercises 2 condition scenarios
MC/DC truth table· 3 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | nothing_actionable | notification_and_exit_zero | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | nothing_actionable | |
| 2 | T | F | F | nothing_actionable | — |
| 3 | T | T | T | notification_and_exit_zero |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
No findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Files to re-check (1)
- omarchy-menu-pluginbin/omarchy-menu-plugin
Tests to re-run (1)
- menu-plugin-test.shtest/shell.d/menu-plugin-test.sh
What this rests on
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.