greetd's session worker hands the login session a minimal environment, so start-cosmic got
PATH=/usr/bin and everything below it inherited that: the compositor, the panel, every app
launched from the panel, and anything those apps fork. The per-user bin dirs that ~/.local/bin
adds (uv, cargo, pip --user) existed for a terminal and nowhere else. It showed up as an agent
started from the panel running with PATH=/usr/bin, where uv was "command not found" and every
uv run in its child shells failed, while the identical command worked in a terminal on the same
machine. Nothing in the output pointed at the environment. start-cosmic now prepends the comfort
profile's directories in the same order, dedupes them, and defaults to /usr/bin so an unset PATH
can't leave an empty component behind. A test asserts the two lists are equal, so a terminal and a
GUI app can't drift to resolving different binaries.
pengyos-postmortem answers a question that used to cost an evening. On a Desktop, an entire COSMIC
session vanished in an instant: every app gone, the login screen back, no reboot. The answer was four
lines in a 6,705-line journal, including a user manager that deactivated without the
Stopping User Manager line a logout produces. Now one command reads the boot's journal
(unprivileged, no writes) and returns one of five verdicts, broadcast signal, logout, out of memory,
single process, or unknown, with the affected processes named and the alternatives reported as found
or "no evidence". strace and unshare joined Core for the same reason: the image could neither
trace a syscall nor run an experiment safely in a private PID namespace, so a fact had to be
reported as "I couldn't demonstrate it live".
sudo pengyos-webui on [USER] runs the Pengy web UI as you at boot, answering on
127.0.0.1:5000; off takes it out of the boot; status says what's running, where. It runs as
the human on purpose, which means no DynamicUser and no ProtectHome, because those hide the
agent's own config, skills and secrets. It's a system unit, so it also comes up on a headless Server
where nobody has logged in. The UI has no login and exposes shell and Python execution, so the bind
stays 127.0.0.1 by default and --host is a typed, documented, unauthenticated network bind that
status prints every time.