Fix reliable TUI startup and Rust release commits

[konard]

Summary

• expose pre-prompt TUI interactions for first-run/workspace-trust dialogs
• default PTY launches to TERM=xterm-256color, preserving caller overrides
• inspect git diff --cached --quiet exit codes instead of expecting command-stream to throw
• restore the already-published Rust 0.2.7 version and collected changelog on main
• cover startup ordering plus clean, changed, and fatal git-diff outcomes with regression tests

Root causes

Real clients can display startup gates before their prompt. Sending a prompt at the first output event loses it before OpenCode is ready and cannot clear Claude/Codex trust dialogs. Codex additionally refuses its TUI under the TERM=dumb commonly inherited in CI.

Separately, command-stream resolves commands with nonzero exit codes. The Rust release script treated the resolved exit-1 result from git diff --quiet as a clean index, so it published the modified working tree but skipped the version/changelog commit.

Verification

• npm test (237 passing)
• focused ESLint on changed source/tests
• cargo check --locked
• Prettier check for changed JavaScript/Markdown files