Having jointcal run as part of ci_hsc would be helpful for checking that jointcal changes don't break HSC processing. There is HSC data in testdata_jointcal, but it is not run with defaults and it is very small.
I don't know how hard it would be to add this as a step, but it would help give me confidence that a jointcal change doesn't cause a trivial HSC breakage.
Does ci_hsc also produce metrics for SQuaSH? If so, having jointcal run there would be even more useful.