The overhead task is asked from 19 ft away, and its card's button overlaps the text #64

The walk's overhead step ("Tilt up to show above the area by your meter") is asked the moment both ends are marked, wherever the phone is: in run 2 that was the right end, 19 ft from the meter. Separately, on this card the "Can't get there" pill was drawn over the detail text.

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 2 (indoor mock wall), 3:20–3:30: the overhead step asked from the right end.
• Run 3 (a real house), 1:35.25: the button overlapping the card text.

What happens.

• Run 2: "Tilt up to show above the area by your meter / Aim at the wall from your meter to 5 ft right of it" came up while the tester stood at the right end, 19 ft away. Next came "What's above that part of the wall?". The tester answered "A roof edge, porch or stairs", which records nothing, and the step was settled.
• The spot the server chose later needed overhead at 17.1–19.7 ft right, which is where the tester had been standing. So the question came at the wrong place for the stretch it asks about, and it didn't help the stretch that turned out to matter.
• Run 3: on "Tilt up to show above the area by your meter / Aim at the wall from 5 ft left to 2 ft right of your meter and whatever is above it", the "Can't get there" pill sits on top of "above it". Another 3-line card a quarter-second later (1:35.5, "8 ft 9 in left of your meter") pushed the button down correctly. In the same frame the bottom buttons are mid-crossfade, so this may be a frame from the card's height animation rather than a static layout bug. Either way, the text was unreadable when it was on screen.

Cause.

• tiltUpSpanIfDue fires as soon as both ends are marked and the step isn't settled. It doesn't look at where the phone is (ScanEngine.swift#L783-L790). It is checked ahead of the walk's other tasks (ScanEngine.swift#L665-L671).
• The stretch is fixed to ±1.5 m around the meter (tiltUpReach), and the copy says "by your meter" without asking the homeowner to go back there (ScanCopy.swift#L45-L49).
• Overlap: InstructionCard swaps the text at once and eases the card to its new height, with the reply button placed under the message (InstructionCard.swift#L36-L61). This is a suspect, not confirmed.

Fix direction.

• Ask for overhead where the phone is, or once a candidate spot is known. If it must be at the meter, say "Go back to your meter" first, and hold the step until the phone is within reach of the stretch.
• Check the overhead card at the default and larger text sizes, and during the transition from the previous card. Make sure the reply never overlaps the detail text.

Related.

• Filed from the same test: "Can't get there" reads wrong on tilt tasks; testers look for a "that's the ground" answer instead (the same pill is on this card).
• Report IDs A41-2015-13 (run 2 report) and A41-2055-08 (run 3 report). PR docs: build 4.1 field-test analyses (three runs) #60 has the public reports.

Screen recordings are in the comment below.