DNF module stream cache expiration behavior with metadata_expire

Context

Rocky Linux 9.2 and later use DNF with modular package streams, where dnf module list displays available streams and profiles. The DNF configuration directive metadata_expire (default 6h) controls how long repository metadata is considered fresh before a forced refresh.

Goal

Understand whether the metadata_expire timer applies uniformly to both base repository metadata and module stream metadata, or if module stream data follows a separate expiration policy.

Constraints and uncertainty

The DNF documentation describes metadata_expire for repository metadata, but module streams introduce an additional metadata layer (modulemd). It is unclear whether a single expiration governs both, or if module metadata can become stale while base metadata remains fresh, leading to dnf module list showing outdated stream availability after a stream is added or removed upstream.

Questions

1. Does metadata_expire control expiration of module stream metadata (modulemd) in the same way as primary repository metadata?
2. If module metadata has a separate cache lifetime, what configuration directive governs it?
3. Can a stale module cache cause dnf module install to fail with a stream-not-found error even when dnf repolist shows current repository data?