Components: Generate Link

Summary

Generate Link with its canonical contract, implementation, tests, stories, platform validation, and explicit package export so inline and standalone navigation are covered. The staged web contract must first be retargeted for React Native navigation, nested text, and the platform limits on underline styling.

Observed. link is entry link in the canonical catalog and has no
implementation in packages/agentic/components. Upstream describes it as: Interactive text element for navigation within or between experiences. Covers the Type set (Functional versus Content with plain or dotted underline), Inline behavior, and an optional trailing icon for a new-tab affordance.

Goal

Generate the link 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. link 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 navigation, inline text,
and unsupported underline controls in React Native.

Observed current state

Canonical spec and source

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

Closest existing FURN or V1 implementation

• packages/components/Link - Link.tsx, useLink.ts, Link.styling.ts, and LinkTokens.ts. LinkTokens.ts is the cross-platform and desktop path; LinkTokens.ios.ts and LinkTokens.android.ts are mobile-only overrides. There is also a legacy/ implementation.

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/primitives/icon - Observed present (primitive).

Known blockers

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

Three blockers were recorded: React Native 0.81 text styling does not expose the underline thickness and offset controls the spec varies by type set and state; href, target="_blank", rel, copied-link affordances, and visited state are web concepts; and inline links must behave as part of a text run, which conflicts with a pressable-container approach.

Reassessment.

Partly valid. The navigation blocker is a spec-retargeting question with a known React Native answer (Linking.openURL). The inline-text-run requirement is addressable with nested Text. The underline thickness and offset gap is a genuine platform limitation. Inferred: implementable once the spec accepts React Native text-decoration limits.

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:
  link.types.ts, link.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 navigation contract: a url prop handled with Linking.openURL, a caller-supplied onPress, or both.
• Record the underline thickness and offset gap as a genuine platform limitation in the component's spec rather than approximating it silently.
• Implement the inline case as a nested Text so it participates in the surrounding text run.

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/link/ implementing the full required file structure.
• SPEC.md and a spec/ companion folder with provenance recording the upstream path,
  SHA, and ingestion date.
• Colocated link.test.tsx, link.types.test.ts, and link.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 type sets, both underline treatments, inline and standalone.
• Trailing icon present and absent, with the icon inaccessible inside a labeled link.
• Press invokes the navigation contract exactly once, and does not fire when disabled.
• Inline rendering inside a paragraph of text, asserted through layout rather than snapshot alone.
• 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/Link, 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/link 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. Visited state has no React Native equivalent and is caller-owned at best; the spec must say so.
2. Hover underline changes on a nested Text behave differently on macOS and Windows Fabric and need on-device checking.

Evidence and references

• Upstream spec: plugins/components/skills/link/SKILL.md and
  components-index/SKILL.md
  at x3-design/fluent-design @ d334acf.
• Local staged spec and blocker record: packages/agentic/components/specs/link.
• 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 packages/agentic/components/src/components/AGENTS.md and packages/agentic/components/specs/link/SPEC.md plus blockers.md, then compare packages/components/Link. Run the component workspace format, lint, build, and test commands before investigating the required link files, colocated tests, stories, and src/index.ts exports. Done means the full contract, platform retargeting, coverage, desktop Storybook validation, readiness evidence, and changeset satisfy the listed acceptance criteria.