R ress v1.2.0 8d ago

A launcher's Exec line is read as an argument list, so the three forms Omarchy has written parse: a bare URL, a bare URL followed by browser flags, and the quoted URL the current installer writes. A quoted launcher, and one carrying a Chromium profile flag, used to be captured and then refused on the machine that needed them — and the launchers Omarchy ships were captured in their place, so the category travelled the wrong set in both directions.
A launcher byte-identical to one in /usr/share/omarchy/applications is not captured: it is not this machine's state, and a fresh install has it already.
Browser flags and the omarchy-launch-or-focus-webapp form travel through the installer's custom-exec argument, assembled from validated pieces rather than copied out of the vault. A launcher whose second word is a command is refused.
An Exec line longer than a launcher could need (1024 bytes) is refused unread, so a fetched vault cannot buy a stall with one.
A launcher a restore cannot rebuild is named at capture, listed as refused by ress verify, and left out of a shared loadout rather than published.

ress status --json no longer exits 2 with no output when a setting holds a value it does not expect (INCLUDE_OMARCHY=, AUTO_INTERVAL_HOURS=24h), when the last-backup stamp is not a number, or when a vault's manifest is not JSON. The panel reads nothing but this command, so a blank panel was the visible symptom.

Changelog