It seems like:
- A Kronos server returning malformed json (in production?)
- A Kronos client being performance-sensitive (in test?)
are mutually exclusive.

That said, I'll add an issue to track this.