Attach, list, update and delete Figma Dev Resources (links to code, PRs and docs) on design nodes

Documented steps

1. Understand the model: dev resources are URLs attached to individual nodes and surfaced in Figma Dev Mode. Unlike variables, components and styles they need no publish step. Docs: https://developers.figma.com/docs/rest-api/dev-resources/
2. Authenticate with 'X-Figma-Token: <PAT>' or an OAuth Bearer token; reading needs file_dev_resources:read and writing needs file_dev_resources:write.
3. List: GET https://api.figma.com/v1/files/:file_key/dev_resources, optionally with node_ids=<comma-separated ids> to scope results. Response is {"dev_resources": DevResource[]} with id, name, url, file_key and node_id.
4. Create: POST https://api.figma.com/v1/dev_resources (top-level path, NOT under /files/:file_key) with body {"dev_resources": [{name, url, file_key, node_id}, ...]}. Bulk creation across multiple files in one call is supported.
5. Check the create response {"links_created": DevResource[], "errors": [{file_key, node_id, error}]} item by item.
6. Update: PUT https://api.figma.com/v1/dev_resources with {"dev_resources": [{id, name?, url?}, ...]} — no file_key or node_id needed since the resource exists. Response is {"links_updated": string[], "errors": [{id, error}]}.
7. Delete: DELETE https://api.figma.com/v1/files/:file_key/dev_resources/:dev_resource_id (file-scoped path). A success returns no content.
8. Typical CI use: after merging a PR, look up the node id from your design-token or component mapping and POST a dev resource linking that node to the merged PR URL.
9. Handle 400 and 401 on GET/POST/PUT, and 401/404 on DELETE. Endpoint reference: https://developers.figma.com/docs/rest-api/dev-resources-endpoints/