fix: do not scan custom wrappers for GleamView.Line

CHANGELOG.md

@@ -16,14 +16,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
-- `GleamView.Line` nested inside intermediate wrappers (e.g. `<View>`) is detected on the first render — stable ref, no NativeGleamView→View flip
+- `GleamView.Line` nested inside `View` or Fragment wrappers is detected on the first render — stable ref, no NativeGleamView→View flip
 
 ### Fixed
 
 - CI: add missing CocoaPods cache step referenced by the iOS build job
 - CI: always run `pod install` after cache restore (codegen needs fresh `build/generated`)
 - CI: stop caching `vendor/bundle` (stale gems broke Ruby 3.4 pod install)
 - Example: add `nkf` and `base64` gems for Ruby 3.4 / CocoaPods compatibility
+- `GleamView.Line` detection no longer walks custom component `children` (avoids disabling the parent shimmer when a nested `GleamView` owns those Lines)
 
 ## [1.0.6] - 2026-05-15
 

README.md

@@ -83,7 +83,7 @@ When `loading={true}`, each `GleamView.Line` renders its own shimmer bar, sized
 
 Lines inherit `loading`, `speed`, `direction`, `baseColor`, `highlightColor`, `intensity`, `transitionDuration`, and `transitionType` from the parent. `delay` and `onTransitionEnd` are per-line.
 
-For best performance, place `GleamView.Line` as direct children of `GleamView` (or inside fragments). Lines nested inside intermediate wrappers (e.g., `<View>`) are detected automatically on the first render.
+For best performance, place `GleamView.Line` as direct children of `GleamView` (or inside fragments). Lines nested inside `<View>` or fragments are detected on the first render. Custom wrappers still work; they register after mount.
 
 Every `GleamView` provides context to its subtree. A `GleamView.Line` always binds to its nearest `GleamView` ancestor — nested `GleamView` components each control their own Lines independently.