fix(server): a zero Git fetch interval also stops the fetch on window focus

[macodev00]

Fixes pingdotgg#13235

Problem

Settings → Source Control → Git fetch interval 0 is documented as avoiding automatic Git prompts. That only stopped the periodic remote poller. Focusing the window, or making it visible again, still ran git fetch --quiet --no-tags <remote> through vcs.refreshStatus.

Change

refreshStatus now takes the same fetch interval the status stream already uses. When the interval is zero it reads remote status with refreshUpstream: false and skips the automatic pull, so the refresh still re-reads local status without contacting the remote. The focus and visibility RPC, the status refresh after git mutations, and the worktree handoff refresh all pass the configured interval. Any other interval, including the default, still fetches. Explicit pull, push, and fetch are unchanged.

Scope and approval

Accepted bug pingdotgg#13235. The triage asked for refreshStatus to pass refreshUpstream: false when the Git fetch interval is zero, including the other callers of that refresh.

Verification

vp test run apps/server/src/vcs/VcsStatusBroadcaster.test.ts apps/server/src/mcp/WorktreeMcpService.test.ts — 75 passed.

• A zero-interval refresh calls remoteStatus with refreshUpstream: false and still invalidates the status cache. A one-minute interval and the default interval pass true.
• With auto-pull enabled and a cached behind upstream, a zero-interval refresh does not pull. A default refresh does.
• A status stream at interval zero with auto-pull enabled loads remote status once and does not pull.
• A worktree handoff refresh passes the configured interval. Zero stays zero. Unset resolves to 30 seconds.

vp run --filter t3 typecheck completed with no errors.

Not checked: a live window-focus session against an SSH agent that prompts. The focus listener still calls vcs.refreshStatus; the server now skips the fetch when the interval is zero.

Model and harness: Grok 4.7 (high effort) in a Cursor Cloud Agent.