Components: Generate Interaction Tag

[JasonVMo]

Summary

Generate Interaction Tag with its canonical contract, implementation, tests, stories, platform validation, and explicit package export so tags can expose primary and dismiss actions. All component dependencies now exist, and the earlier shared-export restriction was a generation-scope artifact rather than a current blocker.

Observed. interaction-tag is entry interaction-tag in the canonical catalog and has no
implementation in packages/agentic/components. Upstream describes it as: Extends Tag with a primary action area and a secondary dismiss action. Supports leading content (icon or Avatar, never both), two styles (Secondary/Primary), two sizes, and two corner shapes (Rounded/Circular).

Goal

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

Inferred. Every local dependency this component needs is already generated, so it is deliverable without new shared infrastructure and contributes directly to the beta catalog.

Observed current state

Canonical spec and source

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

Closest existing FURN or V1 implementation

• The nearest FURN implementation is packages/components/Chip. Use Chip.tsx, Chip.styling.ts, and ChipTokens.ts as the desktop-relevant reference; Chip.ios.tsx, Chip.android.tsx, and Chip.mobile.tsx are mobile-only and must not be treated as the cross-platform baseline.

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/tag - Observed present (component).
• src/components/avatar - Observed present (component).
• src/primitives/icon - Observed present (primitive).

Known blockers

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

Two blockers were recorded: a new component under src/components/interaction-tag must be surfaced from src/index.ts and the generation task forbade editing shared exports; and the spec depends on Avatar and Tag contracts while the package "currently only owns Button/Icon".

Reassessment.

Stale. Both premises are false today. src/index.ts is the normal place to export a new component, and src/components/tag, src/components/avatar, and src/primitives/icon all exist. Inferred: this component is implementable now with no new infrastructure.

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:
  interaction-tag.types.ts, interaction-tag.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.
• Model the two interaction regions (primary action, dismiss) as separate accessible targets rather than one pressable with two handlers.
• Enforce the mutually exclusive leading-content contract (icon or Avatar, never both) at the type level.

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/interaction-tag/ implementing the full required file structure.
• SPEC.md and a spec/ companion folder with provenance recording the upstream path,
  SHA, and ingestion date.
• Colocated interaction-tag.test.tsx, interaction-tag.types.test.ts, and interaction-tag.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 styles, both sizes, and both shapes, table-driven.
• Primary press and dismiss press fire independently and do not fall through to each other.
• Compile-time coverage that icon and Avatar leading content are mutually exclusive.
• Accessible names for both regions; the dismiss control needs an action-oriented label.
• Minimum target size for the dismiss region.
• 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/Interaction Tag, 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/interaction-tag 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. Nested pressables on React Native Windows Fabric can have surprising hit-testing; the two-region model needs on-device verification.
2. Whether dismissal is self-driving or parent-owned must be classified before wiring, per the package's stateful-axis rule.

Evidence and references

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