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.
Native iOS Development support
Reported by rplankenhorn · filed Oct 6, 2025Closed upstream on 2025-10-06. 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
What do you need?
I realize this is a very lofty goal given the closed iOS Development ecosystem but shouldn't we at least try? I am a mobile developer (iOS Native and React Native) and this would allow me to completely switch over to using Omarchy 100% if this was supported.
Most current options use a VM so if that has to be the approach, maybe there is a way to "hide" the VM?
View raw text
### What do you need? I realize this is a very lofty goal given the closed iOS Development ecosystem but shouldn't we at least try? I am a mobile developer (iOS Native and React Native) and this would allow me to completely switch over to using Omarchy 100% if this was supported. Most current options use a VM so if that has to be the approach, maybe there is a way to "hide" the VM?
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
- Related PRpr/14255· confirmed
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.