evening-winddownlisted

# Evening Wind-Down ## Date Handling -- CRITICAL **Step 0:** Run `date` and lock the target date at the start. If current time is before 2:00 AM, target = previous calendar day; otherwise target = current calendar day. Resolve the daily note filename (e.g., `Wednesday, April 1st, 2026`) once and use it for everything -- do NOT re-check the clock if execution crosses midnight. ## Steps Gather all data in parallel where possible, then present conversationally. ### 1. Day Recap **Calendar**: Use `gcal_list_events` for today. List what happened: - Events attended (note if any were skipped or cancelled) - How the day actually played out vs the morning briefing plan (read today's daily note for the briefing) **Tasks**: - `get_today` -- what's still on today's list? What got completed? - Check today's daily note for any tasks that were added during the day - Flag anything that rolled over (didn't get done and should be rescheduled) **Health so far**: Follow the `/health` skill's **Evening Update** section. Pull today's final Fitbit activity totals and update the Health Log note. Steps vs 15,000 goal -- note the gap but don't nag (it's bedtime). **Loki (cat)**: read the **last 7 daily notes** in `Areas/Health & Fitness/Loki Health Log/` (today + the prior 6, by `YYYY-MM-DD.md` filename -- don't re-query the API). Pull `weight_lbs` and `visits` from each note's frontmatter and look across the window for **emerging trends**, not just today's snapshot: - **Weight trajectory**: