Library publish does not propagate image assets referenced by overrides on nested instances

Hi,

Images inside a published library component fail to load in consuming files. We have narrowed down a consistent reproduction.

Steps to reproduce:
1. In a library file, create component A with an image fill applied directly to its own layer. Publish it. This works correctly everywhere.
2. Create an instance of A and replace the image in its slot (an image fill override on the instance).
3. Wrap that instance together with other layers into component B, and publish B as part of the same library.
4. In any consuming file, including a brand-new one, insert component B.

Result: the slot image does not load, and we get "An invalid image or thumbnail was removed."

Key observation: component A on its own always renders correctly, in every file. Only images that are referenced through an override on a nested instance fail to appear in consuming files. This suggests that assets living on a component's own layers are collected at publish time, while assets referenced only by an override on a nested instance are not.

Additional observation: repeatedly re-publishing the library restores images for some components while others remain broken, and the recovering subset differs each time. This indicates the image data does exist server-side and that propagation is partial and unreliable rather than absent.

Already tried, with no effect:
- Restarting the desktop app, and opening in a browser instead
- Replacing the images with freshly uploaded files from disk (new assets, not reused references)
- Duplicating the library file and publishing the duplicate
- Resetting instance overrides, swapping instances, re-inserting instances from the Assets panel 

We are unable to share the affected production file, but we can provide a minimal reproduction file built with placeholder images if that helps.

Question:
-Are image assets referenced by overrides on nested instances expected to propagate on library publish? If yes, this is a defect and we would like it filed.

This blocks our promotion template workflow, where slot-based image replacement is used on every campaign, so any guidance on a supported pattern would be appreciated. Thanks,