1cf5d3841b
The #71637 prune fix cut one stage of -w startup, but the base-ref resolution right after it still ran an uncapped-in-practice 'git fetch origin main' (timeout=30) on every launch — and on a flaky smart-HTTP connection that fetch intermittently stalled to the full 30s, then cascaded into step 2's SECOND 30s fetch. Measured: back-to-back fetches of 0.9s, 1.0s, 63.5s on the same box with healthy TLS (~185ms). _resolve_worktree_base now: - skips the fetch entirely when FETCH_HEAD is < 5 min old and the tracking ref exists (repeat launches pay zero network cost) - caps the fetch at 5s and falls back to the locally-known tracking ref (labelled 'cached') on timeout/failure instead of cascading into a second fetch — genuine staleness stays backstopped by the pre-push stale-base gate - caps 'git remote show origin' the same way Worst case drops ~60s -> ~5s; warm path is ~0.02s (was up to 30.8s). sync_base=False and the offline HEAD fallback are unchanged.