[PR #4729] [CLOSED] fix(session): declare provider composition requirements for trace_call_path #6375

Closed
opened 2026-10-31 01:13:58 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4729
Author: @ahmed-husssain
Created: 10/17/2026
Status: ❌ Closed

Base: main ← Head: fix/trace-call-path-inventory-requirements


📝 Commits (1)

  • 292d969 fix(session): declare provider composition requirements for trace_call_path

📊 Changes

2 files changed (+94 additions, -0 deletions)

View changed files

📝 src/application/CapabilityInventory.test.ts (+90 -0)
📝 src/application/CapabilityInventory.ts (+4 -0)

📄 Description

Summary

Fixes #4687

Declare procedure_address and at least one of procedure_callees or procedure_callers as the composition requirements for trace_call_path in CapabilityInventory. Previously, trace_call_path was omitted from ENHANCED_REQUIREMENTS, causing MCP binary_session inventory to falsely report the working tool as unavailable (provider_missing) with "No provider composition is declared for this operation."

Problem and expected behavior

When a target is open and a provider supplies procedure_address, procedure_callees, and procedure_callers, trace_call_path executes successfully in both directions. However, binary_session capability inventory reported it as available: false with reason provider_missing.

Expected behavior: trace_call_path should report available: true whenever the provider declares procedure_address along with procedure_callees (forward traversal) or procedure_callers (backward traversal).

Change and scope

  • Added trace_call_path to ENHANCED_REQUIREMENTS in src/application/CapabilityInventory.ts.
  • Added 4 test cases to src/application/CapabilityInventory.test.ts verifying availability with single- and dual-direction capabilities, missing procedure_address rejection, missing relationship operations rejection, and provider_unavailable propagation.

Contract and boundary impact

  • Semantic owner and earliest changed stage: CapabilityInventory composition mapping.
  • Contribution scope fit and linked maintainer decision: not applicable (bug fix within existing boundary).
  • CLI and MCP/tool-catalog contract: fixes reported tool availability in MCP binary_session capability inventory.
  • Provider, bridge, target-format, or platform compatibility: platform-independent.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): none.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: src/application/CapabilityInventory.test.ts
  • Base reproduction: buildCapabilityInventory previously reported trace_call_path as available: false with reason provider_missing despite capable provider. With this fix, it reports available: true, reason: "available".

Validation performed

  • npm run test:local -- src/application/CapabilityInventory.test.ts — 31 passed in 4.77s
  • npm run check:fast — typecheck and lint passed
  • npm run docs:check — 6 tasks passed in 39.33s
  • git diff --check — passed clean

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: platform-agnostic inventory logic.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @ahmed-husssain

  • 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/4729 **Author:** [@ahmed-husssain](https://github.com/ahmed-husssain) **Created:** 10/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/trace-call-path-inventory-requirements` --- ### 📝 Commits (1) - [`292d969`](https://github.com/morluto/rea/commit/292d969a20d3b29c922bccc5c1df1ba53fb30761) fix(session): declare provider composition requirements for trace_call_path ### 📊 Changes **2 files changed** (+94 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/application/CapabilityInventory.test.ts` (+90 -0) 📝 `src/application/CapabilityInventory.ts` (+4 -0) </details> ### 📄 Description ## Summary Fixes #4687 Declare `procedure_address` and at least one of `procedure_callees` or `procedure_callers` as the composition requirements for `trace_call_path` in `CapabilityInventory`. Previously, `trace_call_path` was omitted from `ENHANCED_REQUIREMENTS`, causing MCP `binary_session` inventory to falsely report the working tool as unavailable (`provider_missing`) with "No provider composition is declared for this operation." ## Problem and expected behavior When a target is open and a provider supplies `procedure_address`, `procedure_callees`, and `procedure_callers`, `trace_call_path` executes successfully in both directions. However, `binary_session` capability inventory reported it as `available: false` with reason `provider_missing`. Expected behavior: `trace_call_path` should report `available: true` whenever the provider declares `procedure_address` along with `procedure_callees` (forward traversal) or `procedure_callers` (backward traversal). ## Change and scope - Added `trace_call_path` to `ENHANCED_REQUIREMENTS` in `src/application/CapabilityInventory.ts`. - Added 4 test cases to `src/application/CapabilityInventory.test.ts` verifying availability with single- and dual-direction capabilities, missing `procedure_address` rejection, missing relationship operations rejection, and `provider_unavailable` propagation. ## Contract and boundary impact - Semantic owner and earliest changed stage: `CapabilityInventory` composition mapping. - Contribution scope fit and linked maintainer decision: not applicable (bug fix within existing boundary). - CLI and MCP/tool-catalog contract: fixes reported tool availability in MCP `binary_session` capability inventory. - Provider, bridge, target-format, or platform compatibility: platform-independent. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none. - Generated metadata, package, or installation impact: none. Expected effects: - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: `src/application/CapabilityInventory.test.ts` - Base reproduction: `buildCapabilityInventory` previously reported `trace_call_path` as `available: false` with reason `provider_missing` despite capable provider. With this fix, it reports `available: true, reason: "available"`. ## Validation performed - `npm run test:local -- src/application/CapabilityInventory.test.ts` — 31 passed in 4.77s - `npm run check:fast` — typecheck and lint passed - `npm run docs:check` — 6 tasks passed in 39.33s - `git diff --check` — passed clean ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: platform-agnostic inventory logic. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @ahmed-husssain - [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. - [x] 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-10-31 01:13:58 +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#6375
No description provided.