The atproto data model has no float. The editor's sliders are fractions, so every camo carrying settings failed to serialise inside atrium — before any request was built — and players got a 502 about a server that had never been asked. The blob upload before it had already succeeded, which is what made that message so misleading. Sliders are thousandths now: 0..1000 for a 0..1 control, which is the answer the lexicon linter already gives for schemas — no float, use an integer and say what the units are. The version goes to 2 so a v1 record, which could never actually have been written, is dropped rather than read as if 510 meant 0.51. The test now walks everything the record carries and asserts each number is whole. Its fixture used integers before, which is exactly why it passed while production failed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>