# Stage 5 installer controlling terminal correction

2026-10-12. The user reports `sudo: a terminal is required to read the
password` from the nine-runtime home installer. Both hosts still have all
nine root payloads missing; their staged hash checks pass.

`host-cpu-slot` supervises its command with `start_new_session=True`. The
previous installer put `sudo -v` in that new session, which loses the SSH
controlling terminal even when its stdin/stdout remain terminal descriptors.
The user's error is consistent with that exact process boundary.

The corrected [maintained installer](../../../ops/scripts/install-fullbench-stage5-next.sh)
allocates a controlling terminal using util-linux `script` **inside** the
CPU lease. It preserves child exit codes, disables input echo and discards
the transcript at `/dev/null`. Password entry stays in the user's terminal.
HP admission retains high priority; busy leases still queue. Fixed installers,
root ownership checks, all nine runtime hashes and post-install validation
remain unchanged. Progress messages now say nine rather than eight.

Four actual probes execute the corrected wrapper on HP and SCAN under real
shared CPU leases and SSH terminals. On each host the child can open
`/dev/tty`, stdin/stdout are terminals, and exits **0 and 7** propagate
unchanged. No probe runs sudo or a root installation. Both hosts then pass
all nine staged runtime checks. The home copy has been replaced with the
verified source and remains executable.

[Original script, probe logs, corrected source and seal](evidence/installer-terminal-20261012/retention-seal.json)
retain this correction without changing previous sealed evidence. Root
installation still requires the user's interactive run:

```sh
~/install-fullbench-stage5-next.sh
```