Here is an example that creates a new archive that uses compression-level="0" and algorithm="stored" and still compresses that entry.
Note that the archive level option 'algorithm' is unfortumate because often it is only single entries such as 'mimetype' or images that should not be compressed.
Thanks for the example. – My observation is that the entry is indeed archived uncompressed if you choose compression-level="0"; but I think what you are saying is that an uncompressed DEFLATE entry is not the same as an uncompressed STORED entry, right, and that ODS and ePub files require certain files to be stored with the STORED algorithm, is that right?
The Archive Module has a long history, and was initially based on a proposal for the Zorba XQuery Processor back in 2012. I don’t actually remember why the algorithm option was not adopted for the single archive entries; maybe that would have been more reasonable. As we seem to be the only implementation left today, we could think about changing that. I doubt anyway that people will use different compression levels for single archive entries (apart from archiving them uncompressed), so it might be a better solution to define one global compression level for the whole archive.