Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-2179GitHub issuePublicDecided· Out of scope

omarchy update: prune mise tool versions with the same keep-two strategy as the package cache

Reported by shirgall · filed Oct 2, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

omarchy update: prune mise tool versions with the same keep-two strategy as the package cacherevision 1 · captured 2026-10-02 14:13 UTC via poll

What happens

omarchy update prunes the pacman cache (omarchy-update-pkg-prune runs paccache -rk2 before packages update, so the installed version survives with one spare). The mise step (omarchy-update-mise) only runs MISE_MINIMUM_RELEASE_AGE=0 mise up, and install/user/mise.sh sets upgrade.auto_prune false. Nothing ever removes old mise installs, so every update leaves the previous version behind indefinitely.

On my machine ~/.local/share/mise/installs had accumulated nine versions of npm:@xai-official/grok (1.0.13 through 1.0.46), plus older Python and codex installs, until I ran mise prune by hand.

Expected

mise tools follow the same retention strategy as the main update: keep the current version plus one spare, prune the rest.

Suggestion

The reason for disabling auto_prune still holds (don't delete the version a running session is executing from), and the pacman step already shows how to respect that: prune before upgrading. In omarchy-update-mise:

mise prune --yes   # drops versions older than the one currently active
MISE_MINIMUM_RELEASE_AGE=0 mise up

The currently active version is still referenced at prune time, so it survives; after mise up it becomes the one spare. Running sessions keep their install dir until the next update, which mirrors paccache -rk2 behavior.

Environment

  • Omarchy 4.0.4-1 (Surface Go 3)
  • mise 2026.9.14
View raw text
## What happens

`omarchy update` prunes the pacman cache (`omarchy-update-pkg-prune` runs `paccache -rk2` before packages update, so the installed version survives with one spare). The mise step (`omarchy-update-mise`) only runs `MISE_MINIMUM_RELEASE_AGE=0 mise up`, and `install/user/mise.sh` sets `upgrade.auto_prune false`. Nothing ever removes old mise installs, so every update leaves the previous version behind indefinitely.

On my machine `~/.local/share/mise/installs` had accumulated nine versions of `npm:@xai-official/grok` (1.0.13 through 1.0.46), plus older Python and codex installs, until I ran `mise prune` by hand.

## Expected

mise tools follow the same retention strategy as the main update: keep the current version plus one spare, prune the rest.

## Suggestion

The reason for disabling `auto_prune` still holds (don't delete the version a running session is executing from), and the pacman step already shows how to respect that: prune *before* upgrading. In `omarchy-update-mise`:

```bash
mise prune --yes   # drops versions older than the one currently active
MISE_MINIMUM_RELEASE_AGE=0 mise up
```

The currently active version is still referenced at prune time, so it survives; after `mise up` it becomes the one spare. Running sessions keep their install dir until the *next* update, which mirrors `paccache -rk2` behavior.

## Environment

- Omarchy 4.0.4-1 (Surface Go 3)
- mise 2026.9.14

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 20:41 UTC