[cixzhang]

User need

Settings screens, bulleted and numbered lists, and divided lists sit inside cards, sheets, and scroll views on iOS. There is no Swift List that matches core: SwiftUI.List is a scrolling table with its own row styles that can't sit inside a card. Each app spaces, divides, and numbers rows by hand, and people get lists that differ from the web and from each other.

Problem and solution fit

• List view. Core's list: a stack of rows with core's gap, or a divider between rows, that tells each ListItem its density, marker, dividers, and edge, in any container.
• Numbering. A decimal list numbers its ListItem rows in order from start, rows from ForEach included; a nested list counts apart.
• Header. Content above the rows, paired as the label of the rows' container, as core's aria-labelledby names the list, and read before the rows.
• Wire lists. A List node sent by a logic core draws its children as rows and its header above them (AST-082 FR19).
• Edges. All four of core's edges with core's meaning. No Swift container publishes its inset yet, so the missing inset resolves to zero as component:List FR6 defines: outset and bleed rows sit as padded rows do, and bleed rows are square.

Current specification

• spec:AST-082 FR3, FR4, FR7, FR19.
• spec:AST-093 FR1–FR5.
• Swift library records: component API (A2–A4, A7), slots (S3), accessibility (X5).
• component:swift/ListItem, which draws each row; swipe actions stay web-only for now (component:swift/Item DEC-1).
• New: component:swift/List at docs/specs/components/List/List.swift.spec.md (draft, platform_of: component:List), beside core's List record; its views in Sources/Astryx/List/ (AST-093 FR1).

Public delta and caller burden

import Astryx

Astryx.List(hasDividers: true) {
  ListItem("Wi-Fi", description: "Home")
  ListItem("Bluetooth", description: "On")
}
Astryx.List(listStyle: .decimal, start: 3) {
  ForEach(steps) { ListItem($0.title) }
} header: {
  Heading("Steps", level: .v3)
}

• New: List (Astryx) and generated ListProps, ListDensity, ListEdge, ListListStyle (AstryxNative).
• In a file that imports both modules, List names Astryx's list; SwiftUI.List stays available by its full name.
• edgeCompensation, which core deprecates, is carried by ListProps and the wire and resolves as core's List FR1 does (a defined edge wins; inline alone means outset); the labeled initializer omits it (FR6).
• Generator fix: a …Style prop whose type is a closed set of words, like listStyle, is a semantic choice and stays in the core contract; style objects and class names stay on the web. No other generated file changes.

Design and alternatives

• SwiftUI.List does not fit: it scrolls and reuses rows with its own styles, while core's list sits in any container (AST-093 FR2).
• Rows are reached through the public Group(subviews:) on iOS 18 and macOS 15 and later. iOS 17 and macOS 14, which the package still supports, have no public API for a container's children, so only there the list uses SwiftUI's _VariadicView, which Group(subviews:) replaced (FR5). Both lay rows out the same way, a test covers the iOS 17 path, and the fallback goes away when the package's minimum moves to iOS 18.
• Base props (id, isHidden) go through the shared base-prop mapping, as every other view's do.
• Rows learn their numbers from what they report to the list, since per-row environment values do not reach views a container takes apart.

Evidence

Capture set: iPhone 16 simulator, iOS 18.5, Xcode 16.4, built before the rebase onto the new spec layout and ListItem's number alignment; the wire list, hidden list, and number alignment are covered by tests. Each capture shows spaced and divided lists, a list numbered from 3, rows from ForEach, a circle-marker list, selected and disabled rows between dividers, nested lists counting apart, a header, and a flush list inside a padded container, in light and dark at the default and largest text sizes.

Light	Dark	Light, largest text	Light, largest text, end	Dark, largest text	Dark, largest text, end

Not measured: a pressed row, which a capture cannot press, and bleed rows' square corners in light, dark, and the largest text size, which the captures predate; a ListItem render test covers the bleed corner. ListItem has no highlighted state in its contract.

check:knowledge passes with the record at its new path.

Implementation choices under current rules

