[PR #5005] [CLOSED] docs(jeb): qualify JEB Linux CE launch and native method references (#4996) #6725

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5005
Author: @prasad2512
Created: 10/18/2026
Status: ❌ Closed

Base: main ← Head: docs/issue-4996-jeb-ce-launch


📝 Commits (2)

  • a801ba4 docs(jeb): qualify JEB Linux CE launch and native method references
  • bcbd174 docs(jeb): use default 8425 port in CE launch command

📊 Changes

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

View changed files

📝 docs/jeb-analysis.md (+13 -3)

📄 Description

Summary

Fixes #4996

The JEB instrumentation guide previously stated that JEB 5.48 headless mode does not accept --mcp directly, generalizing observations from a licensed build and directing all headless setups to JEB's programmatic API launcher.

This update qualifies the direct CLI headless launch route supported by official JEB Community Edition (CE) 5.48.0 (Linux x64), documenting its explicit loopback binding and caller-selected target input (--infile) while preserving the programmatic alternative and build-specific verification notes.

Problem and expected behavior

Previously, docs/jeb-analysis.md described headless mode as requiring a programmatic Java launcher (JebMcpServerInstance) because "JEB 5.48's -c headless mode does not accept --mcp directly." While this applied to the licensed build observed earlier, official JEB CE 5.48.0 (Linux x64) supports direct CLI startup with -c --mcp. Users consulting the guide were misinformed that direct CLI headless execution was unavailable across all 5.48 distributions.

Expected behavior:
Document the verified CE direct headless launch route, explicit loopback interface binding, and --infile input requirements, while keeping CE native coverage distinct from licensed Android and GUI capabilities.

Change and scope

  • In docs/jeb-analysis.md, documented the verified direct CLI headless command for official JEB CE 5.48.0 (java -Xmx1536m -XX:ActiveProcessorCount=1 -jar bin/app/jeb.jar -c --mcp --interface=127.0.0.1 --port=18425 --infile=probe.elf).
  • Qualified the programmatic API launcher note to licensed JEB 5.48 distributions.
  • Added verified CE build details to the verification list (JEB Community Edition (CE) 5.48.0.202610071539 (Linux x64)).
  • Clarified that open_project is unadvertised across headless modes, requiring --infile on both CE CLI and programmatic launchers.

Follow the contribution scope.
Documentation improvement within existing engine integration; maintainer scope decision: not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: docs/jeb-analysis.md
  • Contribution scope fit and linked maintainer decision: not applicable (documentation improvement)
  • CLI and MCP/tool-catalog contract: none
  • Provider, bridge, target-format, or platform compatibility: JEB CE 5.48.0 on Linux x64
  • 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: tests/conformance/readmeConsistency.test.ts
  • Base reproduction or other evidence: Source-derived against #4996 report and verified JEB CE 5.48.0.202610071539 CLI arguments.
  • User-visible CLI/MCP output (if applicable): not applicable
  • Remaining proof gaps: none

Validation performed

  • npm run format:check — passed (oxfmt checked, all matched files use correct format)
  • npm run check:fast — 2 tasks successful (typecheck + lint passed without errors)
  • npm run test:local -- tests/conformance/readmeConsistency.test.ts — 5 passed (49ms)

Compatibility, safety, and release

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

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 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/5005 **Author:** [@prasad2512](https://github.com/prasad2512) **Created:** 10/18/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/issue-4996-jeb-ce-launch` --- ### 📝 Commits (2) - [`a801ba4`](https://github.com/morluto/rea/commit/a801ba4625c113412f211ed9b03cc96a04994c04) docs(jeb): qualify JEB Linux CE launch and native method references - [`bcbd174`](https://github.com/morluto/rea/commit/bcbd1744a998a4c704bcde33dd6fafcdeb733e10) docs(jeb): use default 8425 port in CE launch command ### 📊 Changes **1 file changed** (+13 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `docs/jeb-analysis.md` (+13 -3) </details> ### 📄 Description ## Summary Fixes #4996 The JEB instrumentation guide previously stated that JEB 5.48 headless mode does not accept `--mcp` directly, generalizing observations from a licensed build and directing all headless setups to JEB's programmatic API launcher. This update qualifies the direct CLI headless launch route supported by official JEB Community Edition (CE) 5.48.0 (Linux x64), documenting its explicit loopback binding and caller-selected target input (`--infile`) while preserving the programmatic alternative and build-specific verification notes. ## Problem and expected behavior Previously, `docs/jeb-analysis.md` described headless mode as requiring a programmatic Java launcher (`JebMcpServerInstance`) because "JEB 5.48's `-c` headless mode does not accept `--mcp` directly." While this applied to the licensed build observed earlier, official JEB CE 5.48.0 (Linux x64) supports direct CLI startup with `-c --mcp`. Users consulting the guide were misinformed that direct CLI headless execution was unavailable across all 5.48 distributions. Expected behavior: Document the verified CE direct headless launch route, explicit loopback interface binding, and `--infile` input requirements, while keeping CE native coverage distinct from licensed Android and GUI capabilities. ## Change and scope - In `docs/jeb-analysis.md`, documented the verified direct CLI headless command for official JEB CE 5.48.0 (`java -Xmx1536m -XX:ActiveProcessorCount=1 -jar bin/app/jeb.jar -c --mcp --interface=127.0.0.1 --port=18425 --infile=probe.elf`). - Qualified the programmatic API launcher note to licensed JEB 5.48 distributions. - Added verified CE build details to the verification list (`JEB Community Edition (CE) 5.48.0.202610071539 (Linux x64)`). - Clarified that `open_project` is unadvertised across headless modes, requiring `--infile` on both CE CLI and programmatic launchers. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Documentation improvement within existing engine integration; maintainer scope decision: not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `docs/jeb-analysis.md` - Contribution scope fit and linked maintainer decision: not applicable (documentation improvement) - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: JEB CE 5.48.0 on Linux x64 - 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: `tests/conformance/readmeConsistency.test.ts` - Base reproduction or other evidence: Source-derived against #4996 report and verified JEB CE 5.48.0.202610071539 CLI arguments. - User-visible CLI/MCP output (if applicable): not applicable - Remaining proof gaps: none ## Validation performed - `npm run format:check` — passed (oxfmt checked, all matched files use correct format) - `npm run check:fast` — 2 tasks successful (typecheck + lint passed without errors) - `npm run test:local -- tests/conformance/readmeConsistency.test.ts` — 5 passed (49ms) ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: platform-independent documentation - Package or release metadata impact: none - Security, privacy, process, or containment review: none ## 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 - [ ] 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:42: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#6725
No description provided.