Thanks for tackling this, Krzysztof, and apologies for the delay. I think this ticket realizes the vague idea for pipeline organization I had in my head, but I didn't quite have enough yaml subset pipeline-writing experience to implement from the get-go.

One question that will need a followup ticket is when we should use the new lsst.ip.diffim.getTemplate.GetMultiTractCoaddTemplateTask + lsst.pipe.tasks.imageDifference.ImageDifferenceFromTemplateTask instead of just lsst.pipe.tasks.imageDifference.ImageDifferenceTask.

That workflow is necessary for multi-tract differencing, has its own config + DM-30210 complications, etc.

The only things I'm confused about are exactly how the camera-specific ApVerify pipelines with fakes are supposed to work (see GitHub comments on the ap_verify PR).

I defer to Nate for any suggestions on making framework things better, but I'm very pleased with the ApPipe pipeline standardization, and as far as I can see, both it and the ApVerify pipelines do what they should without too many complicated import trains.

I had a few minor comments, but it mostly looks good as far as structure goes, and gives me so good feedback and ideas surrounding RFC-775 pipeline building. I am taking myself off the reviewers list.

If you ping me when you're done making changes, I can take a final look. I think I like Nate's suggestion to use "parameters" to streamline e.g. coadd/fakes names, both pre- and post- DM-30210.

Meredith Rawls, can you take a look at the new and improved pipelines? Thanks!

This looks great - thank you for standardizing all the indents and greatly improving all the configs! There's a lot here but as far as I can tell it all looks self-consistent. Let's get it merged, thank you for your attention to detail.