• The header names the list. Core names the list from its header (aria-labelledby). The Swift list pairs the header as the label of the container that holds the rows (accessibilityLabeledPair), and the header is still read first (List AR1). The name VoiceOver announces is not measured yet: tests check the pairing the view sets, and the rendered tree waits on an app-hosted test (AR2). Core's list role is recorded as an AST-082 FR3 implementation gap (AR1): SwiftUI has no public API for a container's accessibility role, and UIKit's and AppKit's list roles belong to platform views, so offering them would mean hosting the rows in a UIKit or AppKit view.

Open-work search

Searched current records and open pull requests before creating component:swift/List, by canonical id (component:swift/List, component:List), paths (packages/native/apple/Sources/Astryx/List/, packages/native/src/components/List.ts), symbols (List, ListProps, ListRows, listStyle), and terms (native, swift, list). No other record or open pull request owns this platform component.

Scope

• One capability is added.
• Unrelated fixes, cleanup, and policy changes were removed or split.
• Consumer docs, focused tests, and migration evidence ship with the feature.
• Public text and artifacts contain no internal Meta context.

Writing rubric results

• R1 narration: none; the record states what the view does.
• R2 research: none.
• R3 evidence: bases name specs, core's List, SwiftUI availability, and tests; no pull request or commit.
• R4 rejected alternatives: one line on SwiftUI.List, which AST-093 FR2 requires the spec to name.
• R5 change references: none.
• R6 open questions: none; core's list role is recorded as an implementation gap (AR1).

Testing

• vitest run packages/native/src/contract: the List contract (all four edges and edgeCompensation, listStyle in the core, content header; xstyle on the web) passes; the committed Swift binding matches the contracts.
• swiftc -typecheck of AstryxNative, Astryx, and the tests passes. An immediate-mode render checks numbering from 3, rows from ForEach, nested lists counting apart, the gap and the single divider between rows, the iOS 17 path, flush rows, the header gap, which lists pair a header with their rows, read from the header's type (the pairing modifiers and the announced name are not measured), outset and bleed sitting as padded with square bleed rows, edgeCompensation resolving as core's, rows growing at the largest text size, a hidden list taking no space, and a wire list drawing its rows and header.
• The Swift tests run in CI on macOS and on the iOS Simulator.
• Screenshot states for the per-component screenshot target, once it lands: spaced, divided, each marker, numbered from 3, nested, header, padded and flush, light and dark, and the largest text size.

Every changed file is under packages/native/, plus the new record in docs/specs/components/List/.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Nov 2, 2026 6:00am UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
❓ Needs maintainer input (for maintainers only)	Nov 2, 2026, 6:12 AM UTC

[github-actions]

PR Analysis Report

🔎 Preview · a1c8efb

Storybook · Sandbox · built from this PR's head

Package size: no published package changed; no new dependencies.

API changes: none in this pull request

Committed API report behind this build: core 1 row; run pnpm api:report.

Not run on this PR: add ci:run-visual, ci:run-a11y or ci:run-rtl to run them.

---

_{Generated by PR Enrichment workflow | View full report}

[astracat-bot]

This adds a Swift List (with the ListItem and Item it draws), and approval waits on an engineering owner deciding the new draft Swift records: component:swift/List FR1-FR6, including the padded/flush-only edge left open in its OQ1, and the carried component:swift/ListItem FR1-FR5 and component:swift/Item FR1-FR6, including swipe actions staying web-only, which no current spec states yet. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately from that decision, these need changes:

• A decimal list whose start changes while its rows keep their identity keeps its old numbers, because numbers are assigned only when the row preference changes (List.swift lines 77-78).
• A ListItem placed in another row's start or end content takes the outer list's density, marker, corners and inset, which draft ListItem FR4 forbids, because Item clears only its own treatment for slots (ListItem.swift line 25).
• Int(_:) traps on labelLines: .infinity or an out-of-range start (Item.swift line 327, List.swift line 113), so check isFinite and clamp first.
• AST-093 FR5 asks for a two-theme render and accessibility assertions for List and ListItem, which their tests do not have yet.

[Automated review]

[astracat-bot]

Numbers are assigned only when ListRowsKey changes, and the rows' @State UUIDs stay the same when only start changes, so a decimal list re-rendered with a new start keeps its old numbers. Keeping the row order in ListNumbers and adding start when a row reads its number (or reassigning in .onChange(of: firstNumber)) fixes it; a test that re-renders with a new start would hold it.

[astracat-bot]

