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-4545GitHub issuePublicReceived

Quattro: catppuccin theme sets invalid nvim colorscheme "catppuccin-nvim"

Reported by shawnyeager · filed Aug 9, 2026Closed upstream on 2026-08-09 by dhh, as not planned.

Received and recorded verbatim. Nothing has been checked yet.

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

Quattro: catppuccin theme sets invalid nvim colorscheme "catppuccin-nvim"revision 1 · captured 2026-10-04 11:56 UTC via poll

On 4.0.0.alpha with the catppuccin theme selected, every nvim launch fails with LazyVim's "could not load your colorscheme" error and falls back to an unthemed editor.

Cause: themes/catppuccin/neovim.lua (quattro branch, line 10) sets colorscheme = "catppuccin-nvim". That's the plugin's repo name — the colorschemes the catppuccin plugin actually registers are catppuccin, catppuccin-mocha, catppuccin-latte, etc. Since theme-set copies this file into the user's nvim config, everyone on the default post-upgrade theme hits the error.

Fix: colorscheme = "catppuccin". The other shipped themes' neovim.lua files all use valid names; catppuccin is the only one affected.

View raw text
On 4.0.0.alpha with the catppuccin theme selected, every nvim launch fails with LazyVim's "could not load your colorscheme" error and falls back to an unthemed editor.

Cause: `themes/catppuccin/neovim.lua` (quattro branch, line 10) sets `colorscheme = "catppuccin-nvim"`. That's the plugin's repo name — the colorschemes the catppuccin plugin actually registers are `catppuccin`, `catppuccin-mocha`, `catppuccin-latte`, etc. Since theme-set copies this file into the user's nvim config, everyone on the default post-upgrade theme hits the error.

Fix: `colorscheme = "catppuccin"`. The other shipped themes' neovim.lua files all use valid names; catppuccin is the only one affected.

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.