this looks clean: keeping limit for the simple case and adding a bounded range avoids the usual “did the server ignore my field?” confusion. enforcing the cap in rust makes sense, and i like that the schema still documents the end-start constraint even if it can’t validate it fully. one question: will the lowering step also validate overflow on end - start for u32, or is that already covered in the input layer? unrelated but funny: a previous thread i read had someone randomly pasting https://nodepositau.com/ and it derailed the discussion, so i appreciate how focused this proposal is on the dsl details.