feat(snapshots)!: persist the target identity as the snapshot target (#11551)

* feat(snapshots)!: persist the target identity as the snapshot target

The snapshot target is now `{ kind, identity }`, where `identity` is the
FileTargetIdentity that `binaryTargetIdentity` produces and `kind` is the
binary kind query IDs commit to. The per-format target projection and
`snapshotTargetIdentity` are deleted; the schema checks the format's
selection, architecture and kind instead of keeping one union arm per format.

Entry execution subjects use the Evidence subject shape (file or explicit
unknown), so a snapshot entry commits to the same identity, including the
selection, as its Evidence record. Workflow entries take the subject of the
workflow's own Evidence. Replay no longer re-derives the selection from the
open target.

`FileTargetSelection` gains `universal-slice` (`offset`, `size`, and the FAT
`cpu_type`/`cpu_subtype` when target admission supplied the FAT table, else
null). `binaryTargetIdentity` produces it for `mach-o-universal` targets, so
Evidence and snapshots for different slices of one container no longer share
an identity.

Refs #11417

BREAKING CHANGE: analysis snapshot files change shape: `target` is
`{ kind, identity: { kind: "file", sha256, format, architecture, selection } }`
and entry `execution.subject` is the Evidence subject
(`{ identity, name, local_path }`, never null). Snapshot binding mismatch
details report `target.snapshot`/`target.selected` in the same shape. Evidence
IDs of universal Mach-O targets change because their subject identity now
carries the selected slice. Recreate saved snapshots and Evidence bundles of
universal Mach-O targets.

* docs(evidence): name the universal Mach-O slice selection in the subject contract

* fix(snapshots): read the snapshot target identity in the Ghidra verification scripts

The real Ghidra snapshot checks (lifecycle, RISC-V, MIPS, PowerPC) read
snapshot.target.sha256 and .architecture, which moved under
snapshot.target.identity, so they would fail after saving a valid snapshot.

* feat(evidence)!: name live browser page Evidence by its page URL (#11559)

Browser page observations (inspect_web_page, analyze_web_bundle,
observe_web_session, discover_webmcp_tools, capture_web_screenshot,
observe_web_execution, inspect_web_event_listeners) named an unknown
(`not-observed`) subject although the provider reports the page URL.

`TargetIdentity` gains a `url` kind: the reported URL with userinfo removed
and its origin (`null` for an opaque origin). The schema refuses a URL that
carries userinfo or an origin the URL does not have.
`browserUrlTargetIdentity` in the browser URL owner builds it from the
provider's reported URL; a withheld or unparseable URL stays unknown
(`not-observed`). Target lists and comparisons still name no single
document. Analysis views keep their parent's URL subject, as they already
keep a file subject.

BREAKING CHANGE: Evidence IDs of live browser page observations and their
analysis views change, and their subject is
`{ "kind": "url", "url", "origin" }` with `name` and `local_path` null.
Recreate stored Evidence for these tools. This lands inside Evidence format
revision 2 under the release hold (#11417); no `evidence_format` bump.
This commit is contained in:
morluto authored and GitHub committed 2026-11-16 07:04:34 +08:00
1 parent f6df353002
commit ff0176256a
30 files changed
+678 -396

No files matched your search

+9 -4
View File
@@ -1023,12 +1023,17 @@ it, or with another revision, as an integrity mismatch whose recovery is to
recreate the observations with the current release; re-exporting an earlier
bundle does not update its format or identities. Revision 2 names the subject
by its target identity, `subject.identity` (`kind: "file"`, `sha256`, `format`,
`architecture` and `selection`: the raw or DOL entry point or the ESP flash
offsets that select what was analysed, otherwise `null`), and the Evidence ID
`architecture` and `selection`: the raw or DOL entry point, the ESP flash
offsets, or the universal Mach-O slice (`offset`, `size`, and the FAT
`cpu_type` and `cpu_subtype`, `null` when the FAT table was not admitted) that
select what was analysed, otherwise `null`), and the Evidence ID
commits to that identity; `subject.name` and `subject.local_path` are display
facts outside the ID. The subject has no separate `digest`, `format` or
`architecture` members; read them from `subject.identity`. Every record has a
subject: one whose target REA did not identify names
`architecture` members; read them from `subject.identity`. A live browser page
observation names the page's reported URL,
`{ "kind": "url", "url": …, "origin": … }`, with userinfo removed and `origin`
`null` for an opaque origin; its `name` and `local_path` are `null`. Every
record has a subject: one whose target REA did not identify names
`{ "kind": "unknown", "reason": … }`, where the reason is
`derived-from-linked-evidence` (comparisons and workflows, whose sources are
committed through `evidence_links`), `not-observed` or `unsupported-subject`,