[GH-ISSUE #7678] [Feature] Let compare_artifacts take retained Evidence references, and compare artifacts from the CLI #4601

New issue

Closed

opened 2026-10-31 00:51:11 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:51:11 +00:00

Owner

Originally created by @Entrpi on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7678

Before submitting

I searched the open and closed issues and pull requests for a related proposal.
I understand the contribution scope must be reviewed before integration; open questions are welcome here.
This request does not include credentials, private samples, or sensitive target data.

Area

Evidence, artifacts, or reconstruction

Current limitation

compare_artifacts accepts only complete inventory Evidence objects for left and right. A {kind: "retained-evidence", evidence_id} reference, which compare_functions accepts, fails its input schema. So every comparison makes the agent send back Evidence that REA already retains. Comparing two ESP-IDF firmware builds, the arguments alone came to about 6.2k estimated output tokens for two app inventories and 10.4k for two flash-dump inventories (2.8k and 5.3k with summaries).

The CLI has no artifact comparison: rea compare compares bundle records and reports unresolved for artifact inventories.

Use cases

Comparing two firmware builds, or a build with a modified copy, in one agent session where both inventories are already retained.

Desired outcome and success criteria

compare_artifacts accepts the same source references as compare_functions and inspect_analysis_view (retained-evidence, inline, evidence-file), parsed by one owner.
Inline Evidence keeps working.
Each kind of source gives the same comparison result, through MCP and the CLI.

Expected interaction with targets

No target interaction (documentation or usability only)

Verification available so far

I have a prototype or observed results

Verification details (optional)

The token figures come from a local run through MCP on ESP-IDF 5.5 builds. A branch implementing this is in progress on my fork.

Alternatives considered

Comparing summaries only: cheaper, but it still resends Evidence.

Originally created by @Entrpi on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7678 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This request does not include credentials, private samples, or sensitive target data. ### Area Evidence, artifacts, or reconstruction ### Current limitation `compare_artifacts` accepts only complete inventory Evidence objects for `left` and `right`. A `{kind: "retained-evidence", evidence_id}` reference, which `compare_functions` accepts, fails its input schema. So every comparison makes the agent send back Evidence that REA already retains. Comparing two ESP-IDF firmware builds, the arguments alone came to about 6.2k estimated output tokens for two app inventories and 10.4k for two flash-dump inventories (2.8k and 5.3k with summaries). The CLI has no artifact comparison: `rea compare` compares bundle records and reports `unresolved` for artifact inventories. ### Use cases Comparing two firmware builds, or a build with a modified copy, in one agent session where both inventories are already retained. ### Desired outcome and success criteria - `compare_artifacts` accepts the same source references as `compare_functions` and `inspect_analysis_view` (`retained-evidence`, `inline`, `evidence-file`), parsed by one owner. - Inline Evidence keeps working. - Each kind of source gives the same comparison result, through MCP and the CLI. ### Expected interaction with targets No target interaction (documentation or usability only) ### Verification available so far I have a prototype or observed results ### Verification details (optional) The token figures come from a local run through MCP on ESP-IDF 5.5 builds. A branch implementing this is in progress on my fork. ### Alternatives considered Comparing summaries only: cheaper, but it still resends Evidence.

bsakaguchi closed this issue

2026-10-31 00:51:12 +00:00

bsakaguchi referenced this issue

2026-10-31 00:51:43 +00:00

[GH-ISSUE #7774] [Design] Bound per-binding member-write records in JavaScript semantic analysis #4639

bsakaguchi referenced this issue

2026-10-31 00:51:48 +00:00

[GH-ISSUE #7808] [Bug] analyze-javascript-application exhausts a 2–16 GiB worker heap on one 75 KB webpack module (minified XPath library); rest of the bundle analyzes after module-level splitting #4646