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.
Update `omarchy-theme-install` to allow applying updates to existing themes
Reported by JaxonWright · filed Jul 23, 2025Closed upstream on 2025-07-30 by dhh; the closing comment says it was fixed by PR #391. GitHub close reason: completed.
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
If you pull custom themes via omarchy-theme-install, there is no a very straightforward way to apply updates made. By updates, I mean upstream updates from the remote repository, not updates made by the user.
Either this command should be updated to essentially perform a git pull from the given theme parameter, or a new one created called omarchy-theme-update that pulls updates for all themes (or a specific theme given as an optional parameter).
View raw text
If you pull custom themes via `omarchy-theme-install`, there is no a very straightforward way to apply updates made. By updates, I mean upstream updates from the remote repository, not updates made by the user. Either this command should be updated to essentially perform a `git pull` from the given theme parameter, or a new one created called `omarchy-theme-update` that pulls updates for all themes (or a specific theme given as an optional parameter).
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.