autoscreen works on data from the repo and puts it in the staging/screened directory (e.g. refactor_test).
Currently it is dumb to any previous work, so acceptance isn't based on tests or criteria.
This may be an OK design. The question is "at what point do we merge in the previous hand-screening?" Do we want to do this inside the staging/formatted? And persist it before hand-screening? The problem is that it is a bit hard to describe that state.
Alternatively, we could apply auto-vs-hand merging at the point of hand screening.
@water-e mused
This is needed once we have hand-screening work which is being worked on here https://github.com/dwr-psandhu/dms_datastore_ui/issues/19