[moetemp]

What changed?

This PR writes and reads a WIT duration in a WIT-only (JSON) record in the proto3 JSON form, such as "1.5s", in .NET and TypeScript, as Python does.

• .NET: a TimeSpan or TimeSpan? property of such a model gets a JsonConverter for the proto3 form.
• TypeScript: an operation whose input or output holds a duration gets a transfer type converter. It always writes the string form, and it reads the string form and a number of milliseconds, so old payloads still decode.

Why?

.NET wrote "00:00:01.5000000", and TypeScript wrote whatever the caller gave, so the languages couldn't read each other's durations.

How did you test it?

The stream-service .NET and TypeScript goldens show the converters on CreateStreamRequest and ReadRecordsRequest. A sample test in each language round-trips wait and checks that the JSON text has "0.25s".

Based on fork PR #65.

[moetemp]

Closed as NOT-STREAM. Every streaming duration is in a proto-backed record, so it never goes through the JSON converter.