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

Theme color inconsistencies after 3.5.0

Reported by felixzsh · filed Apr 6, 2026Closed upstream on 2026-04-22 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Theme color inconsistencies after 3.5.0revision 1 · captured 2026-10-04 11:49 UTC via poll

System details

thinkpad x1 carbon gen7

What's wrong?

After updating to 3.5.0, both LazyVim and lazygit seem to have broken theme colors, specifically with Catppuccin (my main theme).

Example in NeoTree:

<img width="403" height="679" alt="Image" src="https://github.com/user-attachments/assets/a3815ab1-80ed-4fba-8309-29d94b5bdd2a" />

Unstaged files used to be purple, now they're orange.

Modified files no longer have a distinct color, they appear the same as folders (default blue), whereas before they were yellow.

This makes it much harder to quickly recognize file states.

I understand this might sound picky, but it's frustrating when an update changes how a theme’s colors work compared to what I was used to. If there’s a specific fix or config tweak to restore the previous behavior, I’d really appreciate it.

View raw text
### System details

thinkpad x1 carbon gen7

### What's wrong?

After updating to 3.5.0, both LazyVim and lazygit seem to have broken theme colors, specifically with Catppuccin (my main theme).

Example in NeoTree:

<img width="403" height="679" alt="Image" src="https://github.com/user-attachments/assets/a3815ab1-80ed-4fba-8309-29d94b5bdd2a" />

Unstaged files used to be purple, now they're orange.

Modified files no longer have a distinct color, they appear the same as folders (default blue), whereas before they were yellow.

This makes it much harder to quickly recognize file states.

I understand this might sound picky, but it's frustrating when an update changes how a theme’s colors work compared to what I was used to. If there’s a specific fix or config tweak to restore the previous behavior, I’d really appreciate it.
  • a3815ab1-80ed-4fba-8309-29d94b5bdd2a

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.