Item clears only astryxItemListTreatment for slot content, but this row rebuilds its treatment from astryxListContext, so a ListItem in another row's start or end content takes the outer list's density, marker, corners and inset, which draft FR4 rules out. Clearing astryxListContext and astryxListNumbers on slot content, plus an FR4 test, would cover it.

[astracat-bot]

Int(value) traps when value is infinite or above Int.max, so labelLines: .infinity crashes the app; the same applies to Int($0) for start in List.swift. Checking isFinite and clamping first keeps the fallback the records describe.

[astracat-bot]

This adds a Swift List (with the ListItem and Item it draws), and approval waits on an engineering owner deciding the three new draft Swift records: component:swift/List FR1-FR6, including the padded/flush-only edge left open in its OQ1, component:swift/ListItem FR1-FR5, and component:swift/Item FR1-FR6, including swipe actions staying web-only, which no current spec states yet. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately from that decision, these need changes:

• List.ts declares children without a sameMeaning, so the generated ListNode cannot carry the list's rows (AST-082 FR19).
• A decimal list whose start changes while its rows keep their identity keeps its old numbers (List.swift lines 77-78).
• The fixed 16-point number column lets numbers draw over their labels at accessibility text sizes (ListItem.swift line 141); scaling it with the text, as core's 1rem column does, avoids that.
• Int(_:) traps on labelLines: .infinity or an out-of-range start (Item.swift line 327, List.swift line 113).
• List still lacks the two-theme render and accessibility assertions AST-093 FR5 asks for.
• The change carries #8321 and #8370 and so exceeds 2,000 authored lines; landing those first leaves this pull request as the List alone.

[Automated review]

[astracat-bot]

children has no sameMeaning here, so coreNameProblem reports that it "already means something else in web" and files it web-only; the generated ListNode then carries header but no rows, against AST-082 FR19 ("A content slot (FR4) carries child nodes"). Card, HStack, VStack, Text and Heading declare sameMeaning: {children: "the component's content, as on the web"}; adding it, regenerating, and asserting list.core.children in the List contract test fixes it.

[astracat-bot]

Numbers are assigned only when ListRowsKey changes, and the rows' @State UUIDs stay the same when only start changes, so a decimal list re-rendered with a new start keeps its old numbers. Keeping the row order in ListNumbers and adding start when a row reads its number (or reassigning in .onChange(of: firstNumber)) fixes it; a test that re-renders with a new start would hold it.

[astracat-bot]

