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 1789095456.sh collides with the deleted PTL-kernel migration of the same name
Reported by ekollof · filed Sep 16, 2026 · open at source
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
What's wrong?
migrations/1789095456.sh (added by #11336, "Remove unsafe project bin PATH injection") reuses the filename of the deleted Panther Lake kernel migration. That migration was superseded by migrations/1789325478.sh and removed in ff85faf8 ("Make linux-omarchy the default kernel except on T2 Macs"). The new file is an unrelated Mise Work PATH cleanup that happens to carry the same timestamp name.
Two consequences:
- Upstream's tree fails its own test.
test/shell.d/omarchy-kernel-migration-test.shasserts the superseded migration is gone:
[[ ! -e $ROOT/migrations/1789095456.sh ]] || fail "the superseded migration must not install the PTL variant first" This now fails on clean quattro.
- Users who completed the old PTL migration will silently skip the new one.
omarchy-migratetracks completion per filename under~/.local/state/omarchy/migrations/(plus the machine marker). Anyone who ran the PTL migration while it shipped carries a1789095456marker, so the Mise cleanup is considered already completed and never runs for exactly those users.
Suggested fix
Rename the new migration to a fresh timestamp (e.g. the current date-based id) and update the one test reference in test/shell.d/mise-work-path-test.sh (migration="$ROOT/migrations/1789095456.sh"). No marker migration is possible for the skipped users — they never ran the new content — so a rename cleanly makes it pending for everyone.
Evidence
git log --oneline -- migrations/1789095456.shonquattro:a73bcbfc(re-add, #11336) on top offf85faf8(deletion) on top of8a972da9(original PTL migration).- Failing assertion reproduced on a clean
upstream/quattrocheckout with no local changes.
View raw text
## What's wrong?
`migrations/1789095456.sh` (added by #11336, "Remove unsafe project bin PATH injection") reuses the filename of the deleted Panther Lake kernel migration. That migration was superseded by `migrations/1789325478.sh` and removed in `ff85faf8` ("Make linux-omarchy the default kernel except on T2 Macs"). The new file is an unrelated Mise Work PATH cleanup that happens to carry the same timestamp name.
Two consequences:
1. **Upstream's tree fails its own test.** `test/shell.d/omarchy-kernel-migration-test.sh` asserts the superseded migration is gone:
```bash
[[ ! -e $ROOT/migrations/1789095456.sh ]] || fail "the superseded migration must not install the PTL variant first"
```
This now fails on clean `quattro`.
2. **Users who completed the old PTL migration will silently skip the new one.** `omarchy-migrate` tracks completion per filename under `~/.local/state/omarchy/migrations/` (plus the machine marker). Anyone who ran the PTL migration while it shipped carries a `1789095456` marker, so the Mise cleanup is considered already completed and never runs for exactly those users.
## Suggested fix
Rename the new migration to a fresh timestamp (e.g. the current date-based id) and update the one test reference in `test/shell.d/mise-work-path-test.sh` (`migration="$ROOT/migrations/1789095456.sh"`). No marker migration is possible for the skipped users — they never ran the new content — so a rename cleanly makes it pending for everyone.
## Evidence
- `git log --oneline -- migrations/1789095456.sh` on `quattro`: `a73bcbfc` (re-add, #11336) on top of `ff85faf8` (deletion) on top of `8a972da9` (original PTL migration).
- Failing assertion reproduced on a clean `upstream/quattro` checkout with no local changes.
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 14:23 UTC