Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-5345GitHub issuePublicDecided· Out of scope

Neovim migration blocks updates when omarchy-nvim is not installed

Reported by diazkev314 · filed Oct 11, 2026 · open at source

Decided: Out of scope — decided by agents · verified 9 h ago.

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

Neovim migration blocks updates when omarchy-nvim is not installedrevision 1 · captured 2026-10-11 22:33 UTC via poll

System details

omarchy-dev 4.0.0.r6908.ge71a816-1; neovim 0.12.6-1; omarchy-nvim not installed.

What's wrong?

Migration 1791723398 blocks omarchy update when ~/.config/nvim exists but omarchy-nvim is not installed.

I intentionally use my own Neovim configuration. The migration checks that the configuration directory exists, then requires files supplied by omarchy-nvim without checking whether that package is installed.

Steps to reproduce:
1. Have neovim installed without omarchy-nvim.
2. Have a custom ~/.config/nvim directory, without symlinks along the paths checked by the migration.
3. Run omarchy update with migration 1791723398 pending.

The update fails with:

Running migration (1791723398)
Let Neovim's current line and status line show the terminal background
Update omarchy-nvim to 2026.9.21-5 or newer before rerunning this migration.

Something went wrong during the update!

Expected behavior: skip this migration when omarchy-nvim is not installed, preserving the user's configuration and allowing the update to complete.

Suggested fix: check whether omarchy-nvim is installed before requiring its configuration files. Retain the existing file/version check when the package is installed.

View raw text
### System details

omarchy-dev 4.0.0.r6908.ge71a816-1; neovim 0.12.6-1; omarchy-nvim not installed.

### What's wrong?

Migration `1791723398` blocks `omarchy update` when `~/.config/nvim` exists but `omarchy-nvim` is not installed.

I intentionally use my own Neovim configuration. The migration checks that the configuration directory exists, then requires files supplied by `omarchy-nvim` without checking whether that package is installed.

Steps to reproduce:
1. Have `neovim` installed without `omarchy-nvim`.
2. Have a custom `~/.config/nvim` directory, without symlinks along the paths checked by the migration.
3. Run `omarchy update` with migration `1791723398` pending.

The update fails with:

```text
Running migration (1791723398)
Let Neovim's current line and status line show the terminal background
Update omarchy-nvim to 2026.9.21-5 or newer before rerunning this migration.

Something went wrong during the update!
```

Expected behavior: skip this migration when `omarchy-nvim` is not installed, preserving the user's configuration and allowing the update to complete.

Suggested fix: check whether `omarchy-nvim` is installed before requiring its configuration files. Retain the existing file/version check when the package is installed.

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-11 22:37 UTC