[markdennis22]

Why?

Four shared 2.17 schemas didn't match what the API sends: custom object instance attribute values, the admin avatar, event metadata values, and error codes, which a few validation errors send as integers. The Preview spec has the same schemas, and the next version is cut from Preview, so it needs the same fixes.

How?

Corrects the four schemas to match the API's current behaviour, in 2.17 and in Preview.

Risks

The Preview SDKs are generated from this spec, so these changes affect generated Preview types:

Change	Could SDK code stop compiling?	Did that code work before?
CustomObjectInstance.custom_attributes values become a CustomObjectInstanceCustomAttributesValue union of string, integer, number, boolean or reference object	Yes, where they were typed as strings	No. The API already returns numbers, booleans and reference lists
Admin.avatar becomes a new AdminAvatar object with image_url and type, instead of a string	Yes, if it reads avatar as a string	No. The API sends the object
ErrorErrorsItem.code becomes an ErrorErrorsItemCode union of string and integer	Yes, where it was typed as a string	No. A few validation errors send the HTTP status as an integer, for example 422

Notes for reviewers

• data_event.metadata now lists the value types. The Preview Fern overrides already keep metadata a free-form map, so its Preview type doesn't change.
• fern check shows 0 errors. There are no new dangling refs and no operationId changes, and no changed Preview type is a bare unknown.

_{Generated with Claude Code}