[PR #5011] [MERGED] docs(cli): include Kuna in supported doctor providers (#4624) #6731

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5011
Author: @prasad2512
Created: 10/18/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @morluto

Base: main ← Head: docs/issue-4624-kuna-doctor-provider


📝 Commits (1)

  • abe4c0e docs(cli): include Kuna in supported doctor providers (#4624)

📊 Changes

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

View changed files

📝 docs/cli.md (+1 -1)

📄 Description

Summary

docs/cli.md:157-160 previously listed only Hopper, Ghidra, IDA, and JADX as accepted by
ea doctor --provider ID --json and stated other adapters are not accepted. However, DOCTOR_PROVIDER_IDS in src/application/DoctorProviderIds.ts and docs/kuna-provider.md explicitly support kuna as a supported engine diagnostic option.

This PR updates docs/cli.md to list Kuna alongside Hopper, Ghidra, IDA, and JADX, aligning the CLI guide with the runtime implementation and the dedicated Kuna guide.

Fixes #4624

Problem and expected behavior

docs/cli.md explicitly excluded Kuna by stating only Hopper, Ghidra, IDA, and JADX were supported providers for
ea doctor --provider. However, Kuna doctor checks are fully implemented.

Change and scope

  • In docs/cli.md, update provider list to include Kuna.

Contract and boundary impact

  • Semantic owner and earliest changed stage: docs

  • Contribution scope fit and linked maintainer decision: not applicable

  • CLI and MCP/tool-catalog contract: none

  • Provider, bridge, target-format, or platform compatibility: all platforms

  • Evidence, artifact, provenance, or reconstruction contract: none

  • Target selection, authority, upstream behavior, and cleanup details: not applicable

  • Generated metadata: none

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none (docs only)
  • Base reproduction: reported in #4624

Validation performed

px oxfmt docs/cli.md — passed (clean formatting)

pm run check:fast — passed (0 errors)

Compatibility, safety, and release

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

Author readiness

Human owner: @prasad2512

  • 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 ype(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/5011 **Author:** [@prasad2512](https://github.com/prasad2512) **Created:** 10/18/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `docs/issue-4624-kuna-doctor-provider` --- ### 📝 Commits (1) - [`abe4c0e`](https://github.com/morluto/rea/commit/abe4c0e667e7a67b7afe3036c8edc34550ab96ad) docs(cli): include Kuna in supported doctor providers (#4624) ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/cli.md` (+1 -1) </details> ### 📄 Description ## Summary docs/cli.md:157-160 previously listed only Hopper, Ghidra, IDA, and JADX as accepted by ea doctor --provider ID --json and stated other adapters are not accepted. However, DOCTOR_PROVIDER_IDS in src/application/DoctorProviderIds.ts and docs/kuna-provider.md explicitly support kuna as a supported engine diagnostic option. This PR updates docs/cli.md to list Kuna alongside Hopper, Ghidra, IDA, and JADX, aligning the CLI guide with the runtime implementation and the dedicated Kuna guide. Fixes #4624 ## Problem and expected behavior docs/cli.md explicitly excluded Kuna by stating only Hopper, Ghidra, IDA, and JADX were supported providers for ea doctor --provider. However, Kuna doctor checks are fully implemented. ## Change and scope - In docs/cli.md, update provider list to include Kuna. ## Contract and boundary impact - Semantic owner and earliest changed stage: docs - Contribution scope fit and linked maintainer decision: not applicable - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: all platforms - Evidence, artifact, provenance, or reconstruction contract: none - Target selection, authority, upstream behavior, and cleanup details: not applicable - Generated metadata: none - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none (docs only) - Base reproduction: reported in #4624 ## Validation performed - px oxfmt docs/cli.md — passed (clean formatting) - pm run check:fast — passed (0 errors) ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: docs only - Package or release metadata impact: none - Security, privacy, process, or containment review: safe ## Author readiness Human owner: @prasad2512 - [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 ype(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-11-01 21:42:38 +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#6731
No description provided.