Proof Portal
Omarchy
omarchy75 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.
A top-level JSON array is not an object map of menu entries.
component menu · guarantee · assurance level C
What it says
A top-level JSON array is not an object map of menu entries. The parser returns an empty item set for it, as it does for every other non-object root. No phantom rows with numeric ids appear.
when array_root_present the menu_model shall always satisfy array_root_rejectedWhere it sits
- Parent
- SYS-REQ-260922-PPDW
- Satisfies
- SYS-REQ-260922-PPDW
- Component
- menu
- Traces at the evaluated commit
- 1 implemented by · 1 satisfies · 1 verified by
- Fields this change sets
- status, priority, category, req_type, fretish, description, formalization_strategy, parent, component, rationale, variables, traces.satisfies, verification.assurance_level, verification.formalization_status
Evidence in this change
Changed as intended — Not observed · 1 test: 0 passed · 0 failed · 1 without a pass/fail outcome
Obligations
| Kind of evidence | From | Observed | Tests |
|---|---|---|---|
| Boundary | inherited from SYS-REQ-260922-PPDW | No test linked yet | 0 · 0✓ 0✗ 0∅ |
| Error handling | inherited from SYS-REQ-260922-PPDW | No test linked yet | 0 · 0✓ 0✗ 0∅ |
| Malformed input | its own checklist | No outcome recorded | 1 · 0✓ 0✗ 0∅ |
Tests that verify it 1
- test/shell.d/menu-test.shunknown
Code it is traced to
- Changed functions
- shell/plugins/menu/MenuModel.js:parseMenuJsonc
- Implemented by
- shell/plugins/menu/MenuModel.js:parseMenuJsonc
- Changed files (2)
- shell/plugins/menu/MenuModel.js
- test/shell.d/menu-test.sh
What to check in review
- Confirm the new requirement is needed, sits in the right part of the spec, and is labeled with the right kind of rule and concern.
- Check that parent decomposition and planned implementation/test/doc evidence are intentional before merge.
- Make sure lifecycle state is merge-ready and not left as unfinished authoring work.
Every fact on this page comes from the evidence package sha256:8ea75a1e1f0a…