feat(account): seed the time zone from the client's detected offset at creation #116

Merged

developer merged 1 commits from feature/account-seed-timezone into development 2026-06-22 17:07:53 +00:00

Conversation 1 Commits 1 Files Changed 25

+312 -79

developer commented 2026-06-22 16:59:10 +00:00

Owner

Copy Link

Copy Source

Seeds accounts.time_zone at creation from the client's detected ±HH:MM offset (Telegram / guest / email first contact), so the robot sleep window and turn-timeout away-window are anchored to the player's real zone from the first game instead of the UTC default. No migration (the column is already NOT NULL DEFAULT 'UTC').

Stacked on #115 (feedback browser-tz three-time): until #115 merges, this PR's diff also shows #115's commit; it self-cleans to B1-only once #115 lands in development.

Review path: verify on the contour that a freshly-created account's feedback Filed shows a populated user zone (not N/A).

Seeds `accounts.time_zone` at creation from the client's detected `±HH:MM` offset (Telegram / guest / email first contact), so the robot sleep window and turn-timeout away-window are anchored to the player's real zone from the first game instead of the UTC default. No migration (the column is already `NOT NULL DEFAULT 'UTC'`). **Stacked on #115** (feedback browser-tz three-time): until #115 merges, this PR's diff also shows #115's commit; it self-cleans to B1-only once #115 lands in development. Review path: verify on the contour that a freshly-created account's feedback Filed shows a populated **user** zone (not N/A).

developer added 3 commits 2026-06-22 16:59:10 +00:00

feat(feedback): capture the app version; show version + local Filed time ... b78ce42922

Each feedback submission now carries the client app version (__APP_VERSION__),
snapshotted like the interface language: FlatBuffers FeedbackSubmitRequest gains
a version field → gateway transcode → backend, persisted in a new nullable
feedback_messages.app_version column (migration 00003, additive so an image
rollback stays DB-safe). The operator console detail shows the app version and
renders the Filed time in UTC plus the sender's time zone (fmtTimeIn).

Touches: fbs schema + regenerated Go/TS codegen, codec + transport (the client
attaches its build), gateway transcode + backendclient, feedback store/service,
admin view + template, docs (ARCHITECTURE §15, FUNCTIONAL + _ru). Verified:
feedback integration tests (migration + version round-trip), codec round-trip,
check/unit/build green.

feat(feedback): capture the browser UTC offset; Filed time in three zones ... 004aca4e97

The account time zone defaults to UTC until a player saves a profile, so a
report's Filed time could only render in UTC even for a player clearly in
another zone. Capture the client's detected "±HH:MM" offset (browser_tz) with
each submission and show the Filed time in three zones in the operator console
— UTC, the browser offset detected at submit, and the sender's saved profile
zone — each shown "N/A" when not known, so the operator can tell what is
certainly known from what is merely defaulted.

- Thread browser_tz through the fbs envelope (+ Go/TS codegen), the gateway
  transcode + backend client, and the backend feedback service/store; add the
  column via migration 00004 (additive, image-rollback-safe).
- Fix fmtTimeIn to resolve "±HH:MM" offsets via account.ResolveZone;
  time.LoadLocation alone silently fell back to UTC for offset zones, which is
  the second reason a "+02:00" sender showed only UTC.
- Update ARCHITECTURE/FUNCTIONAL(+ru) docs and the feedback integration test.

feat(account): seed the time zone from the client's detected offset at creation ... ef2c2d1eb9

A new account's time_zone defaulted to 'UTC' until the player saved a profile, so the
robot's sleep window and the turn-timeout away-window sweeper — both anchored to the
account zone via account.ResolveZone — ran on UTC for every fresh player, skewing
robot-game timing until a manual Settings save. Seed the zone at creation instead, from
the client's detected "±HH:MM" offset.

- Carry browser_tz on the three account-creating auth requests (TelegramLoginRequest,
  GuestLoginRequest, EmailRequestRequest — the email account is provisioned at the
  code-request step, not at login) through the fbs envelope (+ Go/TS codegen), the
  gateway transcode + backend client, and the backend auth handlers into
  ProvisionTelegram / ProvisionGuest / ProvisionEmail.
- create() now writes time_zone explicitly: the validated detected offset, or 'UTC'
  (equal to the column default) when absent or malformed — deterministic, never guessed.
  The column is already NOT NULL DEFAULT 'UTC', so no migration is needed and existing
  accounts keep 'UTC'. An existing account is never overwritten on re-login.
- A detected zero offset is stored as "+00:00" (the zone is known and equals UTC),
  distinct from the "UTC" default that means "unknown" — which the feedback console's
  three-zone Filed display already reflects.
- Guard the guest handler against an empty payload (the bootstrap historically carried
  none) so it degrades to no-seed rather than panicking in GetRootAs*.
- Tests: zone seeding across Telegram/guest/email plus the "+00:00"/malformed/empty
  cases and the not-overwrite rule; codec round-trip for the three auth encoders.
  ARCHITECTURE + FUNCTIONAL(+ru) updated.

owner approved these changes 2026-06-22 17:05:12 +00:00

developer merged commit d5369a0188 into development 2026-06-22 17:07:53 +00:00

developer deleted branch feature/account-seed-timezone 2026-06-22 17:07:53 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

owner

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

owner (Ilia) developer

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: developer/scrabble-game#116