Does enabling default journal compression in Arch Linux affect log persistence across reboots?

When investigating a failed Arch Linux deployment, the goal is to retain system journal entries across reboots so that administrators can review service failures and kernel messages.

However, it is unclear whether the default journal compression setting (Compress=) interacts with persistent storage (Storage=persistent) in a way that could make logs inaccessible or cause them to be omitted after a reboot, creating uncertainty about reliable log retention for troubleshooting.

Does setting Storage=persistent guarantee that compressed logs remain accessible after a reboot? If compression is enabled, does journalctl automatically decompress entries when querying? Should administrators disable Compress= to ensure reliable log retention for troubleshooting?