@symbiote-native/components 3.1.1 → 3.1.2

package/build/behaviors/activity-indicator/shared.js

@@ -1,42 +1,25 @@
-// ActivityIndicator's host behavior: the composition and the prop fold, below the framework, so the
-// primitive is a bare `activity-indicator` tag and not five wrapper components.
-//
-// THE TWO-NODE SHAPE IS RN'S, not ours to collapse. `ActivityIndicator.js:112` opens a centering
-// `<View>` around the native spinner, so the tag is that View and `buildStructure` builds
-// `activity-indicator-spinner` under it. The container cannot be folded INTO the spinner either: it
-// carries `alignItems`/`justifyContent`, which centre the spinner inside the space it was given,
-// and moved onto the spinner they would centre its children, of which it has none.
-//
-// THE PLATFORM HALF IS THE SPINNER'S DEFAULTS AND NOTHING ELSE. iOS defaults the colour to RN's GRAY
-// and needs no extra native props; Android's default is the theme, which means OMITTING the key
-// rather than sending null (Fabric's colour parser rejects a null), plus `styleAttr` and
-// `indeterminate` — without the first, AndroidProgressBar throws "setStyle() not called".
-// `index.ios` / `index.android` supply them, the same file split `behaviors/scroll-view` uses.
-//
-// WHERE THE APP'S PROPS GO. `slotPropsExcept` is the COMPLEMENT of a rename map: everything an app
-// writes on the tag routes to the spinner under its own name except `ACTIVITY_INDICATOR_HOST_PROPS`,
-// which is RN's own split (`ActivityIndicator.js:99` spreads `...restProps` onto the spinner; `:113`
-// keeps `onLayout` and `style` on the View). The set that moves is OPEN — every aria alias, every
-// accessibility prop, whatever an app writes next — so a name map cannot express it.
-//
-// THE SIZE TRANSLATION IS PLATFORM-INVARIANT and lives here beside the fold that applies it: RN maps
-// 'small'/'large' to a native size enum AND a fixed box style, while a NUMBER never reaches native
-// at all (it sizes the spinner through style alone).
-//
-// Registered by all five adapters since 2026-09-09, in the same commit that deleted the five
-// wrappers — the registry is keyed by TAG, so registering while a wrapper still painted its own
-// spinner would have given every indicator two.
+// ActivityIndicator's host behavior: the composition and the prop fold, below the framework, so
+// the primitive is a bare `activity-indicator` tag and not five wrapper components.
+// The two-node shape is RN's, not ours to collapse: `ActivityIndicator.js:112` opens a centering
+// View around the native spinner. The container can't fold into the spinner either — it carries
+// `alignItems`/`justifyContent`, which would centre the spinner's own (nonexistent) children.
+// The platform half is only the spinner's defaults: iOS defaults colour to GRAY with no extra
+// props; Android's default is the theme (omit the key, Fabric rejects null) plus `styleAttr`/
+// `indeterminate` (AndroidProgressBar throws without the first). Split across index.ios/.android.
+// `slotPropsExcept` is the COMPLEMENT of a rename map: everything an app writes routes to the
+// spinner except `ACTIVITY_INDICATOR_HOST_PROPS` (RN's own split, `ActivityIndicator.js:99,113`).
+// The moved set is OPEN — every accessibility prop an app writes — a name map can't express it.
+// The size translation is platform-invariant: RN maps 'small'/'large' to a native size enum plus
+// a fixed box style, while a number sizes the spinner through style alone.
 import { appendChild, createElement, registerHostBehavior, setProp, } from '@symbiote-native/engine';
 import { descriptorFor } from '../../component-names';
 export const ACTIVITY_INDICATOR_TAG = 'activity-indicator';
 // The NATIVE spinner — `ActivityIndicatorView` on iOS, `AndroidProgressBar` on Android. Built by
 // `buildStructure` below and by nothing else; no app writes it.
 export const ACTIVITY_INDICATOR_SPINNER_TAG = 'activity-indicator-spinner';