The number grows with Dynamic Type (fontSize times textScale, 3.1 at the largest size) but this frame stays 16 points, and the label starts 8 points later. In the PR's own largest-text capture "3." needs about 30 points, so on this head it paints over the label's first letter. Scaling the column with the text (space.s4 * astryx.textScale, as core's 1rem column grows) keeps one text edge and clears the label; a largest-text decimal render would hold it.

[astracat-bot]

Int(value) traps when value is infinite or above Int.max, so labelLines: .infinity stops the app; Int($0) for start in List.swift has the same problem. Checking isFinite and clamping first keeps the fallback the records describe.

[astracat-bot]

This adds a Swift List (with the ListItem and Item it draws), and approval waits on an engineering owner deciding the three new draft Swift records: component:swift/List FR1-FR6, including the padded/flush-only edge left open in its OQ1, component:swift/ListItem FR1-FR5, and component:swift/Item FR1-FR6, including swipe actions staying web-only, which no current spec states yet. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. The fixes asked for on the earlier heads hold here; separately from the spec decision, these still need changes:

• The Swift list gives VoiceOver no name, while core names a list by its header (aria-labelledby in List.tsx); name the rows' container from the header and assert it, or record in List AR1 how reading the header first carries that name on Apple platforms (List.swift lines 88-90).
• The change carries #8321 and #8370 and so exceeds 2,000 authored lines, and no capture attached here shows their Item states (selected, highlighted, disabled, pressed); landing those first leaves this pull request as the 591-line List change.

[Automated review]

[astracat-bot]

This container has no accessible name, while core names a list by its header (aria-labelledby in List.tsx; List.doc.mjs: "Provide a header to label the list and give context to screen readers"), which AST-082 FR3 keeps in the core contract. Giving the rows' container the header as its name, with a ListTests.swift assertion, would cover it; otherwise List AR1 should say how reading the header first carries that name on Apple platforms.

[astracat-bot]

This adds a Swift List (with the ListItem and Item it draws), and approval waits on an engineering owner deciding the three new draft Swift records, whose requirements no current spec states yet: component:swift/List FR1-FR6 and AR1 (including the padded/flush-only edge left open in its OQ1 and the header read first in place of a list name and role), component:swift/ListItem FR1-FR5, and component:swift/Item FR1-FR6 (including swipe actions staying web-only). An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately from that decision, these need changes:

• The list divider is fixed at 1 point (List.swift line 163), while AST-093 FR4 asks for theme values and core draws it at the theme's border-width; reading tokens.size.borderWidth, as Card does, fixes it.
• AST-093 FR1 gives each native component its own folder named for the core component, so ListItem.swift and ListItem.spec.md belong in Sources/Astryx/ListItem/ unless that rule is amended.
• The change carries #8321 and #8370 and so exceeds 2,000 authored lines, and its captures show no circle marker or Item states; landing those first leaves this pull request as the 593-line List change.

[Automated review]

[astracat-bot]

This divider is always 1 point, while core draws it at the theme's --border-width and AST-093 FR4 asks for every such value to come from the theme. Drawing it at astryx.tokens.size.borderWidth (as Card.swift reads border-width) keeps an app theme with 2-pixel borders the same on the web and on iPhone; FR1 and the record's theme values would name it too.

[astracat-bot]

AST-093 FR1 gives each native component its own folder named as the core component (Sources/Astryx/<Name>/<Name>.spec.md), which for ListItem is Sources/Astryx/ListItem/. Moving this record and ListItem.swift there, with the Package.swift exclude, follows it, unless an engineering owner amends FR1 for components core keeps in another component's folder.

[astracat-bot]

This measure runs on every row, while draft ListItem PR1 says only rows in a list with markers measure their words, and only a center-aligned marker row reads wordsHeight. Applying it when listTreatment?.markerOnFirstLine == true, or rewording PR1, would make them agree.

[astracat-bot]

This adds a Swift List (with the ListItem and Item rows it draws), and approval waits on an engineering owner deciding the three new draft Swift records, whose requirements no current spec states yet: component:swift/List FR1-FR6 and AR1 (including the padded/flush-only edge left open in its OQ1 and the header read first in place of a list name and role), component:swift/ListItem FR1-FR5, and component:swift/Item FR1-FR6 (including swipe actions staying web-only). An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately from that decision, these need changes:

• AST-093 FR1 gives each native component its own folder named for the core component, so ListItem.swift and ListItem.spec.md belong in Sources/Astryx/ListItem/ unless that rule is amended.
• The change carries #8321 and #8370 and so exceeds 2,000 authored lines; landing those first leaves this pull request as the 607-line List change.
• AST-093 FR5 asks for captures of every state, and none attached here shows the circle marker or the rows' selected, highlighted, disabled or pressed states.

[Automated review]

[astracat-bot]

This adds a Swift List (with the ListItem and Item rows it draws), and approval waits on an engineering owner deciding the three new draft Swift records, whose requirements no current spec states yet: component:swift/List FR1-FR6 and AR1 (including the padded/flush-only edge left open in its OQ1 and the header read first in place of a list name and role), component:swift/ListItem FR1-FR5, and component:swift/Item FR1-FR6 (including swipe actions staying web-only). An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately from that decision, these need changes:

• AstryxNodeView draws a wire Item or ListItem from its props alone, so the nodes in startContent, endContent and marker are dropped, while AST-082 FR19 says a content slot carries child nodes; passing them through AstryxNodeList, as Card does, fixes it.
• AST-093 FR1 gives each native component its own folder named for the core component, so ListItem.swift and ListItem.spec.md belong in Sources/Astryx/ListItem/ unless that rule is amended.
• The change carries #8321 and #8370 and so exceeds 2,000 authored lines; landing those first leaves this pull request as the 608-line List change.
• The List doc example's Heading("Steps", level: 3) does not compile against the generated HeadingLevel; level: .v3 does.

[Automated review]

[astracat-bot]

ItemNode.Props decodes marker, startContent and endContent as [AstryxNode], but this call passes only the props, so a logic core's icon or chevron in a row's slots is neither drawn nor shown as unsupported, against AST-082 FR19 ("A content slot (FR4) carries child nodes"). Passing each slot as AstryxNodeList(nodes: item.props.startContent ?? [], send: send), as Card does with its children, and the same for .listItem on the next line, keeps the slot content.

[astracat-bot]

AST-093 FR1 gives each native component its own folder named as the core component, with the spec at Sources/Astryx/<Name>/<Name>.spec.md where <Name> is the core component's name, so this record and ListItem.swift belong in Sources/Astryx/ListItem/ (with the Package.swift exclude), unless an engineering owner amends FR1.

[astracat-bot]

Heading takes the generated HeadingLevel enum, which has no integer-literal conformance, so this example does not compile; Heading("Steps", level: .v3) does.

[astracat-bot]

Approval of this Swift List waits on an engineering owner's decision on the three new draft records (component:swift/List, component:swift/ListItem and component:swift/Item), whose requirements no current spec states yet: the padded/flush-only edge, the header read in place of a list name and role, the fixed number column, the whole-row link and swipe actions staying web-only. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner; the earlier approval named an older head. Separately from that decision, these need changes:

• AstryxNodeView draws a wire ListItem from its props alone and drops the child nodes in its startContent and endContent slots, which AST-082 FR19 says a content slot carries; the Item case already passes them.
• Item and List repeat astryxBase from Base/BaseProps.swift for isHidden and id; calling it keeps one path for base props.
• AST-093 FR1 puts a component's views in Sources/Astryx/<Name>/, so ListItem.swift belongs in Sources/Astryx/ListItem/ unless that rule is amended.
• At 2,310 authored lines the change carries #8321 and #8370; landing those first leaves the List commit alone, and tests for a hidden List or ListItem, id mapping and a wire ListItem slot, plus level: .v3 in the doc example, close the rest.

[Automated review]

[astracat-bot]

ListItemNode.Props decodes startContent and endContent (Generated/ListItem.swift:34-35), but this case draws from props alone, so a wire row's icon or chevron is neither drawn nor marked unsupported (AST-082 FR19: "A content slot (FR4) carries child nodes"). Passing both through AstryxNodeList, as the Item case above does, and a wire test with a slot child would close it.

[astracat-bot]

This repeats astryxIdentifier(_:) / astryxBase(_:) in Base/BaseProps.swift:7-20, which Button, Card, Heading and Text call; ListIdentifier in List/List.swift:176-186 is the same copy. Ending each body with .astryxBase(props.base) keeps one path for base props.

[astracat-bot]

Every row measures and stores wordsHeight, while draft ListItem PR1 says only rows in a list with markers measure, and only a center-aligned marker row reads it (:192). Measuring only when listTreatment?.markerOnFirstLine == true, or rewording PR1, makes them agree.

[astracat-bot]

Heading's labeled initializer takes the generated HeadingLevel, an Int-backed enum with no integer-literal conformance, so level: 3 does not compile; level: .v3 does. The description's usage block repeats it.

[astracat-bot]

AST-093 FR1 puts a component's views in Sources/Astryx/<Name>/, where <Name> is the core component's name, so this view belongs in Sources/Astryx/ListItem/ (with the README line), unless FR1 is amended.

[astracat-bot]

List also takes its generated ListProps (List/List.swift), so it belongs in this line too.

[astracat-bot]

This adds a Swift List that spaces, divides and numbers ListItem rows like core's list, and approval waits on an engineering owner's decision on the new draft component:swift/List record. Two of its rules differ from spec:AST-082 FR3, which keeps a component's props and accessibility semantics the same on every platform: edge offers only padded and flush, and the header is read first instead of core's list name and role, so an owner either amends that spec (or component:List) or the Swift list conforms. An engineering owner records the decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner.

• List's doc example Heading("Steps", level: 3) does not compile; level: .v3 does.
• packages/native/specs/swift/library/component-api.md line 157 should list List among the views that take their generated props.

[Automated review]

[astracat-bot]

Heading's labeled initializer takes the generated HeadingLevel, an Int-backed enum with no integer-literal conformance, so level: 3 does not compile; level: .v3 does. The pull request description repeats the example.

[astracat-bot]

List also takes its generated ListProps (List/List.swift:59), so it belongs in this line too.

[astracat-bot]

This adds a Swift List that spaces, divides and numbers ListItem rows like core's list, with no code defect found, and approval waits on an engineering owner's decision on the new draft component:swift/List record. Two of its rules differ from spec:AST-082 FR3, which keeps a component's props and accessibility semantics the same on every platform: edge offers only padded and flush, and the header is read first instead of core's list name and role. An owner either amends that spec (or component:List) or asks for the Swift list to conform. An engineering owner records the decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner.

[Automated review]

[astracat-bot]

Approval of this Swift List waits on an engineering owner's decision on the draft component:swift/List record: whether to approve FR1–FR6 and AR1, and how to settle its two departures from spec:AST-082 FR3 (edge offered with only padded and flush, and no list role where core's list sets one), by amending AST-082 or component:List or by conforming the Swift list. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately, the description and the record say VoiceOver names the list by its header, but theHeaderNamesTheList only checks the header's type and nothing shows the announced name, so please describe it as not measured (as AR2 does) or add evidence that shows it.

