react-from-figma: remaining gaps

[nathanacurtis]

Problem

The recent wave of component-transform capability — slot composition, nested instances, icon glyphs, image support, sticker sheets — shipped with documented gaps: places where output is close to the design but not faithful, or where a capability stops one step short.

Solution

Finish the punch list. Each documented gap becomes a sub-issue; nothing here rebuilds existing capability. Umbrella closes when composed output is visually faithful across the validation libraries and the remaining capability gaps (visibility bindings, effects, tokens) are delivered.

Acceptance criteria

• Each sub-issue closed or explicitly deferred with rationale
• Validation-library comparisons show no known fidelity gaps attributable to the transforms

---

Implementation details are tracked internally.

Working this umbrella

• No umbrella branch. Each sub-issue is worked on its own short-lived branch with its own PR into the appropriate repo — these gaps are independent; this umbrella must not become a long-lived mega-branch.
• Normal per-PR review applies; no special checkpoints.
• Sub-issues are NOT added to the Specs 2 board — only this umbrella is tracked there.
• Sequencing note: most sub-issues land in the transforms package once Refactor specs-from-figma repo as transformers monorepo #228 completes; only start ones here that don't conflict with the migration.

Sequencing (authoritative)

There is NO order among sub-issues — issue numbers are not a sequence. All are independent. All are blocked by #228 completing, except #247 (stylesheet effects) and #243 (image source stamping), which are safe to work at any time.