omarchy-terminal

Version	2026.242.0000
Repo	box/github.com/opencharly/layer-omarchy-terminal:v2026.242.0616

Omarchy’s terminal and the command-line tools its shipped shell configuration and desktop entries actually consume. omarchy-terminal installs foot — the terminal Omarchy’s Hyprland bindings and xdg-terminal-exec launch — plus starship, whose init the shipped rc sources, and the modern coreutils that rc names. Read off the built image rather than assumed: eza, fzf, bat and zoxide are referenced by /usr/share/omarchy/default/bash/{aliases,init,envs}, and dua by the “Disk Usage” desktop entry. Three of those four rc references are guarded by command -v, so a missing binary degrades silently — the alias or key-binding simply never gets defined. bat is the exception: envs exports MANPAGER=“sh -c ‘col -bx | bat -l man -p’” UNGUARDED, so without bat every man invocation breaks. fd, ripgrep, tldr, inxi, qrencode and zbar are in Omarchy’s own base package list but are named by neither the rc nor any omarchy-* command; they are installed for parity with upstream, and this description does not claim the shell needs them. Verifiable on the built image: every binary is on PATH and MANPAGER’s interpreter resolves.

Acceptance plan

This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.

Intent	Step
check	the terminal the desktop’s bindings launch is installed
check	the prompt the shipped shell configuration initialises is installed
check	every command-line tool this candy declares is on PATH
check	the unguarded MANPAGER the shipped rc exports actually runs
check	the Omarchy-published TUIs resolved from the [omarchy] repository