[PR #5251] [MERGED] fix(mcp): describe function comparisons in behavior tool #6839

Closed
opened 2026-11-01 21:43:25 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5251
Author: @dayvison2b
Created: 10/19/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: fix/5080-function-comparison-description


📝 Commits (1)

  • 925bfdb fix(mcp): describe function comparisons in behavior tool

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 src/contracts/sessionToolContracts.ts (+1 -1)

📄 Description

Fixes #5080.

Summary

The find_changed_behavior MCP description now lists process, artifact, and function comparison Evidence. It retains the distinction between runtime observations and static behavior candidates.

Problem and expected behavior

The tool accepts validated function comparison Evidence, but its advertised description named only process and artifact comparisons. The description should match the accepted contract.

Change and scope

Updated the canonical description in src/contracts/sessionToolContracts.ts. This is a wording-only change within the existing comparison workflow; a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: session tool contract; MCP tool description.

  • Contribution scope fit: existing supported workflow.

  • CLI and MCP/tool-catalog contract: the description now lists all accepted comparison Evidence types.

  • Provider, bridge, target-format, or platform compatibility: unchanged.

  • Evidence, artifact, provenance, or reconstruction contract: unchanged.

  • Generated metadata, package, or installation impact: no generated files changed.

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none; accepted inputs and runtime behavior are unchanged.
  • Existing evidence: function comparison MCP boundary coverage exercises this input type; not run for this wording-only change.
  • Remaining proof gap: automated checks were not run.

Validation performed

  • git diff --check — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: no runtime behavior change.
  • Security, privacy, process, or containment review: no target interaction.

Author readiness

Human owner: @dayvison2b

  • 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/5251 **Author:** [@dayvison2b](https://github.com/dayvison2b) **Created:** 10/19/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/5080-function-comparison-description` --- ### 📝 Commits (1) - [`925bfdb`](https://github.com/morluto/rea/commit/925bfdb18a7e231a1ef7ffae52e5ca5df0c1b69d) fix(mcp): describe function comparisons in behavior tool ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/contracts/sessionToolContracts.ts` (+1 -1) </details> ### 📄 Description Fixes #5080. ## Summary The `find_changed_behavior` MCP description now lists process, artifact, and function comparison Evidence. It retains the distinction between runtime observations and static behavior candidates. ## Problem and expected behavior The tool accepts validated function comparison Evidence, but its advertised description named only process and artifact comparisons. The description should match the accepted contract. ## Change and scope Updated the canonical description in `src/contracts/sessionToolContracts.ts`. This is a wording-only change within the existing comparison workflow; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: session tool contract; MCP tool description. - Contribution scope fit: existing supported workflow. - CLI and MCP/tool-catalog contract: the description now lists all accepted comparison Evidence types. - Provider, bridge, target-format, or platform compatibility: unchanged. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Generated metadata, package, or installation impact: no generated files changed. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none; accepted inputs and runtime behavior are unchanged. - Existing evidence: function comparison MCP boundary coverage exercises this input type; not run for this wording-only change. - Remaining proof gap: automated checks were not run. ## Validation performed - `git diff --check` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: no runtime behavior change. - Security, privacy, process, or containment review: no target interaction. ## Author readiness Human owner: @dayvison2b - [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 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:43:25 +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#6839
No description provided.