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 #2496] [MERGED] feat(captures): discover installed protocol and field definitions #5275

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2496
Author: @Olorinm
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @baron

Base: main ← Head: feat/packet-field-discovery

📝 Commits (8)

  • 69682f3 feat(captures): discover installed protocol and field definitions
  • f67ca1a test(captures): isolate the direct glossary oracle profile
  • 730158a test(captures): accept padded kernel limit reports
  • 44899da fix(captures): detach every retained glossary column
  • df821f8 fix(captures): describe every field discovery CLI option
  • f5d9724 test(captures): verify complete field discovery coverage
  • 9ca3c87 chore: synchronize field discovery with CI fixture fixes
  • b2aff43 fix(captures): retain discovery operation across cleanup retries

📊 Changes

19 files changed (+1095 additions, -219 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/SKILL.md (+3 -0)
📝 .github/workflows/real-packet-capture.yml (+1 -1)
📝 docs/packet-captures.md (+46 -0)
📝 scripts/verify-packet-capture.mjs (+150 -3)
📝 src/application/CapabilityInventory.ts (+1 -1)
📝 src/application/captures/PacketCaptureService.ts (+62 -8)
📝 src/captures/TsharkCaptureProvider.ts (+217 -125)
➕ src/captures/parseFieldDiscovery.ts (+92 -0)
📝 src/cli/captureCommands.ts (+67 -26)
📝 src/cliCommandNames.ts (+1 -0)
📝 src/contracts/captures/captureToolContracts.ts (+20 -0)
📝 src/contracts/toolEffects.ts (+5 -0)
➕ src/domain/captures/packetFields.ts (+100 -0)
📝 src/process/ArtifactAnalysisResources.ts (+27 -18)
📝 src/server/registerCaptureTools.ts (+13 -0)
📝 tests/boundary/captures/captureProvider.test.ts (+162 -2)
➕ tests/boundary/captures/fieldDiscovery.test.ts (+67 -0)
📝 tests/boundary/cli/captureCleanup.test.ts (+9 -0)
📝 tests/boundary/mcp/packetCaptureMcp.test.ts (+52 -35)

📄 Description

Summary

Add inspect_packet_fields / inspect-packet-fields so analysts can find the installed TShark protocol and field definitions before selecting fields for inspect_packet_capture. For example, { "kind": "fields", "protocol": "usb", "query": "idVendor" } returns usb.idVendor, its FT_UINT16 type, parent usb, display base and bitmask.

Problem and expected behavior

Capture inspection requires exact field names but currently offers no installation-specific discovery. Search protocol registrations or field definitions by literal substring, optionally selecting an exact protocol. Return 50 matches by default, offset/limit paging, explicit full output within resource limits, and examined/matching/returned counts. Duplicate abbreviations remain separate records with source line numbers. No linked issue: this is a focused follow-up to #2318.

Change and scope

Extend the existing TShark adapter and its shared CLI/MCP Evidence workflow. Reuse the same admission slot, owned process execution, executable verification, inherited Linux limits, private empty personal profile and retryable cleanup. The common resource owner accepts a per-request operation so discovery failures have the correct identity; it does not create a second queue. This small common-owner change is identical to #2487; both PRs are independently based on main.

Contract and boundary impact

  • Semantic owner: strict discovery schemas and one adapter parser for the native -G fields P/F grammar. Preserve names, types, parents, display bases, masks, descriptions and duplicate registrations.
  • Scope decision: not applicable; this extends an integrated provider's installation inspection, with no new provider or target execution/mutation authority.
  • CLI/MCP: additive tool/command; kind, protocol, query, offset, limit. CLI --all conflicts with --limit. Catalog registrations describe tool capabilities, not observed traffic.
  • Compatibility: existing Linux/TShark 4.x/util-linux requirements. Discovery reads no capture file and selects no interface.
  • Evidence: executable and limiter paths/digests, version/warnings, argv, selection and coverage. Global configuration, libraries and plugins remain trusted and are not fully fingerprinted; each request probes again, without caching or frozen-page claims.
  • Resources: the measured TShark 4.6.9 glossary is 22,303,197 bytes, so discovery alone allows 32 MiB producer output; capture analysis retains its 4 MiB cap. Parse incrementally, allocate only selected records, conservatively budget selected representation at 8 MiB, and copy every retained column out of the producer buffer. Over-budget/malformed output fails with captured diagnostics.
  • Installation/generated metadata: contracts, authored skill, guide and existing real-provider lane updated; no new dependencies or committed generated files.

Expected effects:

  • Read existing tool files and installation metadata.
  • Launch an owned local analysis process.
  • Create and clean a private temporary workspace/profile.

Evidence and regression coverage

Parser/provider tests cover duplicate registrations, malformed off-page records, paging/filtering/no matches, representation and command-output budgets, failed version probes, shared admission, executable changes, shutdown, cancellation and cleanup retry. MCP tests validate SDK-converted schemas and actionable unavailable results. Existing signal-provider regressions pass after the common-owner change.

The real verifier compares source ordinals and native field columns against direct TShark output under a separate empty profile; checks USB vendor-ID discovery, protocol paging, full UDP field selection, negative queries and CLI/MCP parity; and retains the existing packet-capture workflow and cleanup checks.

  • Observed facts and interpretation remain distinguishable.
  • Provenance and failed attempts remain preserved.
  • Coverage and unavailable outcomes remain explicit.

Validation performed

Cleanup follow-up on b2aff43e8: retained workspaces now keep the operation that acquired them alongside process ownership. Shutdown and pre-request cleanup retries use that identity, rather than the provider default or the next request's operation. Extended the existing field discovery boundary regression to reject a different operation while cleanup is pending, verify two failed shutdown attempts keep the original operation, and then complete cleanup. No public contract or execution scope changed.

  • Latest local validation: 62 focused regressions, npm run check, git diff --check, and a Gitleaks diff scan passed.
  • Native TShark verification on b2aff43e8 passed: 60 focused tests and 23 real CLI/MCP cases. Full CI is still running; the historical runs below apply to the preceding heads.

Earlier feature validation:

  • npm run check, npm run docs:check, npm run verify:test-discovery — passed; 1,023 test files discovered exactly once.
  • npm run jscpd — passed, 2.95% duplicated lines.
  • Focused local regression on the rebased head — 56 passed, including the product catalog, CLI help and portable advertised-pattern checks.
  • Linux verification on df821f83d — 60 tests and 23 real TShark CLI/MCP cases passed.
  • Full upstream CI on df821f83d — passed.
  • Final diff Gitleaks scan and git diff --check — passed.

Six discovery cases measured 651–761 ms per MCP call and 7.5–20.3 KB response envelopes. tokenx estimates including one tool definition, request and response were 6,634–11,253 tokens. Warm MCP server, fresh native processes, no filesystem-cache control; these are estimates, not billed usage or evidence of improved agent task completion.

Compatibility, safety, and release

No breaking call/configuration changes or migrations. macOS/Windows integration remains unsupported. The private profile does not sandbox installed plugins or libraries. Limits are per process/file, not aggregate quotas. Ambient environment is not serialized. Model-driven task selection, CPU time and peak process-family memory remain unmeasured; no cache or speedup claim.

Before merge

  • Concrete problem and one focused outcome; no material authority expansion.
  • Related upstream work and no-linked-issue reason stated above.
  • Observable behavior, meaningful failures and real public workflows covered.
  • Owning contracts/docs updated; ignored metadata regenerated and checked.
  • Final diff checked for secrets, unrelated cleanup and unsupported claims.

Summary by CodeRabbit

  • New Features
    • Added packet-field discovery through the command-line and MCP interfaces. Search installed protocol and field registrations, filter results, and page through matching records.
  • Improvements
    • Source-map comparisons now recognize Unicode-equivalent paths as possible matches while keeping ambiguous file identities unconfirmed.
    • Ghidra installation checks now account for declared Java version requirements and report unresolved or malformed installation metadata.
  • Bug Fixes
    • Invalid UTF-8 in APK metadata is now reported as unreadable output rather than silently replaced.

🔄 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/2496 **Author:** [@Olorinm](https://github.com/Olorinm) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@baron](https://github.com/baron) **Base:** `main` ← **Head:** `feat/packet-field-discovery` --- ### 📝 Commits (8) - [`69682f3`](https://github.com/morluto/rea/commit/69682f3a82611abdd005df20097e8c038425afbd) feat(captures): discover installed protocol and field definitions - [`f67ca1a`](https://github.com/morluto/rea/commit/f67ca1a4365cc6dcd6f4fb15912c9bb699176a5d) test(captures): isolate the direct glossary oracle profile - [`730158a`](https://github.com/morluto/rea/commit/730158a27fb38d3a298f80f462b5747e91e4cd81) test(captures): accept padded kernel limit reports - [`44899da`](https://github.com/morluto/rea/commit/44899dadc3f00f1f9069ce79d6b6f2ff0436a22d) fix(captures): detach every retained glossary column - [`df821f8`](https://github.com/morluto/rea/commit/df821f83d7575be07fc359039d2d379a1ce56080) fix(captures): describe every field discovery CLI option - [`f5d9724`](https://github.com/morluto/rea/commit/f5d9724066501701b2fa254d12208476d24323b8) test(captures): verify complete field discovery coverage - [`9ca3c87`](https://github.com/morluto/rea/commit/9ca3c87fc9148db7e20ca0a05501077259f381b0) chore: synchronize field discovery with CI fixture fixes - [`b2aff43`](https://github.com/morluto/rea/commit/b2aff43e8e83719e3b8672922f62ae038146b7ae) fix(captures): retain discovery operation across cleanup retries ### 📊 Changes **19 files changed** (+1095 additions, -219 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/SKILL.md` (+3 -0) 📝 `.github/workflows/real-packet-capture.yml` (+1 -1) 📝 `docs/packet-captures.md` (+46 -0) 📝 `scripts/verify-packet-capture.mjs` (+150 -3) 📝 `src/application/CapabilityInventory.ts` (+1 -1) 📝 `src/application/captures/PacketCaptureService.ts` (+62 -8) 📝 `src/captures/TsharkCaptureProvider.ts` (+217 -125) ➕ `src/captures/parseFieldDiscovery.ts` (+92 -0) 📝 `src/cli/captureCommands.ts` (+67 -26) 📝 `src/cliCommandNames.ts` (+1 -0) 📝 `src/contracts/captures/captureToolContracts.ts` (+20 -0) 📝 `src/contracts/toolEffects.ts` (+5 -0) ➕ `src/domain/captures/packetFields.ts` (+100 -0) 📝 `src/process/ArtifactAnalysisResources.ts` (+27 -18) 📝 `src/server/registerCaptureTools.ts` (+13 -0) 📝 `tests/boundary/captures/captureProvider.test.ts` (+162 -2) ➕ `tests/boundary/captures/fieldDiscovery.test.ts` (+67 -0) 📝 `tests/boundary/cli/captureCleanup.test.ts` (+9 -0) 📝 `tests/boundary/mcp/packetCaptureMcp.test.ts` (+52 -35) </details> ### 📄 Description ## Summary Add `inspect_packet_fields` / `inspect-packet-fields` so analysts can find the installed TShark protocol and field definitions before selecting fields for `inspect_packet_capture`. For example, `{ "kind": "fields", "protocol": "usb", "query": "idVendor" }` returns `usb.idVendor`, its `FT_UINT16` type, parent `usb`, display base and bitmask. ## Problem and expected behavior Capture inspection requires exact field names but currently offers no installation-specific discovery. Search protocol registrations or field definitions by literal substring, optionally selecting an exact protocol. Return 50 matches by default, offset/limit paging, explicit full output within resource limits, and examined/matching/returned counts. Duplicate abbreviations remain separate records with source line numbers. No linked issue: this is a focused follow-up to #2318. ## Change and scope Extend the existing TShark adapter and its shared CLI/MCP Evidence workflow. Reuse the same admission slot, owned process execution, executable verification, inherited Linux limits, private empty personal profile and retryable cleanup. The common resource owner accepts a per-request operation so discovery failures have the correct identity; it does not create a second queue. This small common-owner change is identical to #2487; both PRs are independently based on main. ## Contract and boundary impact - Semantic owner: strict discovery schemas and one adapter parser for the native `-G fields` P/F grammar. Preserve names, types, parents, display bases, masks, descriptions and duplicate registrations. - Scope decision: not applicable; this extends an integrated provider's installation inspection, with no new provider or target execution/mutation authority. - CLI/MCP: additive tool/command; `kind`, `protocol`, `query`, `offset`, `limit`. CLI `--all` conflicts with `--limit`. Catalog registrations describe tool capabilities, not observed traffic. - Compatibility: existing Linux/TShark 4.x/util-linux requirements. Discovery reads no capture file and selects no interface. - Evidence: executable and limiter paths/digests, version/warnings, argv, selection and coverage. Global configuration, libraries and plugins remain trusted and are not fully fingerprinted; each request probes again, without caching or frozen-page claims. - Resources: the measured TShark 4.6.9 glossary is 22,303,197 bytes, so discovery alone allows 32 MiB producer output; capture analysis retains its 4 MiB cap. Parse incrementally, allocate only selected records, conservatively budget selected representation at 8 MiB, and copy every retained column out of the producer buffer. Over-budget/malformed output fails with captured diagnostics. - Installation/generated metadata: contracts, authored skill, guide and existing real-provider lane updated; no new dependencies or committed generated files. Expected effects: - [x] Read existing tool files and installation metadata. - [x] Launch an owned local analysis process. - [x] Create and clean a private temporary workspace/profile. ## Evidence and regression coverage Parser/provider tests cover duplicate registrations, malformed off-page records, paging/filtering/no matches, representation and command-output budgets, failed version probes, shared admission, executable changes, shutdown, cancellation and cleanup retry. MCP tests validate SDK-converted schemas and actionable unavailable results. Existing signal-provider regressions pass after the common-owner change. The real verifier compares source ordinals and native field columns against direct TShark output under a separate empty profile; checks USB vendor-ID discovery, protocol paging, full UDP field selection, negative queries and CLI/MCP parity; and retains the existing packet-capture workflow and cleanup checks. - [x] Observed facts and interpretation remain distinguishable. - [x] Provenance and failed attempts remain preserved. - [x] Coverage and unavailable outcomes remain explicit. ## Validation performed Cleanup follow-up on `b2aff43e8`: retained workspaces now keep the operation that acquired them alongside process ownership. Shutdown and pre-request cleanup retries use that identity, rather than the provider default or the next request's operation. Extended the existing field discovery boundary regression to reject a different operation while cleanup is pending, verify two failed shutdown attempts keep the original operation, and then complete cleanup. No public contract or execution scope changed. - Latest local validation: 62 focused regressions, `npm run check`, `git diff --check`, and a Gitleaks diff scan passed. - [Native TShark verification on b2aff43e8](https://github.com/morluto/rea/actions/runs/38356702503) passed: 60 focused tests and 23 real CLI/MCP cases. Full CI is still running; the historical runs below apply to the preceding heads. Earlier feature validation: - `npm run check`, `npm run docs:check`, `npm run verify:test-discovery` — passed; 1,023 test files discovered exactly once. - `npm run jscpd` — passed, 2.95% duplicated lines. - Focused local regression on the rebased head — 56 passed, including the product catalog, CLI help and portable advertised-pattern checks. - [Linux verification on df821f83d](https://github.com/morluto/rea/actions/runs/38351726972) — 60 tests and 23 real TShark CLI/MCP cases passed. - [Full upstream CI on df821f83d](https://github.com/morluto/rea/actions/runs/38351727290) — passed. - Final diff Gitleaks scan and `git diff --check` — passed. Six discovery cases measured 651–761 ms per MCP call and 7.5–20.3 KB response envelopes. `tokenx` estimates including one tool definition, request and response were 6,634–11,253 tokens. Warm MCP server, fresh native processes, no filesystem-cache control; these are estimates, not billed usage or evidence of improved agent task completion. ## Compatibility, safety, and release No breaking call/configuration changes or migrations. macOS/Windows integration remains unsupported. The private profile does not sandbox installed plugins or libraries. Limits are per process/file, not aggregate quotas. Ambient environment is not serialized. Model-driven task selection, CPU time and peak process-family memory remain unmeasured; no cache or speedup claim. ## Before merge - [x] Concrete problem and one focused outcome; no material authority expansion. - [x] Related upstream work and no-linked-issue reason stated above. - [x] Observable behavior, meaningful failures and real public workflows covered. - [x] Owning contracts/docs updated; ignored metadata regenerated and checked. - [x] Final diff checked for secrets, unrelated cleanup and unsupported claims. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added packet-field discovery through the command-line and MCP interfaces. Search installed protocol and field registrations, filter results, and page through matching records. * **Improvements** * Source-map comparisons now recognize Unicode-equivalent paths as possible matches while keeping ambiguous file identities unconfirmed. * Ghidra installation checks now account for declared Java version requirements and report unresolved or malformed installation metadata. * **Bug Fixes** * Invalid UTF-8 in APK metadata is now reported as unreadable output rather than silently replaced. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:05:22 +00:00
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#5275
No description provided.