3 Commits

Author	SHA1	Message	Date
bvandeusen	62dbb8d496	refactor: centralise user timezone as a standalone setting ... Browser timezone is now synced to user_settings["user_timezone"] on every login/page load (App.vue). The briefing scheduler and LLM context both read from this single source, falling back to the legacy briefing_config.timezone for existing users during migration. - App.vue: PUT /api/settings with browser IANA timezone on startAppServices - routes/chat.py: fall back to stored user_timezone when not sent in request - briefing_scheduler: read user_timezone setting; briefing_config.timezone kept as fallback only - routes/briefing.py: pass tz_override from user_timezone to live-patched scheduler - Remove timezone field from BriefingConfig interface and all briefing UI Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-25 20:17:51 -04:00
bvandeusen	9cb3700a5c	fix: add temp_unit and timezone to inline BriefingConfig literals ... BriefingSetupWizard and SettingsView had hardcoded initial objects that predated the new fields, causing TS2345 type errors. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-12 18:33:17 -04:00
bvandeusen	1686289af4	feat: daily briefing frontend — view, setup wizard, settings tab, nav ... - BriefingView: soft chat UI with conversation history dropdown, SSE streaming via chat store, manual refresh trigger, today/past conv toggle - BriefingSetupWizard: 4-step first-time setup overlay (welcome → locations → office days → RSS feeds) - SettingsView: Briefing tab with enable toggle, location geocoding, office day picker, slot toggles, RSS feed management, notifications - AppHeader + router: /briefing route and nav link (desktop + mobile) - client.ts: briefing types and API functions (config, feeds, convs, geocode, trigger) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-11 20:30:45 -04:00