Components: Generate Select

Summary

Generate Select with its canonical contract, implementation, tests, stories, platform validation, and explicit package export so native single-selection has an intentional React Native API. The local spec is missing, and its browser-native HTML contract must be replaced with a Windows/macOS native-control or composed-control decision.

Observed. select is entry select in the canonical catalog and has no
implementation in packages/agentic/components. Upstream describes it as: Browser-native single-selection form control. Renders a real HTML select element styled with Dropdown's trigger chrome, forwarding Style and Size. Single selection only; open/close and the option list are browser- and OS-controlled. It exists as a distinct component to make native accessibility, native mobile pickers, and form semantics the default choice.

Goal

Generate the select 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 3 (production). Wave 4 - platform or native decision required.

Why it matters

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

Inferred. It cannot be resolved by generation alone. Leaving it undecided keeps the catalog reconciliation permanently incomplete.

Observed current state

Canonical spec and source

Field	Value
Canonical spec	plugins/components/skills/select/SKILL.md with usage.md, web/tokens.yaml, web/accessibility.md, and web/interaction.md, at x3-design/fluent-design @ d334acf
Upstream tier	atom
Upstream catalog key	select in component-map.yaml
Local staged spec	None. No specs/select folder exists; the spec must be ingested first
Local implementation	None. No src/components/select directory exists

Closest existing FURN or V1 implementation

• No native picker for desktop exists in FURN. packages/experimental/Dropdown is a custom React Native implementation, not a platform control, and packages/experimental/NativeDatePicker is the only precedent in the repository for wrapping a platform-owned picker.

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/input - Observed present (component).

Known blockers

Observed. There is no recorded blocker, because there is no local spec folder and therefore no
blockers.md. The absence of an ingested spec is itself the first blocker; see
spec-ingestion-and-generation.md.

Scope

• The first deliverable is a decision, not an implementation. Upstream defines this component by its browser-native rendering, which has no direct React Native analogue on Windows or macOS.
• Options observed to be available: wrap a platform-owned picker per desktop platform as a native component; alias select to dropdown and record the deviation; or decline the component and record the rationale in the catalog reconciliation.
• Whichever is chosen, the rationale must address upstream's stated purpose - native accessibility and native form semantics - because aliasing to Dropdown defeats it.
• Record the decision, its rationale, and its consequences in
  the missing-components index catalog reconciliation, whichever way it
  goes. Declining is an acceptable outcome; leaving it unrecorded is not.

If, and only if, the decision is to implement, the remaining scope is the standard
generation 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:
  select.types.ts, select.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.

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/select/ implementing the full required file structure.
• SPEC.md and a spec/ companion folder with provenance recording the upstream path,
  SHA, and ingestion date.
• Colocated select.test.tsx, select.types.test.ts, and select.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:

• Only meaningful once the decision is made. If a platform control is wrapped: value selection, both Input styles across all three sizes, disabled state, and platform accessibility verified on macOS and on Windows Fabric using the platform's own accessibility tree rather than React Native assertions.
• 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/Select, 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

• The implement, approximate, or decline decision is made and recorded, with its rationale.
• The decision explicitly addresses what upstream says this component exists to provide, so the trade-off being accepted is visible.
• The catalog reconciliation in the missing-components index reflects the outcome.

If the decision is to implement, the standard generation criteria also apply:

• src/components/select 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

• Blocked by spec-ingestion-and-generation.md: the spec must be pulled from the pinned upstream revision before generation can start.
• Not a beta blocker. This task must reach a recorded decision before production, but it does not gate the beta catalog.
• If native work is chosen, blocked by focus-zone.md, which establishes the repository's first React Native Windows Fabric native component and its build, autolinking, and CI path.
• 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. Aliasing to Dropdown silently removes the native-accessibility benefit that is the component's entire justification upstream; it must be an explicit, recorded deviation rather than a convenience.
2. A native picker wrapper is per-platform native work with the same Fabric prerequisites as focus-zone.md.

Evidence and references

• Upstream spec: plugins/components/skills/select/SKILL.md and
  components-index/SKILL.md
  at x3-design/fluent-design @ d334acf.
• 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.

Start with the upstream plugins/components/skills/select/SKILL.md and the local spec-ingestion issue 4252, then compare experimental/Dropdown with experimental/NativeDatePicker. Review the missing-components index in issue 4273 and the package conventions in src/components/AGENTS.md. Done means the implement, approximate, or decline decision and its rationale are recorded in the catalog reconciliation; implementation deliverables apply only if that decision is to implement.