v2.6.1

wt rm no longer leaves a removed worktree's files behind when the pane that ran it closes straight away. The background worker that deletes them now starts in its own session, so a pane manager that tears down every process in the pane's session cannot kill it. That was the common shape of the failure when a removed hook closes the worktree's own workspace right after wt rm . returns, which left a full checkout on disk with nothing retrying it until the next wt command in that repo.

What's changed

• Start the reclamation worker in its own session
• Bump the version to 2.6.1

Full changelog: v2.6.0...v2.6.1