Actually done? No. However, one use-case that i couild think of - beyond testing - would be to modularize some dev work. For example, maybe i have a junior dev who knows some http, but not experienced enough to be a lead dev, or something like that. I could give the junior dev a task like draft up some tech spec...Or, i could have them use their basic http skills and craft Hurl files...one for each function that will inevitably be a function in code...either to be done by a more senior dev, or who knows, maybe this same junior dev could eventually learn to code based on their own hurl files...which someone else might call pseudo-code (or pseudo-code in tech docs)...which eventually gets turned into production code...and those same hurl files can also be turned into test cases.

Anyway, for me, hurl looks like an evolution of curl...which makes sense since its built off of curl (https://hurl.dev/#powered-by-curl). So, for uses-cases that might reach beyond curl, that's when i might reach for hurl as well. No doubt, there could be other use-cases for hurl.