[PR #7157] [CLOSED] fix(artifacts): name the failing side in compare_artifacts input errors #7681

Closed
opened 2026-11-03 13:39:36 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7157
Author: @surajvelip
Created: 10/25/2026
Status: ❌ Closed

Base: main ← Head: compare-artifacts-input-path


📝 Commits (2)

  • d130425 Validate environment-serve --port as decimal text
  • b9ad737 Name the failing side in compare_artifacts input errors

📊 Changes

3 files changed (+7 additions, -7 deletions)

View changed files

📝 src/application/artifacts/ArtifactComparisonEvidence.ts (+2 -1)
📝 src/cli/environmentCommands.ts (+3 -6)
📝 src/server/registerArtifactComparisonTool.ts (+2 -0)

📄 Description

Summary

Fixes #7089 — compare_artifacts reported an input issue at ["evidence"], a field that is not a tool input.

Problem and expected behavior

A non-inventory inspect_analysis_view summary supplied as a comparison input produced an issue path ["evidence"] that names no input and does not say which side was wrong. Agents correct requests from the path, so it should be ["left"] or ["right"].

Change and scope

resolveArtifactComparisonEvidence now takes the input name and emits it in the issue path; the tool registration passes left/right at each call site.

Contract and boundary impact

  • Semantic owner and earliest changed stage: evidence resolution for compare_artifacts
  • Contribution scope fit and linked maintainer decision: not applicable
  • CLI and MCP/tool-catalog contract: issue path now names the failing input field
  • Provider, bridge, target-format, or platform compatibility: none
  • Evidence, artifact, provenance, or reconstruction contract: error path only, semantics unchanged
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): none
  • Generated metadata, package, or installation impact: none

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: none added; existing ArtifactComparisonEvidence.test.ts coverage still passes
  • Base reproduction or other evidence: source-derived from the issue report
  • User-visible CLI/MCP output (if applicable): issue path ["left"]/["right"]
  • Remaining proof gaps: no live MCP invocation

Validation performed

  • npm run test:local -- src/application/artifacts/ArtifactComparisonEvidence.test.ts — 6/6 pass
  • lint-staged oxfmt/oxlint on commit — clean

Compatibility, safety, and release

  • Breaking changes or migration steps: none
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: error reporting only

Author readiness

Human owner: @surajvelip

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7157 **Author:** [@surajvelip](https://github.com/surajvelip) **Created:** 10/25/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `compare-artifacts-input-path` --- ### 📝 Commits (2) - [`d130425`](https://github.com/morluto/rea/commit/d1304252033634f1f554a5e827d83509db261c5a) Validate environment-serve --port as decimal text - [`b9ad737`](https://github.com/morluto/rea/commit/b9ad7372ef26e4e5e7e9b3124fb7fd17f2dc79ed) Name the failing side in compare_artifacts input errors ### 📊 Changes **3 files changed** (+7 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `src/application/artifacts/ArtifactComparisonEvidence.ts` (+2 -1) 📝 `src/cli/environmentCommands.ts` (+3 -6) 📝 `src/server/registerArtifactComparisonTool.ts` (+2 -0) </details> ### 📄 Description ## Summary Fixes #7089 — `compare_artifacts` reported an input issue at `["evidence"]`, a field that is not a tool input. ## Problem and expected behavior A non-inventory `inspect_analysis_view` summary supplied as a comparison input produced an issue path `["evidence"]` that names no input and does not say which side was wrong. Agents correct requests from the path, so it should be `["left"]` or `["right"]`. ## Change and scope `resolveArtifactComparisonEvidence` now takes the input name and emits it in the issue path; the tool registration passes `left`/`right` at each call site. ## Contract and boundary impact - Semantic owner and earliest changed stage: evidence resolution for `compare_artifacts` - Contribution scope fit and linked maintainer decision: not applicable - CLI and MCP/tool-catalog contract: issue path now names the failing input field - Provider, bridge, target-format, or platform compatibility: none - Evidence, artifact, provenance, or reconstruction contract: error path only, semantics unchanged - Target selection, authority, upstream behavior, and cleanup details (if applicable): none - Generated metadata, package, or installation impact: none Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: none added; existing `ArtifactComparisonEvidence.test.ts` coverage still passes - Base reproduction or other evidence: source-derived from the issue report - User-visible CLI/MCP output (if applicable): issue path `["left"]`/`["right"]` - Remaining proof gaps: no live MCP invocation ## Validation performed - `npm run test:local -- src/application/artifacts/ArtifactComparisonEvidence.test.ts` — 6/6 pass - lint-staged oxfmt/oxlint on commit — clean ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: not applicable - Package or release metadata impact: none - Security, privacy, process, or containment review: error reporting only ## Author readiness Human owner: @surajvelip - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-03 13:39:36 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7681
No description provided.