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.
finishRequest with a null selection (Escape/cancel) creates only the done file, so the caller observes the cancel as an empty selection.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
finishRequest with a null selection (Escape/cancel) creates only the done file, so the caller observes the cancel as an empty selection.
when finish_requested & prompt_dismissed the dmenu_protocol shall eventually satisfy done_only_written
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Menu.qml finishRequest lines 129-133 and cancel lines 831-835.
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, 20:50 UTC
History
- Created
- Sep 22, 2026, 13:34 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 27, 2026, 20:47 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewedboundaryconcurrentedge_caseconcurrency_scale
Worst case: a dismissal forges an answer - a selection file written where the caller expects done-only - or the done marker lands before the selection content is durable, so the CLI wakes on done and reads an empty selection, converting a real pick into a cancel; the two-arm command (printf selection then truncate done, in one bash -c) plus the null-selection done-only arm are the entire protection. boundary: done-only versus selection+done is the exact two-arm partition this requirement names, and the guard front door (no active request or no done file) is the stale-finish edge shared with 3VTN. concurrent: the request fields are cleared before the write spawns, so a second finish is a silent no-op rather than a second write, and the single-threaded QML event loop serializes entries. edge_case: a selection containing newlines or shell metacharacters passes through Util.shellQuote into the printf verbatim - the quoting helper is the trusted boundary and its own requirements own its correctness; mktemp-unique paths rule out cross-request file collisions. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale applied, part of the menu request lifecycle: a dismissal can race a superseding summon.
- propertyreviewedatomicity
The done file is the protocol commit marker and it is written last, inside the same bash -c after the selection content is flushed, so a caller waking on done observes either a complete selection or its documented absence (cancel) - never a half-written answer; the fields cleared up front make the operation all-or-nothing against reentry.
- structuralnot applicable
Two shell-quoted file writes through a spawned bash -c; no parsing, arithmetic, memory, or encoding transform - the selection bytes are quoted and passed verbatim.
- domainnot applicable
Same-user mktemp'd files written by the menu's own result process; path provenance is the summon payload's (owned by Q6ZS), the CLI polling side is the protocol siblings, and no network, crypto, or privilege boundary is crossed here.
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-25
Read finishRequest at Menu.qml:122-141. No active request or no doneFile: closes menu, writes nothing (3VTN arm). Cancel path (selection null) touches ONLY the done file (: > done). Selection path writes the selection file then the done file. Formula gated on finish_requested & prompt_dismissed -> done_only_written matches the cancel arm exactly; the done file is the unconditional protocol terminator.
Cited code (1) - Kimi Upstream Refresh · AI agentApprovedSpec conformanceSep 25, 2026 · last weekREVIEW-76
Read finishRequest (Menu.qml:131-149) and cancel (Menu.qml:895-899). cancel() calls finishRequest(null) whenever dmenuActive, i.e. prompt_dismissed -> finish_requested with null selection. The null branch (Menu.qml:143-147) runs only ': > doneFile' - no selection write - which is exactly done_only_written. The state-clear block (137-141) runs before the write, so the captured paths are used; no branch in the null path touches the selection file. FRETish models both gating conditions; no silent precondition observed.
Cited code (2)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
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 finish_requested & prompt_dismissed the dmenu_protocol shall eventually satisfy done_only_written
Witnesses· 3 scenarios total
- menu-dmenu-test.sh:1exercises 3 condition scenarios
MC/DC truth table· 4 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| # | done_only_written | finish_requested | prompt_dismissed | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | T | T | finish_requested | |
| 2 | F | T | F | T | prompt_dismissed | |
| 3 | F | T | T | F | done_only_written | — |
| 4 | T | T | T | T | done_only_written |
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.
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)
- Menu.qmlshell/plugins/menu/Menu.qml
Tests to re-run (1)
- menu-dmenu-test.shtest/shell.d/menu-dmenu-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.