Result text shows internal ids ("objects[1] ac"), says "a AC unit", and shows the demo-rules notice to homeowners #74

The result text shown to homeowners leaks an internal id ("objects[1] ac"), says "a AC unit", and ends the summary with the team's demo-rules notice.

Seen in. Device field test of TestFlight build 4.1 (beta at 45017ba), iPhone 14 without LiDAR, iOS 26.6.2.

• Run 2 (indoor mock wall): the notice at 4:34, "objects[1] ac" at 4:56–4:58 (clip 4:55–5:01). Report: run 2, A41-2015-06, A41-2015-19.
• Run 3 (a real house): the notice at 1:46, "a AC unit" at 1:47.25. Report: run 3, A41-2055-12, A41-2055-16.

What happens.

• Run 2, "What we checked": "Distance from AC units: objects[1] ac is 3 ft 0 in (± 6 ft 0 in) from the battery against a 3 ft 0 in rule: too close to call."
• Run 3: "Distance from AC units: Not everything within 3 ft 0 in of the battery was seen, so a AC unit could hide there."
• Both runs, the summary ends: "Demo rules: public values and placeholders (pool 10 ft, drive 5 ft), not Base's." Useful for the team, confusing for a homeowner.

Cause.

• SceneObject.label is f"objects[{self.index}] {self.type}" (scene.py#L120-L122). check_clearance passes it as the check's subject and embeds it in reason (solver.py#L461-L501). The app shows reason verbatim (ScanEngine+Export.swift#L249, ResultScreen.swift#L228).
• The unseen reason hardcodes the article: f"… so a {noun} could hide there." (solver.py#L504-L510), with noun "AC unit" (solver.py#L909-L918).
• The policy notice from rules.yaml (rules.yaml#L19) is appended to summary (solver.py#L1512-L1513), and the app shows summary on the result screen. The notice is already returned separately as policy.notice.

Fix direction.

• Keep subject machine-readable, but build reason from a human label, e.g. "the AC unit about 14 ft right of your meter".
• Pick the article from the noun ("an AC unit"), or reword to avoid it ("an unseen AC unit could be there").
• Stop appending the notice to summary; let the app show policy.notice as a footnote, or only in a team/debug view.
• Add a test that no reason, summary or message contains objects[, and that no text contains "a AC".

Related. A41-2015-06, A41-2015-19, A41-2055-12, A41-2055-16.

Screen recordings are in the comment below.