[Automated review]

[astracat-bot]

"so VoiceOver names the list by it" states a rendered result nothing at this head shows: theHeaderNamesTheList checks only Header.self != EmptyView.self and would still pass without the two accessibilityLabeledPair calls, and AR2 says the rendered tree is not measured. Saying the header is paired as the label of the rows' container, with the announced name not measured, keeps AR1 and the verification row at line 155 within what the tests prove.

[astracat-bot]

This checks the type-level namesRowsFromHeader predicate, not a render or the pairing itself, so the description's "an immediate-mode render checks … the header labelling the rows" overstates it.

[astracat-bot]

Approval waits on an engineering owner's decision on the draft component:swift/List record: whether to approve FR1–FR6 and AR1 as the Swift contract, and how to settle its two departures from spec:AST-082 FR3 (only the padded and flush edges, and no list role), by amending AST-082 or the core List record or by conforming the Swift list. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately, please bring the remaining VoiceOver wording in line with what the tests show:

• The record's End-user impact row and the List doc comment still say VoiceOver names the list by its header, which AR2 reports as not measured.
• The AR1 verification row and the description's Testing line describe a check theHeaderNamesTheList cannot make, since it reads only a static type.

[Automated review]

[astracat-bot]

This row still says VoiceOver names the list by its header, while AR2 reports the announced name as not measured and theHeaderNamesTheList checks only Header.self != EmptyView.self. Saying VoiceOver reads the header before the rows, with the announced list name not measured (AR2), keeps the impact within what the tests show.

