`omarchy update -y` blocks indefinitely at `Remove N orphaned package(s)?`. The package upgrade itself completes; the run then stops at the orphan step and waits forever.

`-y` sets `OMARCHY_UPDATE_UNATTENDED=1`, documented in `omarchy-update` as "a promise not to ask anything. Steps that would need an answer report and move on instead of waiting on a prompt nobody is here to give."

## Cause

`omarchy-update-orphan-pkgs` guards on the TTY only:

```bash
if [[ ! -t 0 || ! -t 1 ]]; then
  echo "${#orphans[@]} orphaned package(s) found. Re-run omarchy-update-orphan-pkgs in a terminal to review/remove them."
  echo
  exit 0
fi

if ! gum confirm --default=false "Remove ${#orphans[@]} orphaned package(s)?"; then
```

That guard is correct when the script is called directly, but `omarchy-update` re-execs itself under `script(1)` to capture the transcript (`omarchy-update:12`):

```bash
exec env OMARCHY_UPDATE_LOGGED=1 script -qefc "$script_command" "/tmp/omarchy-update.log"
```

`script` allocates a pseudo-TTY, so `-t 0` and `-t 1` are true regardless of how the update was invoked. The guard never fires, and `gum confirm` prompts into a PTY nobody is attached to.

```console
$ bash -c '[[ -t 0 && -t 1 ]] && echo TTY || echo no-TTY' < /dev/null
no-TTY

$ script -qefc 'bash -c "[[ -t 0 && -t 1 ]] && echo TTY || echo no-TTY"' /dev/null < /dev/null
TTY
```

## Suggested fix

`omarchy-update-system-pkgs-when-conflicted:74` already has the pattern:

```bash
if [[ ${OMARCHY_UPDATE_UNATTENDED:-} == 1 || ! -t 0 || ! -t 2 ]]; then
```

Adding the same clause to `omarchy-update-orphan-pkgs` would fix it:

```bash
if [[ ${OMARCHY_UPDATE_UNATTENDED:-} == 1 || ! -t 0 || ! -t 1 ]]; then
```

`omarchy-update-restart` has the same shape (a bare `gum confirm` with no guard). It only prompts on a kernel change or a `reboot-required` marker so it is hit less often, but `-y` would block there too.

## Environment

- omarchy 4.0.1-1
- kernel 7.1.9-arch1-2