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>

This commit is contained in:

Bryan Van Deusen

2026-03-25 20:17:51 -04:00

parent fd05c65018

commit 62dbb8d496

7 changed files with 24 additions and 55 deletions

									
										frontend/src/components/BriefingSetupWizard.vue
									
		-1
	
												View File
												
				@@ -20,7 +20,6 @@ const config = reactive<BriefingConfig>({

				  slots: { compilation: true, morning: true, midday: false, afternoon: false },

				  notifications: true,

				  temp_unit: 'C',

				  timezone: '',

				})

				// Step 2 — locations