In the generated schematron files, the match statements all start with "//". This is unnecessary as schematron checks all matches anyhow. The only exception is if a single resource has contexts that could all match a single resource - but including the // shouldn't make a difference there. We need to investigate what was really broken previously that caused schematrons to get missed for "contained" resources and figure out the correct way to fix it. (I've tested and removing "//" from match doesn't seem to interfere with catching issues inside contained resources.)