Goal

Let the generated models parse v2 dates, which arrive as unix nanosecond integers instead of RFC 3339 strings.

Part of AND-1637

Implementation

• ExactDate and IsoDateAdapter are regenerated from the updated generator templates. A digits-only value is read as unix nanoseconds; strings keep the existing path.
• ExactDate.raw holds a nanosecond date as RFC 3339 with 9 fractional digits, so it has the same format whichever API version sent it.
• IsoDateAdapter now returns a copy of the cached Date, as the generator emits it.

No behaviour change on the current endpoints, which still send strings.

Testing

• ExactDateParsingTest and IsoDateAdapterTest cover JSON numbers, quoted digits and zero-padded fractions.
• V2PayloadParsingTest parses a v2 message.new frame through Serializer.moshi and checks its dates and custom data.
• Smoke run on the compose sample (channel list, channel, send, reaction, thread reply, search, threads) with no parse errors.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Improved date handling for Unix nanosecond timestamps, including quoted and unquoted values. Timestamps now retain their full precision in the raw date value while mapping to the correct millisecond date.
  • Improved compatibility when parsing responses containing unrecognized enum values, helping preserve data from newer or differing server responses.