From 077d6c407b3ea7443a7277ae0e5531b3927dd742 Mon Sep 17 00:00:00 2001
From: morluto <76467478+morluto@users.noreply.github.com>
Date: Sat, 10 Oct 2026 05:41:52 +0800
Subject: [PATCH] docs: correct MCP error and capture import guidance

---
 docs/migration-6.2.md   | 2 +-
 docs/process-capture.md | 5 +++--
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/migration-6.2.md b/docs/migration-6.2.md
index 38baae0736..8955f39f7a 100644
--- a/docs/migration-6.2.md
+++ b/docs/migration-6.2.md
@@ -31,7 +31,7 @@ and carry their typed JSON diagnostic in a text content block; they omit
 if (reply.isError === true) {
   const text = reply.content.find((part) => part.type === "text");
   if (text === undefined) throw new Error("REA error has no text diagnostic");
-  const diagnostic = JSON.parse(text.text);
+  const { error: diagnostic } = JSON.parse(text.text);
   // Handle diagnostic.code, diagnostic.message and diagnostic.details.
 }
 ```
diff --git a/docs/process-capture.md b/docs/process-capture.md
index 316d36c99e..21f1f5343f 100644
--- a/docs/process-capture.md
+++ b/docs/process-capture.md
@@ -157,8 +157,9 @@ results for unaffected dimensions and mark affected dimensions unknown; an
 incomplete capture cannot locate the first divergence across all dimensions.
 Trace assertions use coverage for the sources they select, so an assertion
 about complete raw terminal output need not fail because rendered snapshots
-were omitted. Older truncated captures without these details retain the
-conservative comparison behavior. These diagnostics use the existing scenario
+were omitted. Captures missing `truncation_details` are rejected on import;
+preserve them as historical files and recapture for current comparisons.
+These diagnostics use the existing scenario
 budgets; they do not introduce a separate file-hashing budget.
 
 When the host withholds an unrelated process’s ownership token, REA leaves that