The issue has an empty description and so does this MR so I'm not sure how to approach it, but it appears that there were a couple other args that can be threaded through the FFI layer and that does that here, with a single test?

I intended to open this as a draft MR. Not sure why sometimes draft is the default and other times it is not.

Is there a pattern we could use to avoid breaking changes when arguments are changed - like a builder pattern? so qvm_multishot remains stable over time without breaking changes like this PR

I had discussed this with folks a while back, e.g. changing multishot(program, addresses, num_trials, NULL, NULL, &result) to multishot(request, &result) but had difficulty making that work in an ergonomic way. (If everything was in C, it would've been fairly simple, but handing that to (or back from) Lisp was more complicated.) It's also typical, if unsightly, to see C functions like this with many arguments. On the Rust side, it is much easier for us to use a builder pattern. From a BC perspective, I think this is the only incompatibility.