Adapt Exit Scanner to Firefox automation framework
Assuming the forensic automation works out as a stepping stone to automated testing, it wouldn't be too much of a stretch to adapt TorFlow to guide the exit choices of the Firefox tests, to see if any exits cause Firefox to either leak to disk, bypass proxy, or simply do weird stuff or fail to load webpages.
This would also involve integration with prototype sandboxes and possibly even VM instrumentation, to watch for evidence of exploit/violation.
Putting this component in TorFlow for now, but it is probably shard with QA and sandboxing.