Components: Generate List

[JasonVMo]

Summary

Generate List with its canonical contract, implementation, tests, stories, platform validation, and explicit package export so related rows can be grouped with consistent selection behavior. All generated child dependencies exist, but keyboard navigation remains gated on the shared roving-focus decision.

Observed. list is entry list in the canonical catalog and has no
implementation in packages/agentic/components. Upstream describes it as: Composed vertical-stack container that groups ListItem components into a scannable collection of independent, like items, with optional selection (single via Radio, multiple via Checkbox), trailing actions, and divider separators.

Goal

Generate the list component in
packages/agentic/components/src/components against the
canonical Fluent Flex spec, with the colocated coverage, stories, and platform
validation the package requires, and export it explicitly from
src/index.ts.

Stage

Stage 2 (beta). Wave 1 - local component dependencies already generated.

Why it matters

Observed. The canonical catalog has 50 components and the agentic library has
generated 18. list is one of the 32 in the gap, enumerated in
the missing-components index.

Inferred. Every generated component dependency exists, but keyboard
navigation remains gated on the shared roving-focus decision in the FocusZone
task.

Observed current state

Canonical spec and source

Field	Value
Canonical spec	plugins/components/skills/list/SKILL.md with usage.md, web/tokens.yaml, web/accessibility.md, and web/interaction.md, at x3-design/fluent-design @ d334acf
Upstream tier	molecule
Upstream catalog key	list in component-map.yaml
Local staged spec	packages/agentic/components/specs/list - SPEC.md, usage.md, interaction.md, accessibility.md, tokens.yaml, blockers.md
Local implementation	None. No src/components/list directory exists

Closest existing FURN or V1 implementation

• No List container exists in any FURN catalog. The closest structural precedent is packages/components/Menu/src/MenuList, which composes rows and wraps them in a FocusZone.

Note on platform canon. Where a legacy package has platform-specific files, the
desktop path (.win32, .windows, .macos, or the unsuffixed cross-platform file)
is the compatibility reference. .ios, .android, and .mobile variants are not
treated as the cross-platform canonical implementation.

Local dependencies

• src/components/list-item - Observed present (component).
• src/components/checkbox - Observed present (component).
• src/components/radio - Observed present (component).
• src/components/divider - Observed present (component).

Known blockers

Observed (blockers.md, blocker class A in the index).

Recorded as blocked because "the List spec depends on a ListItem implementation" and "this package currently has List specs only; there is no src/components/list-item implementation to compose against".

Reassessment.

Stale. src/components/list-item exists, with a runtime test, a type test, a story, and snapshots. checkbox, radio, and divider also exist. Inferred: the dependency blocker no longer applies; only the keyboard-navigation model remains open, and it depends on focus-zone.md.

Scope

• Ingest or promote the spec into the component directory in the generated shape
  (SPEC.md plus a spec/ folder), per
  spec-ingestion-and-generation.md.
• Establish the public contract first: variants, slots, native props, accessibility,
  interaction states, and platform behavior.
• Implement the required file structure from
  src/components/AGENTS.md:
  list.types.ts, list.styles.ts, use*.ts, use*Styles.ts, render*.tsx, and
  the assembly module with a displayName.
• Style from Flex tokens first and record genuine token gaps rather than substituting
  unrelated values.
• Export the component, its public types, and the state, style, and render stages
  explicitly from src/index.ts under component-qualified unstable names.
• Decide the selection ownership model: the list owns single or multiple selection and drives the item indicators, while items report presses. This must follow the package's externally driven selection rule for item components.
• Decide whether the list renders its children directly or takes a data array; the upstream contract describes a container over ListItem children.
• Decide whether keyboard navigation is in scope for the first version or deferred to the focus decision.

Out of scope

• Changing the contract of an existing generated component, unless this task explicitly
  calls for it above; raise it as its own item.
