Build a weather web widget in three waves: prepare the project, implement it as an open-ended task judged on product fit, craft, and what it looks like in a browser, then pass browser-driven validation.

The widget is a real web page. Your run: <command> (declared in AGENTS.md) starts a local web server on http://localhost:8123 serving the widget; the page reads city and units from the query string and renders that city's weather from the local data/weather.json — no external network calls. The temperature and condition must be present as text in the HTML your server sends (render them server-side): the checks read the page over plain HTTP, and the UX judge reviews real screenshots you capture with your own browser tooling and drop into the requested .ololo folder. Keep the server running for the whole session. Wave one pins the data and the server; wave two is yours to shape; wave three verifies the contract.