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.
Migration package prerequisites are not validated against the target channel before promotion
Reported by SorenHJohansen · filed Oct 1, 2026 · open at source · 4 revisions
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Summary
The current quattro migration set contains migrations with package prerequisites that are not available in the target stable channel, and CI/release validation does not appear to catch this.
Examples:
1788996284.shrequiresomarchy-nvim >= 2026.9.21-2, while stable currently provides2026.8.13-1.1790539857.shinstallsmonologue, which is not available in stable.
Because migrations stop at the first failure and remain pending, an unsatisfied prerequisite blocks that migration and all subsequent migrations on every retry.
I reproduced this from stable 4.0.4-1: 1788996284 fails and leaves the remaining migrations pending.
The current stable release is unaffected because these migrations are not yet included in it.
Suggested fix
Add release/CI validation that verifies migration package prerequisites against the target package channel before promotion. At minimum, ensure required packages/versions are available before shipping the corresponding migrations.
View raw text
## Summary The current `quattro` migration set contains migrations with package prerequisites that are not available in the target stable channel, and CI/release validation does not appear to catch this. Examples: * `1788996284.sh` requires `omarchy-nvim >= 2026.9.21-2`, while stable currently provides `2026.8.13-1`. * `1790539857.sh` installs `monologue`, which is not available in stable. Because migrations stop at the first failure and remain pending, an unsatisfied prerequisite blocks that migration and all subsequent migrations on every retry. I reproduced this from stable `4.0.4-1`: `1788996284` fails and leaves the remaining migrations pending. The current stable release is unaffected because these migrations are not yet included in it. ### Suggested fix Add release/CI validation that verifies migration package prerequisites against the target package channel before promotion. At minimum, ensure required packages/versions are available before shipping the corresponding migrations.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 20:31 UTC