• Building shared infrastructure owned by another task: overlay hosting
  (popover), roving focus (focus-zone.md), spec
  ingestion (spec-ingestion-and-generation.md),
  or the coverage contract (component-test-strategy.md).
• Migrating any legacy FURN consumer onto this component.
• Mobile platform support; the applicable upstream companion is web, retargeted to
  React Native for Windows and macOS.

Deliverables

• src/components/list/ implementing the full required file structure.
• SPEC.md and a spec/ companion folder with provenance recording the upstream path,
  SHA, and ingestion date.
• Colocated list.test.tsx, list.types.test.ts, and list.stories.tsx.
• Snapshot coverage where the visual contract is state-dependent, or a recorded
  exemption.
• Explicit exports from src/index.ts, with src/index.test.ts updated.
• A changeset, per the repository's version management rules.
• A recorded readiness level with its supporting evidence.

Required coverage, stories, and platform validation

Runtime and type coverage:

• Selection off, single, and multiple, with the correct indicator rendered per mode.
• Selecting an item updates the list-owned value and does not mutate item state directly.
• Divider separators present and absent.
• Trailing action slots forwarded to items.
• Group accessibility: role, item count, and per-item selected state.
• User style and handler forwarding, and that user styles are applied after component
  styles.
• Compile-time slot acceptance and any mutually exclusive props.

Stories: a typed Meta titled Components/List, an args-driven Default, a
grouped Overview when the contract has several axes, one focused story per variant
axis, and an interactive story for each stateful axis. Self-driving axes expose
default<State> as the control; externally driven selection is owned by the story with
React.useState. Identity-changing axes are not exposed as controls.

Platform validation: the component's stories render and behave correctly on macOS
and on React Native Windows Fabric through apps/storybook,
including hover, pressed, disabled, focus, optional-slot, and constrained-content
scenarios. Add a stable root testID if the component joins the automated smoke set.

Acceptance criteria

• src/components/list exists with the required file structure and a displayName.
• Every variant axis in the component's SPEC.md is implemented, or a deviation is recorded in the spec.
• The component styles from Flex tokens, with any genuine token gap recorded rather than approximated.
• Focus feedback renders through FocusVisual; no outline* props and no React Native Windows native focus visuals are introduced.
• State precedence is explicit: disabled wins over pressed, which wins over hovered.
• Every stateful axis is classified as self-driving or externally driven, and both paths are covered.
• Runtime, type, and story coverage satisfy the package coverage contract.
• The component, its public types, and its pipeline stages are exported explicitly from src/index.ts, and src/index.test.ts covers them.
• The component's stories render on macOS and on React Native Windows Fabric.
• yarn workspace @fluentui-react-native/components format, lint, build, and test pass, and the Storybook bundle succeeds for both desktop platforms.
• A readiness level is recorded with its supporting evidence.
• A changeset is included.

Dependencies and ordering

• Gated by component-test-strategy.md: the component must satisfy the coverage contract on arrival rather than being retrofitted.
• Gated by readiness-model.md: the target readiness level must be stated before the work starts.
• Consumes the Infrastructure workstream (storybook-e2e.md) for automated macOS and Windows Fabric validation; until it lands, platform validation is manual.

Risks and open decisions

1. Long lists raise a virtualization question the upstream spec does not address; decide explicitly whether this is a plain stack or a FlatList.
2. Keyboard navigation and roving focus depend on the outcome of focus-zone.md.

Evidence and references

• Upstream spec: plugins/components/skills/list/SKILL.md and
  components-index/SKILL.md
  at x3-design/fluent-design @ d334acf.
• Local staged spec and blocker record: packages/agentic/components/specs/list.
• Canonical implementations to follow: src/components/button
  for a styled higher-order component and src/primitives/icon
  for a primitive.
• Authoring rules: src/components/AGENTS.md and the
  agentic component authoring skill.
• Workstream context: Components README and
  the missing-components index.

Sources retrieved 2026-08-20.