diff --git a/docs/cli.md b/docs/cli.md
index 80ccfa59..7494bcdb 100644
--- a/docs/cli.md
+++ b/docs/cli.md
@@ -52,9 +52,11 @@ page 1 "Screens": 380 nodes, 4 top-level
 - `<out>` has an image extension: one file with the given `--node`, or the whole page composited.
 - `--node` takes a layer id (`12` or `0:12`) or a layer name.
 - `--format fig` (or an `<out>` ending in `.fig`) writes the whole file as `.fig`, experimental:
-  written from public format notes and checked only by opening it again in FigCraft; other apps
-  may not open every file. What was left out (shared style links, variables, comments, Dev Mode
-  data…) is printed as `note:` lines.
+  written from public format notes, including variables with their modes and bindings and shared
+  styles with their layer links. Checked by opening it again in FigCraft and, on the example
+  documents and small test files, in other software; other apps may not open every file. What was
+  left out (comments, Dev Mode data, some bindings and settings…) is printed as `note:` lines;
+  `docs/file-format-parity.md` lists what was checked and what is unchecked.
 - The format comes from `--format`, else `<out>`'s extension, else png. `--scale` (default 1, max 64)
   applies to raster formats.
 - SVG/PDF exports with visible descendants more than 256 levels below an exported root fail with
diff --git a/docs/mcp.md b/docs/mcp.md
index db18dddc..4efee72a 100644
--- a/docs/mcp.md
+++ b/docs/mcp.md
@@ -768,10 +768,12 @@ skipped. The result's `opened.warnings` list what was approximated or skipped.
 ending in `.fig`) writes the whole document as a `.fig` file, from the same public format notes the
 import uses: the layer tree, geometry, paints with image bytes, strokes, effects, text with styled
 runs, vector networks, auto layout, constraints, components, sets, instances with their overrides
-and property values, and prototype interactions. `warnings` lists what was left out (shared style
-links, variables, comments, Dev Mode data and the like). Only round trips through FigCraft's own
-importer are verified; other apps may not open every file. Without `path` the file comes back as
-base64 `data`. Check one by opening it again:
+and property values, variable collections with their modes, variables and bindings, shared styles
+with their layer links, and prototype interactions. `warnings` lists what was left out (comments,
+Dev Mode data, some bindings and settings and the like). Round trips through FigCraft's own
+importer are tested, and the example documents and small test files were opened in other software
+(`docs/file-format-parity.md` says what was checked); other apps may not open every file. Without
+`path` the file comes back as base64 `data`. Check one by opening it again:
 
 ```text
 {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"export","arguments":{"format":"fig","path":"/tmp/handoff.fig"}}}