Fix bar::units-shell / bar::lx-shell on hosts without script(1)

[keithharvey]

Problem

just bar::units-shell and just bar::lx-shell fail immediately on some hosts:

scripts/common.sh: line 250: exec: script: not found
error: recipe `units-shell` failed with exit code 127

distrobox_exec_interactive wrapped distrobox enter in script -qec to force a PTY. Fedora ships script(1) in a separate util-linux-script subpackage rather than in util-linux, and image-based distros don't necessarily include it. Bazzite 44 doesn't, so both recipes are unusable there and there's no clean way to layer a package in just to get them back.

Worth noting the container side is unaffected — fedora:43 (our dev.Containerfile base) does pull in util-linux-script, so script exists inside bar-dev but not outside it. The failure is purely host-side.

Fix

Drop the wrapper and call distrobox enter directly.

The PTY wrapper was never load-bearing. A just recipe inherits the caller's terminal on both stdin and stdout, and distrobox-enter allocates a tty itself — it only falls back to headless when it finds neither (if [ ! -t 0 ] || [ ! -t 1 ]). Wrapping it in script just added a host dependency to get a tty that was already there.

Calling it directly also removes the printf %q quoting loop, which existed only because script parses its argument through /bin/sh. Passing argv straight through needs no quoting.

Verification

On Bazzite 44 (host has no script(1)), driving just bar::units-shell under a real pty:

[ok]    Entering lx test shell (busted on PATH).
...
❯ which busted && busted --version
~/code/Beyond-All-Reason/.lux/5.1/test_dependencies/5.1/bin/busted
2.2.0

Confirmed separately that a just recipe sees STDIN_TTY / STDOUT_TTY, and that distrobox enter under a pty passes the tty through to the command (tty reports /dev/pts/0, test -t 0 succeeds).

just doctor clean, 23 passed.

LLM Disclosure

Diagnosed and drafted with Claude Code; reviewed and verified by me on the affected host.