@onekeyfe/react-native-native-list 3.0.157-alpha.248 → 3.0.157-alpha.250

package/docs/MIGRATION_BASELINE.md

@@ -0,0 +1,117 @@
+# Renderer migration baseline
+
+Inventory captured at `a75666930` on 2026-09-22. This records existing behavior,
+not a new public API. Keep each rule until its owning migration explicitly
+replaces the caller contract. Renaming keys must not be an accidental side effect
+of the Message extraction.
+
+## Complete implicit key inventory
+
+The audit covered the TS wrapper/validation/selection/scrolling, Web engine,
+Swift models/cell/container, and Kotlin models/row/adapter/container. Searches
+included key/sectionKey/column-key comparisons, prefix/substring tests and named
+sets. Generated bindings and examples do not define renderer semantics.
+
+| Rule | Existing behavior and source | Disposition |
+| --- | --- | --- |
+| `history-` prefix | iOS `NativeListCell.bindSectionHeader` and `RNCNativeListView.rowHeight`: row key **or** section key implies history title/height. Web `estimateWebRowHeight`: same two keys imply 16-unit header height; its rendering still follows the explicit variant. Android `bindSectionHeader`/`applySize`: only **section key** implies uppercase 12/16 title, 0 padding and 16-unit minimum height. Explicit `variant: history` works independently. | Stage 4 moved these defaults into the SectionHeader renderers. Both example history headers and the validation fixture already set `variant: history`; no implicit history-header caller remains in this repository. Stage 6 audited the app-monorepo callers and removes the compatibility fallback; only the explicit variant selects history styling. |
+| `token-`, `balance-token-`, exact `linear-custom-token` | Android `NativeListRowView.bind` suppresses `separator: true` for these keys across row types. iOS/Web have no equivalent key exception. | Removed in stage 6 after auditing examples and app-monorepo: no matching caller sets `separator: true`. Separators now obey the explicit field on every platform. |
+| exact section keys `linear-tokens`, `action-tokens` | Android `bindSectionHeader`/`applySize` applies token-manager 14/20 regular typography, horizontal 12/top 10/bottom 0 padding and 30-unit minimum height (subject to earlier explicit presentation/variant branches). No matching iOS/Web rule. | Stage 4 migrated both example callers to an explicit 30-unit container height, bottom alignment, 12-unit horizontal / zero vertical padding and regular 14/20 title. Stage 6 verified external consumers and removes the fallback. Renaming either key no longer changes typography or geometry. |
+| exact tail keys `market-loading-more`, `market-load-more-retry`, `market-end` | Android `NativeListView.isMarketPaginationUpdate` drops those trailing rows before checking a stable Market prefix when either snapshot has loadMore; this keeps the scroll anchor during pagination. It is a container update optimization, not a row renderer. | Preserve in the container. Replace with explicit structural-row recognition in a separately validated pagination change. |
+| exact column key `asset` | Web `createDataRow` adds row badges only to that table column. Native table binders attach row badges to the first column instead. | Retained as a documented DataRow compatibility rule. No app-monorepo DataRow caller was found in the stage 6 audit; changing badge placement requires a separate explicit API/caller migration. |
+
+There are no other business-key-dependent decisions in the audited production
+paths. Equality for identity/diffing, selection targets, section membership,
+scroll targets, reorder membership, action lookup, image recycling keys and
+stale-callback guards is intentional identity usage, not a business-key rule.
+Keyboard event keys and style-property whitelist keys are also unrelated.
+
+## Stage 6 consumer audit
+
+Audited on 2026-09-23: local app-monorepo `67fcc71204` and `origin/x`
+`62c645f906`. NativeList imports/builders in AccountSelector, UnifiedNetworkSelector
+and Market have no history/token key styling dependencies. Repository token rows
+omit `separator` (false); history headers specify `variant: history`; token
+headers already specify their height, alignment, spacing and typography.
+No external checkout changes were needed. This is a source audit of these refs,
+not a claim about all published consumers.
+
+The two retained rules above are the container pagination optimization and
+DataRow badge-column ownership. Neither chooses a renderer or maps `row.style`
+fields. List event/selection/reorder identities continue to use keys normally.
+
+## Default geometry and precedence
+
+[STYLE_SPEC.md sections 8–9](STYLE_SPEC.md) inventory all twelve templates' row
+heights, typography, spacing, image sizes and existing platform differences.
+Preserve those unstyled defaults when extracting view ownership. Explicit
+`style.container.height` wins over `row.height`; compact WalletGroup reorder
+height remains a temporary container override. Style removal restores defaults.
+No overflow fitting or font shrinking is introduced.
+
+Message baseline: native 28-unit leading/64-unit thumbnail, title/body 14/20,
+time 12/16; iOS column gaps 2 plus a 2-unit timestamp inset, Android body/time
+margins 2/4. Web retains its existing horizontal timestamp, 40-unit leading,
+64-unit thumbnail, 15/20 title, 13/18 body, 11/16 timestamp and 8/12 padding.
+Explicit native style values use logical units; Android legacy defaults/model
+heights retain NativeListScale, while explicit styles use display density.
+
+The old iOS/Web Message estimators used different fallback metrics from their
+views (including 20 horizontal padding and 14/20 time). Stage 2 must correct this
+as an explicit measurement change, separate from view extraction; explicit
+heights and the unstyled visual defaults above stay unchanged.
+
+## Special update and lifecycle inventory
+
+| Path | Required invariant |
+| --- | --- |
+| Full snapshot/patch | Stable key identifies data; incompatible renderer family replaces the view. Bind A → B is correct without recycling. |
+| Message | Renderer classifies no-op, content/style, asset and replacement work. Unchanged image descriptors retain requests/views; changed or removed assets cancel old callbacks/retries. |
+| Market quote | Preserve price/priceSegments/change/accessibility partial updates and explicit rich text styles. Theme/layout/non-quote changes still require full binding. |
+| Selection echo/summary | Preserve native immediate feedback, latest descriptor/action context and fixed-height summary updates without resetting images. Unknown/mixed payloads keep full binding. |
+| Async image completion | Request identity and binding lifetime reject stale writes; bounded retries/fallbacks cannot cross recycle/disposal. |
+| Action anchors | Rebind/recycle invalidates old epoch-owned source anchors. Selection-only presentation updates retain their current owner. |
+| WalletGroup/reorder | Keep member events, compact 68-unit drag appearance, expansion restoration and bounded member-host retention. Message extraction does not change these paths. |
+| Containers | Header/footer, sections/index, scrolling, table/grid/horizontal allocation and pagination remain list-owned. |
+
+## Acceptance baseline
+
+The existing 150 package tests and seven Android tests, together with the dated
+Message runtime cases in [DESIGN.md](DESIGN.md), establish the pre-migration
+baseline. Native title/body/time bounds were captured before text extraction.
+The Message fixture covers explicit/model height, style set/change/clear, blank
+body/time, same-key Message/Identity changes, images, end/top scrolling, 41-row
+mixed swaps, empty/repopulate and the fixed footer on all three platforms.
+Full native acceptance of the later templates remains a gate for stages 3–5,
+not an implied result of finishing this inventory.
+
+## Rail extraction baseline (stage 3)
+
+Rail keeps iOS title/badge gap 8 versus Android/Web 6. Android's default status
+margin is 0 even though its historical width reserves 6; iOS/Web use 6. Default
+height remains iOS/Web 40 and Android's scaled minimum 28. Native text is 12,
+with 16-unit title/badge line metrics; Android status keeps its natural line
+height. Web retains 12/11/13 for title/badge/status. Leading size is 20 and
+padding is 4. These are existing differences, not different style property APIs.
+Horizontal sizing retains the legacy allowances (including iOS's old 6-unit
+badge-gap estimate inside its trailing budget and Android's status allowance)
+and now applies explicit resolved style metrics. Style removal restores the
+baseline dimensions. Rail does not show persistent row selection; press and
+reorder feedback remain container-owned.
+
+## Stage 4 caller audit
+
+The 2026-09-23 search covered all tracked source and examples.
+`example/react-native/pages/NativeListExamplePage.tsx` has two history headers;
+both already supply `variant: history`. Other `history-` occurrences identify
+Activity section membership or explicitly styled validation fixtures. The two
+Token Manager headers now declare their geometry and typography through the
+shared rowStyle contract. Bottom alignment puts the 20-unit title at the bottom
+of its 30-unit row without requiring a new asymmetric-padding property.
+Those explicit style values use logical units on all platforms, replacing
+Android's old scaled default at these caller sites.
+
+Stage 6 completed the external-consumer source audit described above and removed
+the native/Web header key fallbacks. Stage 5 also migrated WalletGroup members
+to independent Identity hosts. The historical defaults in this baseline remain
+useful when reviewing explicitly styled caller behavior.

package/docs/ROW_TEMPLATES.md

@@ -0,0 +1,359 @@
+# NativeList row template catalog
+
+This catalog defines the **12 types in `RowModel`** on the consolidated spec
+branch. Each template owns a fixed internal structure. Its `style` customizes
+named fields inside that structure; it does not define a new layout or enable a
+list feature. See [STYLE_SPEC.md](STYLE_SPEC.md) for tokens, numeric bounds,
+layout-safety rules, common capabilities and implementation gaps.
+
+The diagrams are **schematics, not device screenshots or pixel specifications**.
+Blue areas denote content fields; green areas denote accessories/actions; dashed
+areas are optional. They illustrate slot relationships, not literal native view
+names. Legacy platform dimensions remain in STYLE_SPEC §4/§6. A diagram showing
+an optional field does not mean every variant displays it.
+
+All rows have a stable `key` and discriminant `type`. Shared `RowBase` metadata
+includes `height`, `size`, `density`, `sectionKey`, `groupId`, `groupPosition`,
+selection/disabled state and separator intent. These are model/layout inputs,
+not a freeform style object. Every template also accepts `style.container.height`
+to override `row.height`; clearing it restores the original height/measurement.
+The style changes the row allocation without changing its internal slot order.
+Declaring `sectionKey` never makes a business
+template the owner of sections or the indexed bar.
+
+| Type | Purpose | Fixed structure |
+| --- | --- | --- |
+| [identity](#identity) | Asset, account, wallet or network | Leading visual + identity text + trailing accessories; named selector variants |
+| [walletGroup](#walletgroup) | Wallet family in the sidebar | Parent wallet followed by child wallets |
+| [rail](#rail) | Compact navigation/status item | Compact visual + title + optional status/badge |
+| [activity](#activity) | Transaction/activity item | Identity/description + amounts + optional row-local actions |
+| [message](#message) | Notification | Title/body/time + optional leading visual/thumbnail |
+| [dataRow](#datarow) | Comparable values | Two to four stable weighted columns |
+| [market](#market) | Token/stock/perpetual quote | Asset identity + price + change block |
+| [mediaTile](#mediatile) | Gallery or browser preview | Media area over caption metadata |
+| [metricCard](#metriccard) | KPI or portfolio summary | Label/value card or named composite metrics arrangement |
+| [sectionHeader](#sectionheader) | Structural section heading | Header text + optional summary value/controls |
+| [action](#action) | A row-level command | Label + optional icon/value/controls |
+| [system](#system) | Loading, retry, warning, empty/end or spacer | Variant-specific bounded status content |
+
+The style roles below form the shared configurable contract on Web, iOS and
+Android. **Template** means structure and content fields; **row style** means
+allowlisted parameters applied to those existing fields. Each template exposes
+only applicable box/image parameters, listed in [STYLE_SPEC §4.1](STYLE_SPEC.md#41-shared-configurable-properties).
+All templates accept the shared `style.container` surface (background, opacity,
+radius, border and content vertical alignment). All text roles share the same
+typography, 1–3 line limit, truncation, alignment and optical-offset properties; supported
+image roles share the same dimensions/shape/fit properties. An absent optional
+field is not created by styling it. Native rendered acceptance is tracked
+separately from source implementation in STYLE_SPEC §9.
+
+## identity
+
+![Identity: leading visual, title and optional secondary text, badges and trailing accessories](images/row-identity.svg)
+
+- **Use:** an identifiable asset, account, wallet, network or setting.
+- **Required data:** `leading`, `title`; optional `subtitle`, `tertiary`, `badges`,
+  `trailing`, `leadingAction`, match ranges and structured subtitle segments.
+- **Variants:** default horizontal row; `accountSelector` and `networkSelector`
+  preserve selector control geometry; `walletSidebar` uses a compact, centered
+  wallet presentation. A variant is explicit model data, never inferred from font size.
+  Selector control geometry applies on all platforms when the row has an
+  explicit height from either `style.container.height` or the legacy `row.height`.
+- **Separator:** the default native separator inset is 60 for identity rows
+  and 12 for other templates (Web 0).
+- **Platform default:** without `subtitleLines` or `style.subtitle.lines`, the
+  subtitle shows one line on iOS and Web but two on Android (STYLE_SPEC §6.2).
+- **Text style roles:** `title`, `subtitle`, `tertiary`, `badge`, `value`,
+  `valueSecondary`. The last two refer to value accessories in `trailing`; `badge`
+  refers to badge text. `value`/`valueSecondary` select the first/second value
+  accessory, ignoring intervening controls. A `valuePair` is one accessory, so
+  its style applies to both text runs. They are semantic roles, not extra top-level data fields.
+- **Layout boundary:** reserve visual and accessory slots; text compresses within
+  its own column. Styling cannot move a checkbox/menu into the title column,
+  reorder accessories or convert a horizontal row into the sidebar presentation.
+- **Verification:** Web style ordering and removal have DOM regression coverage
+  for both selector presentations. Rendered geometry remains to be verified.
+
+## walletGroup
+
+![Wallet group: parent wallet and child wallet members inside one composite container](images/row-wallet-group.svg)
+
+- **Use:** one wallet family in the wallet sidebar, as a single composite row.
+- **Required data:** `parent: IdentityRow`, nonempty `children: IdentityRow[]`.
+  Every member must use `presentation: 'walletSidebar'`; `parent.key` must equal
+  the group row's `key`, and member keys must be unique within the group.
+- **Default appearance:** the group border is drawn beneath member content.
+  Native groups ignore the row-level `backgroundColor` (legacy): the fill is
+  `style.container.backgroundColor` or the theme `subduedBackground`. Legacy Web
+  still applies `backgroundColor` inline, so use `style.container.backgroundColor`
+  for a cross-platform fill. `style.container` background, border and radius
+  override the group fill, border and radius on every platform.
+- **Drag:** only `draggable: false` excludes a member from starting the group
+  drag; disabled members can start it. The compact allocation is 68 on iOS/Web
+  and `max(68, parent height + 2 × vertical inset)` on Android.
+- **Style surface:** group `style` exposes the shared container appearance and horizontal/vertical padding. Text styles belong to
+  `parent.style` or the individual `children[i].style`; there is no inherited
+  group `title`/`value` text style. Measured group height is the sum of member
+  heights, 12-unit member gaps and twice the vertical inset. The default inset
+  is 1 unit (the group border) when the parent member carries `height`, else 0;
+  `style.verticalPadding` / `horizontalPadding` replace it rather than adding
+  to it, and bind uses the same value as measurement on every platform.
+  iOS/Android ignore the group's own `row.height` (legacy; `style.container.height`
+  still wins); Web honors it.
+- **Member lifecycle:** each member uses an independent Identity renderer, reused
+  by member key. Removed members release their images/actions immediately.
+  Press and accessory events use the member key; group dragging remains atomic.
+  Optional trailing controls require sufficient caller-supplied member height.
+- **Layout boundary:** preserve parent-first member order and wallet member
+  structure. Local padding cannot change ownership, member count or drag identity.
+  Group `lineGap` does not override the text spacing inside member rows.
+- **Common-capability boundary:** this is not a generic section and does not
+  control header/footer placement. General grouped cards use `groupId` and
+  `groupPosition`; do not conflate those with this composite template.
+
+## rail
+
+![Rail: compact visual, title, optional badge and status](images/row-rail.svg)
+
+- **Use:** a compact navigation or status item, including horizontal rails.
+- **Required data:** `visual`, `title`; optional `badge`, `status` and `draggable`.
+  Status is one of `none`, `online`, `warning`, `error`.
+- **Text style roles:** `title`, `badge`, `status` where rendered. Status can be a
+  platform-specific indicator rather than a text label; accepting a text style
+  does not prove that path has a visible effect.
+- **Layout boundary:** retain the compact visual/title/accessory structure.
+  Row styling cannot enable horizontal scrolling or reorder for the whole list;
+  orientation and reorder orchestration belong to the container.
+- **Current divergence:** default height is 40 on iOS/Web and 28 on Android.
+  This catalog does not change those defaults.
+
+## activity
+
+![Activity: leading visual and description, trailing amounts, optional actions within the row](images/row-activity.svg)
+
+- **Use:** a transaction/activity record with amounts and optional commands.
+- **Required data:** `leading`, `title`; optional `secondaryLeading`,
+  `description`, `status`, `primaryAmount`, `secondaryAmount`, `footerActions`.
+  At most three footer actions are accepted, each with a unique key.
+- **Text style roles:** `title`, `description`, `status`, `primaryAmount`,
+  `secondaryAmount`. `footerActions` do not gain a freeform style surface.
+- **Layout boundary:** amounts remain in the amount column, description stays
+  in its text region, actions stay in the row's action area. Adding actions is a
+  model/height choice, not a typography trick.
+- **Common-capability boundary:** `footerActions` are inside this activity row.
+  The list footer is independently configured through the container.
+
+## message
+
+![Message: title and timestamp over body text, with optional leading visual and thumbnail](images/row-message.svg)
+
+- **Use:** a notification or message preview.
+- **Required data:** `title`, `body`, `time`; optional `leading`, `thumbnail`,
+  `unread`. `bodyLines` is the legacy fallback for one, two or three body lines.
+- **Text style roles:** `title`, `body`, `time`. `style.body.lines` accepts one, two or three and takes precedence over `bodyLines`.
+- **Layout boundary:** time and thumbnail keep their allocated regions; body
+  text wraps/truncates within the message area. Styling cannot displace the
+  timestamp, grow over the next row, or turn the preview into unbounded content.
+- **Current divergence:** leading-image size and body typography differ across
+  platforms. Larger line boxes need explicit height and visual verification.
+
+## dataRow
+
+![Data row: optional index and visual, stable columns with primary and secondary text, optional checkbox](images/row-data.svg)
+
+- **Use:** compare values in a linear list or table.
+- **Required data:** `columns` with two to four entries. Each column has `key`,
+  `text`, optional secondary text, `weight` (1/2/3), alignment and tones.
+  Optional row fields include `leading`, `index`, badges, checkbox and favorite state.
+- **Text style roles:** `columns` styles primary column text; `columnSecondary`
+  styles secondary column text; `index` styles the ordinal. These are collective
+  semantic roles, not arbitrary per-native-label selectors.
+- **Layout boundary:** column order/count/weights are data, shared table column
+  alignment is layout. Text styles cannot change those or move favorite/checkbox
+  controls into a data column. Default heights (legacy, per platform): linear
+  56, or 60 with secondary text (Android 64); table 60 with secondary text,
+  otherwise 48 on iOS/Web and 52 on Android (STYLE_SPEC §6.1).
+- **Linear layout per platform (legacy defaults):**
+  - *iOS and Android, unstyled:* one label per column holding the primary text,
+    up to two inline badge runs and the secondary text on a second line.
+    `secondaryLeadingText` is not rendered. On Android, `disabled`/`caution`
+    tones render as primary text (legacy tone mapping).
+  - *iOS, styled:* the same single label. `columns`/`columnSecondary` apply
+    font, weight, color, line height and alignment to their text runs/lines;
+    `lines`, `truncate`, `verticalAlignment` and `offsetY` act on the whole
+    label. Badge pills keep the legacy two-space padding inside their
+    background; `titleBadgeGap` adds an exact, unfilled gap between the title
+    and the first pill. Unstyled rows are unchanged.
+  - *Android, text-styled:* only `style.columns`, `columnSecondary`, `lineGap`
+    or `titleBadgeGap` switch a row off the legacy layout (single label per
+    column in linear; fixed 40dp column blocks with 20/16dp lines in table).
+    The separate column view is then used (primary line with pill badges,
+    secondary line with secondary leading text), so each role styles its own
+    view. Container, padding, image, `leadingGap` and `index` styles keep the
+    legacy text layout.
+  - *Web:* `secondaryLeadingText` precedes the primary text on the same line,
+    badges follow it, and secondary text is directly below.
+  - Table layout uses the column view on every platform (Android unstyled:
+    the fixed legacy column geometry above).
+- **Style isolation:** primary and secondary text use independent style targets in
+  linear and table layouts on all three platforms. Column badges keep their own typography.
+
+## market
+
+![Market: asset visual and title/subtitle/badges, followed by price and a bounded change block](images/row-market.svg)
+
+- **Use:** a recycled market quote row with already formatted/localized values.
+- **Required data:** `variant: token | stock | perp`, `leading`, `title`, `price`,
+  `change` (text and tone). Optional subtitle segments/prefix, badges, leading
+  action and press/press-in/long-press action keys remain data.
+- **Text style roles:** `title`, `subtitle`, `price`, `change`.
+- **Additional local parameters:** `titleBadgeLayout: 'inline'`,
+  `contentTrailingGap`, `subtitleTrailingPadding`, `changeWidth`, `changeHeight`,
+  `changeCornerRadius`, plus box/image metrics. Badge models and subtitle prefix
+  have their own existing style fields; they do not create arbitrary child views.
+  A `subscript` segment is `ceil(0.6 × field fontSize)` on a `fontSize` line box
+  (legacy), including under an explicit `fontSize`. Web uses a `fontSize` line box;
+  iOS/Android keep the field line height, as their legacy renderers did.
+- **Layout boundary:** price and change keep their regions; the localized name
+  compresses independently from volume where supported. Styling does not change
+  token/stock/perp structure or affect sections, index navigation or pagination.
+
+## mediaTile
+
+![Media tile: image and optional badge/network/close overlays above title and subtitle](images/row-media-tile.svg)
+
+- **Use:** a gallery tile or browser preview.
+- **Required data:** `variant: gallery | browserPreview`, `title`. Optional
+  image/image-state, subtitle, badge, network image and close-action key.
+- **Text style roles:** `title`, `subtitle`, `badge`.
+- **Layout boundary:** media stays above caption metadata; network/close/badge
+  overlays keep their template anchors. A text style cannot change the grid
+  column count, tile span or move the caption over the image.
+- **Common-capability boundary:** grid columns and list scrolling belong to
+  `snapshot.layout`, not to `MediaTileRowStyle`. Primary-image overrides are
+  supported on all three platforms; network/close overlays retain their anchors.
+
+## metricCard
+
+![Metric card: standard label and large value; named composite variant with bounded metric cells](images/row-metric-card.svg)
+
+- **Use:** a single KPI or a fixed portfolio activity/performance summary.
+- **Required data:** `title`, `value`; optional subtitle, trend/tone, visual, badge,
+  metrics and progress. The model still requires `value` for composite variants.
+- **Variants:** default/`standard` shows a large value; `activity` and `performance`
+  use the fixed composite arrangement. `metrics`, when supplied, contains two to
+  five entries; each entry has key, label and value. Progress is bounded to 0…1.
+- **Text style roles:** `title` is the small label on the standard card; `value`
+  is the large number; `subtitle` and `trend` have their own roles. Do not map them
+  by shared UIKit/Android view names, which are different from these meanings.
+  In `activity`/`performance`, only `title` maps to the composite heading. The
+  other standard-card roles do not address `metrics[].label` or `metrics[].value`.
+- **Layout boundary:** styles cannot change the number/order of metric cells or
+  turn the standard card into a composite card. Composite subfield mapping needs
+  explicit coverage; do not assume `style.value` reaches every nested metric.
+- **Style boundary:** nested metric fields have no declared local text-style roles on any platform.
+  The standard card example alone cannot validate composite heading styling.
+
+## sectionHeader
+
+![Section header: title/subtitle and optional summary value, help or selection control](images/row-section-header.svg)
+
+- **Use:** a structural section heading or list summary, independent of the
+  business templates in the section.
+- **Required data:** `sectionKey`, `title`; optional subtitle, value, title/value
+  icons/actions, checkbox, `sticky`, `indexTitle`. Variants: default, `summary`,
+  `gallery`, `history`; `presentation: 'networkSelector'` is also available.
+- **Text style roles:** `title`, `subtitle`, `value`.
+- **Layout boundary:** preserve heading/value/control regions. `summary` does
+  not accept a checkbox and is not sticky. Pinning and index-entry generation are
+  container behavior, not a text-style property.
+- **Common-capability boundary:** `sectionHeader` is the current serialized
+  heading descriptor, not a header feature attached to `identity` or another
+  content template. `indexTitle` supplies the shared indexed bar's label.
+- **Pinned rendering:** the container reuses the ordinary header renderer on all
+  platforms, including headers with a value or checkbox. Summary is non-sticky.
+
+## action
+
+![Action: optional icon, command title, optional trailing value/accessories or checkbox](images/row-action.svg)
+
+- **Use:** a row-level command, including content used in a fixed footer.
+- **Required data:** `title`, `actionKey`; optional tone (`primary`, `neutral`,
+  `danger`), icon, checkbox and trailing accessories. `accountSelector` is a
+  named presentation variant.
+- **Text style roles:** `title`, `value` (a trailing value accessory).
+- **Layout boundary:** preserve icon/text/control ordering and action hit areas.
+  Styling cannot create a new command or change action routing.
+- **Common-capability boundary:** the same action descriptor can live in
+  `rows`, `fixedFooter` or `emptyState`. The container decides placement and
+  visibility; the action template only renders its content.
+
+## system
+
+![System variants: loading indicator, retry message and action, warning, no-match/end text and explicit spacer](images/row-system.svg)
+
+- **Use:** bounded status content rather than a business record.
+- **Variants and required data:** `loading` has optional message and
+  skeleton/spinner choice; `retry` requires message/action key with optional
+  action text; `warning` requires title/message; `noMatch` requires message;
+  `end` has optional message; `spacer` requires explicit height.
+- **Text style roles:** `title` for a visible title, `message` for status copy,
+  `actionText` for the native retry button text. Web (legacy) draws no retry
+  button for any presentation: a Web retry row is message-only and the row
+  press (click, Enter or Space) emits `actionKey`, so `actionText` and
+  `style.actionText` have no Web target (native only). On Android the Market
+  retry/noMatch message and the retry `actionText` ellipsize at the end by
+  default; an explicit `lines` or `truncate` (including `clip`) wins. A spacer has no text slot; skeleton/spinner styling
+  does not become arbitrary drawing through these text roles.
+- **Height:** without `row.height`/`style.container.height`, Web lays out a
+  warning at its rendered height (padding, both borders, wrapped text), as the
+  legacy engine did; native measures its text.
+- **Layout boundary:** keep each variant's indicator/text/action structure and
+  bounded height. Styling cannot convert loading into retry, turn a spacer into
+  content, or hide adjacent rows.
+- **Common-capability boundary:** a system row can be regular content,
+  `emptyState` or `fixedFooter`. Refresh/pagination state remains on the list;
+  a loading row alone does not enable either capability.
+
+## Composition example: shared sections, footer and indexed bar
+
+This uses existing public fields. Both content templates share one section;
+neither implements its own header, footer, scrolling or indexed bar. There is no
+new header prop in this example: the heading is a structural row.
+
+```ts
+import type { NativeListSnapshot } from '@onekeyfe/react-native-native-list';
+
+const snapshot: NativeListSnapshot = {
+  schemaVersion: 1,
+  generation: 1,
+  layout: { kind: 'sectioned', stickyHeaders: true },
+  capabilities: { sectionIndex: { enabled: true } },
+  rows: [
+    {
+      type: 'sectionHeader', key: 'section-a', sectionKey: 'a',
+      title: 'Assets', indexTitle: 'A',
+    },
+    {
+      type: 'identity', key: 'asset-btc', sectionKey: 'a',
+      leading: { kind: 'icon', name: 'StarOutline' }, title: 'Bitcoin',
+      style: { title: { token: '$bodyMd' } },
+    },
+    {
+      type: 'market', key: 'quote-eth', sectionKey: 'a', variant: 'token',
+      leading: { kind: 'token', fallbackText: 'ETH' }, title: 'Ethereum',
+      price: '$2,400', change: { text: '+2.4%', tone: 'positive' },
+    },
+  ],
+  fixedFooter: {
+    type: 'action', key: 'continue', title: 'Continue', actionKey: 'continue',
+  },
+};
+```
+
+`listRef.current?.scrollToKey({ key: 'quote-eth', animated: true })` addresses the
+stable row key through the shared list API. Changing the quote's content template
+while preserving a valid key/section does not introduce a new scroll API.
+
+For completion criteria and the source audit, return to
+[STYLE_SPEC §6–§9](STYLE_SPEC.md#65-consolidated-gap-audit).