Bug: Export to Figma flattens border radius token references from component aliases to primitives

[rbosker]

Bug Description

After exporting tokens to Figma, border radius token references in Figma variables are being flattened from component-level aliases to their underlying primitive values. The token structure in the plugin remains correct, but the Figma variable loses its semantic reference.

Example:

• Expected reference: components.textInput.medium.borderRadius (component-level alias)
• Actual reference after export: radii.1 (primitive token)
  The resolved numeric value may remain correct, but the reference chain is broken — Figma shows the primitive instead of the component alias.

Environment

• Plugin version: 2.11.0
• Sync provider: GitLab (remote tokens)
• Figma file: Component library (~4,900 variables)

Steps to Reproduce

1. Have a Figma file with existing variables exported via Tokens Studio, including border radius tokens that reference component-level aliases (e.g., components.textInput.medium.borderRadius)
2. Export tokens to Figma using "Export to Figma" with all variable types and themes selected
3. Check the Figma Variables panel — border radius references have been flattened to primitive tokens (e.g., radii.1)

Additional Context

• The customer reports this is intermittent — "we have sometimes, that after syncing, various border radius tokens are going from component tokens to primitive tokens"
• This occurs alongside other export issues reported in Bug: Export to Figma reports "No variables were created" — variable values not updating (v2.11.0) #3775 (variable values not updating) and Partial export with "Remove styles and variables without connection" deletes unchecked variable types #3777 (Remove toggle misbehavior)
• The issue is visible in the customer's screen recording at ~5 seconds, in the Figma right panel when clicking the codeInput collection
• Reported by a community member via Slack #bugs on 2026-02-12