This also makes me wonder if it's a good idea to include a copy of the control experience as a sort of embedded A/A test within my A/B/n tests. True, an extra traffic toll, but also a way to common-sense-check the test results.

Hi Tim,It's an old thread but I was just exploring a similar question, and I believe this is now part of ACS Tools. See here: https://github.com/Adobe-Consulting-Services/acs-aem-tools/issues/15Cheers,Oleg

Just fixed this with the great support people of Dynamic Media. The issue was that the default invalidation template of only takes care of the main asset, and doesn't flush the smart crops. The solution was either to add the specific path to the required refocused smart crop in the confirmation dialog ("The following URLs will be invalidated in the CDN"), including the crop name, or to modify the template so that it mentions the main asset plus all possible smart crops::crop_1_name:crop_2_name....

And what is the limit for INPUT images provided to DM for initial processing?

This is an old thread! But since in 2020 I still had to google more than usual when faced with the same question, here's the link for everyone who'll arrive here looking for the answer:https://docs.adobe.com/content/help/en/dynamic-media-developer-resources/image-serving-api/image-serving-api/http-protocol-reference/command-reference/c-command-reference.html