[astracat-bot]

theHeaderNamesTheList reads only the static namesRowsFromHeader, so it still passes with both accessibilityLabeledPair calls removed and cannot make "a list with a header that does not pair it with the rows" fail. Either narrow this row to what the test checks (a header is paired only when one is given) or add a check that observes the pairing.

[astracat-bot]

"so VoiceOver names the list by its header" states an outcome AR2 reports as not measured; saying the header becomes the label of the rows' container, as core's aria-labelledby names the list, describes what the view sets.

[astracat-bot]

Approval of this Swift List waits on an engineering owner's decision on the draft component:swift/List record: whether to approve FR1–FR6 and AR1 as the Swift contract, and how to settle its two departures from spec:AST-082 FR3, the edge offered with only padded and flush and the missing list role, by amending AST-082 or component:List or by conforming the Swift list. The VoiceOver wording now matches what the tests show, and no other change is needed. An engineering owner, including the author if they are one, records the decision by commenting /approve-spec <full head SHA> on this pull request, or asks for the record or the code to change first.

[Automated review]

[cixzhang]

/approve-spec de6eac7

[astracat-bot]

The engineering-owner approval settles the Swift List record itself, but two parts of it still conflict with the native-first surfaces spec (spec:AST-082), which this pull request leaves unchanged: edge offers only padded and flush although core's contract has four values (FR3; FR4 allows narrowing only for wider-than-portable types), and the Swift list sets no list role where core sets role="list" (FR3). Please either add an owner-approved AST-082 change that admits both gaps, or offer outset and bleed as component:List FR6 defines them where no container publishes an inset (placed as padded, with square bleed rows) and amend AST-082 for the role alone. The layout, numbering, wire support, generated bindings and tests otherwise check out.

[Automated review]

[astracat-bot]

