@symbiote-native/navigation 1.0.0 → 2.0.1

package/build/core/render-drawer.js

@@ -1,88 +0,0 @@
-// Drawer: the render half (framework-agnostic). Like render-stack.ts's screen content, both the
-// drawer panel's content (renderDrawerContent) and the wrapped screen content are arbitrary
-// framework subtrees the adapter owns - so, mirroring render-modal.ts's container-slot precedent,
-// renderDrawer hands back one root Descriptor whose structural children are EMPTY placeholder
-// nodes (`content` / `overlay?` / `panel`) that the adapter fills with real framework children.
-// Paint order (and therefore which slot is present) is drawerType-dependent, so `drawerChildOrder`
-// is exported alongside renderDrawer as the single source of truth the adapter zips its own
-// children against - no adapter re-derives the ordering itself.
-//
-// All positioning here is STATIC (position/top/bottom/side/width) - the animated slide transform
-// and overlay opacity are NOT baked into this Descriptor. They are computed once per drawerType
-// via drawer-options.ts's resolveDrawerGeometry() and then driven per-frame by the adapter's own
-// Animated value (Animated.View), because "how to animate a style" is a framework-lifecycle
-// concern (React: Animated.View; a future Vue adapter: a reactive style binding) - see
-// CLAUDE.md <adapters_stay_thin>.
-import { el } from '@symbiote-native/components';
-import { isDrawerOverlayVisible, resolveDrawerPosition, resolveDrawerType, resolveDrawerWidth, } from './drawer-options/index.js';
-// front: content, overlay (dims it), panel (paints on top, last-sibling-on-top).
-// back: panel (stationary, behind), content (slides away to reveal it) - no overlay. Both are
-// absolutely positioned, so sibling order here only decides z-stacking, not screen side.
-// slide: panel, overlay, content (both panel and content animate; content stays visually on top).
-// permanent: NOT absolutely positioned (an ordinary flexDirection:'row' sidebar), so sibling
-// order IS the left-to-right screen position - it must follow drawerPosition.
-export function drawerChildOrder(options) {
-    const type = resolveDrawerType(options);
-    switch (type) {
-        case 'back':
-            return ['panel', 'content'];
-        case 'slide':
-            return ['panel', 'overlay', 'content'];
-        case 'permanent':
-            return resolveDrawerPosition(options) === 'left'
-                ? ['panel', 'content']
-                : ['content', 'panel'];
-        case 'front':
-        default:
-            return ['content', 'overlay', 'panel'];
-    }
-}
-const ROOT_STYLE = { flex: 1 };
-const CONTENT_STYLE = { flex: 1 };
-// Fabric paints later siblings on top; position:absolute + inset:0 is enough for the overlay
-// (its own sibling order, not zIndex, decides whether it sits above the content).
-const OVERLAY_BASE_STYLE = {
-    position: 'absolute',
-    top: 0,
-    left: 0,
-    right: 0,
-    bottom: 0,
-};
-const DRAWER_PANEL_DEFAULT_BACKGROUND_COLOR = 'white';
-function panelBaseStyle(options) {
-    const type = resolveDrawerType(options);
-    const width = resolveDrawerWidth(options);
-    const side = resolveDrawerPosition(options);
-    if (type === 'permanent') {
-        // A sidebar: an ordinary flex child, no absolute positioning, no translate needed.
-        return { width, backgroundColor: DRAWER_PANEL_DEFAULT_BACKGROUND_COLOR };
-    }
-    return {
-        position: 'absolute',
-        top: 0,
-        bottom: 0,
-        width,
-        backgroundColor: DRAWER_PANEL_DEFAULT_BACKGROUND_COLOR,
-        [side]: 0,
-    };
-}
-export function renderDrawer(view, options) {
-    const type = resolveDrawerType(options);
-    const content = el('symbiote-view', { ...view.contentPassthrough, style: CONTENT_STYLE }, []);
-    const panel = el('symbiote-view', { ...view.panelPassthrough, style: [panelBaseStyle(options), view.drawerStyle] }, []);
-    const slots = { content, panel };
-    if (isDrawerOverlayVisible(options)) {
-        slots.overlay = el('symbiote-view', {
-            ...view.overlayPassthrough,
-            style: [OVERLAY_BASE_STYLE, { backgroundColor: view.overlayColor }],
-        }, []);
-    }
-    const children = drawerChildOrder(options).reduce((acc, slot) => {
-        const descriptor = slots[slot];
-        if (descriptor !== undefined)
-            acc.push(descriptor);
-        return acc;
-    }, []);
-    const rootStyle = type === 'permanent' ? { ...ROOT_STYLE, flexDirection: 'row' } : ROOT_STYLE;
-    return el('symbiote-view', { style: rootStyle }, children);
-}

