@symbiote-native/angular 0.3.0 → 0.3.2

package/src/__tests__/responder-change-detection.test.ts

@@ -4,7 +4,7 @@
 // does nothing" bug, while React/Vue repainted the same demo. SymbioteHostPropsDirective now
 // calls `cdr.markForCheck()` after each such callback (flags the component + ancestors with
 // RefreshView and notifies the scheduler), so the mutation repaints. This is the flat-root case;
-// responder-nested-cd.test.ts covers the App→child nesting the real app has. See skill §17.
+// responder-nested-cd.test.ts covers the App→child nesting the real app has.
 
 import '@angular/compiler';
 import { Component } from '@angular/core';

package/src/__tests__/responder-nested-cd.test.ts

@@ -4,7 +4,7 @@
 // flat-bag responder callback does NOT dirty the child's reactive consumer, and the scheduler's
 // root detectChanges() will NOT descend into it — the child's {{status}} used to stay stale
 // ("pan does nothing"). SymbioteHostPropsDirective now refreshes its own host component's view
-// right after the callback runs, so the nested child repaints. See angular-adapter skill §17.
+// right after the callback runs, so the nested child repaints.
 
 import '@angular/compiler';
 import { Component } from '@angular/core';

package/src/components/activity-indicator/activity-indicator-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): ActivityIndicator is its own
+// Regression test for the anchor/class bug: ActivityIndicator is its own
 // ANCHOR_HOST_COMPONENTS entry AND renders through DescriptorOutlet (`symbiote-descriptor-outlet`,
 // itself also an anchor entry) — a class= on <ActivityIndicator> resolves onto ActivityIndicator's
 // OWN anchor, two levels up from the real committed wrapper View the descriptor builds, and needs

package/src/components/activity-indicator/index.ts

@@ -1,4 +1,4 @@
 // Base/default ActivityIndicator. Re-exports the iOS build; Metro picks index.ios.ts /
-// index.android.ts in platform bundles. See ADR 0020.
+// index.android.ts in platform bundles.
 
 export * from './index.ios';

package/src/components/button.ts

@@ -2,14 +2,14 @@
 // TouchableOpacity wrapping a Text. The base text style, the role constant, and the color fold are
 // shared in @symbiote-native/components/view; here Angular only composes its TouchableOpacity + a
 // symbiote-text child and re-maps the few Button-owned props. The Angular twin of the React/Vue
-// adapter's Button. No JS-side platform branch, so this stays a flat single file (ADR 0026).
+// adapter's Button. No JS-side platform branch, so this stays a flat single file.
 //
 // RN's Button fixes accessibilityRole="button", marks the root accessible, and propagates `disabled`
 // into the accessibility state; those three win over any caller value. `title` becomes the Text
 // child; disabled forwards straight; touchSoundDisabled maps to the pressable's android_disableSound.
 // Every OTHER field of the shared IButtonProps (title, color, disabled, touchSoundDisabled, testID,
-// TV-focus, accessibility state) is agnostic and stays RE-EXPORTED from @symbiote-native/components verbatim
-// (<prop_types_split_agnostic_vs_per_adapter>). onPress and the four accessibility callbacks are the
+// TV-focus, accessibility state) is agnostic and stays RE-EXPORTED from @symbiote-native/components
+// verbatim. onPress and the four accessibility callbacks are the
 // exceptions: each is a real @Output() here (`press`, `accessibilityAction`, `accessibilityTap`,
 // `magicTap`, `accessibilityEscape`), mirroring the Vue adapter's Button, which forks the SAME onPress
 // field the same way (`Omit<ICoreButtonProps, 'onPress'>` + a `press` emit) — not a new precedent, the

package/src/components/flat-list/flat-list-array-style.test.ts

