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.
Back after drilling in from a filtered search parks the cursor on an unrelated parent row
Low-severity issue, currently open.
Description
The issue as recorded.
With omacom/omarchy#13012, setActiveMenu saves the selected index and row id; the index points into the FILTERED search list. A deeper submenu entered from a root search is not a row of the unfiltered root list. Example: query font, Enter on install.style.font at filtered index 1. goBack finds no row-id match and keeps the saved index. Back clears the filter, so the cursor lands on the root row at that index (learn). The baseline reset the cursor to row 0.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
- CVE surface
- None
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
bash test/shell.d/menu-pointer-lifecycle-test.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
bash test/shell.d/menu-pointer-lifecycle-test.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Cursor placement only; no action runs and the user can move the cursor. Enter on the wrong row would open/run that row.
The fix
Save the index only when filterText is empty. Alternatively save the root-level ancestor id of the entered row. Back after a filtered drill-in then starts at row 0 or on the ancestor.
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
Touch this finding and you re-check 1 requirements · 1 code files · 1 tests.
- Menu.qml
- menu-pointer-lifecycle-test.sh
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- proof/evidence/ki-menu-back-filtered-index.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
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.