From 26fba8170ab07e5a80f9e81bfc85bc123676683b Mon Sep 17 00:00:00 2001
From: lorentz <lorentz@wulfconsulting.com>
Date: Thu, 7 May 2026 17:21:44 -0400
Subject: [PATCH] test(07.1): mark BUG-7.1-B resolved by 660d039

---
 .../07.1-user-timezone-fix-inserted-urgent/07.1-HUMAN-UAT.md   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.planning/phases/07.1-user-timezone-fix-inserted-urgent/07.1-HUMAN-UAT.md b/.planning/phases/07.1-user-timezone-fix-inserted-urgent/07.1-HUMAN-UAT.md
index 95cea5c..57ad481 100644
--- a/.planning/phases/07.1-user-timezone-fix-inserted-urgent/07.1-HUMAN-UAT.md
+++ b/.planning/phases/07.1-user-timezone-fix-inserted-urgent/07.1-HUMAN-UAT.md
@@ -71,10 +71,11 @@ But Better Auth's `user` table uses camelCase columns (`updatedAt`, `createdAt`,
 
 **Fix:** changed to `"updatedAt"` (quoted because Postgres folds unquoted identifiers to lowercase). Committed `d31fd48`.
 
-### BUG-7.1-B — `'UTC'` rejected by IANA validator (NOT FIXED)
+### BUG-7.1-B — `'UTC'` rejected by IANA validator (FIXED in 660d039)
 
 severity: medium-high
 scope: Plan 07.1-02 (validator) + Plan 07.1-01 (migration default)
+status: resolved — allowlisted `UTC`, `Etc/UTC`, `GMT`, `Etc/GMT` in `EXTRA_ALLOWED_TIMEZONES`. Verified PUT `{"timezone":"UTC"}` → 200, PUT `{"timezone":"Etc/UTC"}` → 200, PUT `{"timezone":"Etc/Garbage"}` → 400.
 
 `isValidIanaTimezone()` in `app/api/me/timezone/route.ts:20` rejects any value not in `Intl.supportedValuesOf('timeZone')`. On Node 20.20.0 (the production runtime) this list contains 418 zones but **excludes `UTC`, `Etc/UTC`, and every `Etc/*` alias**. Confirmed locally and matches Node's ICU canonical-IANA stance.