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.
Calendar grid duplicates September 5 and shifts dates in month view
Reported by Arturo387 · filed Sep 1, 2026Closed upstream on 2026-10-11 by the merge of PR #10476 (closed by omarchybot, a bot). GitHub close reason: completed.
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Summary
The Omarchy calendar popup is rendering dates out of alignment in the month grid. In September 2026, the date 5 appears twice in the same month: once as the last Saturday cell in one row and again as the first Sunday cell in the next row. That causes the remaining dates to shift by one day for the rest of the month.
Screenshot
Local file captured during reproduction:/home/arturo/Pictures/screenshot-2026-09-01_11-46-58.png
Expected behavior
September 2026 should render as a normal month grid with each date appearing exactly once in the correct weekday slot.
Actual behavior
The popup shows the following sequence in the grid (from the screenshot):
- Week 36:
30 31 1 2 3 4 5 - Week 37:
5 6 7 8 9 10 11
The duplicate 5 is clearly wrong: the first 5 is September 5, but the second 5 is actually the next row's Sunday-started cell, which shifts the remaining dates.
Evidence
- The issue reproduces in the stock Omarchy shell widget, not in the custom user plugin.
- The month-grid logic is implemented in
/usr/share/omarchy/shell/plugins/panels/clock/Model.js. - The render is done in
/usr/share/omarchy/shell/plugins/panels/clock/Panel.qml. - The code intentionally builds a fixed 6x7 month grid and uses
monthGrid(year, month, weekStart, todayKey)to populate it. - This mismatch is visible in the screenshot and makes the following dates invalid for September 2026.
Relevant code references
/usr/share/omarchy/shell/plugins/panels/clock/Model.jsfunction monthGrid(year, month, weekStart, todayKey) { ... }var leading = (new Date(year, month, 1).getDay() - start + 7) % 7var cursor = new Date(year, month, 1 - leading)/usr/share/omarchy/shell/plugins/panels/clock/Panel.qmltext: Qt.formatDate(root.viewDate, "MMMM yyyy").toUpperCase()Repeater { model: root.weeks }and day cells rendering the month grid
Environment
- OS: Omarchy
- Shell widget:
omarchy.clock - Locale:
en_US.UTF-8 - User config:
/home/arturo/.config/omarchy/shell.json
Notes
This is not caused by the custom plugin arturo.system-monitor; the bug persists in the stock calendar widget itself.
View raw text
### Summary
The Omarchy calendar popup is rendering dates out of alignment in the month grid. In September 2026, the date `5` appears twice in the same month: once as the last Saturday cell in one row and again as the first Sunday cell in the next row. That causes the remaining dates to shift by one day for the rest of the month.
### Screenshot
Local file captured during reproduction:
`/home/arturo/Pictures/screenshot-2026-09-01_11-46-58.png`
### Expected behavior
September 2026 should render as a normal month grid with each date appearing exactly once in the correct weekday slot.
### Actual behavior
The popup shows the following sequence in the grid (from the screenshot):
- Week 36: `30 31 1 2 3 4 5`
- Week 37: `5 6 7 8 9 10 11`
The duplicate `5` is clearly wrong: the first `5` is September 5, but the second `5` is actually the next row's Sunday-started cell, which shifts the remaining dates.
### Evidence
- The issue reproduces in the stock Omarchy shell widget, not in the custom user plugin.
- The month-grid logic is implemented in `/usr/share/omarchy/shell/plugins/panels/clock/Model.js`.
- The render is done in `/usr/share/omarchy/shell/plugins/panels/clock/Panel.qml`.
- The code intentionally builds a fixed 6x7 month grid and uses `monthGrid(year, month, weekStart, todayKey)` to populate it.
- This mismatch is visible in the screenshot and makes the following dates invalid for September 2026.
### Relevant code references
- `/usr/share/omarchy/shell/plugins/panels/clock/Model.js`
- `function monthGrid(year, month, weekStart, todayKey) { ... }`
- `var leading = (new Date(year, month, 1).getDay() - start + 7) % 7`
- `var cursor = new Date(year, month, 1 - leading)`
- `/usr/share/omarchy/shell/plugins/panels/clock/Panel.qml`
- `text: Qt.formatDate(root.viewDate, "MMMM yyyy").toUpperCase()`
- `Repeater { model: root.weeks }` and day cells rendering the month grid
### Environment
- OS: Omarchy
- Shell widget: `omarchy.clock`
- Locale: `en_US.UTF-8`
- User config: `/home/arturo/.config/omarchy/shell.json`
### Notes
This is not caused by the custom plugin `arturo.system-monitor`; the bug persists in the stock calendar widget itself.
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
- Fixed bypr/12943· confirmed
- Fixed bypr/10476· confirmed
- Fixed bypr/13186· confirmed
- Fixed bypr/13751· confirmed
- Fixed bypr/13096· confirmed
- Fixed bypr/13127· 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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:27 UTC