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.
logging for upgrades (and for other commands?)
Reported by Dieterbe · filed Dec 2, 2025Closed upstream on 2025-12-08 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
omarchy 3.2.2
What's wrong?
i notice that updates don't log anything
i think we should log the output somewhere persistent, because the text scrolls by too fast.
open questions:
1) should we use the user journal? or text files into the home directory?
2) should multiple omarchy-* scripts be able to log in a unified way? maybe on a per-app-id level?
View raw text
### System details omarchy 3.2.2 ### What's wrong? i notice that updates don't log anything i think we should log the output somewhere persistent, because the text scrolls by too fast. open questions: 1) should we use the user journal? or text files into the home directory? 2) should multiple `omarchy-*` scripts be able to log in a unified way? maybe on a per-app-id level?
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.