@symbiote-native/angular 3.1.1 → 3.1.2

package/src/components/image-shared.ts

@@ -1,8 +1,6 @@
-// The input surface and prop fold `AnimatedImage` builds on. The `Image` COMPONENT that used to
-// share it is gone (2026-09-10) — the primitive is the `<image>` tag, matched by `ImageElement`,
-// and `registerImageBehavior` folds its source on that path. `Animated.Image` is not a primitive
-// and stays a component, so what it needs from here survived the deletion; the folder collapsed to
-// this one flat file with it (`symbiote-file-layout`).
+// The input surface and prop fold `AnimatedImage` builds on. The primitive is the `<image>` tag
+// (`ImageElement`), which folds its source via `registerImageBehavior`; `Animated.Image` stays a
+// component and is the only consumer left, one flat file (`symbiote-file-layout`).
 import { EventEmitter, computed, signal } from '@angular/core';
 import {
   gateWanted,
@@ -562,10 +560,9 @@ export abstract class ImageBase {
     this.inputsRevision.update(revision => revision + 1);
   }
 
-  // MEASURED 2026-08-16: as a getter this rebuilt the bag on every refresh of this view, so
-  // `[symbioteHostProps]`'s reference check failed every time and every key was re-pushed through
-  // Renderer2 -> routeProp - pure waste when nothing changed. computed() returns the SAME object
-  // until a tracked dependency actually changes, and the input setter then skips the whole spread.
+  // A getter would rebuild the bag on every refresh, failing `[symbioteHostProps]`'s reference
+  // check and re-pushing every key through Renderer2 -> routeProp for nothing. computed() returns
+  // the SAME object until a tracked dependency changes, so the input setter skips the whole spread.
   //
   // A computed FIELD cannot be overridden by a subclass accessor the way a getter can, so the
   // platform components override buildImageProps() below and this stays the single memoization

package/src/components/input-accessory-view-props.ts

@@ -1,7 +1,6 @@
-// The `<input-accessory-view>` tag's prop surface. The tag is matched by
-// `InputAccessoryViewElement` (`../elements`) and commits one `RCTInputAccessoryView`; its whole
-// wrapper was a prop FOLD with no aliasing at all (`registerInputAccessoryViewBehavior`), so it was
-// deleted 2026-09-10 and the behavior applies the same mapping on the tag's own path.
+// The `<input-accessory-view>` tag's prop surface. The tag (`InputAccessoryViewElement`) commits
+// one `RCTInputAccessoryView`; `registerInputAccessoryViewBehavior` folds its props on that path,
+// no separate wrapper component needed.
 //
 // The type stays for a component forwarding a bag, and because `IAngularInputAccessoryViewProps` is
 // public API.

package/src/components/pressable-props.ts

@@ -1,7 +1,5 @@
-// The `<pressable>` tag's prop surface. The tag is matched by `PressableElement`
-// (`../elements`) and carries the press machine as an engine behavior
-// (`registerPressableBehavior`), so the wrapper that used to run it in Angular was deleted
-// 2026-09-10.
+// The `<pressable>` tag's prop surface. The tag (`PressableElement`) carries the press machine
+// as an engine behavior (`registerPressableBehavior`), no separate wrapper component.
 //
 // The type stays for a component forwarding a bag, for the four `Touchable*` prop types that share
 // this base, and because `IAngularPressableProps` is public API. Mirrors React's IPressableProps

package/src/components/refresh-control-props.ts

@@ -1,8 +1,6 @@
-// The `<refresh-control>` tag's prop surface. The tag is matched by `RefreshControlElement`
-// (`../elements`) and carries the controlled-spinner handshake as an engine behavior
-// (`registerRefreshControlBehavior` — mirror what native last reported, command it back when the
-// app's `refreshing` disagrees, RefreshControl.js:145-166), so the wrapper that ran that in Angular
-// was deleted 2026-09-11.
+// The `<refresh-control>` tag's prop surface. The tag (`RefreshControlElement`) carries the
+// controlled-spinner handshake as an engine behavior (`registerRefreshControlBehavior`: mirror
+// what native last reported, command it back when `refreshing` disagrees), no wrapper component.
 //
 // WHERE it goes is the ScrollView's decision, not this tag's: write it as an ordinary FIRST CHILD
 // on both platforms and the scroll-view behavior re-parents it — iOS a sibling before the content

package/src/components/safe-area-view-props.ts

@@ -1,8 +1,6 @@
-// The `<safe-area-view>` tag's prop surface. The tag is matched by `SafeAreaViewElement`
-// (`../elements`) and commits a single `SafeAreaView` native view whose host insets its children to
-// the safe area; there is no JS-side translation to do, so the wrapper that used to fold
-// aria/role and forward a host bag was deleted 2026-09-10 — the engine's own aria fold and the
-// renderer's `id` -> `nativeID` alias cover both, on every path.
+// The `<safe-area-view>` tag's prop surface. The tag (`SafeAreaViewElement`) commits a single
+// `SafeAreaView` native view that insets its children; no wrapper component needed, since the
+// engine's own aria fold and the renderer's `id` -> `nativeID` alias already cover both.
 //
 // The type stays for a component forwarding a bag, and because `IAngularSafeAreaViewProps` is
 // public API. Mirrors React's ISafeAreaViewProps minus children, which Angular takes via

package/src/components/scroll-view-props.ts

@@ -1,12 +1,9 @@
 // The `<scroll-view>` / `<horizontal-scroll-view>` tag's prop surface — the axis is the TAG you
 // write, not a `horizontal` binding, because Android resolves a different native class per axis.
 //
-// The wrapper was deleted 2026-09-11 and nothing replaced it in the adapter: the ENGINE owns the
-// whole shape now (`core/components/src/behaviors/scroll-view/`). `buildStructure` builds the
-// content node the children go under, `slotProps` routes `contentContainerStyle` onto it as its
-// `style`, `payloadFold` composes the two base styles, and the sticky machinery pins by DOCUMENT
-// ORDER through the `<sticky-header>` tag — so the Angular projection bridge that used to wrap
-// projected children by index is gone with it, along with its renderer hooks.
+// The ENGINE owns the whole shape (`core/components/src/behaviors/scroll-view/`), no adapter
+// wrapper: `buildStructure` builds the content node, `slotProps` routes `contentContainerStyle`,
+// `payloadFold` composes the base styles, sticky pins by DOCUMENT ORDER via `<sticky-header>`.
 //
 // A `<refresh-control>` is an ordinary FIRST CHILD on both platforms; the behavior re-parents it
 // per platform (iOS a sibling before the content, Android the swipe layout WRAPPING the scroll

package/src/components/text-input-props.ts

@@ -1,7 +1,6 @@
-// The `<text-input>` / `<text-input-multiline>` tag's prop surface. The tags are matched by
-// `TextInputElement` / `MultilineTextInputElement` (`../elements`) and carry the controlled-input
-// machine as an engine behavior (`registerTextInputBehavior`), so the wrapper that used to run the
-// handshake, the imperative handle and the autoFocus command in Angular was deleted 2026-09-11.
+// The `<text-input>` / `<text-input-multiline>` tag's prop surface. The tags
+// (`TextInputElement`/`MultilineTextInputElement`) carry the controlled-input handshake, the
+// imperative handle and the autoFocus command as an engine behavior (`registerTextInputBehavior`).
 //
 // Which of the two intrinsics a `<text-input multiline>` commits is the ENGINE's decision
 // (`intrinsicWhen` on the spec entry), not a template branch — the wrapper's `@if`/`@else` over two

package/src/components/touchable-props.ts

@@ -1,10 +1,8 @@
 // The prop surfaces of `<touchable-opacity>` and `<touchable-highlight>`, for Angular.
 //
-// No components left to type — the elements ARE the tags, matched by `TouchableOpacityElement` and
-// `TouchableHighlightElement` (`../elements`), and both machines run on the engine node
-// (`registerTouchableOpacityBehavior` / `registerTouchableHighlightBehavior`): the opacity fade is
-// an engine-side style layer over the responder, and the underlay swap is the same `activeStyle`
-// channel a `:active` rule uses. The wrappers that ran those in Angular were deleted 2026-09-11.
+// No components left to type — the elements ARE the tags (`TouchableOpacityElement` /
+// `TouchableHighlightElement`), both running on the engine node: opacity fade is an engine-side
+// style layer over the responder, underlay swap rides the same `activeStyle` a `:active` rule uses.
 //
 // Declared per-adapter over the Angular Pressable INPUT surface, since children arrive through
 // content projection rather than as a field — the split

package/src/components/virtualized-list/index.ts

@@ -362,13 +362,9 @@ interface IWindowCell<ItemT> {
           @if (gapSpacerStyle !== null) {
             <view [style]="gapSpacerStyle"></view>
           }
-          <!-- The separator sits INSIDE the measuring view, as RN's own cell renderer places it
-               (VirtualizedListCellRenderer.js:218-221). As a sibling it is an extra flex child, so
-               the chrome between two cells is gap + separator + gap while a spacer collapsing that
-               region replaces it with a single gap — every cell below the leading spacer then lands
-               short by (separator + gap) and the content jumps by that much whenever the window's
-               first index moves. Measured at exactly 17px on device 2026-08-19; see
-               .claude/rules/list-geometry-feedback-loop.md. -->
+          <!-- Separator sits INSIDE the measuring view, matching RN's cell renderer
+               (VirtualizedListCellRenderer.js:218-221) — as a sibling it'd add an extra flex gap.
+               See list-geometry-feedback-loop.md. -->
           @for (cell of windowCells; track cell.key) {
             @if (cell.isSticky) {
               <sticky-header
@@ -1205,11 +1201,9 @@ export class VirtualizedList<ItemT = unknown>
 
     const cells: IWindowCell<ItemT>[] = [];
     for (const planned of plan.cells) {
-      // RN gates the separator on the last index of the DATA, not of the WINDOW
-      // (VirtualizedList.js:793 `const end = getItemCount(data) - 1`), and now that the separator
-      // lives INSIDE the measuring wrapper that distinction is load-bearing: gating on the window
-      // would make a cell's own measured height change as the window slides past it. Device-measured
-      // 2026-08-19 as a run of cells all shifting by exactly the divider's 1px.
+      // RN gates the separator on the last index of the DATA, not the WINDOW
+      // (VirtualizedList.js:793 `getItemCount(data) - 1`). The separator lives INSIDE the
+      // measuring wrapper, so gating on the window would shift a cell's height as it slides past.
       const includeSeparator = hasSeparators && planned.index < m.count - 1;
       cells.push(
         this.buildWindowCell(

package/src/create-portal/index.ts

@@ -27,12 +27,9 @@
 // resolving a template reference variable, so `strictTemplates` rejects anything else at compile
 // time and there is nothing left to guard at runtime.
 //
-// THE MARKER GOES ON AN `<ng-container>` INSIDE THE TARGET, never on the target element. A
-// ViewContainerRef anchors AT its host and `createEmbeddedView` inserts after that anchor, so
-// `<view portalOutlet>` delivers a SIBLING where React's `createPortal(node, host)` and Vue's
-// `<Teleport to>` deliver a child. Device-reported 2026-09-02: a card portaled into an absolutely
-// positioned overlay laid out in the scroll flow, since the overlay cannot centre a node that is
-// not in it.
+// THE MARKER GOES ON AN `<ng-container>` INSIDE THE TARGET, never on the target element:
+// ViewContainerRef anchors AT its host, so `<view portalOutlet>` delivers a SIBLING where React's
+// `createPortal` and Vue's `<Teleport to>` deliver a child — breaks centering inside an overlay.
 
 import {
   Directive,

package/src/elements.ts

@@ -105,11 +105,9 @@ export abstract class SymbioteElement implements OnChanges {
   // MATCHES on the callback attributes instead, registering it against the node; `markViewFor` is how
   // the wrapper reaches it. The inputs did not move, so nothing about this file's public surface did.
 
-  // THE `on*` WRAPPER LEFT THIS CLASS on 2026-09-18, for `SymbioteRenderer.setProperty`. Most of
-  // these directives are withheld from runtime matching now (`./runtime-matching`), so a binding
-  // reaches the renderer through `ɵɵproperty` without passing through any directive — a wrapper that
-  // lives here would simply stop running. The renderer is reached by every path, which is the home it
-  // should have had.
+  // No `on*` wrapper here: `SymbioteRenderer.setProperty` handles it. Most directives are withheld
+  // from runtime matching (`./runtime-matching`), so a binding reaches the renderer through
+  // `ɵɵproperty` without passing through any directive — the renderer is reached by every path.
 
   @Input() testID?: IElementProps['testID'];
   @Input() nativeID?: IElementProps['nativeID'];
@@ -255,22 +253,9 @@ abstract class ReadBackElement extends SymbioteElement implements OnDestroy {
     }
   }
 
-  // REPORTED, NOT RETHROWN, and it is Angular's own contract rather than a swallow. Every other
-  // change detection in an app runs inside `ApplicationRef.tick()`, which catches and hands the
-  // error to `ErrorHandler` — `render/index.ts` provides `SymbioteErrorHandler` for exactly that,
-  // after an unprovided token once turned every async tick exception into a hard crash. This flush
-  // is the ONE change detection that runs outside that boundary: the engine calls it from inside a
-  // native event dispatch, where a throw has nowhere to go but `RCTFatal`.
-  //
-  // Device-diagnosed 2026-09-20 on ApiPlaygroundScreen. `PlaygroundLifecycleLogger` emits from
-  // `ngDoCheck`/`ngAfterContentChecked`/`ngAfterViewChecked` and the screen's handler writes a
-  // signal its own template reads, so the view re-dirties itself on every pass and
-  // `detectChangesInViewWhileDirty` throws NG0103 after MAXIMUM_REFRESH_RERUNS. The scheduler's own
-  // ticks were already hitting it and reporting it quietly; the first KEYSTROKE took the same throw
-  // through here and killed the app — `Terminating app due to uncaught exception
-  // 'RCTFatalException: Unhandled JS Exception: Error: NG0103'`, with no redbox because Release has
-  // none. So the app bug is the app's, and a flush that turns a reported error into a fatal one is
-  // ours: a keystroke must not be stricter than a tick.
+  // REPORTED, NOT RETHROWN — Angular's own contract. Every other change detection runs inside
+  // `ApplicationRef.tick()`, caught by `ErrorHandler` (`SymbioteErrorHandler`); this flush instead
+  // runs from a native event dispatch, where an uncaught throw has nowhere to go but `RCTFatal`.
   private flush(): void {
     try {
       this.detector.detectChanges();
@@ -739,7 +724,7 @@ abstract class SymbioteValueAccessor
         // mirrors it, which is the shape rather than a workaround. A later `writeValue` still wins,
         // so an app that transforms or refuses the value keeps doing so, one microtask on.
         //
-        // Device-reported 2026-09-20: every character snapped the field back to its mounted text.
+        // Without this, every character snaps the field back to its mounted text.
         this.setProp('value', value);
         fn(value);
       },
@@ -945,10 +930,9 @@ type IMissingInputs<TProps, TDirective, TIgnored extends PropertyKey = never> =
 const DECLARES_EVERY_PROP: {
   view: IMissingInputs<IElementProps, ViewElement>;
   pressable: IMissingInputs<IAngularPressableProps, PressableElement>;
-  // The two touchables, added when their wrappers were deleted (2026-09-11). They inherit
-  // `PressableElement`, so the rows above would pass whatever these declared — what they pin is the
-  // per-touchable surface (`activeOpacity`, `underlayColor`, the three timing knobs), which used to
-  // be fenced by a source-text assertion over the wrapper's template in `angular-gaps.test.ts`.
+  // The two touchables inherit `PressableElement`, so the rows above would pass whatever these
+  // declared — what they pin is the per-touchable surface (`activeOpacity`, `underlayColor`, the
+  // three timing knobs).
   touchableOpacity: IMissingInputs<
     IAngularTouchableOpacityProps,
     TouchableOpacityElement

package/src/gate-demand.ts

@@ -18,7 +18,7 @@
 // nothing in this repo could detect and nothing on screen would show. A `viewProviders` entry is
 // not part of the component's binding surface, so an app cannot reach it by accident.
 //
-// WHY `viewProviders` AND NOT `providers` — measured, both arms, 2026-09-02:
+// WHY `viewProviders` AND NOT `providers`:
 //
 //   viewProviders   the wrapper's OWN template sees it, projected content does NOT
 //   providers       both see it

package/src/index.ts

@@ -5,12 +5,9 @@
 // SEAM SCAFFOLD: mount/unmount + the renderer seam + host intrinsic selectors. Full RN-like
 // composed components still flow through the shared @symbiote-native/components bridge.
 //
-// `View` AND `Text` ARE NO LONGER WORTH IMPORTING, and on 2026-09-18 the examples stopped. They are
-// `@Component`s on the `view` and `text` SELECTORS — a second mechanism on the same tags
-// `SYMBIOTE_ELEMENTS` covers, kept for one stated reason their own header gives: "Declaring `style`
-// as a real Angular input prevents Angular's CSS style engine from decomposing RN `StyleProp`
-// arrays". A tag takes an array or press-state callback as `[styleProp]`, a plain property binding
-// with no instance behind it.
+// `View` AND `Text` ARE NOT WORTH IMPORTING — a tag covers the same selectors via
+// `SYMBIOTE_ELEMENTS`. They stay as `@Component`s only because a real Angular `style` input stops
+// Angular's CSS engine decomposing RN `StyleProp` arrays; a tag takes it as `[styleProp]` instead.
 //
 // An app loses nothing it cannot spell better: `@ViewChild('ref')` on a template reference returns
 // Angular's own `ElementRef<IHostInstance>`, whose `nativeElement` IS the engine host node — the same
@@ -137,28 +134,9 @@ export type {
   ITextInputChangeEvent,
 } from './components';
 export { setImageSourceResolver } from './components';
-// The element directives that make a HAND-WRITTEN intrinsic tag (`<view>`, `<text-input>`, ...)
-// compile under ngtsc with no schema, and with a real type on every declared prop. See `elements.ts`
-// for why a directive rather than `CUSTOM_ELEMENTS_SCHEMA`/`NO_ERRORS_SCHEMA`.
-//
-// `imports: [SYMBIOTE_ELEMENTS]` IS THE ONLY SUPPORTED SPELLING — and the individual classes are
-// exported anyway, because ngtsc requires it and a build proves it.
-//
-// They were removed on 2026-09-18 and put back the same hour. The reason to remove them is real: a
-// withheld tag directive (`./runtime-matching`) is a compile-time declaration and nothing else, so
-// what makes `<view [onPress]="fn">` work at all is `SymbioteCallbackHost` claiming the name before
-// `setDomProperty` throws NG0306. It rides this array, so a narrow `imports: [ViewElement]`
-// type-checks and then fails on a device the first time the app binds an `on*` prop.
-//
-// WHAT PUTS THEM BACK is NG3004: `Unable to import directive ViewElement — the symbol is not
-// exported from index.d.ts`. ngtsc resolves every directive reachable through an imported array to an
-// IMPORTABLE NAME in the package's public types, so a class inside `SYMBIOTE_ELEMENTS` that the
-// barrel does not name breaks AOT for every screen that uses the array. The removal passed its own
-// vitest guard and every headless suite, and failed on the first real `ngc` run — the same
-// wrong-harness green this repo keeps finding.
-//
-// So the narrow spelling is DISCOURAGED and not prevented, and `elements-are-exported-for-aot.test.ts`
-// now asserts the opposite invariant: every member of the array is named here.
+// Element directives for a hand-written intrinsic tag (`<view>`, `<text-input>`, ...); see
+// `elements.ts` for why a directive rather than a schema. `imports: [SYMBIOTE_ELEMENTS]` is the
+// only supported spelling — a narrower array type-checks but fails AOT's NG3004 on-device.
 export {
   SYMBIOTE_ELEMENTS,
   SymbioteElement,

package/src/modules/animated/create-animated-component.ts

@@ -409,13 +409,9 @@ export class AnimatedImage
   changeDetection: ChangeDetectionStrategy.OnPush,
 })
 export class AnimatedScrollView extends AnimatedComponentBase {
-  // Nothing left to override: `registerScrollViewBehavior()` (`../../register.ts`) now owns the
-  // content node, `scrollViewBaseStyle`/`nestedScrollEnabled` defaults, and the sticky seam for
-  // this SAME `scroll-view` tag. This class used to build its own `<scroll-content>` child by
-  // hand — deleted 2026-09-11, since that made TWO owners of the content node the moment the
-  // behavior registered on this tag: the engine's own `buildStructure` and this template both
-  // creating one. `<ng-content>` now lands directly under the owner and the behavior redirects it
-  // into the content node it builds, same as every other `<scroll-view>` in the app.
+  // Nothing left to override: `registerScrollViewBehavior()` owns the content node, base style
+  // and sticky seam for this SAME `scroll-view` tag. Building `<scroll-content>` here too would
+  // give the node two owners; `<ng-content>` lands under the one the behavior already builds.
 }
 
 // List components are already explicit AOT-compiled Angular components with their own full input

package/src/primitives/index.ts

@@ -21,21 +21,8 @@ export {
 })
 export class ViewHost extends SymbiotePrimitiveHost {}
 
-/**
- * Text is an ORDINARY primitive host as of 2026-09-18, and the two `@Input()`s it used to declare
- * are gone with the code that needed them.
- *
- * They existed for one stated reason: a default can only be applied by code that can SEE whether the
- * caller supplied a value, and a pass-through host binding is invisible to the component — so the
- * defaults had to be applied where the inputs were readable. That argument was sound and it is now
- * answered one layer down. The payload builder reads the AUTHORED bag, so it can tell an absent
- * `ellipsizeMode` from an explicit `clip` without anyone declaring anything; the rule is keyed on the
- * component (`foldTextDefaults`, `SymbioteFabricProps.cpp`) and reaches every `RCTText` however it
- * was spelled.
- *
- * The pass-through is therefore the CORRECT path for both props now, and `text-defaults.test.ts`'s
- * "never overwrites a value the caller supplied" is what proves the authored value still arrives.
- */
+// Text is an ordinary primitive host — no `@Input()`s for defaults; `foldTextDefaults` (C++)
+// reads the authored bag directly, so an absent value never needs declaring here.
 @Component({
   selector: 'text',
   standalone: true,
@@ -99,10 +86,9 @@ export class MultilineTextInputHost extends SymbiotePrimitiveHost {}
 })
 export class SwitchHost extends SymbiotePrimitiveHost {}
 
-// The centering RCTView RN wraps the spinner in (ActivityIndicator.js:112), not the spinner —
-// which is what this tag resolved to until 2026-09-09. The native view moved to
-// `activity-indicator-spinner`, built by the engine's ActivityIndicator behavior, so nothing writes
-// it in a template and it needs no host here.
+// The centering RCTView RN wraps the spinner in (ActivityIndicator.js:112) is
+// `activity-indicator-spinner`, built by the engine's ActivityIndicator behavior — nothing writes
+// it in a template, so it needs no host here.
 @Component({
   selector: 'activity-indicator',
   standalone: true,

package/src/primitives/shared.ts

@@ -287,12 +287,9 @@ export class SymbioteHostPropsDirective {
     return this.elementRef.nativeElement;
   }
 
-  // MEASURED 2026-08-20, headless 1000-row create: writing every key of every bag cost 104 000
-  // engine setProp calls where Solid's identical screen cost 12 000 — and 90 000 of them carried
-  // `undefined`. A composed component's bag is a FIXED-SHAPE literal (Pressable's is ~48 keys,
-  // most of them unset on any given instance), so the first push of a fresh node spends most of
-  // its work deleting keys the node never had. Diffing per key removes exactly that: an unset key
-  // is skipped on mount and still written the moment it changes to or from a real value.
+  // A composed component's bag is a FIXED-SHAPE literal, most keys unset on any given instance, so
+  // writing every key on the first push spends most of its work on keys the node never had.
+  // Diffing per key skips an unset one on mount and writes it only when it gains a real value.
   set symbioteHostProps(props: Record<string, unknown>) {
     const pushed = this.pushed;
     // Only keys the node actually carries, so the vanished-key sweep below walks a handful rather

package/src/renderer/index.ts

@@ -62,17 +62,9 @@ function isRecord(value: unknown): value is Record<string, unknown> {
   return typeof value === 'object' && value !== null;
 }
 
-// RN's TWO TEXT DEFAULTS LEFT THIS RENDERER ENTIRELY ON 2026-09-18, in two steps a fortnight apart.
-// The SEED went first, to the payload builder — writing them as props cost a crossing every time an
-// app authored the same value (6 000 per 1 000-row create, `writesOfUnchanged`). What stayed was a
-// resolver for the clear-back path: a write of `undefined` looked up the default instead of clearing.
-//
-// That is gone too, and for the reason the seed was: `applyTextDefaults` (and its C++ twin) runs on
-// EVERY commit of every `RCTText`, so a cleared key is absent for exactly as long as it takes the
-// payload builder to supply the default again. The resolver was answering a question nothing asks.
-//
-// `PROP_ALIASES` (`id` -> `nativeID`) left this renderer on 2026-09-18 — `routeProp` resolves it
-// for every adapter now, so every path that can set a prop still reaches it.
+// RN's two TEXT DEFAULTS and `PROP_ALIASES` (`id` -> `nativeID`) are NOT resolved here: text
+// defaults run once per commit in `applyTextDefaults` (C++ twin included), and `routeProp` resolves
+// aliases for every adapter — every path that can set a prop still reaches both.
 // Angular's two-way sugar `[(value)]` compiles to a `(valueChange)` binding; the engine knows the
 // same fold as the function prop `onValueChange`. See `listen()`. The two names live in a leaf
 // module so `elements.ts`'s ControlValueAccessor can name them without importing this cyclic file.
@@ -636,19 +628,9 @@ export class SymbioteRenderer implements Renderer2 {
     this.surface.requestCommit();
   }
 
-  // FlatList/VirtualizedList cells are content projected into a component host (our
-  // ANCHOR_HOST_COMPONENTS, e.g. ScrollView) — Angular's own addLViewToLContainer
-  // (.vendors/angular node_manipulation.ts/container.ts) treats a null parent here as "defer —
-  // the child component's own <ng-content>/ɵɵprojection will place this once its structure
-  // resolves" (e.g. ScrollView's `@if(isHorizontal)` branch). Renderer2's contract types this
-  // return as nullable for exactly that reason; returning `this.surface` as a non-null fallback
-  // defeated that defer check and caused premature top-level insertion (2026-07: FlatList cells
-  // rendered outside their ScrollView).
-  //
-  // Safe only because appendChild/insertBefore above now also treat a null parent as "skip, wait
-  // for projection" — a second Angular call site (`insertAnchorNode`, hit whenever a directive
-  // does `inject(ViewContainerRef)`, e.g. VListOutletDirective) forwards this null straight into
-  // insertBefore without checking it; without that guard it crashed on-device.
+  // FlatList/VirtualizedList cells project into a component host (ANCHOR_HOST_COMPONENTS, e.g.
+  // ScrollView); Angular defers insertion on a null parent until projection resolves, so a
+  // non-null fallback here breaks that. appendChild/insertBefore/insertAnchorNode skip null too.
   parentNode(node: IHostNode): IHostElement | null {
     return parentOf(node) ?? null;
   }