tui: worktree setup progress for the open thread

[krishhgg]

Shows the selected thread's worktree setup under its first prompt, with stage status and elapsed time, checkout progress, the last four script-output lines, and expandable branch, base, path and command details. Press w in the transcript or click Details. A script still running after the agent starts has a compact row whose Details opens the stages.

Stacked on #26. Merge order is #23, #24, #25, #26, then #27. Only the user merges.

Sol verified formatting, strict Clippy and all 376 tests at 74d9f68. The new regression fails on the old implementation at 90f6f50 and passes with the fix. The connecting, reconnecting and reopening control passes on both. CI passes on macOS and Linux, and Greptile has resolved its sole finding.

Verification and seven captures · 18-second capture slideshow

The gallery records source 621e8ac. The later fix changes subscription eligibility only. Sol also tested 74d9f68 in the real TUI against the isolated fake server: closed worktree and preparing-run watches stayed closed through later shell updates, retained cards caused no idle output between samples, and switching away and back opened one fresh setup watch.

What I noticed

#26 supplied the progress stream, but the TUI showed no setup card or failure output.

How I confirmed it

Compared the pinned nightly f570bd2 contracts, WorktreeSetupTracker.ts, worktreeSetup.ts, ChatView.tsx, MessagesTimeline.logic.ts and WorktreeSetupCard.tsx. Sol checked lifecycle changes, Details controls, thread switches, sequence resets, reconnects, refusals, Unicode, control text and resize/draft preservation down to 10×5.

Options

Reuse #26's read-only subscription and keep one bounded setup per open thread. Place the card in the transcript, with an inline expandable row for a background script. Compare progress sequences within a subscription epoch because null and a server restart can reset them. Keep normal eligibility changes reversible; skip permanently closed thread watches.

What review changed

Sol corrected README claims about offscreen Details controls and elapsed labels on other redraws. Claude added the inspected captures and verification record. Greptile found that a shell update could reopen setup watching after the thread watch failed. Claude added a closed-thread guard and two offline tests in separate commits. Sol confirmed failure before the fix, all 376 tests afterward, and both failure cases in the built TUI. Greptile resolved the finding.

Known limits

Preparation actions and terminal access remain for later PRs. This finishes progress display only. The card has its own title row, Details opens below its control, and follow-up retirement waits for the prompt in T3's projection. Small windows clip content. Any setup stream error disables further setup subscriptions until restart. A closed thread needs a fresh thread watch; selecting the already-open thread only focuses the composer, so switch away and back. Verification uses synthetic data and rendered terminal cells; the video is a static capture slideshow. No real setup or performance measurement ran.

Confidence Score: 5/5

The PR appears safe to merge; the previous finding is fixed and no new actionable issues remain.

Summary

Adds a read-only worktree setup card under the open thread’s first prompt.

• The open thread shows worktree setup progress under its first prompt.
• The setup card’s Details row stays in place when it opens or closes.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  Open[Open thread with worktree or preparing run] --> Watch[Watch setup progress]
  Watch --> Card[Show setup card under first prompt]
  Card --> Details[Expand details with w or click]
  Failed[Thread watch fails] --> Close[Close setup watch]
  Close --> Guard[Ignore later requests to reopen setup watching]
  New[Open another thread] --> Open

Loading

_{Reviews (2) · Last reviewed commit: "tui: a closed thread watch opens no setu..." · Reviewed by Greptile}