Route OpenCode/Pi install prompts through /dev/tty too

[winjer]

Follow-up to #9. The email prompt still didn't fire under curl -sfL .../install.sh | bash for anyone who has OpenCode or Pi installed.

Root cause: #9 fixed only the email prompt. The earlier "Install OpenCode/Pi plugin? [y/N]" prompts still ran read -p … -r reading from stdin — which under curl | bash is the pipe carrying the script. That read consumed the rest of the piped script and execution desynced, so create_config (and its /dev/tty email prompt) was never reached. Reproduced: the run stops right after "OpenCode detected… Install the code-trace plugin?" with no config written.

Fix: resolve the interactive input source once (resolve_tty_in → TTY_IN) and route all three prompts through it — reading from the controlling terminal under curl | bash, and skipping the prompt entirely when no terminal exists (CI/unattended) rather than reading from the script pipe.

Verified (bash reading the script from a real pipe, controlling terminal via a pty):

• OpenCode present, decline plugin → reaches email prompt, writes it ✓ (the reported case)
• OpenCode present, accept plugin → installs, then email prompt ✓
• Pi present → prompts, then email ✓
• no controlling terminal (setsid/CI) → skips all prompts, does not hang ✓
• no agents, blank email → skips, commented placeholder ✓

Existing installer hook-registration test still passes.

🤖 Generated with Claude Code