Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
"Sort keybindings" in commit de2b32d also deleted workspace 10
Reported by lukehowson · filed Oct 29, 2025Closed upstream on 2025-11-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
N/A
What's wrong?
Commit de2b32d says it sorts keybindings.
It also removed the keybinding super-0, which previously switched to workspace 10, and super-shift-0, which previously moved current application to workspace 10. Nothing appears to be newly bound to either of these keybindings.
If this was intended, can I ask what the rationale was, so I don't mess anything up by reverting this change in my bindings.conf? Otherwise can it be reinstated?
I could not find anything to document this change in the PR, the commit, or the release notes, but I'm good at not finding things like that, so it may well just be me.
Thanks.
View raw text
### System details N/A ### What's wrong? Commit de2b32d says it sorts keybindings. It also removed the keybinding super-0, which previously switched to workspace 10, and super-shift-0, which previously moved current application to workspace 10. Nothing appears to be newly bound to either of these keybindings. If this was intended, can I ask what the rationale was, so I don't mess anything up by reverting this change in my bindings.conf? Otherwise can it be reinstated? I could not find anything to document this change in the PR, the commit, or the release notes, but I'm good at not finding things like that, so it may well just be me. Thanks.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.