package/build/core/render-stack.d.ts

@@ -1,35 +0,0 @@
-import type { IDescriptor } from '@symbiote-native/components';
-import type { ISymbioteEvent } from '@symbiote-native/engine';
-import type { IHeaderConfigViewProps, INavigatorPlatform, IScreenOptions, IScreenViewProps, ISearchBarOptions, ISearchBarViewProps, IStackPresentation, IStackViewProps } from './navigator-props';
-export declare function resolveScreenViewName(stackPresentation: IStackPresentation | undefined, isAndroid: boolean): string;
-export declare function resolveScreenContentWrapperStyle(stackPresentation: IStackPresentation | undefined, headerHidden: boolean, headerTranslucent: boolean | undefined, isAndroid: boolean): Record<string, unknown>;
-export declare function isHeaderInModal(stackPresentation: IStackPresentation | undefined, headerHidden: boolean, isAndroid: boolean): boolean;
-export declare function resolveHeaderInModalStackStyle(): Record<string, unknown>;
-export declare function resolveHeaderInModalScreenStyle(): Record<string, unknown>;
-export declare function resolveScreenProps(view: IScreenViewProps): Record<string, unknown>;
-export declare function resolveStackProps(view: IStackViewProps): Record<string, unknown>;
-export declare function renderHeaderConfig(view: IHeaderConfigViewProps, searchBarProps?: Record<string, unknown>): IDescriptor;
-export declare function resolveSearchBarProps(view: ISearchBarViewProps): Record<string, unknown>;
-export declare function buildSearchBarPassthrough(options: ISearchBarOptions, log?: (message: string) => void): Record<string, (event: ISymbioteEvent) => void>;
-export type IScreenRenderPlanInput = {
-    screenId: string;
-    index: number;
-    routeCount: number;
-    options: IScreenOptions | undefined;
-    platform: INavigatorPlatform;
-    isAndroid: boolean;
-    screenPassthrough: Record<string, unknown>;
-    searchBarPassthrough?: Record<string, unknown>;
-};
-export type IScreenRenderPlan = {
-    activityState: number;
-    screenViewName: string;
-    screenProps: Record<string, unknown>;
-    headerConfig: IDescriptor;
-    searchBarProps: Record<string, unknown> | undefined;
-    contentWrapperProps: Record<string, unknown>;
-    inModal: boolean;
-    innerStackStyle: Record<string, unknown>;
-    innerScreenStyle: Record<string, unknown>;
-};
-export declare function resolveScreenRenderPlan(input: IScreenRenderPlanInput): IScreenRenderPlan;

package/build/core/render-stack.js

