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.
Documentation: Writebook thinks [email protected] is an email address
Reported by ardavis · filed Aug 28, 2025Closed upstream on 2025-08-28 by its own reporter ardavis. GitHub close reason: completed. Closed by its own reporter — not by itself 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
In the Development Tools -> Environment section:
To install, say, Ruby 3.3, you'd run mise use -g [email protected], which will both install Ruby 3.3 and set it as the global default.
It looks like [email protected] is being replaced with [email protected].
View raw text
In the Development Tools -> [Environment](https://learn.omacom.io/2/the-omarchy-manual/62/development-tools?search=mise#environment) section: > To install, say, Ruby 3.3, you'd run mise use -g [email protected], which will both install Ruby 3.3 and set it as the global default. It looks like `[email protected]` is being replaced with `[email protected]`.
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.