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.
test/cli vscode assert expects a symlink that 977e0fcd replaced with a real file
Reported by anandude · filed Sep 24, 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
On current quattro, ./test/cli fails with:
not ok - vscode generated theme references current theme filetest/cli:580-581 asserts omarchy-color-theme.json is a symlink into current/theme/vscode-theme.json. But 977e0fcd ("Make VS Code-family editors reload the Omarchy theme when it changes") deliberately switched install_generated_extension to a real file — a symlink would dangle while omarchy-theme-set swaps current/theme via rm + mv, and the _watch watcher needs a same-inode rewrite. The script even documents this in a comment at bin/omarchy-theme-set-vscode:76-81.
Reproduced on a clean quattro checkout (28ceaae7); the failure is independent of any other change. Either the test should assert a real file matching the generated theme, or the script should go back to a symlink (which would reintroduce the dangling-watch problem).
View raw text
On current quattro, ./test/cli fails with:
```
not ok - vscode generated theme references current theme file
```
test/cli:580-581 asserts `omarchy-color-theme.json` is a symlink into `current/theme/vscode-theme.json`. But 977e0fcd ("Make VS Code-family editors reload the Omarchy theme when it changes") deliberately switched install_generated_extension to a real file — a symlink would dangle while omarchy-theme-set swaps current/theme via rm + mv, and the _watch watcher needs a same-inode rewrite. The script even documents this in a comment at bin/omarchy-theme-set-vscode:76-81.
Reproduced on a clean quattro checkout (28ceaae7); the failure is independent of any other change. Either the test should assert a real file matching the generated theme, or the script should go back to a symlink (which would reintroduce the dangling-watch problem).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 17:55 UTC