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.
Clock panel: hero date clipped by the card border when [font] base-size is below 12
Reported by St1aan · filed Sep 27, 2026 · open at source
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
What happened
With [font] base-size set below the default of 12, the clock panel's hero date is clipped by the card's right border. At base-size = 9 (fontScale 0.75) the month name runs straight through the border — "September 26" renders as "September 2" plus a cut-off glyph.
Why
The card's width scales with the font, but the hero text does not.
Commons/Style.qml:
readonly property real effectiveSpacingScale: spacingScale * (spacingScaleWithFont ? fontScale : 1)
readonly property real fontScale: Math.max(1 / 12, fontBaseSize / 12)plugins/panels/clock/Panel.qml sizes the card through that scale:
contentWidth: panel.fittedContentWidth(Style.space(560))but the hero row is hardcoded outside it:
Text { // calendar glyph
font.pixelSize: 48
}
Text {
id: heroDate
text: Qt.formatDate(root.today, "MMMM d")
font.pixelSize: 52
font.bold: true
}So at base-size = 9 the card drops from 560 to 420px while the hero stays at 52px, and the longest month names no longer fit. The same mismatch presumably affects any panel that pairs Style.space() geometry with a hardcoded pixelSize.
The comment on the glyph says the size is "deliberately outside the Style.font.* scale" — that is reasonable for the ratio between the glyph and the digits, but it still needs to scale with the card that contains it.
Steps to reproduce
- Put this in
~/.config/omarchy/shell.toml:
[font]
base-size = 9- Restart the shell:
omarchy restart shell - Open the calendar (click the clock in the bar) during a month with a long name — September, November, December.
Worse at smaller base sizes; at 12 (default) it fits.
Expected
The hero date stays inside the card at any base-size, either by scaling pixelSize with fontScale or by fitting the text to the card (fontSizeMode: Text.HorizontalFit).
Screenshots
base-size = 9, before — clipped:
<!-- attach omarchy-clock-hero-clipped-before.png -->
Same setting with [spacing] scale-with-font = false, which restores the card to 560px and is the workaround I am using:
<!-- attach omarchy-clock-hero-clipped-after.png -->
System
| Omarchy | 4.0.4-1 |
| Kernel | 7.2.5-3-omarchy |
| CPU | Intel Core i7-6820HQ |
| GPU | Intel HD Graphics 530 (Skylake-H GT2) |
| Hyprland | 0.56.2 |
| Quickshell | 0.3.1 (Arch) |
| Display | 3840x1080 @ 60Hz, scale 1 |
omarchy debug does not exist in 4.0.4 (Unknown Omarchy command), so the above is collected by hand.
View raw text
## What happened
With `[font] base-size` set below the default of 12, the clock panel's hero date is clipped by the card's right border. At `base-size = 9` (fontScale 0.75) the month name runs straight through the border — "September 26" renders as "September 2" plus a cut-off glyph.
## Why
The card's width scales with the font, but the hero text does not.
`Commons/Style.qml`:
```qml
readonly property real effectiveSpacingScale: spacingScale * (spacingScaleWithFont ? fontScale : 1)
readonly property real fontScale: Math.max(1 / 12, fontBaseSize / 12)
```
`plugins/panels/clock/Panel.qml` sizes the card through that scale:
```qml
contentWidth: panel.fittedContentWidth(Style.space(560))
```
but the hero row is hardcoded outside it:
```qml
Text { // calendar glyph
font.pixelSize: 48
}
Text {
id: heroDate
text: Qt.formatDate(root.today, "MMMM d")
font.pixelSize: 52
font.bold: true
}
```
So at `base-size = 9` the card drops from 560 to 420px while the hero stays at 52px, and the longest month names no longer fit. The same mismatch presumably affects any panel that pairs `Style.space()` geometry with a hardcoded `pixelSize`.
The comment on the glyph says the size is "deliberately outside the `Style.font.*` scale" — that is reasonable for the ratio between the glyph and the digits, but it still needs to scale with the card that contains it.
## Steps to reproduce
1. Put this in `~/.config/omarchy/shell.toml`:
```toml
[font]
base-size = 9
```
2. Restart the shell: `omarchy restart shell`
3. Open the calendar (click the clock in the bar) during a month with a long name — September, November, December.
Worse at smaller base sizes; at 12 (default) it fits.
## Expected
The hero date stays inside the card at any `base-size`, either by scaling `pixelSize` with `fontScale` or by fitting the text to the card (`fontSizeMode: Text.HorizontalFit`).
## Screenshots
`base-size = 9`, before — clipped:
<!-- attach omarchy-clock-hero-clipped-before.png -->
Same setting with `[spacing] scale-with-font = false`, which restores the card to 560px and is the workaround I am using:
<!-- attach omarchy-clock-hero-clipped-after.png -->
## System
| | |
|---|---|
| Omarchy | 4.0.4-1 |
| Kernel | 7.2.5-3-omarchy |
| CPU | Intel Core i7-6820HQ |
| GPU | Intel HD Graphics 530 (Skylake-H GT2) |
| Hyprland | 0.56.2 |
| Quickshell | 0.3.1 (Arch) |
| Display | 3840x1080 @ 60Hz, scale 1 |
`omarchy debug` does not exist in 4.0.4 (`Unknown Omarchy command`), so the above is collected by hand.
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/11639· confirmed
- Fixed bypr/13459· 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 18:58 UTC