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 #5430] [CLOSED] fix(native): declare filesystem write effect for inspect_signature #6928

New issue
Closed
opened 2026-11-01 21:44:07 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:44:07 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5430
Author: @prashantpiyush1111
Created: 10/20/2026
Status: ❌ Closed

Base: main ← Head: fix/native-signature-filesystem-effects

📝 Commits (5)

  • 12c656f fix(native): declare filesystem write effect for inspect_signature
  • 50100e5 fix(native): declare filesystem write effect for inspect_signature
  • 5217324 test(native): cover signature filesystem write effect
  • e7e80ec test(native): cover signature filesystem capability
  • 83346d0 test(native): cover signature filesystem write effect

📊 Changes

4 files changed (+26 additions, -2 deletions)

View changed files

📝 src/contracts/toolEffects.test.ts (+6 -0)
📝 src/contracts/toolEffects.ts (+5 -1)
➕ src/native/NativeMacOSProviderMetadata.test.ts (+13 -0)
📝 src/native/NativeMacOSProviderMetadata.ts (+2 -1)

📄 Description

Summary

Fixes #5423.

Correct discovery metadata for inspect_signature: the operation already creates and writes a private temporary snapshot, but its capability descriptor and canonical tool effects omit that filesystem effect.

Problem and expected behavior

Capability discovery currently omits may_write_filesystem for inspect_signature, and TOOL_EFFECTS.inspect_signature.writesFilesystem is false. Discovery should report both effects truthfully. The existing failure when the temporary parent is unwritable remains valid; this PR does not alter error classification or make inspection succeed in that environment.

Change and scope

  • Add inspect_signature to the native capability's filesystem-write declaration.
  • Give only inspect_signature canonical effects mutatesSession, launchesProcess, and writesFilesystem; leave other nativeEvidence entries unchanged.
  • Add focused regression coverage for capability discovery and TOOL_EFFECTS.
  • Ordinary fix within existing boundaries; maintainer scope decision: not applicable.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Native macOS capability metadata and canonical tool-effects declaration; discovery/effect projection.
  • Contribution scope fit and linked maintainer decision: Ordinary metadata correction within existing provider boundaries; not applicable.
  • CLI and MCP/tool-catalog contract: capabilities --json should advertise may_write_filesystem; canonical effects expose writesFilesystem. MCP annotations remain derived from canonical effects.
  • Provider, bridge, target-format, or platform compatibility: Metadata correction for the existing native macOS inspect_signature operation only.
  • Evidence, artifact, provenance, or reconstruction contract: No change.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): No implementation or cleanup behavior changed. The existing private snapshot and its cleanup/failure handling remain unchanged.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): No generated metadata is intentionally changed. Adding writesFilesystem should not change the current MCP annotation values because this tool already launches a process and mutates session state.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

The checkbox describes this metadata-only patch; it does not imply that the existing runtime operation has no process or filesystem effects.

Evidence and regression coverage

  • Tests added or updated: src/native/NativeMacOSProviderMetadata.test.ts asserts inspect_signature advertises mayWriteFilesystem === true and launchesProcess === true. src/contracts/toolEffects.test.ts asserts TOOL_EFFECTS.inspect_signature.writesFilesystem === true.
  • Base reproduction or other evidence: with the source change stashed and the new tests kept, both new tests fail with expected false to be true; with the change they pass (run by an AI assistant in a Linux sandbox on an equivalent patch).
  • User-visible CLI/MCP output: after npm run build, node scripts/rea.mjs capabilities --json reports effects ["launches_process", "may_write_filesystem"] for the capability containing inspect_signature (now grouped with observe_native_ui, which has identical effects).
  • Remaining proof gaps: the macOS runtime reproduction from #5423 was not executed. Full typecheck, knip, the full test suite and check:pr were not run locally; CI is the authority for those. No change was made to error classification or unwritable-temp behavior.
  • Brittleness check: inspected the capability inventory/effect projection path, annotationsFromEffects, the native inventory test, and the docs. No golden or documentation change was needed for this metadata-only correction. No broader audit of every native tool's temporary-file behavior was done; scope remains limited to inspect_signature.

For evidence-bearing changes:

  • 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

