JevCodecs

The models endpoint wraps its array in a models field:

{"models": [{"name": "jev-latest", "description": "...", "release_date": "..."}]}

That envelope is a wire detail the official SDKs unwrap, and so does the client's models, so it gets a decoder rather than a type of its own. Not a given: it would shadow circe's list decoder for every caller.

Jev never refuses, so com.softinio.verdict4s.algebra.Answer.Refused has no documented encoding; it is written as a bare {"type": "refusal"} so that a fake can still serve one, and read back by the decoder.

Hand-written rather than derived, because three details matter and a generic derivation gets all three wrong:

• an absent Noul criteria means the key is absent, never null
• a Choice rubric of null is meaningful and must be emitted as an explicit null value under its key, so dropNullValues is wrong
• key order is deterministic, which is what makes the golden tests stable and identical on the JVM and on Node