- Shipped
- 22 ஆகஸ்ட், 2026 அன்று 3:37 AM UTC
- Author
- kamo
- Commit
- 177f5e1
The two datetime fields hold offsetless wall-clock text and the API binds them to a java.util.Date, so the server read them in ITS zone — UTC. A member setting 8pm Pacific had 20:00Z stored and 1pm handed back on the next open, and every subsequent save shifted it again. The draft already carried correctly-converted instants; only this call site was not using them. Same fix for update-and-notify, whose endpoint binds an Instant and could not read a wall clock at all. Changing either time now pushes the end to an hour past the start whenever it would land before it.