Hotfix-style follow-up to v26.04.29.1 — single-commit, surface-only.
Why
The journal screen pinned a WeatherCard to the top of the chat, but the card expected a flat shape (current_temp, condition, today_high, ...) while the prep payload sends raw OpenMeteo data nested under forecast_json per location. Every field read as null, so the rendered card showed null° and null/null covering the prep prose.
What
a77b71e — Drop the WeatherCard render from the journal screen, delete the unused widget file. The prep prose itself already mentions weather plainly ("Weather at home will reach a high of 15.9° with a 0% chance of precipitation") — the visual card was redundant on top of that. Removing it eliminates the "null" bug without losing any actual info; the underlying weather data is still in metadata.sections.weather if a future reader wants a different rendering.
Test plan
flutter analyze clean
Existing tests unchanged, all pass
Visual check on device: today's prep renders without a "null"-laden card on top
Hotfix-style follow-up to v26.04.29.1 — single-commit, surface-only.
## Why
The journal screen pinned a `WeatherCard` to the top of the chat, but the card expected a flat shape (`current_temp`, `condition`, `today_high`, ...) while the prep payload sends raw OpenMeteo data nested under `forecast_json` per location. Every field read as null, so the rendered card showed `null°` and `null/null` covering the prep prose.
## What
**`a77b71e` — Drop the WeatherCard render from the journal screen, delete the unused widget file.** The prep prose itself already mentions weather plainly (*"Weather at home will reach a high of 15.9° with a 0% chance of precipitation"*) — the visual card was redundant on top of that. Removing it eliminates the "null" bug without losing any actual info; the underlying weather data is still in `metadata.sections.weather` if a future reader wants a different rendering.
## Test plan
- [x] `flutter analyze` clean
- [x] Existing tests unchanged, all pass
- [ ] Visual check on device: today's prep renders without a "null"-laden card on top
🤖 Generated with [Claude Code](https://claude.com/claude-code)
This repo is archived. You cannot comment on pull requests.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hotfix-style follow-up to v26.04.29.1 — single-commit, surface-only.
Why
The journal screen pinned a
WeatherCardto the top of the chat, but the card expected a flat shape (current_temp,condition,today_high, ...) while the prep payload sends raw OpenMeteo data nested underforecast_jsonper location. Every field read as null, so the rendered card showednull°andnull/nullcovering the prep prose.What
a77b71e— Drop the WeatherCard render from the journal screen, delete the unused widget file. The prep prose itself already mentions weather plainly ("Weather at home will reach a high of 15.9° with a 0% chance of precipitation") — the visual card was redundant on top of that. Removing it eliminates the "null" bug without losing any actual info; the underlying weather data is still inmetadata.sections.weatherif a future reader wants a different rendering.Test plan
flutter analyzeclean🤖 Generated with Claude Code