Summary
@include cannot forward a :for loop variable into a child component that has its own <script client> scope. The loop var stops at the child's scope boundary and its bindings render empty, so list-item components can't be composed — the markup must be duplicated into the parent instead.
Impact (real app)
In bench, the review-card component (resources/components/Bench/Feed.stx) was meant to be the reusable list item. Because the :for="review in reviews" variable can't cross into Feed's client scope, the entire card markup had to be inlined and duplicated into the parent (resources/components/Bench/ReviewsFeed.stx:354-439), and Feed.stx is now effectively dead code. The in-code comment documenting the boundary is at ReviewsFeed.stx:26-32.
This directly blocks adoption of defineProps / defineSlots for the most common UI pattern there is: rendering a list of item components.
Repro sketch
<!-- parent -->
<div :for="item in items">
@include('ItemCard', { item: 'item' }) <!-- item is the loop var -->
</div>
<!-- ItemCard.stx has a <script client> scope -->
<article>{{ item.title }}</article> <!-- renders empty: item never crosses the scope boundary -->Ask
Allow @include (or a first-class <ItemCard :item="item" /> component invocation) to forward the loop variable / props across a child component's client-scope boundary, so list items can be real components instead of duplicated markup.