Feature Request: Allow main components to expose properties of components added via slots

Hi there! Our team is also using Slots and while we are really excited about the flexibility it gives, not being able to expose the properties of nested instances is proving to be a real drawback. 
 

I appreciate it at least saying ‘Modified’, but that’s not really helpful in knowing what that modification is or, more importantly, seeing the modifiable properties for the nested component (‘Interaction Destination’) in this example.

Yes, +1
 

Migrating to slots from instance swapping actually means losing that ability...

+1 this is such a loss when migrating to slots :( 

another thing is missing is the ability to use booleans when wrapping a Slot components.

For example, I have a NavBar base component with slots. I used this component as an instance, filled the slot with 2 component instances (Button 1 and Button 2), and i wrapped the NavBar into a ProductNavBar component. I want to add a boolean prop to show and hide one of the buttons.. I can’t do that right now.

same. to everything in this thread. running into the problem ​@NicoleSaidy is having, today.

100% support everything in this thread. This should be a must with nested components within a slot. Having to dive into complex nested layer structures just to edit props of a component inside a slot is poor UX.

+1 from another angle: we need to actually read what's inside a slot nested inside a sub-instance — not just expose its properties for editing, but see the content itself — and today slot.children doesn't cross that boundary at all via the Plugin API. There's no way to check what's there.

Looks like the same root cause as this thread (slots not fully traversable once nested), just a different symptom. Even read-only access to nested slot content would unblock a lot of tooling that needs to react safely to library updates.