edge is a closed string set, so AST-082 FR4's projection (for a web type wider than the portable kinds) does not cover narrowing it, and the native core contract then differs from the web's (AST-082 FR3). component:List FR6 already defines outset and bleed where no host inset is published (placed as padded, bleed rows square), so Swift could offer all four values, or AST-082 needs an owner-approved amendment for this gap.

[astracat-bot]

Approval of this Swift List waits on an engineering owner's decision: the draft component:swift/List and component:swift/ListItem records changed after the last /approve-spec, which named an earlier commit, and the list still sets no list role although spec:AST-082 FR3 puts the role in the core contract on every platform. An engineering owner, including the author if they are one, records the decision by commenting /approve-spec <full head SHA>, and settles the role either with an AST-082 amendment in this pull request or by asking for a Swift list that sets it. Separately, two things need fixing:

• The lint check fails on packages/native/src/components/List.ts:25; that edge projection maps each value to itself and can be removed, which also fixes the formatting.
• No capture shows the new bleed rows (square corners) in light, dark and the largest text size; please attach one or list it as not measured.

The outset and bleed values now follow the core List's placement when no container inset is published.

[Automated review]

[astracat-bot]

This line fails the required lint check (Prettier wants it wrapped). It also maps each edge value to itself, and without it the generator still puts edge in the core with the same four values; a projection is meant for a web type wider than the portable kinds (spec:AST-082 FR4). Deleting lines 22-25 fixes both.

[astracat-bot]

spec:AST-082 FR3 puts accessibility semantics, role included, in the core contract "the same on every platform that offers the component", and it has no implementation-gap exception; spec:AST-093 FR1 says AST-082 wins over a native spec. Leaving the role out needs an owner-approved AST-082 amendment in this pull request (FR3, or its Current-state impact), or the Swift list needs to set the role.

[astracat-bot]

Approval of this Swift List waits on an engineering owner's decision: the draft component:swift/List and component:swift/ListItem records have no approval at this head (the last /approve-spec named an earlier commit), and two parts of the Swift list leave the core contract that spec:AST-082 FR3 keeps the same on every platform. An engineering owner, including the author if they are one, records approval by commenting /approve-spec <full head SHA>, and settles both departures either with an AST-082 amendment in this pull request or by asking for a Swift list that conforms:

• The list sets no list role where core sets role="list"; List AR1 calls it an implementation gap, but FR3 has no such exception.
• edgeCompensation is left out of Swift, though Swift can honor it as outset and FR3 lets a prop leave the core only when a platform cannot match it.

The earlier lint failure is fixed, and the bleed corners are now listed as not measured.

[Automated review]

[astracat-bot]

spec:AST-082 FR3 puts accessibility semantics, role included, in the core contract "the same on every platform that offers the component", and it has no implementation-gap exception; spec:AST-093 FR1 says AST-082 wins over a native spec. Leaving the role out needs an owner-approved AST-082 amendment in this pull request (FR3, or its Current-state impact), or a Swift list that sets the role. The rationale here also does not say whether accessibilityRepresentation was tried.

[astracat-bot]

AST-082 FR3 lets a prop leave the core only when a platform cannot match core's defined behavior, and Swift can honor edgeCompensation: 'inline' as it honors edge: .outset. Either the same AST-082 amendment that covers the list role says a deprecated alias stays out of a new platform's contract, or Swift offers edgeCompensation as the alias of outset.

[astracat-bot]

Approval of this Swift List waits on an engineering owner's decision: the draft component:swift/List and component:swift/ListItem records have no approval at this head, and the list still sets no list role although spec:AST-082 FR3 keeps the role in the core contract on every platform. An engineering owner, including the author if they are one, records approval by commenting /approve-spec <full head SHA> on this pull request, and settles the role either with an AST-082 amendment in this pull request or by asking for a Swift list that sets it. That approval also covers the new FR6 rule that the labeled initializer leaves out the deprecated edgeCompensation, which now reaches Swift through ListProps and the wire as core resolves it.

[Automated review]

[astracat-bot]

spec:AST-082 FR3 puts accessibility semantics, role included, in the core contract "the same on every platform that offers the component", with no implementation-gap exception, and spec:AST-093 FR1 says AST-082 wins over a native spec. Leaving the role out needs an owner-approved AST-082 amendment in this pull request (FR3, or its Current-state impact), or a Swift list that sets the role.