We want to make it easy to spin up bots for executing specific tests against hyperdrive.
"Fuzz" testing a range of inputs and trade types is one example of this.

Another more specific example is outlined in this issue:
delvtech/hyperdrive#375

The idea is to quickly & easily write an endpoint script (e.g. a notebook) that executes a series of deterministic trades and plots results so that one can better understand Hyperdrive behavior. This is unique from a "CI test", and is more of an investigation that would result in an internal infodoc.