### Overview On Drupal 11.3, the prop shape repository's cache is left orphaned during installation, so Canvas does not (re)generate Components when configuration that should trigger regeneration changes. For example, on a fresh site, creating an image media type before Canvas has been used does not rewire image-prop components to offer the media library — the affected Components keep their earlier (file/image widget) definition until the next cache rebuild. The cache is warmed lazily the first time Canvas is used, so the failure only manifests in the window between install and first Canvas use / cache rebuild. Root cause: since Drupal 11.3, installing a theme rebuilds the service container (core: *ThemeInstaller now resets the container in install/uninstall*, via `DrupalKernel::updateThemes()` — https://www.drupal.org/node/3551652). Canvas installs `canvas_stark` during its own module install, rebuilding the container mid-hook and orphaning the injected component source manager / prop shape repository; the prop shapes resolved immediately afterwards are written to the orphaned instance, never the live one, so the persistent cache is left cold after install. Latent until #3591606 (commit `987c26102`, 2026-06-02) moved prop-shape resolution into the discovery invoked during component generation — `git bisect`: green at `2e71db1`, first failing at `987c26102`. ### Steps to reproduce 1. Install Drupal with the **Minimal** profile, then install Canvas and the `canvas_test_sdc` test module, on Drupal 11.3 (fresh site). 2. *Before opening the Canvas page builder*, create an image media type (Structure → Media types → Add media type → Image). 3. Open the Canvas page builder and add the *card with a stream-wrapper image* component (provided by `canvas_test_sdc`). 4. Observe the image prop's input: it offers the plain file/image widget, not the media library selector — the Component was not regenerated to reference the new media type. 5. Run `drush cr` (or any cache rebuild) and repeat steps 3–4: the media library selector now appears. ### Proposed resolution When Canvas (re)generates Components immediately after installing `canvas_stark` during module installation, resolve the component source manager from the live container instead of the instance injected before the theme-install container rebuild — so the prop shape repository that gets populated is the one whose cache outlives the request. ### User interface changes None.