Put the week on the resort page, and fold the detail cards

[greenido]

Why

• The resort page answered "how is it now" and nothing else. To find the best day for one mountain you had to switch to the Planner and find its row.
• On a phone the page was 17 cards in one column, about 5 screens. Everything had the same weight, and several numbers repeated.
• On desktop it was the same stack, just wider.

What

• ResortWeekStrip (new), shown under the Today summary: 7 days, each with its score, a snow bar scaled to the week's snowiest day and the snow amount. The best day is outlined. It uses usePlanner([resort]), which reads the planner's mid-mountain outlook and shared cache, so each day scores the same as it does in the Planner grid.

• DashboardSection (new): a collapsible group built on native <details>, with a one-line hint in the header so a closed section still shows its headline number. Sections:

  • Snow: always starts open.
  • Wind & visibility: opens itself on a lift-hold-risk day.
  • Temperature & humidity: opens itself on a frostbite-risk day.
  • Forecast discussion: NWS resorts only.

  Desktop (≥1024px) starts with every section open. A closed section's cards aren't rendered at all.

• Desktop two-column layout: the summary and week strip sit in a sticky left column while the details scroll on the right. The TodaySummary tiles show 2 across in that column and 4 across on tablets.

• Pro View: unchanged.

Testing

• tsc --noEmit, next lint and all 9 offline test suites pass.
• 375×812: no sideways page scroll, and the page is ~2,950px tall instead of ~4,100px with only Snow open. Tapping a section header opens it.
• 1440×900: the left column stays pinned while the right side scrolls. No console errors.

Merge order

This is 2 of 3. It branches off main and only edits components/ (WeatherDashboard, TodaySummary, plus the two new components), so it merges cleanly before or after #13.

🤖 Generated with Claude Code