After last Flock, I wrote a tool called check-compose which runs various checks on composes, and sends those mails to test@ and devel@ called "compose check reports".

The image-related checks it does could in fact move here. It checks whether any 'expected' images are missing, and diffs the images in the current compose against those in the last one. Both of these things could just as well happen here and show up in the Rawhide / Branched Report emails. Then check-compose would just be an openQA status mail.

It would be just about possible to do this right now, but I'd have to somehow hack up fedfind to handle a compose on a local filesystem (currently it always assumes it will be accessing the compose remotely). The reason we need fedfind is to synthesize the 'payload' for the compose. If we add that to productmd and pungi, we could do the checks quite efficiently without needing to involve fedfind at all.

(fedfind also provides a "previous compose" implementation - in fact it provides two! - but they're both about as silly as the one the releng scripts use at present. The lists of 'expected' images are also in fedfind, but they don't really have to be.)