v2.7.0

wt rm can now remove worktrees that contain submodules.

What's changed

• A worktree with initialized submodules gets a new ◆ marker in the wt rm picker and the stale-branch cleanup prompt, and the legend explains it. Before, git refused to remove such a worktree and the only way through was --force.
• Ticking a ◆ row, or confirming the warning for wt rm <target> or wt rm ., removes the worktree along with its submodule repositories. The warning says that any unpushed commits or stashes inside them will be lost, because perch can't check for them.
• Without a terminal, a worktree with submodules is refused with a non-zero exit. --force still removes it.
• perch forces past git's guard only for risks you were warned about. If a ◆ worktree becomes dirty after its row was drawn, git's own guard decides.
• Fixed: a worktree whose submodule had been deinitialized, or removed with git rm, still keeps that submodule's repository. perch used to remove such a worktree silently, losing any unpushed commits in it. It now gets the ◆ warning.
• just install now replaces the installed binary instead of overwriting it in place, which macOS could kill on launch.

• Warn about submodules so removal can force past git's guard
• Replace the installed binary rather than overwrite it
• Bump the version to 2.7.0

Full changelog: v2.6.4...v2.7.0