[PR #7277] fix(cli): preserve provider acronym spellings #7804

Open
opened 2026-11-05 01:47:47 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7277
Author: @ducanhnguyen223
Created: 10/26/2026
Status: 🔄 Open

Base: main ← Head: codex/fix-7275-provider-spelling


📝 Commits (1)

  • 63dd31f fix(cli): preserve provider acronym spellings

📊 Changes

2 files changed (+36 additions, -1 deletions)

View changed files

📝 src/cli/interactiveSetup.ts (+6 -1)
📝 tests/boundary/cli/cliSetup.test.ts (+30 -0)

📄 Description

Summary

Fixes #7275 by rendering the existing IDA and JADX providers with their canonical product spellings in the interactive setup completion summary.

Problem and expected behavior

The renderer capitalized only the first character of provider IDs, displaying ida and jadx as “Ida” and “Jadx”. The summary should show “IDA” and “JADX”; ordinary names such as Hopper and Ghidra should remain unchanged.

Change and scope

Add display-name overrides for the two acronym IDs at the CLI presentation boundary and retain the existing capitalization fallback for all other IDs. Provider discovery, setup, and analysis behavior are unchanged.

Contract and boundary impact

  • Semantic owner and earliest changed stage: interactive setup completion rendering, CLI presentation.
  • Contribution scope fit and linked maintainer decision: existing CLI wording only; no new capability or maintainer scope decision required.
  • CLI and MCP/tool-catalog contract: CLI text only; MCP schemas and catalog are unchanged.
  • Provider, bridge, target-format, or platform compatibility: no provider execution or compatibility changes.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: no target interaction, configuration writes, or cleanup.
  • Generated metadata, package, or installation impact: none.
  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/cli/cliSetup.test.ts checks the combined acronym output and confirms the Hopper/Ghidra control remains unchanged.
  • Base reproduction or other evidence: the new boundary regression failed on the base revision and captured “Ida” and “Jadx”.
  • User-visible output: expected Deep analysis: Hopper, Ghidra, IDA, and JADX.
  • Remaining proof gaps: no real provider was installed or launched; provider behavior is outside this presentation-only fix.

Validation performed

  • npm run test:focused -- tests/boundary/cli/cliSetup.test.ts — 17 tests passed.
  • npm run check:fast — typecheck and lint passed.
  • git diff --check — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; this change only formats provider IDs.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no target interaction or side effects.

Author readiness

Human owner:

  • 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/7277 **Author:** [@ducanhnguyen223](https://github.com/ducanhnguyen223) **Created:** 10/26/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `codex/fix-7275-provider-spelling` --- ### 📝 Commits (1) - [`63dd31f`](https://github.com/morluto/rea/commit/63dd31f51d2627d15199f2367f29f9e57e24b465) fix(cli): preserve provider acronym spellings ### 📊 Changes **2 files changed** (+36 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/cli/interactiveSetup.ts` (+6 -1) 📝 `tests/boundary/cli/cliSetup.test.ts` (+30 -0) </details> ### 📄 Description ## Summary Fixes #7275 by rendering the existing IDA and JADX providers with their canonical product spellings in the interactive setup completion summary. ## Problem and expected behavior The renderer capitalized only the first character of provider IDs, displaying `ida` and `jadx` as “Ida” and “Jadx”. The summary should show “IDA” and “JADX”; ordinary names such as Hopper and Ghidra should remain unchanged. ## Change and scope Add display-name overrides for the two acronym IDs at the CLI presentation boundary and retain the existing capitalization fallback for all other IDs. Provider discovery, setup, and analysis behavior are unchanged. ## Contract and boundary impact - Semantic owner and earliest changed stage: interactive setup completion rendering, CLI presentation. - Contribution scope fit and linked maintainer decision: existing CLI wording only; no new capability or maintainer scope decision required. - CLI and MCP/tool-catalog contract: CLI text only; MCP schemas and catalog are unchanged. - Provider, bridge, target-format, or platform compatibility: no provider execution or compatibility changes. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: no target interaction, configuration writes, or cleanup. - Generated metadata, package, or installation impact: none. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/cli/cliSetup.test.ts` checks the combined acronym output and confirms the Hopper/Ghidra control remains unchanged. - Base reproduction or other evidence: the new boundary regression failed on the base revision and captured “Ida” and “Jadx”. - User-visible output: expected `Deep analysis: Hopper, Ghidra, IDA, and JADX`. - Remaining proof gaps: no real provider was installed or launched; provider behavior is outside this presentation-only fix. ## Validation performed - `npm run test:focused -- tests/boundary/cli/cliSetup.test.ts` — 17 tests passed. - `npm run check:fast` — typecheck and lint passed. - `git diff --check` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; this change only formats provider IDs. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no target interaction or side effects. ## Author readiness Human owner: <!-- @GitHub-handle --> - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#7804
No description provided.