morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #2771] fix(ghidra): keep unreported Java bitness unknown #5380

New issue
Open
opened 2026-10-31 01:06:10 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:06:10 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2771
Author: @yasshmittal
Created: 10/13/2026
Status: 🔄 Open

Base: main ← Head: fix/ghidra-unknown-java-bitness

📝 Commits (10+)

  • 85f960c fix(ghidra): keep unreported Java bitness unknown
  • 2cfb259 fix(ghidra): retain malformed Java data-model text
  • 4443398 fix(ghidra): keep empty Java settings on their own line
  • e8315ea fix(ghidra): keep lossy Java data-model digits unparsed
  • 6e47205 fix(ghidra): reconcile unknown Java bitness with bounded probing
  • 93d5f95 fix(ghidra): keep Java setting values verbatim after the delimiter
  • ad06284 fix(ghidra): retain incomplete Java probe observations
  • a30bb98 test(ghidra): keep incomplete-observation cases in their own suite
  • 38c6cde fix(ghidra): retain mismatch facts in incomplete probes
  • c21fae9 fix(ghidra): classify incomplete Java mismatches

📊 Changes

3 files changed (+321 additions, -34 deletions)

View changed files

📝 src/ghidra/GhidraInstallation.test.ts (+131 -0)
📝 src/ghidra/GhidraInstallation.ts (+115 -34)
📝 tests/boundary/filesystem/ghidraJavaProbe.test.ts (+75 -0)

📄 Description

Summary

Fixes #2532.

When the Java settings probe reported version, home and VM name but omitted sun.arch.data.model, Ghidra inspection and doctor described the runtime as 0-bit and returned unsupported_version. The probe never established a bitness, so the result stated a measurement that did not exist.

Problem and expected behavior

The probe parser in src/ghidra/GhidraInstallation.ts substituted "0" for the absent property, and the Java check formatted that as a determined 0-bit runtime. AGENTS.md requires unresolved identity to stay unknown. Admission must still be refused until a 64-bit JDK is established, but without claiming a measured incompatible bitness.

Change and scope

  • GhidraJavaObservation.bits is now number | null. The parser returns null when the property is absent or is not a decimal value.
  • A reported value that is not an exactly representable decimal (non-digits, or digits beyond the safe-integer range) is retained as unparsedBits, so absent and malformed reports stay distinguishable (review feedback).
  • javaProperty matches horizontal whitespace only, so an explicitly empty setting returns "" instead of absorbing the next line (review feedback). An empty java.version or java.home still cannot identify the runtime.
  • The Java check describes these as bitness unknown or bitness unknown (sun.arch.data.model = "64-bit") and still fails.
  • When unknown bitness is the only unestablished requirement, the check code is version_unresolved. Known mismatches (32-bit, JRE, wrong major version) keep unsupported_version.

Judgment call for review: the issue does not name a code for unknown bitness. I chose the existing version_unresolved because the runtime's required identity is unresolved rather than known to be incompatible. If you prefer to keep unsupported_version, that is a one-line change and the bitness unknown wording fix stands on its own.

Contribution scope: an ordinary fix within existing boundaries; no maintainer scope decision applies.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Java settings parsing in the system Ghidra installation host (probeJava).

  • Contribution scope fit and linked maintainer decision: not applicable (bug fix).

  • CLI and MCP/tool-catalog contract: the doctor/provider Java check detail changes from 0-bit to bitness unknown, and its code becomes version_unresolved in that case. No schema change.

  • Provider, bridge, target-format, or platform compatibility: JDKs that report bitness behave exactly as before.

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

  • Target selection, authority, upstream behavior, and cleanup details: Ghidra is not launched; admission still requires an established 64-bit JDK.

  • Generated metadata, package, or installation impact: none.

  • Read existing files or captured data.

  • Launch or attach to a process. (Existing behavior: the java -XshowSettings:properties -version probe, unchanged.)

