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.
A summon can arrive while a select/input request is still active.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
A summon can arrive while a select/input request is still active. The menu then answers that prior request as cancelled (done file only, empty selection) before it opens the new menu. The caller that polls the done file is thus never abandoned by a later summon.
when menu_open_called & ! no_active_request the dmenu_protocol shall eventually satisfy prior_request_cancelled
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Upstream PR omacom/omarchy#9056 (head 0b4fe292) adds the guard "if (root.requestActive) root.finishRequest(null)" at the top of Menu.qml open(), ahead of the openDmenu/openRoute dispatch that overwrites or clears selectionFile/doneFile/requestActive. Fixes omacom/omarchy#9057 and the re-summon leg (SX26/C06/C07) of KI-MENU-REQUEST-LIFECYCLE. The later head b7bd59c4 keeps this guard unchanged.
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
- V2 Third Party Review · AI agent
- Reviewed
- Oct 1, 2026, 08:20 UTC
History
- Created
- Oct 1, 2026, 08:00 UTC · V2 Third Party Review · AI agent
- Modified
- Oct 1, 2026, 07:43 UTC · V2 Third Party Review · AI agent
Hazard review
- scenarioreviewedconcurrentconcurrency_scale
The guard is the mitigation for the concurrent-summon hazard: a summon interleaved with an in-flight select/input request now answers the prior request as cancelled before opening, closing the abandoned-request trigger of omacom/omarchy#9057 (KI-MENU-REQUEST-LIFECYCLE re-summon leg). Worst case without the guard: the caller polls its done file forever. Residual: on 0b4fe292 the cancel write went through the shared resultProc and a burst could still drop it (busy-resultProc leg, SX26/C14); head b7bd59c4 writes each answer in a process of its own, which SW-REQ-261001-C19S covers. The peer-death trigger (the shell dies after a summon) stays tracked on KI-MENU-REQUEST-LIFECYCLE. Catalog 1.11.0 re-review: concurrency_scale applied. A burst of summons is the case the guard handles, one summon at a time; the witnesses in menu-test.sh drive back-to-back summons, and the live 20-summon burst left 0 callers stuck on b7bd59c4. input_domain not applicable: the guard reads only requestActive, and payload parsing belongs to SW-REQ-260922-50RE.
- propertyreviewedatomicity
The cancel-before-open is ordered strictly ahead of any state mutation by the new open (openDmenu/openRoute), so the prior request is answered from its own captured file paths before they can be overwritten or cleared; finishRequest captures both paths before clearing state.
- domainnot applicable
No domain workload tags; the menu dmenu protocol is a local QML plugin plus bash scripts with no network, crypto, or privilege surface.
- structuralnot applicable
QML/JS (GC'd) plus bash writing a constant-format truncation; no manual memory, pointers, or binary framing.
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.
- V2 Third Party Review · AI agentApprovedSpec conformanceOct 1, 2026 · 2 days agoREVIEW-261001-SYQB
Read open() and finishRequest on the PR #9056 tree. The guard if (root.requestActive) root.finishRequest(null) runs first in open(), before the openDmenu/openRoute dispatch that overwrites or clears selectionFile/doneFile/requestActive. requestActive is set only by openDmenu as !!doneFile, so requestActive implies a done file and the guard antecedent is exactly menu_open_called & !no_active_request. finishRequest(null) passes its own no-active-request early return, captures the done-file path, clears state, and issues the done-only write (: > doneFile) through Quickshell.execDetached (head b7bd59c4; resultProc on 0b4fe292), which is prior_request_cancelled. The violation row (open called, request active, no cancel) needs the guard call removed, so it is dispositioned defensive. The guard-false path leaves state untouched. On 0b4fe292 the write went through the shared resultProc, and a command change while it still ran an earlier write was ignored (busy-resultProc leg, SX26/C14); b7bd59c4 writes each answer in its own process (SW-REQ-261001-C19S, REVIEW-261001-W7QD). Re-read on b7bd59c4 2026-10-01.
Cited code (3)
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 menu_open_called & ! no_active_request the dmenu_protocol shall eventually satisfy prior_request_cancelled
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| menu_open_called | — | The host called open(payloadJson) after summon. | |
| no_active_request | — | finishRequest runs with no active request or no done file. | |
| prior_request_cancelled | — | A summon arriving while a select/input request is active first answers that prior request as cancelled (finishRequest(null), done file only) before the new open proceeds. |
Witnesses· 3 scenarios total
- bashReferenceSummonexercises 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| # | menu_open_called | no_active_request | prior_request_cancelled | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | menu_open_called | |
| 2 | T | F | F | F | menu_open_called | — |
| 3 | T | F | T | T | prior_request_cancelled | |
| 4 | T | T | F | T | no_active_request |
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)
- Menu.qmlshell/plugins/menu/Menu.qml
Tests to re-run (1)
- menu-test.shtest/shell.d/menu-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.