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

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.

2026-06-22 18:05:39 +02:00

..

attachment_test.go

feat(feedback): in-app user feedback with admin review and account roles

2026-06-15 12:23:10 +02:00

attachment.go

feat(feedback): in-app user feedback with admin review and account roles

2026-06-15 12:23:10 +02:00

service.go

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

2026-06-22 18:05:39 +02:00

store.go

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

2026-06-22 18:05:39 +02:00