Run by an AI assistant in a Linux sandbox on this PR merged with main (Node v22.22.2, npm 10.9.7 — NOT the pinned 24.18.0 / 11.16.0):

  • npx oxfmt --check src/native src/contracts — pass
  • npm run lint — exit 0 (only pre-existing warnings; one max-lines warning on toolEffects.ts also exists on main)
  • targeted tsc over the 4 changed files — pass
  • npm run test:focused -- <new tests + nativeInventory golden> — 3 files, 28 tests passed
  • npx vitest run src/contracts src/native tests/boundary/providers/native tests/composition — 97 files passed, 1165 tests passed (14 skipped)
  • MCP tests nativeSignatureTargetBindingMcp, managedNativeVerificationAdapters — 4 passed
  • npm run verify:module-boundaries, npm run verify:architecture-guards, metadata:check, docs:check, test:python (81 OK), scan:todos, jscpd — pass

Not run: full tsc --noEmit (sandbox out of memory), knip (crashes in the sandbox on main too), full test:run, check:pr, macOS runtime repro.

Compatibility, safety, and release

  • Breaking changes or migration steps: None expected; this makes metadata truthful for existing behavior.
  • Real Hopper/Ghidra, browser, or OS coverage: The issue's macOS runtime reproduction was not executed.
  • Package or release metadata impact: None expected.
  • Security, privacy, process, or containment review: No new target interaction or filesystem operation; the existing private snapshot path and fail-closed behavior are unchanged.

Author readiness

Human owner: @prashantpiyush1111

  • 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.

Reviewer follow-up

  • Snapshot caching: isSnapshotCacheable permits caching only when mayWriteFilesystem === false, unless the descriptor explicitly sets cachePolicy: "snapshot". No cachePolicy override was found under src/native. Therefore this metadata correction can make inspect_signature ineligible for snapshot caching where it was previously eligible. I have not verified whether an active native-macos analysis profile currently caches this operation, so I am documenting this as a possible cache-eligibility change rather than claiming that runtime cache behavior was observed. This is consistent with the newly declared filesystem write.
  • CI: the latest PR-triggered workflow runs on this head are marked action_required; they did not execute. I have not represented them as passing. Maintainer approval/authorization may be required to run these workflows.

