Fix premature OVERDUE on the API and the Complete tap doing nothing

Overdue: the API read the host clock (the deployed container runs UTC,
the household is US Eastern), so every morning quest turned overdue
from ~04:00 local, and the snapshot routes built a default settings
object instead of the stored one. Add an additive `timezone` setting
(IANA name; "" keeps the host-local behaviour), validated through the
shared settings field table and exposed on the admin settings GET/PATCH.
Every API clock read (panel/admin routes, the missed-sweep scheduler)
now re-expresses the one host read in that zone, and the snapshot
routes load the persisted settings.

Complete: with target ES2022, TypeScript's useDefineForClassFields
default emitted the cards' reactive fields as native class fields that
shadow Lit's accessors, so setting `_confirm` never re-rendered and the
confirm dialog never opened. Set useDefineForClassFields to false (Lit's
documented TypeScript setting) and rebuild the bundle.

Tests pin the clock at the due-time boundary for both snapshot shapes,
cover the scheduler and on-time stamp, and drive the built bundle's
Complete tap through to the complete_quest service call.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This commit is contained in:

overseer

2026-09-26 09:29:24 -04:00

co-authored by

Claude Opus 5.5

parent 8f38946c04

commit 64aa8e99f6

12 changed files with 792 additions and 353 deletions

									
										frontend/tsconfig.json
									
		+1
		
												View File
												
				@@ -1,6 +1,7 @@

				{

				  "compilerOptions": {

				    "target": "ES2022",

				    "useDefineForClassFields": false,

				    "module": "ESNext",

				    "moduleResolution": "bundler",

				    "lib": ["ES2022", "DOM"],