[skunkworker]

Summary

Six fixes from an analysis of v0.1.2. Each one was reproduced in a throwaway repository first.

• Remote delete trusted the last fetch. A teammate's push after that fetch was deleted with the branch. The push now carries --force-with-lease on the commit the tracking ref was at. A lease refusal runs git ls-remote: a branch someone else already deleted counts as deleted. A gone upstream (no tracking ref) refuses the remote delete.
• A reload changed the confirm screen. A fetch, checkout or undo that landed there removed the "will discard" warning and, for p, selected more branches. A reload now closes the screen with a status line.
• The remote restore command named the wrong commit. The result line and the git push restore line used the local tip. They now use the remote's commit (branch.upSha).
• The force retry ran inside Update (item 34). It now runs as one cmd per branch on the deleting screen.
• Undo followed by a fast new delete crashed with an index out of range. d and a second u now wait while an undo runs.
• m did not wait for the merge status. During the load it selected nothing.

Tests

• Six new tests in review_test.go, one per fix. Each fails against the old code.
• Four tests in main_test.go changed: three drive the background force retry, one gives its hand-made branch the remote commit.
• go test -race, go vet and gofmt are clean.

Not in this PR

• The tests read the global git config (tag.gpgsign breaks two of them locally).
• v obeys diff.external.

🤖 Generated with Claude Code