I went the tighter spec route in https://concise-encoding.org because that's the only safe way to go, and also versioned the spec AND documents because I know that even with the care I'm taking there will be mistakes to fix in the spec after release.
Aside: I like this data format. What prompted you to make your own?
> Inconsistent Duplicate Key Precedence
Ok this could still be a problem, though I doubt it would be in practice and the article states "some serializers refused to create binary representations of multiple keys".
> Key Collision: Character truncation and Comments
Not possible with binary formats.
> JSON Serialization Quirks
N/A
> Float and Integer Representation
Not an issue with binary formats.
> Permissive Parsing and Other Bugs
Mostly not an issue with binary formats.
Unfortunately they said they tested some binary formats but didn't present the results!