Does a Fedora Silverblue rebase preserve rpm-ostree layered packages in newly created Toolbox containers?

Fedora Silverblue delivers an immutable base image via rpm-ostree, allowing developers to add packages with rpm-ostree install as layered overlays that survive atomic rebases. Toolbox containers provide mutable userspace environments tied to the host Fedora version, sharing the kernel and system libraries. The goal is to achieve a repeatable development environment where layered host packages are automatically visible inside Toolbox containers after a system rebase, ensuring consistency regardless of when the container is created.

However, the documentation does not clearly state whether layered packages are automatically included in newly created Toolbox containers following a rebase, leading to uncertainty about environment reproducibility when containers are created before or after an update.

Does the current Toolbox creation process inherit the host’s layered package set after a rebase? If not, what steps are required to synchronize the container’s userspace with the host’s layered overlays? Are there any plans to document or change this behavior in upcoming Fedora Silverblue releases?