Summary

• Fix a dev/production mismatch in KiloClaw onboarding weather previews: wttr.in inferred its default unit system from the server-side request origin, so development calls came from the developer's local network where correct, while production calls came from Vercel infrastructure and could display different units for the same selected location.
• Resolve location metadata before requesting the formatted weather preview, then explicitly request USCS/Fahrenheit output for United States locations and metric/Celsius output for other or unresolved locations.
• Keep metadata lookup best-effort so a temporary failure to resolve the country does not prevent an otherwise successful metric weather preview.
• Add regression coverage for US and non-US unit selection, missing country metadata, and partial upstream outages.

Verification

• Manually compared wttr.in responses for Amsterdam with unspecified, explicit metric (m), and explicit USCS (u) output; the unqualified response used the request origin's default while explicit unit options produced deterministic output.
• No authenticated end-to-end onboarding walkthrough was performed in a deployed environment because the defect mechanism was isolated to the server-side upstream request and explicit-unit behavior was verified directly against wttr.in.
• Additional manual verification details from reviewer/tester

Visual Changes

N/A

Reviewer Notes

• Review the country-to-units mapping: only resolved United States locations use u; missing or failed metadata falls back to m.
• The shared backend procedure serves both web and mobile onboarding clients; neither client requires a UI change.