@@ -1,294 +0,0 @@
-// Navigator: framework-agnostic render half. A screen's content is an arbitrary framework
-// subtree the adapter owns (unlike the slider's one native leaf), so these resolvers hand back
-// plain props objects for the RNSScreen/RNSScreenStack leaves the adapter builds itself with real
-// children, and one full Descriptor for the header config. The header config Descriptor never
-// takes framework children (headerLeftBarButtonItems/headerRightBarButtonItems are native config
-// arrays from screen-options.ts, not elements), but can nest one RNSSearchBar leaf wrapped in an
-// RNSScreenStackHeaderSubview(type: 'searchBar'), matching how react-native-screens' own
-// ScreenStackHeaderSearchBarView mounts it. RNSScreenStackHeaderConfig.mm's mountChildComponentView
-// rejects a bare RNSSearchBar child natively ("only accepts children of type
-// ScreenStackHeaderSubview") and reads the search bar back out via `subview.subviews[0]`.
-import { el } from '@symbiote-native/components';
-import { HEADER_ON_PRESS_BAR_BUTTON_ITEM, HEADER_ON_PRESS_BAR_BUTTON_MENU_ITEM, RNS_MODAL_SCREEN_VIEW_NAME, RNS_SCREEN_STACK_HEADER_CONFIG_VIEW_NAME, RNS_SCREEN_STACK_HEADER_SUBVIEW_VIEW_NAME, RNS_SCREEN_VIEW_NAME, RNS_SEARCH_BAR_VIEW_NAME, SEARCH_BAR_ON_BLUR, SEARCH_BAR_ON_CANCEL_BUTTON_PRESS, SEARCH_BAR_ON_CHANGE_TEXT, SEARCH_BAR_ON_CLOSE, SEARCH_BAR_ON_FOCUS, SEARCH_BAR_ON_OPEN, SEARCH_BAR_ON_SEARCH_BUTTON_PRESS, STACK_DEFAULT_ANIMATION, STACK_DEFAULT_PRESENTATION, } from './constants.js';
-import { computeActivityState } from './navigator-state/index.js';
-import { resolveHeaderConfigView, resolveScreenView, resolveSearchBarView } from './screen-options.js';
-// Mirrors react-native-screens' ScreenStackItem.tsx (getPositioningStyle): a formSheet's content
-// wrapper does not get `flex: 1`. RNSScreen.mm's updateBounds pushes the sheet's live native size
-// into Fabric's shadow state on every frame of a detent drag, and a `bottom: 0`-pinned wrapper
-// forces React to set a strict frame on every update, causing the flicker PR #1870 fixed by
-// switching to `absoluteWithNoBottom` (RNSScreen.mm: "we do not set bottom: 0 in JS for wrapper of
-// the screen content, causing React to not set strict frame every time the sheet size is updated").
-// Tradeoff: content shorter than the sheet's current detent leaves a gap below it.
-// RNSScreenContentWrapper.mm's coerceChildScrollViewComponentSizeToSize fixes that natively, but
-// only for a ScrollView child, which it resizes directly to the sheet's real frame bypassing
-// Yoga/flex, not something reachable from a style choice here.
-const SCREEN_CONTENT_WRAPPER_FLEX_STYLE = { flex: 1 };
-const SHEET_CONTENT_WRAPPER_STYLE = {
-    position: 'absolute',
-    top: 0,
-    start: 0,
-    end: 0,
-    bottom: undefined,
-};
-// Android's native header (react-native-screens' CustomToolbar in a CoordinatorLayout alongside
-// an AppBarLayout) auto-offsets screen content below the header via a Material
-// `AppBarLayout.ScrollingViewBehavior` (ScreenStackFragment.kt's setToolbarTranslucent: `behavior
-// = if (translucent) null else ScrollingViewBehavior()`). A plain (non-translucent) header gets
-// this offset for free and needs no JS compensation. `headerTranslucent: true` removes that
-// behavior: react-native-screens' contract for translucent is "background goes away AND content
-// is no longer auto-pushed below it", meant for a screen painting under a see-through header. An
-// app that sets headerTranslucent just for a custom (still opaque) header look, while relying on
-// its own SafeAreaView for safe-area content, loses the free offset and gets clipped:
-// SafeAreaView's Android inset only reflects WindowInsetsCompat's systemBars() (status
-// bar/cutout), with no awareness of the sibling Toolbar, so content paints its first 56dp under
-// the header. Verified empirically (2026-07-10) via `adb shell uiautomator dump`: a
-// translucent-header screen's content measured starting at y=0 (see the
-// navigation-header-content-offset skill for the full incident). iOS's UINavigationController
-// already lays out below its real nav bar regardless of translucency, so this compensation is
-// Android-only and applies only when translucent (a non-translucent header already gets the
-// native offset; padding there would double it).
-const ANDROID_HEADER_TOOLBAR_HEIGHT = 56;
-// react-native-screens' own Screen.tsx picks a different Fabric component for a modally-presented
-// screen ('RNSModalScreen' instead of plain 'RNSScreen') because "there is a need for different
-// shadow nodes" (its own comment). RNSScreen.mm's updateLayoutMetrics only skips applying Yoga's
-// computed frame for `[self isKindOfClass:RNSModalScreen.class]` ("the available space is most
-// likely restricted & differs from what Yoga resolves during first layout - we want to rely on
-// native layout here"). Emitting plain 'RNSScreen' for a formSheet/modal means that check never
-// matches, so Yoga's frame (computed as an ordinary push-stack sibling) applies uncorrected,
-// shifting the modal down by one full screen height (see register.ts's incident note). Mirrors
-// Screen.tsx's `shouldUseModalScreenComponent` exactly, including the iOS-only scope (Android
-// sizes modals natively regardless of Fabric view name).
-export function resolveScreenViewName(stackPresentation, isAndroid) {
-    if (isAndroid)
-        return RNS_SCREEN_VIEW_NAME;
-    const isPlainPresentation = stackPresentation === undefined ||
-        stackPresentation === 'push' ||
-        stackPresentation === 'containedModal' ||
-        stackPresentation === 'containedTransparentModal';
-    return isPlainPresentation ? RNS_SCREEN_VIEW_NAME : RNS_MODAL_SCREEN_VIEW_NAME;
-}
-export function resolveScreenContentWrapperStyle(stackPresentation, headerHidden, headerTranslucent, isAndroid) {
-    let baseStyles;
-    if (stackPresentation !== 'formSheet') {
-        baseStyles = SCREEN_CONTENT_WRAPPER_FLEX_STYLE;
-    }
-    else if (isAndroid) {
-        baseStyles = {
-            ...SHEET_CONTENT_WRAPPER_STYLE,
-            bottom: 0,
-        };
-    }
-    else {
-        baseStyles = SHEET_CONTENT_WRAPPER_STYLE;
-    }
-    // paddingTop compensates the Android-only ScrollingViewBehavior removal above; iOS never needs
-    // it, so the `!isAndroid` check must stay.
-    if (!isAndroid || headerHidden || !headerTranslucent)
-        return baseStyles;
-    return { ...baseStyles, paddingTop: ANDROID_HEADER_TOOLBAR_HEIGHT };
-}
-// A modally-presented screen (anything but 'push') has no UINavigationController on iOS, so
-// RNSScreenStackHeaderConfig has nothing to attach a header bar to. react-native-screens' own
-// ScreenStackItem.tsx (isHeaderInModal) works around this by nesting header + content inside a
-// second, inner RNSScreenStack/RNSScreen pair purely to host the native nav bar. This is a UIKit
-// constraint, not a React-renderer one, so it applies identically here. Android has no such
-// requirement (its header draws without a nav-controller host).
-export function isHeaderInModal(stackPresentation, headerHidden, isAndroid) {
-    if (isAndroid)
-        return false;
-    return (stackPresentation ?? STACK_DEFAULT_PRESENTATION) !== 'push' && !headerHidden;
-}
-// Inner-modal wrapper styles for isHeaderInModal: the inner RNSScreenStack fills its outer
-// RNSScreen, and the inner RNSScreen fills the stack absolutely on all four edges. This mirrors
-// react-native-screens' own `styles.container` / `StyleSheet.absoluteFill` for this exact pair.
-const HEADER_IN_MODAL_STACK_STYLE = { flex: 1 };
-const HEADER_IN_MODAL_SCREEN_STYLE = { position: 'absolute', top: 0, start: 0, end: 0, bottom: 0 };
-export function resolveHeaderInModalStackStyle() {
-    return HEADER_IN_MODAL_STACK_STYLE;
-}
-export function resolveHeaderInModalScreenStyle() {
-    return HEADER_IN_MODAL_SCREEN_STYLE;
-}
-// The RNSScreen leaf's own props; the adapter spreads this record directly onto the element it
-// builds and appends the header config child and real screen content itself, not here.
-export function resolveScreenProps(view) {
-    return {
-        ...view.passthrough,
-        screenId: view.screenId,
-        activityState: view.activityState,
-        gestureEnabled: view.gestureEnabled,
-        stackAnimation: view.stackAnimation ?? STACK_DEFAULT_ANIMATION,
-        stackPresentation: view.stackPresentation ?? STACK_DEFAULT_PRESENTATION,
-        // Off by default upstream; a formSheet's updateBounds pushes the sheet's live native size
-        // into Fabric's shadow state on every drag frame, and this switches that push from
-        // Asynchronous to EventQueue::UpdateMode::unstable_Immediate. The ScrollView-frame correction
-        // that fills a taller detent (RNSScreenContentWrapper.mm's
-        // coerceChildScrollViewComponentSizeToSize) is driven by that same state, so an async push
-        // likely lags one step behind a fast drag. Scoped to formSheet: push/plain-modal screens have
-        // no comparable live-resize need.
-        synchronousShadowStateUpdatesEnabled: view.stackPresentation === 'formSheet',
-        transitionDuration: view.transitionDuration,
-        sheetAllowedDetents: view.sheetAllowedDetents,
-        // Native RNSScreen's real prop names carry an "Index" suffix (react-native-screens' own
-        // types.tsx); without it the value never reaches the native view and silently falls back to
-        // RNS's default.
-        sheetLargestUndimmedDetentIndex: view.sheetLargestUndimmedDetent,
-        sheetInitialDetentIndex: view.sheetInitialDetent,
-        sheetGrabberVisible: view.sheetGrabberVisible,
-        sheetCornerRadius: view.sheetCornerRadius,
-        sheetExpandsWhenScrolledToEdge: view.sheetExpandsWhenScrolledToEdge,
-        sheetElevation: view.sheetElevation,
-        sheetShouldOverflowTopInset: view.sheetShouldOverflowTopInset,
-        sheetDefaultResizeAnimationEnabled: view.sheetDefaultResizeAnimationEnabled,
-        statusBarStyle: view.statusBarStyle,
-        statusBarHidden: view.statusBarHidden,
-        statusBarAnimation: view.statusBarAnimation,
-        screenOrientation: view.screenOrientation,
-    };
-}
-// `style: {flex: 1}` is ours, not react-native-screens': RNSScreenStackView sizes its nav
-// controller to `self.bounds`, which Yoga would otherwise collapse to zero, and (unlike RN's
-// own ScreenStack.tsx) we drive the native view directly (<third_party_rn_packages_are_react_only>).
-export function resolveStackProps(view) {
-    return { style: { flex: 1 }, ...view.passthrough };
-}
-// The RNSScreenStackHeaderConfig leaf is a full Descriptor since it never hosts framework children,
-// so the adapter bridges it verbatim (descriptorToReact/descriptorToVue) as the screen's first
-// child, ahead of the real content. `searchBarProps` nests as an RNSSearchBar wrapped in an
-// RNSScreenStackHeaderSubview(type: 'searchBar'), matching how react-native-screens' own JS
-// component mounts it (see resolveSearchBarView's comment in screen-options.ts); omitted when the
-// screen has no search bar.
-export function renderHeaderConfig(view, searchBarProps) {
-    const props = {
-        ...view.passthrough,
-        title: view.title,
-        hidden: view.hidden,
-        // Android-only (CustomToolbar.kt gates its WindowInsets padding on these; iOS's
-        // UINavigationController lays out under the safe area regardless). Upstream's JS
-        // ScreenStackHeaderConfig computes these via an EdgeInsetApplicationContext that coordinates a
-        // "consume once" top inset across nested headers; we drive RNSScreenStackHeaderConfig directly
-        // and skip that layer, so without this the native default (false) leaves the header glued
-        // under the status bar/cutout on Android. Every adapter renders one active header at a time,
-        // so consuming all four edges matches upstream's default for the common case; a genuine
-        // nested-header edge case would need upstream's same coordination.
-        consumeTopInset: !view.hidden,
-        consumeLeftInset: !view.hidden,
-        consumeRightInset: !view.hidden,
-        consumeBottomInset: !view.hidden,
-        backTitle: view.backTitle,
-        backTitleVisible: view.backTitleVisible,
-        backButtonDisplayMode: view.backButtonDisplayMode,
-        largeTitle: view.largeTitle,
-        translucent: view.translucent,
-        color: view.color,
-        titleColor: view.titleColor,
-        backgroundColor: view.backgroundColor,
-        largeTitleBackgroundColor: view.largeTitleBackgroundColor,
-        userInterfaceStyle: view.userInterfaceStyle,
-        headerLeftBarButtonItems: view.headerLeftBarButtonItems,
-        headerRightBarButtonItems: view.headerRightBarButtonItems,
-        [HEADER_ON_PRESS_BAR_BUTTON_ITEM]: view.onPressHeaderBarButtonItem,
-        [HEADER_ON_PRESS_BAR_BUTTON_MENU_ITEM]: view.onPressHeaderBarButtonMenuItem,
-    };
-    const children = searchBarProps
-        ? [
-            el(RNS_SCREEN_STACK_HEADER_SUBVIEW_VIEW_NAME, { type: 'searchBar' }, [
-                el(RNS_SEARCH_BAR_VIEW_NAME, searchBarProps),
-            ]),
-        ]
-        : [];
-    return el(RNS_SCREEN_STACK_HEADER_CONFIG_VIEW_NAME, props, children);
-}
-// The RNSSearchBar leaf's static config props; event handlers ride in `passthrough`.
-// renderHeaderConfig wraps this into the RNSSearchBar Descriptor and nests it as the header
-// config's child.
-export function resolveSearchBarProps(view) {
-    return {
-        ...view.passthrough,
-        placeholder: view.placeholder,
-        autoCapitalize: view.autoCapitalize,
-        placement: view.placement,
-        hideWhenScrolling: view.hideWhenScrolling,
-        allowToolbarIntegration: view.allowToolbarIntegration,
-        obscureBackground: view.obscureBackground,
-        hideNavigationBar: view.hideNavigationBar,
-        cancelButtonText: view.cancelButtonText,
-        barTintColor: view.barTintColor,
-        tintColor: view.tintColor,
-        textColor: view.textColor,
-        autoFocus: view.autoFocus,
-        disableBackButtonOverride: view.disableBackButtonOverride,
-        inputType: view.inputType,
-        hintTextColor: view.hintTextColor,
-        headerIconColor: view.headerIconColor,
-        shouldShowHintSearchIcon: view.shouldShowHintSearchIcon,
-    };
-}
-// The 7 search-bar event keys -> option-callback passthrough: zero lifecycle dependency, so every
-// adapter built the identical map by hand. `log` is an optional per-event hook so an adapter can
-// still attach its own route-scoped dlog line (React/Vue do; Angular doesn't) without forking the
-// map itself.
-export function buildSearchBarPassthrough(options, log) {
-    return {
-        [SEARCH_BAR_ON_FOCUS]: () => {
-            log?.('search bar focused');
-            options.onFocus?.();
-        },
-        [SEARCH_BAR_ON_BLUR]: () => {
-            log?.('search bar blurred');
-            options.onBlur?.();
-        },
-        [SEARCH_BAR_ON_CHANGE_TEXT]: (event) => {
-            const { text } = event.nativeEvent;
-            const changedText = typeof text === 'string' ? text : '';
-            log?.(`search text changed: ${changedText}`);
-            options.onChangeText?.(changedText);
-        },
-        [SEARCH_BAR_ON_SEARCH_BUTTON_PRESS]: (event) => {
-            const { text } = event.nativeEvent;
-            const pressedText = typeof text === 'string' ? text : '';
-            log?.(`search button pressed: ${pressedText}`);
-            options.onSearchButtonPress?.(pressedText);
-        },
-        [SEARCH_BAR_ON_CANCEL_BUTTON_PRESS]: () => {
-            log?.('search bar cancel pressed');
-            options.onCancelButtonPress?.();
-        },
-        [SEARCH_BAR_ON_CLOSE]: () => {
-            log?.('search bar closed');
-            options.onClose?.();
-        },
-        [SEARCH_BAR_ON_OPEN]: () => {
-            log?.('search bar opened');
-            options.onOpen?.();
-        },
-    };
-}
-export function resolveScreenRenderPlan(input) {
-    const { options, isAndroid } = input;
-    const headerHidden = options?.headerShown === false;
-    const activityState = computeActivityState(input.index, input.routeCount);
-    const screenProps = resolveScreenProps(resolveScreenView(input.screenId, activityState, options, input.screenPassthrough));
-    const searchBarOptions = options?.headerSearchBarOptions;
-    const searchBarProps = searchBarOptions
-        ? resolveSearchBarProps(resolveSearchBarView(searchBarOptions, input.searchBarPassthrough ?? {}))
-        : undefined;
-    // See renderHeaderConfig's own header comment for why `props` never reflects `searchBarProps` --
-    // only `children` does -- so passing it here unconditionally is safe even for Angular, which
-    // never reads `children` off the result.
-    const headerConfig = renderHeaderConfig(resolveHeaderConfigView(options, input.platform), searchBarProps);
-    return {
-        activityState,
-        screenViewName: resolveScreenViewName(options?.stackPresentation, isAndroid),
-        screenProps,
-        headerConfig,
-        searchBarProps,
-        contentWrapperProps: {
-            style: resolveScreenContentWrapperStyle(options?.stackPresentation, headerHidden, options?.headerTranslucent, isAndroid),
-            collapsable: false,
-        },
-        inModal: isHeaderInModal(options?.stackPresentation, headerHidden, isAndroid),
-        innerStackStyle: resolveHeaderInModalStackStyle(),
-        innerScreenStyle: resolveHeaderInModalScreenStyle(),
-    };
-}

