"2 more views to finish" shows only one view after "I can't get there"

Seen in device field test run 2: TestFlight build 3.1, beta at ad91620, capture code t3/ios-mvf e9e405d, server e106acb. The exported scan was lost before it was copied off the phone, so this comes from the screen recording and the code at ad91620. Times are in the recording. b7f51ba and 49a676e on t3/ios-mvf don't change this.

What happens. The first upload ended on "2 more views to finish" and "Take 2 more views". The first view was "Show
the ground around your meter / Keep walking past the left end of the scan (0 ft 4 in left of the meter)…". The tester
tapped "I can't get there" at 3:56.6. The app uploaded at once and showed the result about 1.2 s later. The second view
was never asked for.

Cause.

The count is every capturable item in the answer (GapRequestScreen.swift#L75-L78,
and "Take N more views" on the upload screen).
But skipCurrentGap sets automaticGapsStopped when a server request is refused (ScanEngine.swift#L1290-L1302).
nextAutomaticGap returns nil after that (ScanEngine.swift#L1386-L1390).

The button's hint does say "Skips this view and shows your result", so stopping may be intended. Either way, the count
promises views that won't come.

Possible fixes (your call):

say "1 view to finish" and don't count the rest; or
keep asking for the other views after one refusal, and stop only on a second refusal or a "Show my result" button.

Merge origin/t3/ios-mvf into t3/gap-skip-continues (#39)

Build 4.1 field test (TestFlight 4.1, beta 45017ba, iPhone 14 without LiDAR, three runs on 2026-09-26): still present in all three runs.

Run 1: "6 more views to finish" (5:43). One view was shown; "I can't get there" at 6:05 went straight to the result (6:06).
Run 2: "3 more views to finish" (3:54). One view; "I can't get there" at 4:31, then the result at 4:34.
Run 3: "4 more views to finish" (1:42). One view, refused at about 1:45; result at 1:46.

In every run the one view shown was the placeholder-driven "Show the ground out to about 14–16 ft" request (#75), which couldn't be met. Analyses: PR #60 (run 1, run 2, run 3).