A finished clone is never marked cloned if another repo is selected meanwhile, so it is skipped by Fetch All / Pull All / auto-fetch

[matt-edmondson]

What's wrong

When a clone completes, the render thread runs Clones.RefreshIfRequested(RefreshPage) (ProjectDirector/ProjectDirector.cs ~L689). RefreshPage (~L812-821) only calls UpdateClonedStatus for Options.Repos[Options.BaseRepo], i.e. whatever repo is selected now, not the repo that was cloned. CloneTracker does not record which path finished.

Failure scenario

1. Select repo X, click Clone (Clones.TryRun(repo.LocalPath, …), ~L717).
2. While it runs, select repo Y.
3. The clone finishes; RefreshPage updates Y's cloned status and re-runs Y's comparison.
4. X is never added to Options.ClonedRepos: its indicator stays grey, and FetchAllReposIfStale, Fetch All and Pull All (which iterate ClonedRepos) skip it.
5. Startup's RefreshPage also only checks the selected repo, so the state persists across restarts until X is selected again or a full scan runs.

Side effect: any clone completion restarts the comparison for the selected repo and resets its browser path to the root.

Why it matters

Selecting another repo while a clone runs is the natural thing to do (clones take a while), and the outcome is a silently untracked working copy that never gets fetched.

Suggested fix

Have CloneTracker record the local paths that completed; on the render thread call UpdateClonedStatus for each of those repos (or the parameterless full UpdateClonedStatus()), and only re-run SwitchPage when the completed repo is the selected one or one of its similar repos.

Acceptance criteria

• After cloning X and switching to Y before completion, X is in ClonedRepos and shows as cloned.
• Completion of X's clone doesn't reset Y's comparison/browse state unless X is related to Y.
• A test on CloneTracker asserts the completed path is reported to the refresh callback.

Not covered by #439 / #474, which only moved the refresh onto the render thread.

[matt-edmondson]

Triage

• Category: Bug
• Priority: Medium. If you select another repository while a clone runs, the cloned repository is left out of ClonedRepos. Fetch All, Pull All and auto-fetch then skip it until it is selected again or a full scan runs. Nothing is lost, but the clone silently goes stale.
• Area / suggested assignment: CloneTracker and RefreshPage in ProjectDirector/ProjectDirector.cs. Record the completed path, call UpdateClonedStatus for that path, and run SwitchPage again only when the completed repository is related to the selected one.
• Duplicates / in progress: No duplicate. Clone button's continuation runs RefreshPage on a thread-pool thread, racing the render thread over Options.Repos/ClonedRepos and the browser collection #439 (closed) and Refresh after a clone on the render thread, and allow one clone per folder [patch] #474 only moved the refresh onto the render thread. Repo list never shows which clones are dirty or behind their remote (GitRepository.UpdateStatus is never called) #479 (dirty/behind status is never computed) is in a nearby area but is a separate issue. No open PR covers it.

---

Generated by Claude Code