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.
Every picker row carries the plugin id as tab subtext.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
Every picker row carries the plugin id as tab subtext. This tells same-named plugins apart on screen. The pick resolves to the id, which the verb command receives.
when same_named_plugins the plugin_picker shall eventually satisfy pick_resolves_by_id
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 lines 25-37 and 45.
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
- scenarioreviewedmalformed_inputboundaryedge_case
Worst case: the pick resolves to the wrong target - cut -f2 on a selection line whose id contains a tab or the row label itself contains a tab yields a truncated or shifted token, and for the remove verb that wrong token is passed to omarchy-plugin-remove, a destructive action on a plugin the user did not select. malformed_input: plugin ids are directory-derived and user-clonable, so odd identifiers are reachable input, and the unconditional field-2 cut is the declared parse policy. boundary: exactly-two-field lines are the well-formed case; one-field (missing tab) and three-plus-field lines are the edges where the cut silently mangles the id. edge_case: two plugins sharing a display name is the subject and is witnessed; the arguments are shell-quoted with printf %q at the terminal-launch sinks, so no injection chain composes onto the wrong-token case beyond the wrong-target removal graded here. Catalog 1.11.0 re-review: input_domain not applicable, plugin ids come from the installed plugin list, not from a parsed text file. concurrency_scale not applicable, one run per user action that owns its own temp files and shares no state with a concurrent run.
- propertyreviewedtotality
Every row the picker emits (Label<TAB>id) resolves through the same unconditional field-2 cut to a defined id string that the verb command receives; no selection shape leaves the pick unresolved or falls through to acting on a name.
- structuralnot applicable
Bash string cutting and printf %q quoting; no arithmetic, memory, or encoding round-trip surface - the tab-delimited line is ASCII-structured and never re-encoded.
- domainnot applicable
Local picker over the installed-plugin inventory dispatching to local omarchy-plugin-* commands through a quoted terminal launch; no network, IPC-channel, crypto, or privilege-boundary surface, and no domain tag fires.
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-37
Read omarchy-menu-plugin and menu-plugin-test.sh. Every picker row is built with the plugin id as tab-separated subtext so same-named plugins display distinctly, and the selection handler cuts field 2 (the id) unconditionally — the verb command receives the id, never the display name. The same_named_plugins condition models the ambiguous-label case the subtext design resolves. 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 same_named_plugins the plugin_picker shall eventually satisfy pick_resolves_by_id
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| # | pick_resolves_by_id | same_named_plugins | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | same_named_plugins | |
| 2 | F | T | F | pick_resolves_by_id | Exempted · defensive — the picker cuts field 2 of the selection line as the id unconditionally; resolving by name needs that cut removed (reviewed: REVIEW-M9) |
| 3 | T | T | T | pick_resolves_by_id |
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.