fix(upgrade skills): run abra over a pseudo-TTY (fixes FATA inappropriate ioctl)

abra over plain 'ssh cc-ci abra ...' has no TTY -> FATA 'inappropriate ioctl
for device' (the abra error). The working harness (runner/harness/abra.py)
wraps abra in util-linux 'script' for a pseudo-TTY + passes -n. Apply the
same in the recipe-upgrade and upgrade-all skills: every abra call becomes
ssh cc-ci 'script -qec "abra <args> -n" /dev/null'. Confirmed: abra server
ls FATAs plain, works pty-wrapped.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.claude/skills/upgrade-all/SKILL.md

@@ -30,12 +30,16 @@ Enrolled recipes = the cc-ci `tests/<recipe>/` dirs (same set `ci-test-review` s
 ```
 ssh cc-ci 'cd /root/cc-ci/tests && ls -d */' | sed 's#/##' | grep -vE '^(_generic|unit|__pycache__)$'
 ```
-(or the names passed in `$ARGUMENTS`). For each, on cc-ci, check availability — skip dirty/up-to-date:
+(or the names passed in `$ARGUMENTS`). For each, on cc-ci, check availability — skip dirty/up-to-date.
+
+> ⚠️ **Run abra over a pseudo-TTY** or it FATAs `inappropriate ioctl for device` (no TTY under plain
+> ssh). Wrap every abra call in `script` (the working-harness fix in `runner/harness/abra.py`) and pass
+> `-n`: `ssh cc-ci 'script -qec "abra <args> -n" /dev/null'`. `git`/other commands need no wrapper.
 ```
 ssh cc-ci 'export PATH=/run/current-system/sw/bin:$PATH; \
   git -C ~/.abra/recipes/<r> status --short; \
-  abra recipe fetch <r> --force; \
-  abra recipe upgrade <r> -m -n'
+  script -qec "abra recipe fetch <r> --force -n" /dev/null; \
+  script -qec "abra recipe upgrade <r> -m -n" /dev/null'
 ```
 Build `RECIPES_TO_UPGRADE` = recipes with a **clean worktree** AND **≥1 available upgrade**. Others go
 to `SKIPPED_UPFRONT` with a reason (`dirty-worktree`, `up-to-date`, `not-fetchable`).
@@ -103,7 +107,8 @@ End with the report path and a reminder that **nothing was merged**.
 ## Safety / coordination (this matters — shared host with the build loops)
 - **Sequential is the default for a reason.** Recipe deploys are **stateful on the shared Swarm** and
   parallel deploys can OOM/collide. Between sequential recipes, the per-recipe `recipe-upgrade` tears
-  down what it deployed; verify a recipe is undeployed before the next starts (`abra app ls` on cc-ci).
+  down what it deployed; verify a recipe is undeployed before the next starts
+  (`ssh cc-ci 'script -qec "abra app ls -n" /dev/null'` — pseudo-TTY wrapped, per the box above).
 - **Single-writer:** every PR (recipe or cc-ci test) is on a dedicated branch; **never push `main`**,
   never touch the build loops' `/cc-ci` `/cc-ci-adv` working clones or their in-flight state.
 - **Contention with active loop development:** while the loops are still building cc-ci, this run