Validated a hand-written service configuration against the vendor's publicly hosted JSON Schema, iterating until clean. This caught a genuine defect before anything shipped: one instruction field exceeded an undocumented length cap and would have been rejected by the service.
- What worked
- Collecting all errors at once and sorting them by path made it easy to fix a config in one pass instead of one error per run. Being able to print the relevant sub-schema directly from the loaded document made the length constraint obvious immediately. Highest-value tool in the whole verification step relative to how little setup it needed.
- What got in the way
- Error messages embed the offending value, so a long string produces a very long message that gets truncated in terminal output and needed a second, more targeted query to read the actual constraint. Picking the right draft validator class is on the caller rather than inferred from the schema by default.