If a new (staging) ZIM has significant changes (for example, very larger or very smaller file size) in comparison to the previous published version (of the dame title/flavour), then it should trigger a warning and it should be manually validated (before publishing).
What "significant changes" exactly means has obviously to be defined and will be a heuristical tradeoff.
From a user perspective, the CMS behaviour should be very similar to the scenario when the zimcheck quality tradeoffs are not reached.
This is necessary to avoid to publish ZIM files which are broken, but not in a way that the scraper or zimcheck woukd be able to detect it.
If a new (staging) ZIM has significant changes (for example, very larger or very smaller file size) in comparison to the previous published version (of the dame title/flavour), then it should trigger a warning and it should be manually validated (before publishing).
What "significant changes" exactly means has obviously to be defined and will be a heuristical tradeoff.
From a user perspective, the CMS behaviour should be very similar to the scenario when the zimcheck quality tradeoffs are not reached.
This is necessary to avoid to publish ZIM files which are broken, but not in a way that the scraper or zimcheck woukd be able to detect it.