package/build/core/render-tabs.d.ts

@@ -1,20 +0,0 @@
-import type { IDescriptor } from '@symbiote-native/components';
-import type { IColorValue, IViewStyle, IStyleProp } from '@symbiote-native/engine';
-import type { ITabBarIcon } from './tab-options';
-export type ITabBarItemView = {
-    key: string;
-    focused: boolean;
-    label: string;
-    icon?: ITabBarIcon;
-    badge?: string | number;
-    activeTintColor?: IColorValue;
-    inactiveTintColor?: IColorValue;
-    passthrough: Record<string, unknown>;
-};
-export type ITabBarViewProps = {
-    items: readonly ITabBarItemView[];
-    style?: IStyleProp<IViewStyle>;
-    passthrough: Record<string, unknown>;
-};
-export declare function renderTabBarItem(item: ITabBarItemView): IDescriptor;
-export declare function renderTabBar(view: ITabBarViewProps): IDescriptor;

package/build/core/render-tabs.js

@@ -1,97 +0,0 @@
-// TabBar: the render half (framework-agnostic). A bottom-tabs bar is a PURE-JS UI - unlike
-// Stack, which drives real native RNSScreen/RNSScreenStack views, this paints ordinary
-// `symbiote-view`/`symbiote-text` primitives, so it needs no react-native-screens ViewConfig
-// work at all (see the task brief in packages/navigation's skill notes). Mirrors renderSwitch's
-// shape: pure prop-driven functions building a `Descriptor` tree from pre-resolved view props;
-// the adapter supplies focus state, tint-color resolution inputs, and the press wiring via
-// `passthrough` (exactly like Stack wires onDismissed/onHeaderBackButtonClicked into
-// resolveScreenView's passthrough) - this layer never invents an onPress/responder pair itself.
-import { el, txt } from '@symbiote-native/components';
-// react-navigation's own bottom-tabs default to the surrounding theme's primary/text colors;
-// symbiote's navigation package has no app-level theme yet, so these are placeholder defaults -
-// the same iOS-system-blue/neutral-grey pair render-button.ts already uses for its default
-// tint/disabled colors, reused here rather than inventing a third pair (no shared semantic color
-// tokens exist yet in @symbiote-native/engine as of this writing).
-const DEFAULT_ACTIVE_TINT_COLOR = '#007AFF';
-const DEFAULT_INACTIVE_TINT_COLOR = '#8e8e93';
-const BADGE_BACKGROUND_COLOR = '#FF3B30';
-const BADGE_TEXT_COLOR = '#ffffff';
-const TAB_BAR_HEIGHT = 49;
-const TAB_ICON_FONT_SIZE = 20;
-const TAB_LABEL_FONT_SIZE = 10;
-const BADGE_SIZE = 16;
-const BADGE_BORDER_RADIUS = BADGE_SIZE / 2;
-const BADGE_OFFSET_TOP = -4;
-const BADGE_OFFSET_RIGHT = -8;
-const TAB_BAR_STYLE = {
-    flexDirection: 'row',
-    height: TAB_BAR_HEIGHT,
-};
-const TAB_ITEM_STYLE = {
-    flex: 1,
-    alignItems: 'center',
-    justifyContent: 'center',
-};
-const ICON_WRAPPER_STYLE = {
-    alignItems: 'center',
-    justifyContent: 'center',
-};
-const BADGE_STYLE = {
-    position: 'absolute',
-    top: BADGE_OFFSET_TOP,
-    right: BADGE_OFFSET_RIGHT,
-    minWidth: BADGE_SIZE,
-    height: BADGE_SIZE,
-    borderRadius: BADGE_BORDER_RADIUS,
-    backgroundColor: BADGE_BACKGROUND_COLOR,
-    alignItems: 'center',
-    justifyContent: 'center',
-    paddingHorizontal: 3,
-};
-const BADGE_TEXT_STYLE = {
-    color: BADGE_TEXT_COLOR,
-    fontSize: 8,
-    fontWeight: '600',
-};
-function resolveTintColor(item) {
-    if (item.focused)
-        return item.activeTintColor ?? DEFAULT_ACTIVE_TINT_COLOR;
-    return item.inactiveTintColor ?? DEFAULT_INACTIVE_TINT_COLOR;
-}
-// A string icon paints as a glyph (an emoji/ligature font name - same convention a caller uses
-// for a vector-icon-font label); an IDescriptor icon (an <Image>/vector-icon element the adapter
-// already resolved) is spliced in verbatim, exactly like renderHeaderConfig treats a pre-built
-// Descriptor child.
-function renderIcon(icon, color) {
-    if (icon === undefined)
-        return undefined;
-    if (typeof icon === 'string')
-        return txt({ style: { color, fontSize: TAB_ICON_FONT_SIZE } }, [icon]);
-    return icon;
-}
-function renderBadge(badge) {
-    if (badge === undefined)
-        return undefined;
-    return el('symbiote-view', { style: BADGE_STYLE }, [
-        txt({ style: BADGE_TEXT_STYLE }, [String(badge)]),
-    ]);
-}
-export function renderTabBarItem(item) {
-    const color = resolveTintColor(item);
-    const icon = renderIcon(item.icon, color);
-    const badge = renderBadge(item.badge);
-    const iconChildren = [];
-    if (icon)
-        iconChildren.push(icon);
-    if (badge)
-        iconChildren.push(badge);
-    const children = [];
-    if (iconChildren.length > 0)
-        children.push(el('symbiote-view', { style: ICON_WRAPPER_STYLE }, iconChildren));
-    children.push(txt({ style: { color, fontSize: TAB_LABEL_FONT_SIZE } }, [item.label]));
-    return el('symbiote-view', { ...item.passthrough, style: TAB_ITEM_STYLE, accessibilityRole: 'tab' }, children, item.key);
-}
-export function renderTabBar(view) {
-    const items = view.items.map(renderTabBarItem);
-    return el('symbiote-view', { ...view.passthrough, style: [TAB_BAR_STYLE, view.style] }, items);
-}

package/build/core/screen-options.d.ts

@@ -1,4 +0,0 @@
-import type { IHeaderConfigViewProps, INavigatorPlatform, IScreenOptions, IScreenViewProps, ISearchBarOptions, ISearchBarViewProps } from './navigator-props';
-export declare function resolveHeaderConfigView(options: IScreenOptions | undefined, platform: INavigatorPlatform, passthrough?: Record<string, unknown>): IHeaderConfigViewProps;
-export declare function resolveScreenView(screenId: string, activityState: number, options: IScreenOptions | undefined, passthrough?: Record<string, unknown>): IScreenViewProps;
-export declare function resolveSearchBarView(options: ISearchBarOptions | undefined, passthrough?: Record<string, unknown>): ISearchBarViewProps;