-// The two size boxes, the default size and the centering style are NOT here any more: they are
-// literals inside `foldActivityIndicatorProps` / `foldActivityIndicatorSpinnerProps`
-// (`SymbioteFabricProps.cpp`). Keeping a JS copy of a value only C++ reads is the mirror this port
-// exists to remove — it would compile, export and test cleanly while nothing on a device consulted
-// it.
+// The size boxes, default size, and centering style live only in `foldActivityIndicatorProps`/
+// `foldActivityIndicatorSpinnerProps` (SymbioteFabricProps.cpp) — no JS copy of a value only C++
+// reads.
 // The props that stay on the centering host instead of travelling to the spinner: RN's own two
 // (`ActivityIndicator.js:113`) plus the spellings the ENGINE resolves against a node's own style.
 const ACTIVITY_INDICATOR_HOST_PROPS = [
@@ -44,33 +27,19 @@ const ACTIVITY_INDICATOR_HOST_PROPS = [
     'onLayout',
     // The composed `StyleSheet.compose(styles.container, style)` array (`:114`).
     'style',
-    // A class NAME resolves to a style (`routeProp`'s class branch), so a class written on the tag has
-    // to reach the centering view — the node `style` lands on — or the app's rule paints a spinner it
-    // was never written for.
+    // A class resolves to a style (`routeProp`'s class branch), so it must reach the centering view
+    // — the node `style` lands on — or the app's rule paints a spinner it was never written for.
     'class',
     'className',
 ];
-// `activeStyle` is deliberately NOT here. It looked like it belonged — it is slot 1 of the same
-// `pushClassStyle` merge `style` and `class` feed — but this primitive has no pressed state, so
-// `routeProp` consumes the key on whichever node it lands on and it never reaches Fabric either
-// way. An entry no test can make fail is an entry that was never wired in.
-// BOTH FOLDS LEFT THIS FILE on 2026-09-18 and neither was replaced by anything here: they are
-// `foldActivityIndicatorProps` and `foldActivityIndicatorSpinnerProps` in `SymbioteFabricProps.cpp`.
-// Every input either read was the node's own bag — no owner, no listener, no live state — which is
-// what made them tag rules rather than composition, and it is why both nodes now cost ZERO trips
-// into JS instead of one each. Contract:
-// `core/engine/cpp/tests/js/activity-indicator-payload.itest.ts`.
-//
-// The size constants, the container style and the default colour went WITH them rather than staying
-// as a second copy for the tests to assert. `platform.defaultColor` survives as the last field of
-// `IActivityIndicatorPlatform` only because the rule's Android half is chosen by COMPONENT NAME in
-// C++, so the JS value would have no reader — see the type's own note.
-// The composition. Returns the spinner as the slot because the prop redirect is gated on
-// `childHost` being set — the redirect is what this slot is FOR, and NOT where children go: RN's
-// ActivityIndicator renders only the spinner (`ActivityIndicator.js:112-118`) and takes no children
-// at all. Hence `slotTakesNoChildren` below; without it a stray child would mount INSIDE the native
-// spinner, which on Android is a `ProgressBar` and not a `ViewGroup` — the `addView` crash
-// `IHostBehavior.slotTakesNoChildren` records for ImageBackground's Image.
+// `activeStyle` is deliberately NOT here: this primitive has no pressed state, so it never
+// reaches Fabric — an entry no test can fail is one that was never wired in.
+// Both prop folds are C++ now (`SymbioteFabricProps.cpp`), asserted in
+// `core/engine/cpp/tests/js/activity-indicator-payload.itest.ts`. `platform.defaultColor` stays
+// because the Android half is chosen by COMPONENT NAME in C++.
+// Returns the spinner as the slot because the prop redirect gates on `childHost` being set — not
+// because children go there: RN's ActivityIndicator takes no children at all, hence
+// `slotTakesNoChildren` below (Android's ProgressBar isn't a ViewGroup and would crash on addView).
 function buildSpinner(platform) {
     return (node) => {
         const descriptor = descriptorFor(ACTIVITY_INDICATOR_SPINNER_TAG);
@@ -99,20 +68,9 @@ function activityIndicatorBehavior(platform) {
 // Called by the platform files; nothing else should.
 export function registerActivityIndicatorBehaviors(platform) {
     registerHostBehavior(ACTIVITY_INDICATOR_TAG, activityIndicatorBehavior(platform));
-    // A REGISTRATION WITH NO RUNTIME, and it is what hands the spinner's tag to the host.
-    //
-    // A tag crosses only through `recordSetTag`, which `attachHostBehavior` emits and nothing else
-    // does — so a tag with no behavior registered carries an EMPTY `tagName` in C++ and no rule can
-    // fire for it. The spinner is built by `buildStructure` and no app ever names it, so it had a tag,
-    // had platform semantics, and the host could not see either. Its rule lives in
-    // `SymbioteFabricProps.cpp` now (the size translation, RN's two `!== false` defaults, the
-    // platform's default colour), which is why this registration has to exist even though there is no
-    // JS left to run.
-    //
-    // Not a workaround for the seam: a registration is how this codebase declares that a tag HAS
-    // platform semantics, which is exactly the claim. Emitting the tag from `createElement` for every
-    // node was the alternative and is rejected where `attachHostBehavior` explains itself — an app's
-    // own `<div>`-equivalent would pay an intern and an op to name something the host has no rule for.
+    // A registration with no runtime: a tag with no behavior registered carries an empty `tagName`
+    // in C++ and no rule can fire for it, so this has to exist even though there's no JS left to run
+    // — a registration is how this codebase declares a tag HAS platform semantics.
     registerHostBehavior(ACTIVITY_INDICATOR_SPINNER_TAG, {
         attach() { },
         detach() { },

package/build/behaviors/button.d.ts

@@ -1,13 +1,4 @@
 export declare const BUTTON_TAG = "button";
-/**
- * NO MEMO, and the earlier version's memo is deliberately gone. It guarded `setProp`'s `Object.is`,
- * which a FRESH style object per call can never satisfy — so pushing unconditionally would have
- * dirtied a node on every commit and re-committed forever
- * (`.claude/rules/list-geometry-feedback-loop.md`). A payload fold does not go through `setProp`:
- * its result reaches `reconcile`, which compares against the mirror with a recursive `propsEqual`
- * (commit.ts) and reuses the committed handle when nothing moved. An equal-but-fresh style is
- * therefore not a change, and there is nothing to feed back.
- */
 export declare const BUTTON_LABEL_TEXT_TAG = "button-label-text";
 export declare const BUTTON_LABEL_TAG = "button-label";
 export declare function registerButtonBehavior(): void;

package/build/behaviors/button.js

@@ -1,116 +1,16 @@
-// Button as an ENGINE-NODE behavior, so RN's one batteries-included control can be an intrinsic
-// tag instead of five framework components (`.claude/rules/host-primitive-tier.md`, tier 2).
-//
-// THE WHOLE PRIMITIVE IS COMPOSITION. RN's Button is a touchable wrapping a View wrapping a Text
-// (Button.js:363-388) and takes NO children — `title` is a string prop. So `buildStructure` owns
-// the entire subtree, and the nodes below it are a PROJECTION of three owner props.
-//
-// AND THE TOUCHABLE IS NOT THE SAME ONE ON BOTH PLATFORMS (Button.js:281-284), which is why the
-// two trees have different HEIGHTS. TouchableOpacity WRAPS — it renders its own `<Animated.View>`
-// and puts the child inside it (TouchableOpacity.js:302,344). TouchableNativeFeedback RENDERS
-// NOTHING and clones its props onto the child instead (TouchableNativeFeedback.js:339), so on
-// Android Button's own `<View style={buttonStyles}>` IS the responder:
-//
-//   iOS      button   RCTView      TouchableOpacity's Animated.View — the responder + the fade
-//            └ view   RCTView      no style at all, and no fold
-//              └ text RCTText      `button-label-text` — foldButtonLabelStyle + RN's Text defaults
-//                └ raw RCTRawText  `button-label`    — uppercaseTitle (Android)   FOUR nodes
-//
-//   Android  button   RCTView      the styled button view, CLONED onto: the responder, the ripple
-//            │                     background, the whole a11y fold. No fade, no wrapper.
-//            └ text   RCTText
-//              └ raw  RCTRawText   UPPERCASED (Button.js:352-353)                 THREE nodes
-//
-// EVERY RULE IS IN THE ENGINE AS OF 2026-09-18, and off Android this primitive binds no
-// `payloadFold` on any of its four nodes — it costs ZERO trips into JS, down from five. The one that
-// survives is the OWNER's on Android, for the view style and the ripple background.
-//
-// The last to move was the label text's, and it needed a seam none of the others did: its style is a
-// function of the BUTTON's `color` and `disabled`, and the button is its GRANDPARENT here and its
-// parent on Android. `IAncestorLookup` asks for the nearest ancestor carrying a tag — a CSS ancestor
-// selector — so one rule is correct on both trees.
-//
-// ---------------------------------------------------------------------------------------------
-// HOW THE PROJECTION REACHES ITS NODES, given that each `payloadFold` MUST be pure:
-//
-//   title    a REDIRECT. The raw text is the slot, and `slotProps` renames `title` -> `text` on it,
-//            so the app's write lands on the label through the label's own `routeProp` and marks
-//            it. `resolveButtonTitle`'s uppercase is then the label's own fold over its OWN props —
-//            no owner to read, and `isEmptyRawText` still sees the real title, so an empty one is
-//            dropped by the commit walk exactly as it was before.
-//   color    a per-node FOLD over the owner, on the text and — on iOS — on the view (the shape
-//   disabled `behaviors/scroll-view/shared.ts` uses). `slotDerived` marks the slot, and
-//            `addDerivedNode` extends that mark to the nodes past it. On Android the second
-//            consumer is the OWNER itself, which `setProp` already dirties.
-//
-// So no node writes to another and no follow-up commit is needed. Two seams that do NOT work here,
-// measured against the real commit path, so neither is tried again:
-//
-//   slotDerived alone     marks `node.childHost` and nothing else — ONE node, where a colour change
-//                         moves two. `addDerivedNode` is the hop past it.
-//   afterCommit           UNREACHABLE for exactly the props that matter. `title` and `color` never
-//                         reach the host payload, so a write to either produces a byte-identical
-//                         payload and `commitContainer` returns on a no-op ABOVE
-//                         `runDeferredAttaches`. Recorded at `IHostBehavior.afterCommit`.
-//
-// WHY THE OWNER'S FOLD IS BOUND IN `buildStructure` rather than declared as `behavior.foldPayload`.
-// It needs two things that are not in the bag it is handed: `onPress` lives in the listener STASH
-// (`ownedListeners` diverts it, so `props.onPress` is always undefined), and `focusable` is a
-// function of it. `scroll-view/index.android.ts` assigns `owner.payloadFold` from `onWrapChange`
-// for the same reason; `attachHostBehavior` sets the field one line BEFORE it calls
-// `buildStructure`, so the binding here is what stands.
-// ---------------------------------------------------------------------------------------------
-// KNOWN DIVERGENCES, stated rather than left to be discovered on a device:
-//
-// 1. CLOSED 2026-09-09, and it closed by DELETION rather than by a fix. The gap was that all five
-//    wrappers rendered TouchableOpacity unconditionally where RN swaps in TouchableNativeFeedback
-//    (Button.js:280-283), so a Button faded on Android and committed four nodes where RN ripples
-//    and commits three. There is no wrapper left to diverge: `button` is a tag, registered by all
-//    five adapters, and the swap above is the only implementation.
-//
-//    THE ORDER MATTERED AND IS THE REUSABLE HALF. The registry is keyed by TAG, so registering
-//    while a wrapper still built its own view and text would have given every Button a SECOND copy
-//    of the subtree — the hazard `behaviors/scroll-view/shared.ts` records. Entry, registration and
-//    the five deletions are one change, which is also what `touchable-native-feedback` did hours
-//    earlier and for the same reason.
-//
-//    WHAT AN APP SEES, stated because it is a behaviour change and not a refactor: on Android a
-//    Button now ripples instead of fading and commits three nodes instead of four. That is the RN
-//    parity this whole line of work was for.
-//
-// 2. CLOSED 2026-09-09, kept for the seam rather than the gap. `aria-disabled` — and an authored
-//    `accessibilityState.disabled` — now suppress the press, not just grey the label.
-//
-//    THE RESOLUTION IS BUTTON'S, NOT THE MACHINE'S, and that asymmetry is the finding. RN hands
-//    Pressability the RAW prop (Pressable.js:266), so on a bare `pressable` `aria-disabled` changes
-//    only what is ANNOUNCED and the press still fires; resolving it down there would be a new
-//    divergence pointing the other way. Button is the outlier (Button.js:337), so it hands the
-//    touchable an `IDisabledResolver` (`./pressable`) and `rebuild` calls it at every gesture start.
-//
-//    A RESOLVER RATHER THAN A WRITE, because writing the answer into `node.props.disabled` LATCHES:
-//    `resolveButtonDisabled` short-circuits on `disabled !== undefined`, so the injected value would
-//    answer the next resolution as the app's own and the button could never re-enable. Reading per
-//    gesture also means a flip needs no commit to reach the machine.
-//
-//    AND THE PRESS WAS ONLY HALF OF IT. `./touchable-opacity`'s `afterCommit` re-settles the fade
-//    when `disabled` moves, and it read the RAW prop — so for an hour after the press half closed, a
-//    Button disabled by `aria-disabled` mid-press stayed at its ACTIVE opacity while already
-//    refusing the press. It reads through the same resolver now. The general shape: one prop
-//    resolved in two places, and closing the first makes the second look done.
-//
-// 3. CLOSED 2026-09-09, repo-wide, and kept here for the finding rather than the gap. `focusable`
-//    was emitted by NOTHING in `core/components` — not a wrapper, not the press behavior — so a
-//    keyboard or TV host could focus a disabled button, on every adapter and both paths. RN carries
-//    two formulas (`Pressable.js:258` vs the four `Touchable*`, which also require a press handler
-//    and a non-disabled state); both now live in `../view/render-pressable` and every behavior and
-//    surviving wrapper calls them.
-// ---------------------------------------------------------------------------------------------
-//
-// REGISTRATION IS THE HAZARD, not the machine — see `./pressable` for why each adapter entry does
-// a bare `import './register';` that the barrel does not re-export. Registered by ALL FIVE adapters
-// since 2026-09-09, in the same commit that deleted the five wrappers, which is what makes it safe:
-// while a wrapper still built its own view and text under this tag, registering would have given
-// every Button a second copy of the subtree.
+// Button as an ENGINE-NODE behavior: RN's Button is a touchable wrapping a View wrapping a Text
+// (Button.js:363-388) with no children, so `buildStructure` owns the whole subtree as a
+// PROJECTION of `title`/`color`/`disabled`.
+// The touchable differs by platform (Button.js:281-284): iOS's TouchableOpacity WRAPS (an extra
+// Animated.View, FOUR nodes total); Android's TouchableNativeFeedback clones onto the child, so
+// Button's own view IS the responder (THREE nodes — ripple + a11y cloned onto it, no fade).
+// `title` is a rename via `slotProps`; `color`/`disabled` are a per-node fold over the owner via
+// `slotDerived`/`addDerivedNode`. Neither needs a follow-up commit: neither prop ever reaches the
+// host payload, so an `afterCommit` write on either would be a byte-identical no-op.
+// The owner's fold binds in `buildStructure`, not `behavior.foldPayload`: it needs `onPress` from
+// the listener stash (`props.onPress` is always undefined) and `focusable`, derived from it —
+// same reason `scroll-view/index.android.ts` assigns `owner.payloadFold` from `onWrapChange`.
+// Registered by all five adapters — see `./pressable` for why via a bare `import './register'`.
 import { addDerivedNode, appendChild, createElement, createRawText, markPropsDirty, Platform, registerHostBehavior, requestCommitFor, } from '@symbiote-native/engine';
 import { descriptorFor } from '../component-names';
 import { resolveButtonDisabled } from '../view/render-button.js';
@@ -118,15 +18,12 @@ import { booleanOr, createPressBehavior, } from './pressable.js';
 import { nativeFeedbackRefinement } from './touchable-native-feedback.js';
 import { createTouchableOpacityBehavior } from './touchable-opacity.js';
 export const BUTTON_TAG = 'button';
-// Read once, like `render-button`'s own module-level `buttonViewStyle`: the platform cannot change
-// under a running app, and every test that needs the other branch already has to mock `Platform`
-// for `render-button` regardless — which is why this is a branch rather than a `button/` folder
-// split. A file split would move the behavior and leave its style half still reading `Platform`.
+// Read once: the platform cannot change under a running app. A branch, not a `button/` folder
+// split, since a split would move the behavior but leave its style half still reading Platform.
 const IS_ANDROID = Platform.OS === 'android';
-// The owner props the derived nodes' styles are derived from. A name missing here is a node frozen
-// at its mount value, which is the whole failure mode this list has. `title` is NOT one of them: it
-// is redirected by `SLOT_PROPS` and never reaches `setProp` on the owner, so listing it would be
-// dead.
+// The owner props the derived nodes' styles are derived from. A name missing here is a node
+// frozen at its mount value. `title` is NOT one of them — SLOT_PROPS redirects it, so it never
+// reaches setProp on the owner.
 const SLOT_DERIVED = [
     'color',
     'disabled',
@@ -160,117 +57,42 @@ function projectionOf(props) {
 // What the press machine reads instead of the raw prop — see KNOWN DIVERGENCES 2. Pure: the
 // projection is derived per call and nothing is written back.
 const buttonDisabled = props => projectionOf(props).disabled;
-/**
- * NO MEMO, and the earlier version's memo is deliberately gone. It guarded `setProp`'s `Object.is`,
- * which a FRESH style object per call can never satisfy — so pushing unconditionally would have
- * dirtied a node on every commit and re-committed forever
- * (`.claude/rules/list-geometry-feedback-loop.md`). A payload fold does not go through `setProp`:
- * its result reaches `reconcile`, which compares against the mirror with a recursive `propsEqual`
- * (commit.ts) and reuses the committed handle when nothing moved. An equal-but-fresh style is
- * therefore not a change, and there is nothing to feed back.
- */
-// THE VIEW'S FOLD IS GONE AND WAS NOT PORTED — it was doing nothing, on the only platform where it
-// ran. It wrote `style: resolveButtonViewStyle(color, disabled)`, and that function returns the
-// constant `buttonViewStyle` on every platform but Android while the view node is built ONLY in the
-// non-Android branch of `buildStructure`. `buttonViewStyle` off Android is `{}`. So it read two
-// props off its owner, discarded both, and spent a JSI round trip per button per commit to write an
-// empty style.
-//
-// This is the `input-accessory-view` shape again, and the second time this migration has found one:
-// a fold's price is the TRIP, not the body, so a fold that does nothing is the worst value in the
-// file and deleting it is worth as much as porting one that does a lot.
-//
-// Proven not to move the payload rather than argued: `button-derived-payload.itest.ts` pins the
-// view's committed keys, including with an app-set `color` — which lands on the LABEL here and must
-// not reach this node.
-// THE LABEL TEXT'S TAG. Its style is a function of the BUTTON's `color` and `disabled`, and the
-// button is this node's grandparent on iOS (`button -> view -> text`) and its parent on Android —
-// so the rule asks for the NEAREST BUTTON ancestor rather than for a fixed number of hops, which is
-// the same question a CSS ancestor selector asks and is true on both trees.
-//
-// `foldButtonLabelStyle` in `SymbioteFabricProps.cpp`, reached through `IAncestorLookup`. That seam
-// was the thing this fold was waiting for: `ownerProps` answers "my parent" and this node's parent
-// is the wrapping view, which knows none of it.
+// NO MEMO: a payload fold doesn't go through setProp, so its result reaches reconcile, which
+// compares against the mirror with a recursive propsEqual and reuses the committed handle when
+// nothing moved. An equal-but-fresh style is not a change, so there's nothing to feed back.
+// The view's fold is gone, not ported: it wrote a style that's the constant `buttonViewStyle` on
+// every platform but Android, where the view node isn't even built — so it read two props,
+// discarded both, and paid a JSI round trip per button per commit for an empty style.
+// Proven, not argued: button-derived-payload.itest.ts pins the view's committed keys, including
+// with an app-set `color`, which lands on the LABEL and must not reach this node.
+// THE LABEL TEXT'S TAG. Its style is a function of the button's `color`/`disabled`, and the button
+// is this node's grandparent on iOS but its parent on Android — so foldButtonLabelStyle asks for
+// the NEAREST BUTTON ancestor rather than a fixed hop count, true on both trees.
 export const BUTTON_LABEL_TEXT_TAG = 'button-label-text';
 // The label's own tag, on the raw text that holds the title. Its Android uppercase (`Button.js:352`)
 // is `uppercaseTitle` below, in JS: the C++ tag rule it briefly was could only do ASCII.
 export const BUTTON_LABEL_TAG = 'button-label';
 // ---- the Android touchable -------------------------------------------------------------------
-// Button.js:281-284. Not two variants of one component: see the tree diagram at the top for what
-// wrapping instead of cloning costs. The Android arm composes the bare press machine, so no
-// opacity value is opened and no fade runs — the ripple IS the feedback there.
-//
-// The refinement is TNF's own and now lives with TNF (`./touchable-native-feedback`). This file
-// held a private copy while the `touchable-native-feedback` TAG did not exist and its wrappers
-// still wrapped where RN clones; the tag landed, the responder node was already a parameter, and
-// one caller became two.
+// Not two variants of one component: see the tree diagram at the top for what wrapping instead
+// of cloning costs. The Android arm composes the bare press machine, so no opacity value opens
+// and no fade runs — the ripple IS the feedback there. The refinement lives with TNF.
 const touchable = IS_ANDROID
     ? createPressBehavior(nativeFeedbackRefinement, buttonDisabled)
     : createTouchableOpacityBehavior(buttonDisabled);
 // ---- the owner's own payload -------------------------------------------------------------------
-/**
- * The wrapper-body folds, over the touchable's own. What is deliberately NOT here:
- *
- *   accessible          the touchable's fold already applies `accessible !== false`, which is
- *                       exactly RN's split — Button forwards the caller's value RAW (Button.js:365)
- *                       and the touchable one level down defaults it (TouchableOpacity.js:303).
- *   accessibilityState  the engine's aria fold gives `ariaDisabled ?? state.disabled` and the press
- *                       fold then merges `props.disabled` over it, which composes to RN's
- *                       `props.disabled ?? aria ?? state.disabled` — the same value, with
- *                       busy/checked/expanded/selected preserved, without a Button-specific fold.
- *
- * THE TOUCHABLE'S HALF IS NO LONGER A FUNCTION ON EITHER PLATFORM, and the absence is the design
- * rather than a gap: neither `createPressBehavior` nor `createTouchableOpacityBehavior` has a
- * `foldPayload` any more, because both rules moved into the engine (`foldPressableProps` and
- * `foldIdAlias`, `SymbioteFabricProps.cpp`), which names `button` among the tags it serves. So the
- * same work happens, one layer down and before this fold runs — the order is unchanged, the trip
- * into JS is gone.
- *
- * The composition used to be spelled `touchable.foldPayload === undefined ? props : ...`, and that
- * shape is deleted rather than left standing at its `undefined` branch: a conditional call through
- * a field nothing assigns any more is a whole rule that vanishes silently the day the field is
- * removed, which is exactly how it would have gone unnoticed here.
- */
-// `focusable` LEFT THIS FOLD ON 2026-09-18, and with it the whole fold off Android.
-//
-// It was the last thing here that ran on both platforms, and it stayed because its middle leg is
-// `onPress !== undefined` — an owned listener, stashed in JS. That bit crosses now
-// (`OP_SET_OWNED_LISTENER`), and Button's three-way `disabled` was only ever three PROPS, so
-// `foldButtonProps` resolves the expression itself. It reads the AUTHORED bag rather than the folded
-// one, which is the same Trap A correction this fold carried as `projectionOf(propsOf(node))`.
-//
-// The ANDROID half went the same day, once the test host grew an arm that compiles `#ifdef ANDROID`
-// (`tests/CMakeLists.txt`, `SYMBIOTE_PLATFORM_ANDROID`). It is inside `foldButtonProps` now: the
-// Material view style and the theme's selectable background, which TNF clones onto this very node
-// (`TouchableNativeFeedback.js:339`) because it renders no view of its own.
-//
-// SO BUTTON BINDS NO FOLD ON EITHER PLATFORM, and it is the first primitive to reach that with a
-// subtree — four nodes, four crossings per commit when this migration started.
-//
-// Contract: `core/engine/cpp/tests/js/button-payload.itest.ts` for the platform-invariant half and
-// `android-rules.itest.ts` for the style, the colour override and the disabled greying.
-/**
- * Builds the whole subtree, once, at `attachHostBehavior`.
- *
- * RETURNS THE RAW TEXT. RN's Button declares no `children` prop and renders none, so the slot is
- * not where the app's children go — it is where its `title` goes, which is what `SLOT_PROPS`
- * redirects onto it. `childHost` is also the GATE on both engine seams this behavior uses:
- * `slotDerived`'s mark and the prop redirect are both skipped unless it is set (node.ts), so
- * returning `undefined` would leave the whole subtree frozen at its mount values.
- */
+// Button binds NO `payloadFold` on either platform: the touchable's half is in the engine
+// (`foldPressableProps`/`foldIdAlias`), the Android style/ripple/focusable half is
+// `foldButtonProps` in C++. Asserted in `button-payload.itest.ts` / `android-rules.itest.ts`.
+// Builds the whole subtree, once, at attachHostBehavior. RETURNS THE RAW TEXT: RN's Button
+// renders no children, so the slot is where `title` goes. `childHost` also gates both engine
+// seams this behavior uses, so returning undefined would freeze the whole subtree at mount values.
 function buildStructure(node) {
     const textDescriptor = descriptorFor('text');
     const text = createElement(textDescriptor.component, textDescriptor.isText, BUTTON_LABEL_TEXT_TAG);
-    // RN's two Text defaults are NOT written here, and that is deliberate as of 2026-09-18: they are
-    // the platform's, applied by the payload builder to every `RCTText` (`foldTextDefaults`), so this
-    // node inherits them for being a text rather than for being handed them. Seeding them was two
-    // writes per button per commit producing the payload the builder already produces — the shape
-    // `seedTextDefaults` had in three adapters. `button-derived-payload.itest.ts` reads them off the
-    // committed payload and is what proves the node still gets them.
-    //
-    // Empty until the redirected `title` arrives. The commit walk drops an empty raw text
-    // (`isEmptyRawText`, node.ts), so no Fabric node exists for it until it has a label — and that
-    // check reads `props.text`, which the redirect writes, not the fold's uppercased output.
+    // RN's two Text defaults are NOT written here: they're the platform's, applied to every RCTText,
+    // so this node inherits them for being text, not for being handed them.
+    // Empty until the redirected `title` arrives: the commit walk drops an empty raw text, so no
+    // Fabric node exists for it until it has a label.
     const label = createRawText('', BUTTON_LABEL_TAG);
     // The hop `slotDerived` alone does not make: it marks the slot (the label), and this is past it.
     addDerivedNode(node, text);
@@ -292,10 +114,8 @@ function buildStructure(node) {
         // setting the field itself.
         appendChild(node, view);
     }
-    // ANDROID ONLY since 2026-09-18. See the header: the owner's fold needs its own node, and this
-    // NOTHING IS BOUND HERE ON EITHER PLATFORM as of 2026-09-18, which is the point — a fold with an
-    // empty body still costs a full JSI round trip per commit, so leaving one that returns its input
-    // is the worst value available (`input-accessory-view`, and Button's own `viewFold`).
+    // No fold bound here on either platform: an empty-body fold still costs a full JSI round trip
+    // per commit, worse than not having one at all.
     return label;
 }
 // `focusable` is a function of a LISTENER, and a listener flip changes no payload by itself — so
@@ -317,9 +137,7 @@ function uppercaseTitle(slotKey, value) {
 // Idempotent: an adapter entry may be imported more than once in a bundle.
 export function registerButtonBehavior() {
     // `attach`/`detach` come from the touchable unwrapped: the internal nodes are ordinary children
-    // that leave with the sweep, and each carries only a pure fold, so this behavior owns no per-node
-    // runtime of its own to release.
-    //
+    // that leave with the sweep, so this behavior owns no per-node runtime of its own to release.
     const behavior = {
         ...touchable,
         buildStructure,
@@ -329,12 +147,8 @@ export function registerButtonBehavior() {
         ...(IS_ANDROID ? { slotValueFor: uppercaseTitle } : {}),
     };
     // The two DERIVED nodes' tags, registered with no runtime at all. A tag reaches C++ only through
-    // `recordSetTag`, which `attachHostBehavior` emits, so a tag nobody registered carries an empty
-    // `tagName` in the host and no rule fires for it — however the rule is written. Same shape as the
-    // ActivityIndicator spinner's and ImageBackground's inner image.
-    //
-    // A registration is how this codebase declares a tag HAS platform semantics, which is exactly the
-    // claim: the label's style is RN's, not the app's.
+    // recordSetTag, which attachHostBehavior emits — a tag nobody registered fires no rule at all.
+    // A registration is how this codebase declares a tag HAS platform semantics.
     const derived = { attach() { }, detach() { } };
     registerHostBehavior(BUTTON_LABEL_TEXT_TAG, derived);
     registerHostBehavior(BUTTON_LABEL_TAG, derived);