Evidence and regression coverage

  • Tests added or updated:

    • tests/boundary/filesystem/ghidraJavaProbe.test.ts: the real parser on probe output without sun.arch.data.model gives a failed check, version_unresolved, and detail 21.0.11; bitness unknown; JDK;. An empty sun.arch.data.model = line keeps "" instead of reading the next line. A lossy 9007199254740993 keeps its text instead of reporting 9007199254740992-bit. A malformed 64junk gives version_unresolved and retains the reported text; on the base revision parseInt read it as 64 and the check passed. A 32 control gives 32-bit and unsupported_version.
    • src/ghidra/GhidraInstallation.test.ts: two rows in the existing check-code table (32-bit and unreported bitness).

  • Base reproduction or other evidence: run against the base GhidraInstallation.ts, the new boundary test fails with detail 21.0.11; 0-bit; JDK; …; with this change it passes.

  • User-visible CLI/MCP output: Java check detail 21.0.11; bitness unknown; JDK; <home>; accepted a 64-bit full JDK 21 or newer.

  • Remaining proof gaps: no real JDK that omits the property is known; this was exercised with controlled probe output, as in the issue.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Host: Windows 11, Node.js 24.21.0.

  • npx vitest run --project boundary tests/boundary/filesystem/ghidraJavaProbe.test.ts: 8 passed (fails on the base revision as described above).
  • npm run test:local -- src/ghidra/GhidraInstallation.test.ts: 53 passed.
  • npm run check: passed.
  • npm run verify:test-discovery: passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Behavior changes only when the probe omits bitness.
  • Real Hopper/Ghidra, browser, or OS coverage: Windows only; no real Ghidra lane run (Ghidra is not launched by this path).
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new processes or I/O; admission stays fail-closed.

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.

🤖 Generated with Claude Code

