r on a PR does not refresh its worktree status (deleted worktree not noticed)

[mayfieldiv]

This was generated by AI during triage.

Summary

Pressing r (refresh selected PR) does not refresh worktree status. After deleting a PR's worktree outside the app, r still shows the PR as having a worktree; the stale entry stays until something re-lists worktrees.

Reproduction (maintainer report + code trace)

1. Create a worktree for a PR (w).
2. Delete that worktree on disk / via git worktree remove.
3. Select the PR and press r.
4. The PR still shows worktree status as if the worktree exists.

Code trace

• Cmd::ListWorktrees is only dispatched from list_worktree_cmds (src/app/update.rs:93), which is called in exactly two places:
  • Msg::ConfigLoaded (src/app/update.rs:984)
  • after a successful worktree creation (src/app/update.rs:1184)
• r → Msg::RefreshSelected → refresh_selected_cmds → begin_refresh (src/app/update/refresh.rs:29,159) only dispatches Cmd::RefreshPr (GitHub enrichment). It never re-lists worktrees, so model.worktrees_by_repo keeps the deleted entry.
• R notices deletions only incidentally: refresh_all_cmds (src/app/update/refresh.rs:49) dispatches Cmd::LoadConfig, whose ConfigLoaded re-lists worktrees.

Expected

r on a PR should also refresh that PR's (or its repo's) worktree listing, so a deleted worktree disappears from the UI. Arguably R's worktree re-list should also be explicit rather than a side effect of the config reload.

[mayfieldiv]

This was generated by AI during triage.

Agent Brief

Category: bug
Summary: Refresh worktree listings when refreshing PR data so externally removed worktrees disappear from the UI

Current behavior:
Pressing w creates a worktree and immediately updates the cached worktree listing. If that worktree is later removed outside Legit, the cached entry remains. Pressing lowercase r refreshes the selected PR's GitHub enrichment but does not re-list worktrees, so the list glyph and summary path remain stale. Uppercase R currently notices the deletion only indirectly because its config reload triggers worktree listing.

This was reproduced in the running TUI with an isolated source clone: create a worktree for a selected PR, remove it externally with git worktree remove, press r, wait for Refreshed 1 PR, and observe that the deleted worktree's glyph and summary path remain visible.

Desired behavior:
Lowercase r on a selected PR should re-list worktrees for that PR's repository as part of the refresh. A fresh listing should replace the repository's cached entries, removing worktrees that no longer exist.

Uppercase R should explicitly re-list worktrees for configured repositories with source clones. Config reload may remain part of global refresh, but worktree reconciliation must not depend on config loading as an incidental side effect or dispatch duplicate listings.

Key interfaces:

• The lowercase selected-PR refresh command builder — include worktree listing for the selected PR's repository alongside GitHub enrichment
• The uppercase global refresh command builder — explicitly include worktree listing for configured source clones
• The existing worktree-list command and WorktreesArrived handling — reuse their replacement semantics rather than adding separate pruning state
• Source-clone resolution — repositories without a configured source clone should remain harmless no-ops

Acceptance criteria:

• After a selected PR's worktree is removed externally, pressing r removes its worktree glyph and summary path once refresh completes
• Lowercase r re-lists only the selected PR's repository, not every configured repository
• Uppercase R explicitly re-lists worktrees for configured repositories with source clones
• Global refresh does not dispatch duplicate worktree listings through both explicit refresh behavior and config-load side effects
• Existing worktree creation and initial config-load detection continue to work
• Automated reducer tests cover selected refresh, global refresh, repositories without source clones, and externally deleted-entry replacement

Out of scope:

• Watching the filesystem or Git metadata for live worktree changes
• Adding a separate worktree-only refresh keybinding
• Changing GitHub PR enrichment, PR membership reconciliation, or worktree creation behavior