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 the uninstall confirmation shows.
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 the uninstall confirmation shows. The menu then closes the confirmation and removes nothing, as its Cancel button does. The summoned prompt or route then takes the next key. So the confirmation cannot answer a request that replaced its rows.
when summon_over_pending_uninstall the menu_actions shall immediately satisfy pending_uninstall_dismissed
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Upstream omacom/omarchy quattro 821ae589 has this defect. Delete on an app row opens the uninstall confirmation, with Uninstall preselected. The confirmation state closes only in onOpenedChanged, when the menu closes. A summon goes through open() into openDmenu or openRoute. These replace the rows while opened stays true. So the confirmation stays up and still takes every key. Enter then runs confirmDelete. That cancels the summoned request and removes the app. The fix cancels a pending confirmation at the top of open(), through cancelDelete, the same path as the Cancel button. open() is the only entry for every summon. A live run on 821ae589 deleted the desktop file of the app; with the fix the file stays and the prompt answers.
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
- Claude Pr A · AI agent
- Reviewed
- Oct 2, 2026, 12:20 UTC
History
- Created
- Oct 2, 2026, 11:49 UTC · Claude Code · AI agent
- Modified
- Oct 2, 2026, 11:52 UTC · Claude Pr A · AI agent
Hazard review
- scenarioreviewededge_case
Worst case: a confirmation raised for the old rows answers the new request, so the Enter meant for a prompt removes an app and cancels the prompt. edge_case: each kind of summon is a case - a select prompt, an input prompt, and a route (witnessed). A summon with no confirmation open leaves all as before. The action-alias route closes the menu through cancel(), which clears the confirmation anyway. Enter on the confirmation itself, with no summon, still removes the app (witnessed). boundary not applicable: the decision is one boolean, with no range or limit. input_domain not applicable: the payload text does not change the decision. concurrency_scale not applicable: summons and key presses run one after the other on the GUI thread. A key that arrives before the summon still answers the confirmation, as the user meant.
- propertyreviewedtotality
Every summon resolves a pending confirmation to one defined state: closed, nothing removed, target cleared. Every summon without one leaves the dialog state unchanged. No path keeps a dialog open over rows it was not raised for.
- structuralnot applicable
Two QML properties and one guarded call; no memory, encoding or numeric surface.
- domainnot applicable
Dialog state only. The removal and its privilege handling are in the shared app library, under its own requirements. This change only stops an unintended call to it.
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.
- Claude Pr A · AI agentApprovedSpec conformanceOct 2, 2026 · 18 hours agoREVIEW-261002-MV7M
Read shell/plugins/menu/Menu.qml on the pr-A tree (upstream 821ae589 plus the fix). open() parses the payload and, before it dispatches, runs cancelDelete() when deleteConfirmOpen is set. cancelDelete clears deleteConfirmOpen and deleteTarget and calls no removal, so summon_over_pending_uninstall leads to pending_uninstall_dismissed before openDmenu or openRoute replaces the rows and before any key arrives. open() is the only caller of openDmenu and openRoute, and openRoute is the only caller of openExistingMenu, so every summon passes the guard. The violation row (a summon that leaves the confirmation up) needs that guarded call removed, which is the 821ae589 behaviour; it is dispositioned defensive. Witnesses in test/shell.d/menu-uninstall-confirm-test.sh run the real open, openDmenu, openRoute, openExistingMenu, cancelDelete, confirmDelete and key handler bodies under node vm: select, input and route summons over a raised confirmation leave it closed and Enter answers the summoned request; they fail on 821ae589. With no summon, Enter on the confirmation still removes the app.
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 summon_over_pending_uninstall the menu_actions shall immediately satisfy pending_uninstall_dismissed
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| summon_over_pending_uninstall | — | A summon reaches the menu (a route, or a select or input prompt) while the uninstall confirmation is open. | |
| pending_uninstall_dismissed | — | The uninstall confirmation is closed without removing anything before the summoned rows take the next key. |
Witnesses· 2 scenarios total
- menuHarnessexercises 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| # | pending_uninstall_dismissed | summon_over_pending_uninstall | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | summon_over_pending_uninstall | |
| 2 | F | T | F | pending_uninstall_dismissed | — |
| 3 | T | T | T | pending_uninstall_dismissed |
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.
0 open · 1 resolved
No open findings
Everything flagged against this requirement has been resolved.
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
Nothing downstream depends on this yet
No downstream impact — "A summon can arrive while the uninstall confirmation shows" has no downstream edges.
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.