Components: Generate Label

[JasonVMo]

Summary

Generate Label with its canonical contract, implementation, tests, stories, platform validation, and explicit package export so form controls have consistent visible and accessible names. The visual design is implementable, but the web-native label association in the staged spec must first be retargeted to a React Native accessibility contract.

Observed. label is entry label in the canonical catalog and has no
implementation in packages/agentic/components. Upstream describes it as: Non-interactive text element that names an associated form control. Two weights (Regular for inline controls, Strong for Field labels), three sizes, an optional required-asterisk trailing slot, and a Disabled visual state that mirrors its associated control.

Goal

Generate the label 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. label is one of the 32 in the gap, enumerated in
the missing-components index.

Inferred. No generated component dependency is missing, but implementation
is gated on the shared spec-retargeting decision for replacing web label
association with a React Native accessibility contract.

Observed current state

Canonical spec and source

Field	Value
Canonical spec	plugins/components/skills/label/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	label in component-map.yaml
Local staged spec	packages/agentic/components/specs/label - SPEC.md, usage.md, interaction.md, accessibility.md, tokens.yaml, blockers.md
Local implementation	None. No src/components/label directory exists

Closest existing FURN or V1 implementation

• No Label component exists in FURN. The nearest reference is packages/components/Text, whose desktop typography variants are Variants.win32.ts and Variants.windows.ts with Variants.ts as the cross-platform default; Variants.ios.ts and Variants.android.ts are mobile-only.

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

• No generated agentic component is required as a direct dependency.

Known blockers

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

Recorded as blocked because the spec requires native HTML label semantics: a real <label> element, a for attribute pointing at the associated control id, and aria-labelledby fallback wiring, none of which exist in React Native for Windows or macOS.

Reassessment.

Still valid as written, but retargetable. The visual contract (weights, sizes, required asterisk, disabled mirroring) is fully implementable. Only the web association mechanism is not. Inferred: the spec needs a React Native association contract - an explicit accessibilityLabelledBy-style prop or a Field-owned pairing - decided in spec-ingestion-and-generation.md before implementation.

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:
  label.types.ts, label.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 and document the React Native control-association contract that replaces for / aria-labelledby.
• Decide whether Disabled is a prop on Label or is inherited from a Field context.

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

• Both weights across all three sizes.
• Required asterisk present and absent.
• Disabled visual state.
• Whatever association mechanism is chosen, asserted through the accessibility tree rather than through internal 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/Label, 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/label 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. Label is a dependency of field, info-label, and the radio-group legend, so its association contract decision propagates to three other tasks.
2. Retargeting the spec away from web semantics is the first real test of the spec-retargeting policy.

Evidence and references

• Upstream spec: plugins/components/skills/label/SKILL.md and
  components-index/SKILL.md
  at x3-design/fluent-design @ d334acf.
• Local staged spec and blocker record: packages/agentic/components/specs/label.
• 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.