Verify Figma MCP Transports

A Figma MCP tool answers the same question over two paths: REST (personal access token) and WebSocket (the Figma plugin). Fixing one and not the other still typechecks, so the drift is silent. Run both and compare mechanically.

두 경로의 구현 차이가 판단에 필요할 때만 packages/mcp/AGENTS.md를 읽는다.

[!IMPORTANT] Run this skill on the main thread. Phase 3 is a hard stop that waits on a person, and a subagent has nobody to ask — it will pass itself.

Prerequisites

• FIGMA_PERSONAL_ACCESS_TOKEN is set. If not, stop at Phase 0 and ask for it.
• The Figma desktop app is installed.
• The tool under test is registered in PROBES in the probe script. If it isn't, register it first — see the header comment in that file.

Phase 0: Decide what to inspect

Both transports need a target, so this comes before any probing — REST in Phase 1 already needs it.