@@ -33,7 +33,7 @@ const chips: IChip[] = Array.from({ length: 24 }, (_unused, index) => ({
 // it reaches a `[style]=` binding — required of app authors (see App.ts) AND of every adapter
 // component that forwards its own `style` @Input() onward (see the `resolvedStyle` getters/fields
 // in virtualized-list, section-list, virtualized-section-list — flat-list's own `rowStyle` had the
-// identical landmine, always assigning an array). See the angular-adapter skill for the full story.
+// identical landmine, always assigning an array).
 @Component({
   selector: 'symbiote-chip-list-host',
   standalone: true,

package/src/components/flat-list/flat-list-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): FlatList is its own
+// Regression test for the anchor/class bug: FlatList is its own
 // ANCHOR_HOST_COMPONENTS entry, separate from the VirtualizedList/ScrollView anchors it wraps two
 // levels down — a class= on <FlatList> resolves onto FlatList's OWN anchor and needs its OWN
 // anchorHostStyle merge (see index.ts's ngOnChanges), it is NOT transitively fixed by

package/src/components/flat-list/flat-list-scroll-containment.test.ts

@@ -21,8 +21,8 @@ const chips: IChip[] = Array.from({ length: 24 }, (_unused, index) => ({
 }));
 
 // Mirrors examples/angular/App.ts's "FlatList · 24 chips" demo end to end: a horizontal FlatList
-// with getItemLayout. Regression coverage for a bug fixed 2026-07 (see angular-adapter skill §18):
-// cell content used to land OUTSIDE the ScrollView's content view entirely — as top-level siblings
+// with getItemLayout. Regression coverage for a bug fixed 2026-07: cell content used to land
+// OUTSIDE the ScrollView's content view entirely — as top-level siblings
 // of the committed RCTScrollView node, instead of children of its RCTScrollContentView — which is
 // why the device screenshot showed full-width vertically-stacked chips instead of a small
 // horizontal row. Root cause was `<ng-content>` declared once per `@if`/`@else` branch in

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

@@ -31,8 +31,7 @@
 // surface; FlatList re-exposes it by delegating to the inner VirtualizedList (@ViewChild). The
 // element-returning props (renderItem / ItemSeparatorComponent / List{Header,Footer,Empty}Component)
 // are templates in Angular, so they are absent from IFlatListProps, per the per-adapter
-// children/render split of <prop_types_split_agnostic_vs_per_adapter>; everything agnostic mirrors
-// IVirtualizedListProps.
+// children/render prop split; everything agnostic mirrors IVirtualizedListProps.
 
 import {
   CUSTOM_ELEMENTS_SCHEMA,

package/src/components/image/image-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): Image is its own
+// Regression test for the anchor/class bug: Image is its own
 // ANCHOR_HOST_COMPONENTS entry — a class= on <Image> resolves onto Image's OWN anchor and needs
 // its OWN anchorHostStyle merge (see index.ios.ts/index.android.ts's imageProps override), not
 // transitively fixed by anything else. Mirrors pressable.test.ts's "resolves a class=" case.

package/src/components/image-background-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): ImageBackground is its own
+// Regression test for the anchor/class bug: ImageBackground is its own
 // ANCHOR_HOST_COMPONENTS entry, separate from the Image it composes internally — a class= on
 // <ImageBackground> resolves onto ImageBackground's OWN anchor and needs its OWN anchorHostStyle
 // merge onto its wrapper View (see image-background.ts's wrapperStyle getter), NOT onto its

package/src/components/image-background.ts

@@ -41,7 +41,7 @@ import { anchorHostStyle, ViewHost } from '../primitives';
 
 // Mirrors React's IImageBackgroundProps minus children (Angular takes children via <ng-content>):
 // every forwarding Image prop flows onto the inner image; `style` is the WRAPPER View style and
-// `imageStyle` the inner image's, per <prop_types_split_agnostic_vs_per_adapter>.
+// `imageStyle` the inner image's.
 export interface IAngularImageBackgroundProps extends Omit<IImageProps, 'style'> {
   style?: IStyleProp<IViewStyle>;
   // A bare string resolves through the shared style registry, like `class` on the wrapper.

package/src/components/keyboard-avoiding-view.ts

@@ -6,7 +6,7 @@
 // Angular twin of React's setState / Vue's reactive ref), ngOnDestroy tears the subscriptions down,
 // and the wrapper's onLayout measures the frame that feeds the next event's inset. The user
 // children nest under the wrapper (or, for 'position', an inner View) via <ng-content>. No native
-// host of its own — it wraps symbiote-view — so this stays a flat single file (ADR 0026).
+// host of its own — it wraps symbiote-view — so this stays a flat single file.
 //
 // Full parity: behavior 'height'|'position'|'padding', enabled, keyboardVerticalOffset,
 // contentContainerStyle, onLayout, plus the full a11y/aria surface every View carries.
@@ -58,8 +58,8 @@ function isSymbioteEvent(value: unknown): value is ISymbioteEvent {
 }
 
 // Mirrors React's IKeyboardAvoidingViewProps minus children (Angular takes children via
-// <ng-content>), declared per-adapter over the shared a11y base per
-// <prop_types_split_agnostic_vs_per_adapter>.
+// <ng-content>), declared per-adapter over the shared accessibility base since a framework-specific
+// children field keeps it from being fully shared across adapters.
 export interface IAngularKeyboardAvoidingViewProps extends IAccessibilityProps, IAriaProps {
   behavior?: IKeyboardAvoidingBehavior;
   enabled?: boolean;
@@ -118,7 +118,7 @@ export class KeyboardAvoidingView implements IAngularKeyboardAvoidingViewInputs,
   // The wrapper's onLayout is a real @Output(): `(layout)="…"`, not `[onLayout]="…"`. Safe to
   // name it the same as the native `layout` event fired inside this component's own template
   // (see the class's `handleLayout`) — the engine's bubble() treats ANCHOR_HOST_COMPONENTS as
-  // transparent to listener lookup, so there is no double-fire (angular-adapter skill §7).
+  // transparent to listener lookup, so there is no double-fire.
   @Output() readonly layout = new EventEmitter<ISymbioteEvent>();
   @Output() readonly accessibilityAction = new EventEmitter<ISymbioteEvent>();
   @Output() readonly accessibilityTap = new EventEmitter<ISymbioteEvent>();

package/src/components/refresh-control.ts

@@ -1,12 +1,12 @@
 // RefreshControl, the Angular lifecycle half. On iOS this is the PullToRefreshView Fabric node that
 // lives INSIDE a ScrollView (a childless sibling before the content container); on Android it is
-// AndroidSwipeRefreshLayout and WRAPS the scroll view (ADR 0020), receiving it through <ng-content>.
+// AndroidSwipeRefreshLayout and WRAPS the scroll view, receiving it through <ng-content>.
 // The Angular twin of the React/Vue RefreshControl. There is no JS-side platform renaming and no
 // shared render fn — every prop forwards straight to the native node, which reads the ones it
 // understands and ignores the rest, so the Android-only and iOS-only families ride down harmlessly
 // on both. So this folds aria/role through the shared resolveAccessibilityProps and maps the native
 // props + a11y + onRefresh straight onto the symbiote-refresh-control host, children via <ng-content>.
-// No platform branch (one composed component both platforms), so this stays a flat single file (ADR 0026).
+// No platform branch (one composed component both platforms), so this stays a flat single file.
 //
 // `refreshing` is a controlled prop: the parent owns it and pushes it down each commit; native
 // reports the gesture via the direct `topRefresh` event, which the engine routes to the host's
@@ -54,8 +54,9 @@ function isSymbioteEvent(value: unknown): value is ISymbioteEvent {
 }
 
 // Mirrors React's IRefreshControlProps minus children (Angular takes the Android-wrapped scroll view
-// via <ng-content>), declared per-adapter over the shared a11y base per
-// <prop_types_split_agnostic_vs_per_adapter>. Read the React reference for the native prop names.
+// via <ng-content>), declared per-adapter over the shared accessibility base since the framework-specific
+// children slot keeps it from being fully shared across adapters. Read the React reference for the
+// native prop names.
 export interface IAngularRefreshControlProps extends IAccessibilityProps, IAriaProps {
   refreshing: boolean;
   // RN's onRefresh is `() => void | Promise<void>`, the handler may be async; the promise is

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

@@ -4,7 +4,7 @@
 // so this folds aria/role through the shared resolveAccessibilityProps and maps style +
 // a11y + onLayout straight onto the symbiote-safe-area-view host, children via <ng-content>.
 // The Angular twin of the React/Vue SafeAreaView. No platform branch (one Fabric name both
-// platforms), so this stays a flat single file (ADR 0026).
+// platforms), so this stays a flat single file.
 
 import {
   CUSTOM_ELEMENTS_SCHEMA,
@@ -32,7 +32,8 @@ function isSymbioteEvent(value: unknown): value is ISymbioteEvent {
 }
 
 // Mirrors React's ISafeAreaViewProps minus children (Angular takes children via <ng-content>),
-// declared per-adapter over the shared a11y base per <prop_types_split_agnostic_vs_per_adapter>.
+// declared per-adapter over the shared accessibility base since the framework-specific children
+// slot keeps it from being fully shared across adapters.
 export interface IAngularSafeAreaViewProps extends IAccessibilityProps, IAriaProps {
   style?: IStyleProp<IViewStyle>;
   onLayout?: (event: ISymbioteEvent) => void;
@@ -73,8 +74,7 @@ export class SafeAreaView implements IAngularSafeAreaViewInputs {
   @Input() style?: IStyleProp<IViewStyle>;
   // Real @Output()s, not `[onX]="…"` callbacks. Safe to name `layout` the same as the native
   // `layout` event fired inside this component's own template — the engine's bubble() treats
-  // ANCHOR_HOST_COMPONENTS as transparent to listener lookup, so there is no double-fire
-  // (angular-adapter skill §7).
+  // ANCHOR_HOST_COMPONENTS as transparent to listener lookup, so there is no double-fire.
   @Output() readonly layout = new EventEmitter<ISymbioteEvent>();
   @Output() readonly accessibilityAction = new EventEmitter<ISymbioteEvent>();
   @Output() readonly accessibilityTap = new EventEmitter<ISymbioteEvent>();
@@ -134,7 +134,7 @@ export class SafeAreaView implements IAngularSafeAreaViewInputs {
   // the host node never sees an aria-* key (native ignores them), same transform React's
   // SafeAreaView runs over its whole `rawProps`. The anchor's class-derived style goes FIRST, this
   // component's own explicit `style` @Input SECOND — flattenStyle's later-wins collapse keeps an
-  // explicit [style] winning over its ambient class (angular-adapter skill's anchorHostStyle doc).
+  // explicit [style] winning over its ambient class.
   get hostProps(): Record<string, unknown> {
     return resolveAccessibilityProps({
       style: [anchorHostStyle(this.elementRef), this.style],

package/src/components/scroll-view/android-scroll-view-axis-projection.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the Android content-projection bug documented in angular-adapter skill §18:
+// Regression test for an Android content-projection bug:
 // ScrollView on Android picks a different native content view per axis (RCTView vs
 // AndroidHorizontalScrollContentView), which used to require a separate <ng-content> per
 // axis x refresh-control combination — and Angular only reliably projects into a component's

package/src/components/scroll-view/index.android.ts

@@ -1,11 +1,11 @@
-// ScrollView on Android (ADR 0024 Phase 2). An Android ScrollView accepts only ONE child, so a
+// ScrollView on Android. An Android ScrollView accepts only ONE child, so a
 // RefreshControl can't be a sibling of the content the way iOS allows ("addViewAt: failed to insert
 // view ... at index 1"). RN solves this by having the RefreshControl (AndroidSwipeRefreshLayout)
 // WRAP the scroll view (cloneElement(refreshControl, {style}, scrollView)). Angular mirrors that
 // shape by querying a projected <RefreshControl>, re-rendering its native prop surface as the outer
 // wrapper, and projecting every non-RefreshControl child into the inner scroll content.
 //
-// FIXED (angular-adapter skill §18, 2026-07): Android genuinely needs a different Fabric view per
+// Android genuinely needs a different Fabric view per
 // axis for BOTH the outer scroll container (RCTScrollView is vertical-only; AndroidHorizontalScrollView
 // is a dedicated ViewManager) AND the inner content view (vertical content is a plain Android View,
 // horizontal content is AndroidHorizontalScrollContentView, which carries its own ShadowNode::

package/src/components/scroll-view/index.ios.ts

@@ -1,4 +1,4 @@
-// ScrollView on iOS (ADR 0024 Phase 2). The RefreshControl is a CHILD of the scroll view, rendered
+// ScrollView on iOS. The RefreshControl is a CHILD of the scroll view, rendered
 // as a SIBLING BEFORE the content container (RN ScrollView.js: {refreshControl}{contentContainer}).
 // The developer composes it as a projected child of <ScrollView>; this template selects it into the
 // sibling slot before the scroll-content. Also the base (index.ts re-exports it) for headless /
@@ -13,8 +13,8 @@
 // FIRST (`@if`) branch never receives Angular's native catch-up placement, only the SECOND
 // (`@else`) branch does (angular/angular#53310, #54840 — Angular's own docs: "You should not
 // conditionally include <ng-content> with @if, @for, or @switch"). Symptom here was axis-specific:
-// a horizontal FlatList's cells landed outside the ScrollView entirely. See angular-adapter skill
-// §18 for the full investigation. Fix: single unconditional `<ng-content>` call site.
+// a horizontal FlatList's cells landed outside the ScrollView entirely. Fix: single unconditional
+// `<ng-content>` call site.
 
 import {
   CUSTOM_ELEMENTS_SCHEMA,

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

@@ -1,6 +1,6 @@
 // Base / default ScrollView. Re-exports the iOS build. Metro overrides this with index.ios.ts /
 // index.android.ts on a real host; under tsx / tsc / web the host resolves here. Filename is the
-// selector, no Platform.OS read. See ADR 0020 / 0024.
+// selector, no Platform.OS read.
 
 export * from './index.ios';
 export { ScrollViewStickyHeader } from './sticky-header';

package/src/components/scroll-view/scroll-view-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): a composed component's own
+// Regression test for the anchor/class bug: a composed component's own
 // use-site `class="..."` resolves through Angular's addClass/removeClass onto the component's
 // non-painting ANCHOR host (ANCHOR_HOST_COMPONENTS in renderer.ts), never onto the real Fabric
 // node its own template renders — so the resolved style was silently lost. Fixed via

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

@@ -1,4 +1,4 @@
-// ScrollView, the Angular lifecycle half (ADR 0024). The Fabric tree is nested: a scroll view
+// ScrollView, the Angular lifecycle half. The Fabric tree is nested: a scroll view
 // wraps a content view that holds the children (RN's ScrollView.js shape). The platform-invariant
 // math (decelerationRate, the per-axis intrinsics/base style, the content-size dedupe, the
 // imperative handle, the native sticky scroll-attach, the aria/role fold) lives in
@@ -8,7 +8,7 @@
 // flashScrollIndicators), the content-size dedupe, and the native sticky scroll-attach wired
 // through whenCommitted. This is the Angular twin of the React useRef + Vue shallowRef host.
 //
-// What diverges per platform (ADR 0020/0024), how a RefreshControl integrates, stays in the
+// What diverges per platform, how a RefreshControl integrates, stays in the
 // .ios/.android files (Metro filename-selected): iOS renders the RefreshControl as a SIBLING
 // before the content container; on Android an AndroidSwipeRefreshLayout WRAPS the scroll view.
 //
@@ -160,8 +160,8 @@ export const SCROLL_VIEW_INPUTS = [
 // The Angular-facing prop surface. React's IScrollViewProps is React-coupled (ReactNode children,
 // ReactElement refreshControl); Angular takes children via <ng-content> and composes the
 // RefreshControl through projection / an outer wrap, so this mirrors the same pass-through surface
-// minus those, declared per-adapter over the shared a11y base per
-// <prop_types_split_agnostic_vs_per_adapter>. Every prop is accepted and typed against the full
+// minus those, declared per-adapter over the shared accessibility base since a framework element/ref
+// field can't live in a shared agnostic type. Every prop is accepted and typed against the full
 // React surface so app code type-checks against parity now.
 export interface IAngularScrollViewProps extends IAccessibilityProps, IAriaProps {
   style?: IStyleProp<IViewStyle>;
@@ -734,7 +734,7 @@ export abstract class ScrollViewBase implements IAngularScrollViewInputs, AfterV
 
   // The imperative API a parent reaches via @ViewChild(ScrollView). buildScrollViewHandle is the
   // shared, proven handle (React/Vue use it verbatim); it reads the node through the LAZY getter on
-  // every call, so a command before commit no-ops rather than freezing a null node (ADR 0024 §3).
+  // every call, so a command before commit no-ops rather than freezing a null node.
   private readonly handle: IScrollViewHandle = buildScrollViewHandle(() => this.hostNode);
 
   scrollTo(options?: { x?: number; y?: number; animated?: boolean }): void {

package/src/components/scroll-view/sticky-header.ts

@@ -6,7 +6,7 @@
 // it to the top (or bottom, inverted) until the next header collides with it. The native Fabric
 // scroll view does NOT honor `stickyHeaderIndices` on its own. The load-bearing top/inverted
 // interpolation math (computeStickyInterpolation) lives framework-agnostic in @symbiote-native/components
-// (ADR 0024); this file holds the Angular component shell, the layout state, and the interpolation
+// this file holds the Angular component shell, the layout state, and the interpolation
 // build, sharing the math verbatim with React/Vue. Angular supplies only the lifecycle (inputs +
 // manual change detection instead of useState/useEffect or refs/watch).
 //

package/src/components/text-input-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): TextInput is its own
+// Regression test for the anchor/class bug: TextInput is its own
 // ANCHOR_HOST_COMPONENTS entry — a class= on <TextInput> resolves onto TextInput's OWN anchor and
 // needs its OWN anchorHostStyle merge (see text-input.ts's buildPassthrough), for BOTH the
 // single-line and multiline host it renders through (`@if`/`@else` picks one at runtime). Mirrors

package/src/components/text-input.ts

@@ -90,8 +90,8 @@ function isSymbioteEvent(value: unknown): value is ISymbioteEvent {
 }
 
 // Mirrors React's ITextInputProps minus nothing (TextInput has no children) — declared
-// per-adapter over the shared a11y base per <prop_types_split_agnostic_vs_per_adapter>, because
-// Angular's input surface aliases the aria-* keys to camelCase @Inputs.
+// per-adapter over the shared accessibility base because Angular's input surface aliases the
+// aria-* keys to camelCase @Inputs, unlike the plain agnostic fields shared across adapters.
 export interface IAngularTextInputProps extends IAccessibilityProps, IAriaProps {
   value?: string;
   defaultValue?: string;

package/src/components/touchable-native-feedback.ts

@@ -7,9 +7,9 @@
 // so the child still renders with working press wiring. The static factories + background mapping
 // are shared in @symbiote-native/components and reused verbatim — Angular only attaches them onto the
 // component class and nests the feedback view. No JS-side platform branch (one Fabric path both
-// platforms), so this stays a flat single file (ADR 0026), mirroring React/Vue.
+// platforms), so this stays a flat single file, mirroring React/Vue.
 //
-// This component's own press/hover events are now real @Output() EventEmitters too, matching
+// This component's own press/hover events are real @Output() EventEmitters too, matching
 // Pressable (which it wraps) — `(press)="press.emit($event)"`, never `[onPress]="onPress"`.
 // Non-event config (delayLongPress, hitSlop, ...) still rides down as plain @Input() bindings. The
 // a11y identity bag + the four a11y events live on the feedback view — the one host intrinsic here —
@@ -57,7 +57,7 @@ export type {
 // Mirrors React's ITouchableNativeFeedbackProps (Omit<IPressableProps, 'style'> + the native
 // feedback config) minus children (Angular takes children via <ng-content>) and minus the press/
 // hover events (declared as this component's OWN @Output()s below). Declared per-adapter over the
-// shared Pressable INPUT surface per <prop_types_split_agnostic_vs_per_adapter>.
+// shared Pressable INPUT surface.
 export type IAngularTouchableNativeFeedbackProps = Omit<IAngularPressableInputs, 'style'> & {
   background?: INativeFeedbackBackground;
   useForeground?: boolean;

package/src/components/touchable.ts

@@ -17,9 +17,9 @@
 // (`(accessibilityAction)="accessibilityAction.emit($event)"`); accessibility STATE folds the web
 // aria-*/role aliases and merges `disabled` into the a11y state on Pressable's own host — no re-fold
 // here (the a11y host is Pressable's view, mirroring React's `...rest` -> Pressable). No JS-side
-// platform branch, so this stays a flat single file (see the
-// symbiote-file-layout skill), mirroring React/Vue. Each Touchable forwards the Angular Pressable
-// surface verbatim; parity is against that surface, exactly as React's Touchable parity is against
+// platform branch, so this stays a flat single file, mirroring React/Vue. Each Touchable
+// forwards the Angular Pressable surface verbatim; parity is against that surface, exactly as
+// React's Touchable parity is against
 // the React Pressable surface.
 
 import {
@@ -62,8 +62,8 @@ import { Animated, AnimatedView } from '../modules/animated';
 // The shared field base for all three: the Pressable INPUT surface (minus style, which each
 // Touchable routes differently, and minus the press/hover events, which each Touchable declares as
 // its OWN @Output()s below) + RN's press-timing config + the public style. Mirrors React/Vue's
-// ITouchableBaseProps. Declared per-adapter over the Angular Pressable surface per
-// <prop_types_split_agnostic_vs_per_adapter> (children ride <ng-content>, so they are not a field).
+// ITouchableBaseProps. Declared per-adapter over the Angular Pressable surface, since children
+// ride <ng-content> here rather than a field, unlike React/Vue's element-returning props.
 type IAngularTouchableBaseProps = Omit<IAngularPressableInputs, 'style'> &
   IPressTimingProps & {
     style?: IStyleProp<IViewStyle>;

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

@@ -3,8 +3,7 @@
 // `ItemSeparatorComponent`. React/Vue pass an element-returning callback; that does NOT
 // translate to Angular, where per-item content is a TEMPLATE. So the app supplies each
 // slot as an `<ng-template>` carrying one of these structural directives, and the list
-// stamps the windowed slice through them. This is the per-adapter children/render split of
-// <prop_types_split_agnostic_vs_per_adapter>: the agnostic windowing surface stays shared,
+// stamps the windowed slice through them. The agnostic windowing surface stays shared,
 // only the cell-AUTHORING shape is framework-specific.
 //
 // Authoring API (what FlatList / SectionList build on, and what the app imports):

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

@@ -1,7 +1,7 @@
 // VirtualizedList, the Angular lifecycle half. The windowing engine (offset table, window
 // compute, batch throttle, viewability, edge-reached, the child PLAN, the imperative-handle
 // geometry) lives in @symbiote-native/components/state, shared verbatim with the React and Vue adapters
-// (<adapters_reach_full_feature_parity>). Here Angular supplies only the lifecycle: plain fields
+// so every adapter keeps the same feature surface. Here Angular supplies only the lifecycle: plain fields
 // for scroll offset / viewport / measurement bumps, a once-per-CD metrics + view recompute in
 // ngDoCheck (the Angular twin of React render / Vue `computed` — it owns the controlled
 // committedWindow throttle and assembles the windowed cells before the template bindings are read),
@@ -19,11 +19,10 @@
 // (a core-only NgTemplateOutlet twin — @angular/common is not a dependency). See ./directives.ts.
 // Every React/Vue behavior is present (windowing, onEndReached, viewability, headers/footers/empty/
 // separators, refresh, imperative scroll, horizontal, inverted, MVCP); only the cell AUTHORING
-// shape differs, per the per-adapter children/render split of
-// <prop_types_split_agnostic_vs_per_adapter>.
+// shape differs, since a callback prop returning an element has no Angular equivalent.
 //
-// Lists have no Descriptor render fn (the cell content is the framework's own children); see
-// core/components/.docs-note-lists.md. Cells/spacers are plain symbiote-view host elements.
+// Lists have no Descriptor render fn — the cell content is the framework's own children.
+// Cells/spacers are plain symbiote-view host elements.
 
 import {
   CUSTOM_ELEMENTS_SCHEMA,
@@ -127,8 +126,8 @@ export type { IVListItemContext, IVListSeparatorContext } from './directives';
 
 // The Angular VirtualizedList prop surface. Mirrors React/Vue's IVirtualizedListProps MINUS the
 // element-returning props (renderItem, ListHeader/Footer/Empty Component, ItemSeparatorComponent):
-// those are the per-adapter children/render fields and become `<ng-template>` directives in Angular
-// (<prop_types_split_agnostic_vs_per_adapter>). Everything agnostic is the SAME surface.
+// those are the per-adapter children/render fields and become `<ng-template>` directives in Angular.
+// Everything agnostic is the SAME surface.
 export interface IVirtualizedListProps<ItemT> extends IAccessibilityProps, IAriaProps {
   data: unknown;
   getItem: (data: unknown, index: number) => ItemT;

package/src/components/virtualized-list/virtualized-list-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): VirtualizedList is its own
+// Regression test for the anchor/class bug: VirtualizedList is its own
 // ANCHOR_HOST_COMPONENTS entry — a class= on <VirtualizedList> resolves onto VirtualizedList's OWN
 // anchor and needs its OWN anchorHostStyle merge (see index.ts's recomputeView), it is NOT
 // transitively fixed by ScrollView's own fix one level down. Mirrors pressable.test.ts's

package/src/components/virtualized-section-list/directives.ts

@@ -3,8 +3,7 @@
 // React/Vue pass element-returning callbacks; that does NOT translate to Angular, where per-cell
 // content is a TEMPLATE. So the app supplies each section slot as an `<ng-template>` carrying one
 // of these structural directives, and VirtualizedSectionList stamps the windowed slice through
-// them. This is the per-adapter children/render split of <prop_types_split_agnostic_vs_per_adapter>:
-// the shared flatten/window surface stays in @symbiote-native/components, only the cell-AUTHORING shape is
+// them. The shared flatten/window surface stays in @symbiote-native/components, only the cell-AUTHORING shape is
 // framework-specific. SectionList (the next layer) reuses these same directives verbatim.
 //
 // Authoring API (what the app imports and what SectionList builds on):

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

@@ -12,8 +12,8 @@
 // `vListItem` template that @switch-es on the flattened entry's tag and stamps the matching app
 // template (captured via @ContentChild on the vSection* directives) through VListOutletDirective.
 // list-level header/footer/empty/item-separator reuse VirtualizedList's own directives, forwarded
-// the same way. This is the per-adapter children/render split of
-// <prop_types_split_agnostic_vs_per_adapter>: only the cell-AUTHORING shape is framework-specific.
+// the same way. Only the cell-AUTHORING shape is framework-specific; the rest of the surface
+// stays shared with React/Vue.
 //
 // Accessibility / aria props are forwarded unchanged to the inner VirtualizedList, which owns the
 // shared aria→accessibility* fold before the props reach the ScrollView host.
@@ -88,8 +88,8 @@ export type { IVSectionContext, IVSectionItemContext } from './directives';
 
 // The Angular VirtualizedSectionList prop surface. Mirrors React/Vue's IVirtualizedSectionListProps
 // MINUS the element-returning props (renderItem, renderSectionHeader/Footer, the *Component slots):
-// those are the per-adapter children/render fields and become `<ng-template>` directives in Angular
-// (<prop_types_split_agnostic_vs_per_adapter>). Everything agnostic is the SAME surface as the
+// those are the per-adapter children/render fields and become `<ng-template>` directives in Angular.
+// Everything agnostic is the SAME surface as the
 // React/Vue adapters, including the a11y/aria prop family forwarded through VirtualizedList.
 export interface IVirtualizedSectionListProps<ItemT> extends IAccessibilityProps, IAriaProps {
   sections: ReadonlyArray<ISection<ItemT>>;

package/src/components/virtualized-section-list/virtualized-section-list-class-style.test.ts

@@ -1,4 +1,4 @@
-// Regression test for the anchor/class bug (angular-adapter skill): VirtualizedSectionList is its
+// Regression test for the anchor/class bug: VirtualizedSectionList is its
 // own ANCHOR_HOST_COMPONENTS entry — a class= on <VirtualizedSectionList> resolves onto its OWN
 // anchor and needs its OWN anchorHostStyle merge (see index.ts's resolvedStyle getter), it is NOT
 // transitively fixed by VirtualizedList's/ScrollView's own fixes further down. Mirrors

package/src/create-portal.ts

@@ -1,8 +1,8 @@
 // createPortal for @symbiote-native/angular — the Angular twin of the React/Vue same-surface portal
 // (create-portal.ts / Teleport in runtime-helpers.ts). Scope is identical: the target must be
-// an already-mounted location WITHIN THE SAME SURFACE as the portal's call site — see the
-// react-adapter-portal skill for why cross-surface targets are permanently out of scope
-// (createTunnel, create-tunnel.ts, is the answer for that case).
+// an already-mounted location WITHIN THE SAME SURFACE as the portal's call site — moving content
+// across independently-mounted surfaces has no safe host-level primitive to hook into, so
+// createTunnel (create-tunnel.ts) covers that cross-surface case instead.
 //
 // React/Vue implement this as a thin validating wrapper around a mechanism the FRAMEWORK
 // ITSELF already has (react-reconciler's Fiber-level HostPortal, Vue's own <Teleport>) — all

package/src/descriptor-to-angular/index.ts

@@ -1,8 +1,8 @@
 // Angular descriptor outlet. The React/Vue bridges can return framework elements directly
 // (`descriptorToReact` / `descriptorToVue`); Angular needs a tiny standalone component that
-// consumes a Descriptor tree and drives Renderer2 imperatively. This mirrors wolf-tui's
-// WNodeOutlet, but patches same type/key nodes instead of clearing and recreating the subtree so
-// Symbiote keeps retained-node identity and Fabric stays on the clone-on-write path.
+// consumes a Descriptor tree and drives Renderer2 imperatively, patching same type/key nodes
+// instead of clearing and recreating the subtree so it keeps retained-node identity and Fabric
+// stays on the clone-on-write path.
 
 import {
   ChangeDetectionStrategy,

package/src/host-instance/host-instance.test.ts

@@ -1,4 +1,4 @@
-// Co-located test for findNodeHandle (ADR 0025), the Angular twin of adapters/vue/src/host-instance/host-instance.test.ts.
+// Co-located test for findNodeHandle, the Angular twin of adapters/vue/src/host-instance/host-instance.test.ts.
 // Proves the Angular adapter can resolve a raw engine node, an engine public instance, a bare
 // reactTag, and null/undefined to a native tag using the engine's getNativeTag.
 

package/src/index.ts

@@ -3,8 +3,7 @@
 // lives in the engine, shared with every other adapter. App code names only @symbiote-native/angular.
 //
 // SEAM SCAFFOLD: mount/unmount + the renderer seam + host intrinsic selectors. Full RN-like
-// composed components still flow through the shared @symbiote-native/components bridge — see the
-// `angular-adapter` skill (§6 descriptorToAngular, the layered milestones).
+// composed components still flow through the shared @symbiote-native/components bridge.
 
 export {
   ActivityIndicator,
@@ -49,8 +48,8 @@ export {
 } from './components';
 export { Animated } from './modules/animated';
 // Also exposed as named top-level symbols (not just Animated.View/.Text/...): ngtsc's partial-mode
-// static evaluator (real AOT, see angular-adapter skill §4) can't trace a component class through
-// property access on an external namespace object, only through a direct named import binding —
+// static evaluator can't trace a component class through property access on an external
+// namespace object, only through a direct named import binding —
 // so `<AnimatedView>` in a template requires `import { AnimatedView } from '@symbiote-native/angular'`,
 // not `const AnimatedView = Animated.View`. Plain tsc/vitest don't catch this; only a real ngc run does.
 export {
@@ -123,8 +122,8 @@ export type {
 } from './components';
 export { setImageSourceResolver } from './components';
 export { mount, unmount } from './render';
-// The generic Descriptor→Angular bridge (§6 of the angular-adapter skill), the twin of
-// descriptorToReact/descriptorToVue. Exported so a component defined OUTSIDE this package (e.g.
+// The generic Descriptor→Angular bridge, the twin of descriptorToReact/descriptorToVue.
+// Exported so a component defined OUTSIDE this package (e.g.
 // @symbiote-native/slider) can render a shared @symbiote-native/components/@symbiote-native/slider Descriptor tree
 // without hand-writing its own Renderer2 walker.
 export { DescriptorOutlet } from './descriptor-to-angular';
@@ -133,7 +132,7 @@ export { DescriptorOutlet } from './descriptor-to-angular';
 // Angular can't synthesize components at runtime (no JIT under Metro/Hermes), so both are
 // static, pre-authored structural directives (`*portal`/`*tunnelIn`, the `*ngIf`/`*ngFor`
 // idiom) parameterized by an `@Input()`, rather than a factory returning fresh components per
-// call — see the react-adapter-portal / angular-adapter skills.
+// call.
 export { PortalDirective, PortalOutletDirective } from './create-portal';
 export { createTunnel, TunnelInDirective, TunnelOut, type ITunnelStore } from './create-tunnel';
 export { SymbioteRenderer, SymbioteRendererFactory } from './renderer';

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

@@ -1,7 +1,7 @@
 // createAnimatedComponent for @symbiote-native/angular: the Angular twin of the React/Vue
 // wrapper. React/Vue have a runtime HOC (`createAnimatedComponent(Component)` builds a
 // fresh wrapped component on the fly). Angular has NO such idiom AND it cannot have one:
-// the AOT-under-Metro build (angular-adapter skill §4) compiles every @Component at build
+// the AOT-under-Metro build compiles every @Component at build
 // time and ships NO JIT compiler to Hermes, so a runtime `Component({...})(class)` would
 // throw. The idiomatic, AOT-safe equivalent is therefore an EXPLICIT set of standalone
 // components — AnimatedView / AnimatedText / AnimatedImage / AnimatedScrollView — each a
@@ -13,7 +13,7 @@
 //
 // The framework-agnostic half (reduceProps / readPassthroughStyle / resolveHostNode /
 // AnimatedProps / attachNativeEventHandler / isNativeAnimatedAvailable) comes from
-// @symbiote-native/engine, shared verbatim with React and Vue (ADR 0016/0017). Angular supplies
+// @symbiote-native/engine, shared verbatim with React and Vue. Angular supplies
 // only the lifecycle wiring. The per-frame path NEVER goes through Angular change
 // detection: value.setValue / animation -> flushValue -> AnimatedProps.update() ->
 // setNativeProps(node), exactly as on the other adapters.

package/src/modules/animated/index.ts

@@ -2,7 +2,7 @@
 // animated/index.ts. The animated COMPONENTS (View / Text / Image / ScrollView) are explicit
 // standalone components (Angular has no runtime HOC — see create-animated-component.ts); the
 // value graph, easing and imperative drivers come from @symbiote-native/engine (framework-agnostic,
-// JS-driven, ADR 0016), spread in verbatim. Both halves meet here so the familiar surface,
+// JS-driven), spread in verbatim. Both halves meet here so the familiar surface,
 // `Animated.timing(new Animated.Value(0), …).start()`, works against the Angular-driven engine.
 
 import {