On master, ci_hsc simply runs all CmdLineTasks in the prototype DRP pipeline, then runs custom validate code after each to check that outputs exist.
On the gen3-middleware branch, we also create a Gen3 data repository containing all outputs and re-run all validation code.
Once SuperTask conversion begins, we will want to have an easy way to include executing those SuperTasks in ci_hsc, regardless of whether preceding CmdLineTasks have been converted (we can do this by allowing SuperTasks to use the converted Gen2 outputs as inputs). We'd then want to follow this up with validating those outputs as well.
In the long-term, we will those validation steps to themselves be SuperTasks, and we'll want them to live outside ci_hsc. We'll also want to replace ci_hsc's SCons control logic with a real SuperTask executor. With those goals in mind, the end point of this ticket should just be a way to easily add a concrete SuperTask to ci_hsc and validate its outputs.