figma-typings-audit

Absorbing a `@figma/plugin-typings` release into Figwright, end to end: audit → upgrade → implement what's worth having. **One hard ordering constraint: diff before upgrading.** The audit compares the *installed* version against the target, so upgrading first destroys the baseline. (Recoverable — the old version is in git history and `npm pack` can still fetch it — but don't create the problem.) Target version: whatever the user named, otherwise the latest on npm. ## Stage 0 — Resolve versions ```bash grep '@figma/plugin-typings' packages/plugin/package.json # the declared range grep '"version"' packages/plugin/node_modules/@figma/plugin-typings/package.json # what is installed npm view @figma/plugin-typings version # latest npm view @figma/plugin-typings versions --json # how many releases are being skipped ``` Compare against the **installed** version, not the declared range — a caret range can already be satisfied by something newer than what the lockfile pinned. If installed and target are equal, say so and stop. Don't spend tokens on the rest. ## Stage 1 — Get the authoritative diff There is no other source. `figma/plugin-typings` ships **no CHANGELOG and no GitHub Releases** (the releases API returns an empty array), and its commit messages are content-free (`1.132.0`, `Release v1.132 updates`). The `.d.ts` diff is the only ground truth. Work in the session scratchpad directory (`$SCRATCH` below): ```...