Per-request context for source operations?

I need to be able to pass a context object to a source's remote operation, and then have that same context object passed to the success/error action that will follow.

It must be possible for this object to be a different object each time, so binding it with a closure when creating the source does not satisfy this requirement.

Is there already a way to do this?

No file or test is named. Start by locating the source remote-operation API and its success/error action flow, then determine whether each invocation can accept and forward a distinct context object. Done means the issue's per-request context requirement is answered or implemented and verified for both success and error paths.

Written by the indexing model from the issue text.