Release v0.6.0

Added

• Binary values: []byte fields (and named byte-slice types, with one optional pointer) are written as base64 strings that match the C# client, including + escaped as \u002B, "" for empty values and omission of nil values. Supported shapes are fields in event payloads, including fields inside nested objects, top-level read-model fields, and From AutoMap copies between binary fields (part of #64)

Changed

• Binary values are refused with ErrUnsupported before registration in every other use. That includes collections of binary values, which the pinned kernel corrupts when projecting them (Cratis/Chronicle#4595). It also includes maps, joins, variants, keys, identities, subjects, indexes, unique constraints, protection, event migrations and literals. Types that contain binary values must use simple ASCII property names that are unique regardless of case and are not reserved by the kernel (part of #64)
• Decoding a binary value accepts only canonical, padded base64. Values with whitespace or null elements, which the C# client tolerates, are rejected (part of #64)