🔄 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/2771 **Author:** [@yasshmittal](https://github.com/yasshmittal) **Created:** 10/13/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/ghidra-unknown-java-bitness` --- ### 📝 Commits (10+) - [`85f960c`](https://github.com/morluto/rea/commit/85f960ccc10ab8c3822aa3976643a0b55b2a12e4) fix(ghidra): keep unreported Java bitness unknown - [`2cfb259`](https://github.com/morluto/rea/commit/2cfb259d57fe38afd78f17d1d6ddc8a0ef7f7c72) fix(ghidra): retain malformed Java data-model text - [`4443398`](https://github.com/morluto/rea/commit/44433989a04d0165184a6538d8d95a0ee91929a9) fix(ghidra): keep empty Java settings on their own line - [`e8315ea`](https://github.com/morluto/rea/commit/e8315ea304f557733c826d49c97ad6a5ac1369cb) fix(ghidra): keep lossy Java data-model digits unparsed - [`6e47205`](https://github.com/morluto/rea/commit/6e47205540a3c0e8591f2080b50c9d08776b50b2) fix(ghidra): reconcile unknown Java bitness with bounded probing - [`93d5f95`](https://github.com/morluto/rea/commit/93d5f956109d77413ffde253f915167ba338551f) fix(ghidra): keep Java setting values verbatim after the delimiter - [`ad06284`](https://github.com/morluto/rea/commit/ad062848f63b11d5df9c4f0bd91752a7b2d2d3ab) fix(ghidra): retain incomplete Java probe observations - [`a30bb98`](https://github.com/morluto/rea/commit/a30bb988f34a6c5a30098484da3a3c7b5b3ccad6) test(ghidra): keep incomplete-observation cases in their own suite - [`38c6cde`](https://github.com/morluto/rea/commit/38c6cde298795ae04f67ab9c8de1b185a4830af1) fix(ghidra): retain mismatch facts in incomplete probes - [`c21fae9`](https://github.com/morluto/rea/commit/c21fae98ae18ff8f8d3c99193ed1ab01d30d18ca) fix(ghidra): classify incomplete Java mismatches ### 📊 Changes **3 files changed** (+321 additions, -34 deletions) <details> <summary>View changed files</summary> 📝 `src/ghidra/GhidraInstallation.test.ts` (+131 -0) 📝 `src/ghidra/GhidraInstallation.ts` (+115 -34) 📝 `tests/boundary/filesystem/ghidraJavaProbe.test.ts` (+75 -0) </details> ### 📄 Description ## Summary Fixes #2532. When the Java settings probe reported version, home and VM name but omitted `sun.arch.data.model`, Ghidra inspection and doctor described the runtime as `0-bit` and returned `unsupported_version`. The probe never established a bitness, so the result stated a measurement that did not exist. ## Problem and expected behavior The probe parser in `src/ghidra/GhidraInstallation.ts` substituted `"0"` for the absent property, and the Java check formatted that as a determined `0-bit` runtime. AGENTS.md requires unresolved identity to stay unknown. Admission must still be refused until a 64-bit JDK is established, but without claiming a measured incompatible bitness. ## Change and scope - `GhidraJavaObservation.bits` is now `number | null`. The parser returns `null` when the property is absent or is not a decimal value. - A reported value that is not an exactly representable decimal (non-digits, or digits beyond the safe-integer range) is retained as `unparsedBits`, so absent and malformed reports stay distinguishable (review feedback). - `javaProperty` matches horizontal whitespace only, so an explicitly empty setting returns `""` instead of absorbing the next line (review feedback). An empty `java.version` or `java.home` still cannot identify the runtime. - The Java check describes these as `bitness unknown` or `bitness unknown (sun.arch.data.model = "64-bit")` and still fails. - When unknown bitness is the only unestablished requirement, the check code is `version_unresolved`. Known mismatches (32-bit, JRE, wrong major version) keep `unsupported_version`. Judgment call for review: the issue does not name a code for unknown bitness. I chose the existing `version_unresolved` because the runtime's required identity is unresolved rather than known to be incompatible. If you prefer to keep `unsupported_version`, that is a one-line change and the `bitness unknown` wording fix stands on its own. Contribution scope: an ordinary fix within existing boundaries; no maintainer scope decision applies. ## Contract and boundary impact - Semantic owner and earliest changed stage: Java settings parsing in the system Ghidra installation host (`probeJava`). - Contribution scope fit and linked maintainer decision: not applicable (bug fix). - CLI and MCP/tool-catalog contract: the doctor/provider Java check detail changes from `0-bit` to `bitness unknown`, and its code becomes `version_unresolved` in that case. No schema change. - Provider, bridge, target-format, or platform compatibility: JDKs that report bitness behave exactly as before. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Target selection, authority, upstream behavior, and cleanup details: Ghidra is not launched; admission still requires an established 64-bit JDK. - Generated metadata, package, or installation impact: none. - [x] Read existing files or captured data. - [x] Launch or attach to a process. (Existing behavior: the `java -XshowSettings:properties -version` probe, unchanged.) ## Evidence and regression coverage - Tests added or updated: - `tests/boundary/filesystem/ghidraJavaProbe.test.ts`: the real parser on probe output without `sun.arch.data.model` gives a failed check, `version_unresolved`, and detail `21.0.11; bitness unknown; JDK;`. An empty `sun.arch.data.model =` line keeps `""` instead of reading the next line. A lossy `9007199254740993` keeps its text instead of reporting `9007199254740992-bit`. A malformed `64junk` gives `version_unresolved` and retains the reported text; on the base revision `parseInt` read it as 64 and the check passed. A `32` control gives `32-bit` and `unsupported_version`. - `src/ghidra/GhidraInstallation.test.ts`: two rows in the existing check-code table (32-bit and unreported bitness). - Base reproduction or other evidence: run against the base `GhidraInstallation.ts`, the new boundary test fails with detail `21.0.11; 0-bit; JDK; …`; with this change it passes. - User-visible CLI/MCP output: Java check detail `21.0.11; bitness unknown; JDK; <home>; accepted a 64-bit full JDK 21 or newer`. - Remaining proof gaps: no real JDK that omits the property is known; this was exercised with controlled probe output, as in the issue. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed Host: Windows 11, Node.js 24.21.0. - `npx vitest run --project boundary tests/boundary/filesystem/ghidraJavaProbe.test.ts`: 8 passed (fails on the base revision as described above). - `npm run test:local -- src/ghidra/GhidraInstallation.test.ts`: 53 passed. - `npm run check`: passed. - `npm run verify:test-discovery`: passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Behavior changes only when the probe omits bitness. - Real Hopper/Ghidra, browser, or OS coverage: Windows only; no real Ghidra lane run (Ghidra is not launched by this path). - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new processes or I/O; admission stays fail-closed. ## 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <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 Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#5380
No description provided.