"Looks complete" sends with the window's open/shut answer and the ground type unanswered #65

"Looks complete" is enabled with the two review questions unanswered ("Does this window open?" and "What's on the ground along this wall?"), and the scan is sent without them. Each gap can turn a check the homeowner could have settled in one tap into an unsure one.

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), 4:22–4:28: "Does this window open?" left unanswered, then "Looks complete".
• Run 3 (a real house), 1:38.5–1:39.5: the ground type left unanswered, then "Looks complete".
• Run 2 answered the window question, so it's not every time.

What happens.

• Run 1: the window card's "It opens" / "It stays shut" were never tapped. The scan was accepted, and scene.json's window has no operable field (the schema allows one).
• Run 3: "What's on the ground along this wall?" (Grass / Mulch / Gravel / Concrete / Driveway / Deck / Not sure) sat above "Anything else near your meter?". Nothing was chosen, "Looks complete" was enabled, and the tester sent it. scene.ground is empty, so the result's "Ground under the battery" check is unsure. The ground there was clearly gravel.

Cause.

• Leaving the ground question unanswered is by design: "skipping it counts as not sure" (MarkFeaturesScreen.swift#L53-L56, GroundQuestion.swift#L3-L6).
• "Looks complete" has no condition on either answer (MarkFeaturesScreen.swift#L63-L72).
• An unanswered window is exported with operable left out (ScanEngine+Export.swift#L41).
• When the rules exempt windows that stay shut, the solver then treats that window's exemption as unknown, and the check comes out unsure (solver.py#L521-L535).

Fix direction.

• Either require an answer before "Looks complete" ("Not sure" is one tap and stays available), or scroll to and highlight the unanswered question when "Looks complete" is tapped.
• Or pre-select the ground type from the camera, for the homeowner to confirm.
• If skipping stays allowed, say in the result what was assumed ("You didn't say whether the window opens, so an installer will check it").

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 (asking for the ground type on the ground card would settle it earlier).
• Report IDs A41-1-15 (run 1 report) and A41-2055-13 (run 3 report). PR docs: build 4.1 field-test analyses (three runs) #60 has the public reports.