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.
Create a contributor's guide (CONTRIBUTING.md)
Reported by flaviolivolsi · filed Sep 29, 2025Closed upstream on 2025-11-03. 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
As mentioned in PR #2072 a contributor's guide would be useful. This issue is to track that effort.
As a new contributor I ran into a few points of uncertainty that a guide could clarify. Having a CONTRIBUTING.md would make it easier for new people to submit high-quality PRs and reduce the review burden on maintainers.
Some potential topics to cover:
- Branching strategy: clarification on the default branch for PRs (currently seems to be
deveven though it might be just temporary). - Migrations: guidelines on creating and testing migrations for existing installations
- Code style: clarification on any linters, formatters or general style guidelines in use if any
- Setting up a dev environment: any specific steps needed to test changes locally
Happy to help contribute to a draft once a direction is decided!
View raw text
As mentioned in PR #2072 a contributor's guide would be useful. This issue is to track that effort. As a new contributor I ran into a few points of uncertainty that a guide could clarify. Having a `CONTRIBUTING.md` would make it easier for new people to submit high-quality PRs and reduce the review burden on maintainers. Some potential topics to cover: * **Branching strategy:** clarification on the default branch for PRs (currently seems to be `dev` even though it might be just temporary). * **Migrations:** guidelines on creating and testing migrations for existing installations * **Code style:** clarification on any linters, formatters or general style guidelines in use if any * **Setting up a dev environment:** any specific steps needed to test changes locally Happy to help contribute to a draft once a direction is decided!
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.