docs: clarify parser ownership and reader contracts

This commit is contained in:
morluto committed 2026-11-18 22:34:45 -05:00
1 parent 2b7d54257f
commit a6469719ce
9 files changed
+58 -15

No files matched your search

+14 -4
View File
@@ -918,6 +918,16 @@ the original observation through `evidence_links` and reports that the
provider was not rerun. The original and its available source records remain
in the investigation bundle.
### Use snapshot Evidence in file-based workflows
Open the matching target with the saved provider and analysis profile, supplying
the snapshot as `snapshot_path` to `open_binary`. Then call
`export_evidence_bundle` in that MCP session. Use the resulting standalone
Evidence bundle with file-based comparison or inspection. When a reader
recognizes a snapshot in an Evidence file slot, its diagnostic identifies
the observed artifact kind. Restoring the snapshot validates its contents and
checks its binding to the target, provider and profile.
## Import, export and compare Evidence
Evidence records retain artifact identity, source locations, observations,
@@ -946,9 +956,8 @@ records, or one opaque change when you pair them. Use `compare-artifacts`,
described at the end of this section, to compare their contents.
If a selected file looks like an analysis snapshot, comparison reports the
wrong artifact kind. To compare its Evidence, restore the snapshot with its
matching target, provider and analysis profile, then export a standalone
Evidence bundle from that session.
wrong artifact kind. Follow the [snapshot Evidence workflow](#use-snapshot-evidence-in-file-based-workflows)
to export its Evidence for comparison.
`--record_pairs` accepts an inline JSON array or the path to a local JSON
file containing that array, matching MCP `compare_bundles.record_pairs`. For a
@@ -1002,7 +1011,8 @@ from the bundle for every supported view kind. Bundles exported from MCP work
for these commands. Its inline source form cannot also select a bundle.
An `evidence-file` source accepts a standalone Evidence record or a bundle.
When either file input resembles an analysis snapshot, the error identifies
the snapshot and directs you to export session Evidence.
the snapshot. Follow the [snapshot Evidence workflow](#use-snapshot-evidence-in-file-based-workflows)
to export session Evidence.
A missing ID is refused with `details.reason: "missing"`;
supplying a bundle does not make incompatible Evidence valid for a workflow.
`compare-managed-members` keeps its two assembly paths and the