"Can't get there" reads wrong on tilt tasks; testers look for a "that's the ground" answer instead #63

On tilt tasks the card's only reply is "Can't get there", which doesn't describe the situation: the tester is standing at the spot, it's the phone that can't fill it. Testers don't press it, and instead look for a way to say "that's the ground".

Seen in. Device field test of TestFlight build 4.1 (beta at 45017ba), iPhone 14 without LiDAR, iOS 26.6.2. Times are in each run's screen recording.

• Run 1 (indoor mock wall): "Tilt down… at your meter" held the walk for 151 s of the first 225 s (0:33–4:13). The tester was at the meter, so they never pressed "Can't get there" and stayed stuck.
• Run 2 (same mock wall), 0:55–1:07: stuck on the same ground task, the tester opened "Mark something" looking for a ground answer: "Mark something. There's nothing there. There's grass option."

What happens.

• During "Tilt down to show the ground" (and "Tilt up to show more wall") the reply pill reads "Can't get there". The tester could get there, so they read it as the wrong answer and kept tilting.
• Pressing it would have unblocked them: on a tilt task it marks ±0.5 m of that band skipped and moves on.
• The "What do you see?" sheet offers gas meter, door, window, AC unit, driveway and fence, with nothing for the ground. The ground type question ("What's on the ground along this wall?") only comes after "Done with this wall".

Cause.

• reply gives the same "Can't get there" title to every walk task except the walk itself and see-behind. Only the VoiceOver hint says what it does ("Skips this part of the wall…") (WallWalkScreen.swift#L264-L289).
• On .aimAtGround / .aimAtWall it marks ±0.5 m skipped (ScanEngine+Actions.swift#L341-L358).
• The ground type is asked only on the feature review (MarkFeaturesScreen.swift#L53-L56).

Fix direction.

• On tilt and gap tasks, label the reply for what it does: "Skip this spot" or "It won't fill". Keep "Can't get there" for walk tasks.
• Consider a "This is the ground: Grass / Gravel / Concrete / …" answer on the ground card. It would give people the explicit answer they reach for, count as the skip, and fill in the ground type early.

Related.

• Filed from the same test: The first "Tilt down… at your meter" task blocked the start in all three runs: no timeout, and the two-spots rule is never explained (why the task gets stuck), and "Looks complete" sends with the window's open/shut answer and the ground type unanswered.
• Report IDs A41-1-14 (run 1 report) and A41-2015-17 (run 2 report). PR docs: build 4.1 field-test analyses (three runs) #60 has the public reports.

Screen recordings are in the comment below.