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.
open(payload) dispatches on mode: select/input open the dmenu flow, anything else opens the resolved route.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
open(payload) dispatches on mode: select/input open the dmenu flow, anything else opens the resolved route. close() cancels. refresh() reloads both JSONC files and returns ok. ping() returns ok.
when menu_open_called the menu_lifecycle shall eventually satisfy lifecycle_answered
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Menu.qml open/close/refresh/ping lines 21-44 and openExistingMenu/openDmenu lines 837-881; this is the plugin lifecycle the dispatcher IPC reaches.
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, 15:09 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 27, 2026, 20:47 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewedmalformed_inputerror_handlingboundaryconcurrent
Worst case: a malformed or hostile IPC payload - unparsable JSON, unknown mode, absent menu id - crashes or wedges the IpcHandler and takes down the whole Quickshell desktop shell, or a second summon arrives while the menu is open and clobbers the live request's doneFile/selection state. malformed_input: JSON.parse sits in a try/catch degrading to {} so an unparsable payload answers as a root-menu open instead of killing the handler - the declared parse policy. error_handling: every dispatch arm answers (dmenu flow, route fallback to root, close, refresh, ping); no payload shape leaves the call unanswered. boundary: the exact mode strings select/input split dmenu from route, and initialMenu/menu/root is a three-step fallback chain whose arms are the tested partition. concurrent: open-while-open and open-while-dmenu-active interleave through the opened/requestActive/requestSerial discipline, but a second select summon while the first is unanswered replaces selectionFile/doneFile without answering the first caller, so that omarchy-menu-select polls forever - KI-MENU-REQUEST-LIFECYCLE (omacom/omarchy#9057), behavioural reproducer test/reports/report-cmulr95nw0kqr1gw46i7f50xj.sh; upstream e332dc97 has no cancel-prior guard (that is PR #9056). Note: payload.fontFamily is an accepted same-user cosmetic override, graded low - the IPC endpoint is same-user local and carries no privilege.
- propertyreviewedidempotency
refresh() and ping() are pure read-side verbs returning ok with identical observable effect when repeated; open() with the same payload twice re-reaches the same route through the fallback chain. Repeated lifecycle calls converge instead of accumulating state - the witness suite re-summons menus across scenarios and asserts the same rendered state.
- structuralnot applicable
The only parse is JSON.parse wrapped in try/catch with a defined fallback; no memory, pointer, format-string, or encoding surface - payload strings are consumed as opaque JSON or dropped wholesale.
- domainnot applicable
The IPC endpoint is Quickshell's same-user local IpcHandler with no authentication surface to declare (auth posture: none, same-user by construction, no network listener), and refresh() reads only the two fixed menu JSONC paths - no egress sink, no tamper/replay surface beyond what the same-user threat model already grants, so no domain class applies_when 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-24
Read open/close/refresh/ping at Menu.qml:21-44. open parses payloadJson with try/catch (bad JSON silently degrades to empty object - a precondition the code honors and the formula abstracts over), dispatches select/input to openDmenu and everything else to openRoute; close cancels; refresh reloads both JSONC files and returns ok; ping returns ok. Every lifecycle verb produces an answer, matching menu_open_called -> lifecycle_answered.
Cited code (3) - Kimi Upstream Refresh · AI agentApprovedSpec conformanceSep 25, 2026 · last weekREVIEW-79
Read open/close/refresh/ping (Menu.qml:22-56) and openExistingMenu/openDmenu (902-949). open() parses payload (malformed JSON falls back to {} via catch), then dispatches: mode select/input -> openDmenu, else openRoute; both set opened=true, so every menu_open_called yields lifecycle_answered. close() -> cancel(); refresh() reloads both JSONC files and returns ok; ping returns ok. Note: no in-flight-request pre-answer exists on this baseline; that guard and its requirement (SW-REQ-260925-XTGG) are PR#9056-scoped and audited on the PR mirror line. Formula models all four lifecycle verbs; no silent precondition found.
Cited code (4)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
- LowOpen
Failed menu FileView reloads are asymmetric: user handler wipes last good items, default keeps stale set
KI-MENU-FILEVIEW-FAILURE-ASYMMETRY
- LowOpen
Map reads walk Object.prototype: item(), results maps, providersLoaded treat constructor/toString as real entries
KI-MENU-ITEM-PROTOTYPE-LEAK
- LowOpen
open() throws on a JSON null payload: parse succeeds, the catch does not run, the property read throws
KI-MENU-OPEN-NULL-PAYLOAD
- LowOpen
pendingInitialMenu is stored and never read: a route summoned before the JSONC loads opens root and stays there
KI-MENU-PENDING-INITIAL-MENU-DEAD
- LowOpen
Payload fontFamily is sticky: a later open that omits it keeps the previous caller's font
KI-MENU-STICKY-FONTFAMILY
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 the menu_lifecycle shall eventually satisfy lifecycle_answered
Witnesses· 2 scenarios total
- pokeGuardsexercises 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| # | lifecycle_answered | menu_open_called | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | menu_open_called | |
| 2 | F | T | F | lifecycle_answered | — |
| 3 | T | T | T | lifecycle_answered |
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.
5 open · 0 resolved
- LowOpen
Failed menu FileView reloads are asymmetric: user handler wipes last good items, default keeps stale set
KI-MENU-FILEVIEW-FAILURE-ASYMMETRY
- LowOpen
Map reads walk Object.prototype: item(), results maps, providersLoaded treat constructor/toString as real entries
KI-MENU-ITEM-PROTOTYPE-LEAK
- LowOpen
open() throws on a JSON null payload: parse succeeds, the catch does not run, the property read throws
KI-MENU-OPEN-NULL-PAYLOAD
- LowOpen
pendingInitialMenu is stored and never read: a route summoned before the JSONC loads opens root and stays there
KI-MENU-PENDING-INITIAL-MENU-DEAD
- LowOpen
Payload fontFamily is sticky: a later open that omits it keeps the previous caller's font
KI-MENU-STICKY-FONTFAMILY
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-compositor-test.shtest/shell.d/menu-compositor-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.