v0.11.3

Trace a built screen back to the design revision it used

A bundle names its frame by node id and Figma file key, but saving the same .fig again keeps both. A screen built from a bundle could not be tied to the exact revision it came from. bundle can now record the source file's hash:

figlens bundle design.fig 12:8 handoff.zip --hash-source
figlens bundle design.fig --frames frames.txt --out-dir handoff --hash-source

Over MCP, pass hashSource: true to bundle.

manifest.json then carries source.sha256, the SHA-256 of the saved .fig:

• It matches shasum -a 256 design.fig.
• A search result's snapshotId is sha256: plus the same digest.
• Keep it with the node ids to tell one save of a file from the next.
• It is null when the file changed while it was decoded or bundled, so the digest never names bytes the bundle did not come from.
• Without the flag the field is absent, so existing bundles and tooling are unchanged.

It is opt-in because hashing reads the whole .fig once more. On a 409 MB file this took 0.15 s of a 1.15 s single-frame bundle. A batch or a running MCP server hashes each saved revision only once.

Update

figlens update

Or brew upgrade runkids/tap/figlens, or npx @runkids/figlens@0.11.3.