Stale module resolution after repository restore in Ceylon

Local Repository Metadata Consistency

Ceylon utilizes a local repository (typically ~/.ceylon/repo) to store compiled module artifacts. When restoring this repository from a backup to maintain build reproducibility or migrate environments, the directory structure is restored to its original location to allow the toolchain to locate dependencies.

While the physical artifacts are restored, there is uncertainty regarding the behavior of the internal metadata cache. If the restored repository contains metadata files that do not align with the current environment or if the cache is not automatically invalidated upon restoration, the toolchain may attempt to resolve modules using stale data.

Given that the toolchain lacks a dedicated automated verification command for repository integrity, it is unclear how the system handles these cached states during a manual restore process.

• Does the Ceylon toolchain automatically detect and refresh the internal metadata cache after a repository restoration?
• Is a manual clearing of the .ceylon metadata files required to prevent stale module resolution?