🔄 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/5430 **Author:** [@prashantpiyush1111](https://github.com/prashantpiyush1111) **Created:** 10/20/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/native-signature-filesystem-effects` --- ### 📝 Commits (5) - [`12c656f`](https://github.com/morluto/rea/commit/12c656f0944ede40d72ed16cc27cc7d6c9f53f43) fix(native): declare filesystem write effect for inspect_signature - [`50100e5`](https://github.com/morluto/rea/commit/50100e53c89aef48fbfa580c529388948d58061d) fix(native): declare filesystem write effect for inspect_signature - [`5217324`](https://github.com/morluto/rea/commit/52173242195371fb5df4c0281b8a8b665c34a741) test(native): cover signature filesystem write effect - [`e7e80ec`](https://github.com/morluto/rea/commit/e7e80ec40f4883f914ef06ffabd970ef03ec8e6c) test(native): cover signature filesystem capability - [`83346d0`](https://github.com/morluto/rea/commit/83346d00be8fbd60812054b2f72732d0fbf1d559) test(native): cover signature filesystem write effect ### 📊 Changes **4 files changed** (+26 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/contracts/toolEffects.test.ts` (+6 -0) 📝 `src/contracts/toolEffects.ts` (+5 -1) ➕ `src/native/NativeMacOSProviderMetadata.test.ts` (+13 -0) 📝 `src/native/NativeMacOSProviderMetadata.ts` (+2 -1) </details> ### 📄 Description ## Summary Fixes #5423. Correct discovery metadata for `inspect_signature`: the operation already creates and writes a private temporary snapshot, but its capability descriptor and canonical tool effects omit that filesystem effect. ## Problem and expected behavior Capability discovery currently omits `may_write_filesystem` for `inspect_signature`, and `TOOL_EFFECTS.inspect_signature.writesFilesystem` is false. Discovery should report both effects truthfully. The existing failure when the temporary parent is unwritable remains valid; this PR does not alter error classification or make inspection succeed in that environment. ## Change and scope - Add `inspect_signature` to the native capability's filesystem-write declaration. - Give only `inspect_signature` canonical effects `mutatesSession`, `launchesProcess`, and `writesFilesystem`; leave other `nativeEvidence` entries unchanged. - Add focused regression coverage for capability discovery and `TOOL_EFFECTS`. - Ordinary fix within existing boundaries; maintainer scope decision: not applicable. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: Native macOS capability metadata and canonical tool-effects declaration; discovery/effect projection. - Contribution scope fit and linked maintainer decision: Ordinary metadata correction within existing provider boundaries; not applicable. - CLI and MCP/tool-catalog contract: `capabilities --json` should advertise `may_write_filesystem`; canonical effects expose `writesFilesystem`. MCP annotations remain derived from canonical effects. - Provider, bridge, target-format, or platform compatibility: Metadata correction for the existing native macOS `inspect_signature` operation only. - Evidence, artifact, provenance, or reconstruction contract: No change. - Target selection, authority, upstream behavior, and cleanup details (if applicable): No implementation or cleanup behavior changed. The existing private snapshot and its cleanup/failure handling remain unchanged. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): No generated metadata is intentionally changed. Adding `writesFilesystem` should not change the current MCP annotation values because this tool already launches a process and mutates session state. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. The checkbox describes this metadata-only patch; it does not imply that the existing runtime operation has no process or filesystem effects. ## Evidence and regression coverage - Tests added or updated: `src/native/NativeMacOSProviderMetadata.test.ts` asserts `inspect_signature` advertises `mayWriteFilesystem === true` and `launchesProcess === true`. `src/contracts/toolEffects.test.ts` asserts `TOOL_EFFECTS.inspect_signature.writesFilesystem === true`. - Base reproduction or other evidence: with the source change stashed and the new tests kept, both new tests fail with `expected false to be true`; with the change they pass (run by an AI assistant in a Linux sandbox on an equivalent patch). - User-visible CLI/MCP output: after `npm run build`, `node scripts/rea.mjs capabilities --json` reports effects `["launches_process", "may_write_filesystem"]` for the capability containing `inspect_signature` (now grouped with `observe_native_ui`, which has identical effects). - Remaining proof gaps: the macOS runtime reproduction from #5423 was not executed. Full typecheck, knip, the full test suite and `check:pr` were not run locally; CI is the authority for those. No change was made to error classification or unwritable-temp behavior. - Brittleness check: inspected the capability inventory/effect projection path, `annotationsFromEffects`, the native inventory test, and the docs. No golden or documentation change was needed for this metadata-only correction. No broader audit of every native tool's temporary-file behavior was done; scope remains limited to `inspect_signature`. For evidence-bearing changes: - [ ] 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 Run by an AI assistant in a Linux sandbox on this PR merged with main (Node v22.22.2, npm 10.9.7 — NOT the pinned 24.18.0 / 11.16.0): - `npx oxfmt --check src/native src/contracts` — pass - `npm run lint` — exit 0 (only pre-existing warnings; one `max-lines` warning on `toolEffects.ts` also exists on main) - targeted `tsc` over the 4 changed files — pass - `npm run test:focused -- <new tests + nativeInventory golden>` — 3 files, 28 tests passed - `npx vitest run src/contracts src/native tests/boundary/providers/native tests/composition` — 97 files passed, 1165 tests passed (14 skipped) - MCP tests `nativeSignatureTargetBindingMcp`, `managedNativeVerificationAdapters` — 4 passed - `npm run verify:module-boundaries`, `npm run verify:architecture-guards`, `metadata:check`, `docs:check`, `test:python` (81 OK), `scan:todos`, `jscpd` — pass Not run: full `tsc --noEmit` (sandbox out of memory), `knip` (crashes in the sandbox on main too), full `test:run`, `check:pr`, macOS runtime repro. ## Compatibility, safety, and release - Breaking changes or migration steps: None expected; this makes metadata truthful for existing behavior. - Real Hopper/Ghidra, browser, or OS coverage: The issue's macOS runtime reproduction was not executed. - Package or release metadata impact: None expected. - Security, privacy, process, or containment review: No new target interaction or filesystem operation; the existing private snapshot path and fail-closed behavior are unchanged. ## Author readiness Human owner: @prashantpiyush1111 - [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. - [ ] 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. ## Reviewer follow-up - Snapshot caching: `isSnapshotCacheable` permits caching only when `mayWriteFilesystem === false`, unless the descriptor explicitly sets `cachePolicy: "snapshot"`. No `cachePolicy` override was found under `src/native`. Therefore this metadata correction can make `inspect_signature` ineligible for snapshot caching where it was previously eligible. I have not verified whether an active `native-macos` analysis profile currently caches this operation, so I am documenting this as a possible cache-eligibility change rather than claiming that runtime cache behavior was observed. This is consistent with the newly declared filesystem write. - CI: the latest PR-triggered workflow runs on this head are marked `action_required`; they did not execute. I have not represented them as passing. Maintainer approval/authorization may be required to run these workflows. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:44:07 +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#6928
No description provided.