[PR #4336] [MERGED] fix(javascript): preserve effective child-process stdio options #6183

New issue

Closed

opened 2026-10-31 01:12:30 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:12:30 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4336
Author: @Xinglan233
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/17/2026
Merged by: @morluto

Base: main ← Head: fix/3355-effective-stdio-11eb7480

---

📝 Commits (10+)

• 11eb748 fix(javascript): preserve effective child-process stdio options
• 696bf00 fix(javascript): retain proven callbacks and primitive stdio keys
• 0ee5b86 fix(javascript): preserve argv shapes and nullish spreads
• b4a466d fix(javascript): bound callable proofs and retain exposed binding uncertainty
• ed78525 test(javascript): keep callback acceptance within transport budget
• 3449b59 test(javascript): inspect application coverage for callback proof limits
• 250c0a9 fix(javascript): keep spread command argument slots uncertain
• 979dfd1 fix(javascript): adapt option proofs to current main
• 87d7203 fix(javascript): reject exposed object content proofs
• ea2607e fix(javascript): bound mapped argument content proofs

📊 Changes

18 files changed (+1114 additions, -93 deletions)

View changed files

📝 src/application/javascript/JavaScriptSemanticGraphChildProcessProjection.ts (+13 -1)
📝 src/domain/javascript/electronStaticAnalysisBrowser.ts (+6 -6)
📝 src/domain/javascript/electronStaticAnalysisValues.ts (+0 -21)
➕ src/domain/javascript/javascriptAstValues.test.ts (+72 -0)
📝 src/domain/javascript/javascriptAstValues.ts (+84 -15)
📝 src/domain/javascript/javascriptModuleDeclaration.ts (+15 -0)
📝 src/domain/javascript/javascriptRpcEndpoints.test.ts (+23 -0)
📝 src/domain/javascript/javascriptSemanticAnalysis.empty_keys.test.ts (+16 -0)
📝 src/domain/javascript/javascriptSemanticAnalysis.ts (+1 -0)
📝 src/domain/javascript/javascriptSemanticAnalysisSteps.test.ts (+24 -1)
📝 src/domain/javascript/javascriptSemanticChildProcesses.ts (+74 -43)
📝 src/domain/javascript/javascriptSemanticDerivedAnalysis.ts (+3 -0)
➕ src/domain/javascript/javascriptSemanticExpressionShapes.test.ts (+161 -0)
➕ src/domain/javascript/javascriptSemanticExpressionShapes.ts (+135 -0)
📝 src/domain/javascript/javascriptSourceParser.test.ts (+46 -1)
📝 src/domain/javascript/javascriptSourceParser.ts (+79 -5)
➕ tests/acceptance/applications/javascriptChildProcessStdioCli.test.ts (+359 -0)
📝 tests/boundary/filesystem/referenceSourceShadowedRequire.test.ts (+3 -0)

📄 Description

Summary

Fixes #3355. Respect the final effective child-process stdio property and preserve explicit uncertainty for unproved options and call layouts.

Prepared with assistance from OpenAI Codex.

Problem and expected behavior

In spawn("x", [], {stdio:"pipe", stdio:"inherit"}), the final property must win. Known non-overriding keys and spreads, including [+1], ...{} and unrelated copied methods, must preserve the effective value; unresolved writes must retain dynamic/candidate stdio.

Named argv/callback overloads require a stable local identity. In non-strict CommonJS, var argv=[]; {function argv(){}} can replace the outer array with a callback, so its stale initializer cannot prove the options slot. Value TypeScript module markers permit isolated local proofs, while erased syntax and unproved contexts must retain uncertainty.

Change and scope

Read object properties in reverse source order through one shared domain helper used by child-process, Electron, RPC and GraphQL readers. Inline object-literal spreads use the same effective lookup, bounded by the existing 256-level expression limit, including transparent spread wrappers. A missing inline property leaves the outer value intact; an effective explicit property wins. Inline getters retain side-effect uncertainty because copying can execute them and change another source key. Ordinary methods and setter-only members on unrelated keys are copied without invocation; requested-key methods/accessors remain unknown. Named/unknown spreads and unresolved computed keys stay conservative. Literal propertyless primitives and proved child nullish spreads are no-ops. Unary plus is recognized only on a numeric literal under existing transparent wrappers. Void keys remain exact without suppressing operand effects.

Select overloads using bounded array/callback identity from a single stable initializer chain and reuse collected lexical references. Parser-owned module/CommonJS facts, definite initialization, five wrapper-name exclusions, and eval/erased/transformed-scope guards govern proofs. Non-module block-function names conservatively block same-named var proofs. No named-object recovery, cross-statement evaluation or general interpreter is added.

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: Domain effective-property and child-argument identity readers; parser owns module/CommonJS/unknown context facts; graph projection retains unresolved stdio.
• Contribution scope fit and linked maintainer decision: Existing static-analysis boundary; separate maintainer decision not applicable.
• CLI and MCP/tool-catalog contract: Public schemas/catalog and internal worker IR remain unchanged. Unproved stdio retains candidate relations and unknown-value evidence.
• Provider, bridge, target-format, or platform compatibility: JavaScript/TypeScript static analysis; verified macOS arm64 source checkout.
• Evidence, artifact, provenance, or reconstruction contract: Retain child/source identities, complete Evidence, candidate/unknown endpoints and failed attempts.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): Analyze selected fixtures as inert text; verification starts REA and self-owned Node controls. The MCP server's exit was observed after close.
• 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 dependency, lockfile, package, release or committed generated-output change.

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.

Evidence and regression coverage

• Tests added or updated: Both public adapters exercise effective properties, overloads, source ranges, env/argv facts, candidate/unknown stdio and graph endpoints. Focused tests cover shared RPC lookup, ordinary copied methods versus getter mutations, requested-key accessor/computed-key guards, the inline-spread depth boundary, narrow unary-plus numeric keys, parser contexts, stable initializers and reference reuse.
• Base reproduction or other evidence: Node controls confirm an ordinary helper method is copied with zero invocations, while a getter executes once and can mutate the source stdio to pipe. Before the getter-only distinction, source-owner/shared-RPC regressions and both compiled adapters incorrectly reported the unrelated ordinary method as unknown; those regressions now pass.
• User-visible CLI/MCP output (if applicable): An eight-case final-commit control reports inherit/resolved for nested ordinary methods and an unrelated setter-only member. A mutating getter, requested-key method/setter, unknown computed method key, nested unknown spread and the unchanged string-spread control stay dynamic/candidate with unknown-value evidence. Complete normalized CLI/MCP results match; graph endpoints, MCP ping and owned-server exit checks pass.
• Remaining proof gaps: Inline lookup stops at its depth limit and does not follow named objects. String spreads and other primitive expressions remain conservative. Block-function names are conservative across the source; full Annex B strictness/copy eligibility is not modeled. Named nullish values, wrapper parameters and unproved initialization stay unknown. Ordinary .js/.ts sources whose sole module marker is import.meta retain unknown context. Alias, effect and array-content/count precision remains bounded; static facts do not prove runtime calls, completion or OS connections.

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

Verified commit: c035bcc0c06f8cdeccfd21d62a8aba2c1cb90353, macOS arm64, Node 24.18.0/npm 11.16.0 and locked dependencies.

• npm run check — passed, including typecheck, lint, format, knip, metadata, module boundaries and architecture guards.
• vitest run src/domain/javascript/ src/application/javascript/ src/javascript/analysis/ tests/boundary/filesystem/referenceSourceShadowedRequire.test.ts — 95 files, 2,325 tests passed.
• npm run test:focused -- tests/acceptance/applications/javascriptChildProcessStdioCli.test.ts tests/acceptance/applications/javascriptChildProcessArgumentsCli.test.ts tests/acceptance/applications/javascriptWindowOptionsCli.test.ts — 3 files, 5 tests passed.
• npm run docs:check — passed, including 5 README consistency tests. node scripts/verify-test-discovery.mjs discovered all 1,418 test files exactly once.
• Compiled CLI and real stdio MCP — the eight-case output, complete normalized-result parity, graph, ping and cleanup checks passed.
• Independent source review of this commit — no blockers. Nine independent method/getter, requested-key, computed/nested and property-precedence probes passed.
• npm test — not run; full-suite coverage remains incomplete.

GitHub CI and remote bot reviews have not established a pass for this commit. Full-suite, installed-package and external-provider verification remain unconfirmed.

Compatibility, safety, and release

• Breaking changes or migration steps: No public schema migration. Unproved stdio is represented by candidate relations and explicit unknowns.
• Real Hopper/Ghidra, browser, or OS coverage: macOS arm64 source-checkout CLI/stdio MCP and a self-owned Node control only. Linux/Windows, installed package, actual Electron/browsers, external engines and third-party clients are unverified on this commit.
• Package or release metadata impact: None.
• Security, privacy, process, or containment review: Static source analysis adds no execution/mutation/network authority. Performance was not benchmarked.

Author readiness

Human owner: @Xinglan233

• 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/4336 **Author:** [@Xinglan233](https://github.com/Xinglan233) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/17/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/3355-effective-stdio-11eb7480` --- ### 📝 Commits (10+) - [`11eb748`](https://github.com/morluto/rea/commit/11eb74804a84971c2738a3b630a5aab6053399ba) fix(javascript): preserve effective child-process stdio options - [`696bf00`](https://github.com/morluto/rea/commit/696bf0045e05649861288e013b4f176735c9f455) fix(javascript): retain proven callbacks and primitive stdio keys - [`0ee5b86`](https://github.com/morluto/rea/commit/0ee5b869bb1eb6cdaec83277998cbc67ca542299) fix(javascript): preserve argv shapes and nullish spreads - [`b4a466d`](https://github.com/morluto/rea/commit/b4a466dfa841ba80959652375c896af092152339) fix(javascript): bound callable proofs and retain exposed binding uncertainty - [`ed78525`](https://github.com/morluto/rea/commit/ed78525241c1b0db5d7e6b3b6266e54518107592) test(javascript): keep callback acceptance within transport budget - [`3449b59`](https://github.com/morluto/rea/commit/3449b5901be11520f5f463360fbf9ad93ee56190) test(javascript): inspect application coverage for callback proof limits - [`250c0a9`](https://github.com/morluto/rea/commit/250c0a9babf42d85b3f4a0b108226f8f437ac0ea) fix(javascript): keep spread command argument slots uncertain - [`979dfd1`](https://github.com/morluto/rea/commit/979dfd1eacfb0b97da7d91c2a04abd9517ec5623) fix(javascript): adapt option proofs to current main - [`87d7203`](https://github.com/morluto/rea/commit/87d7203f4b8f55b486b22a70eebe78ba834af352) fix(javascript): reject exposed object content proofs - [`ea2607e`](https://github.com/morluto/rea/commit/ea2607e986cf30b5433477d1c5012a9d938c8ddd) fix(javascript): bound mapped argument content proofs ### 📊 Changes **18 files changed** (+1114 additions, -93 deletions) <details> <summary>View changed files</summary> 📝 `src/application/javascript/JavaScriptSemanticGraphChildProcessProjection.ts` (+13 -1) 📝 `src/domain/javascript/electronStaticAnalysisBrowser.ts` (+6 -6) 📝 `src/domain/javascript/electronStaticAnalysisValues.ts` (+0 -21) ➕ `src/domain/javascript/javascriptAstValues.test.ts` (+72 -0) 📝 `src/domain/javascript/javascriptAstValues.ts` (+84 -15) 📝 `src/domain/javascript/javascriptModuleDeclaration.ts` (+15 -0) 📝 `src/domain/javascript/javascriptRpcEndpoints.test.ts` (+23 -0) 📝 `src/domain/javascript/javascriptSemanticAnalysis.empty_keys.test.ts` (+16 -0) 📝 `src/domain/javascript/javascriptSemanticAnalysis.ts` (+1 -0) 📝 `src/domain/javascript/javascriptSemanticAnalysisSteps.test.ts` (+24 -1) 📝 `src/domain/javascript/javascriptSemanticChildProcesses.ts` (+74 -43) 📝 `src/domain/javascript/javascriptSemanticDerivedAnalysis.ts` (+3 -0) ➕ `src/domain/javascript/javascriptSemanticExpressionShapes.test.ts` (+161 -0) ➕ `src/domain/javascript/javascriptSemanticExpressionShapes.ts` (+135 -0) 📝 `src/domain/javascript/javascriptSourceParser.test.ts` (+46 -1) 📝 `src/domain/javascript/javascriptSourceParser.ts` (+79 -5) ➕ `tests/acceptance/applications/javascriptChildProcessStdioCli.test.ts` (+359 -0) 📝 `tests/boundary/filesystem/referenceSourceShadowedRequire.test.ts` (+3 -0) </details> ### 📄 Description <!-- PR title: type(optional-scope): imperative outcome The title becomes the squash-merge commit subject and generated changelog entry. --> ## Summary <!-- What user, agent, or maintainer problem does this solve? Link the issue with "Fixes #123" when applicable. Keep the prior behavior, expected contract, and new behavior understandable without private context. --> Fixes #3355. Respect the final effective child-process stdio property and preserve explicit uncertainty for unproved options and call layouts. Prepared with assistance from OpenAI Codex. ## Problem and expected behavior <!-- For fixes, give the smallest trigger and violated invariant. For features, describe the use case and observable outcome. --> In `spawn("x", [], {stdio:"pipe", stdio:"inherit"})`, the final property must win. Known non-overriding keys and spreads, including `[+1]`, `...{}` and unrelated copied methods, must preserve the effective value; unresolved writes must retain dynamic/candidate stdio. Named argv/callback overloads require a stable local identity. In non-strict CommonJS, `var argv=[]; {function argv(){}}` can replace the outer array with a callback, so its stale initializer cannot prove the options slot. Value TypeScript module markers permit isolated local proofs, while erased syntax and unproved contexts must retain uncertainty. ## Change and scope <!-- Explain the chosen approach, why it fits REA's architecture, and what is intentionally not included. --> Read object properties in reverse source order through one shared domain helper used by child-process, Electron, RPC and GraphQL readers. Inline object-literal spreads use the same effective lookup, bounded by the existing 256-level expression limit, including transparent spread wrappers. A missing inline property leaves the outer value intact; an effective explicit property wins. Inline getters retain side-effect uncertainty because copying can execute them and change another source key. Ordinary methods and setter-only members on unrelated keys are copied without invocation; requested-key methods/accessors remain unknown. Named/unknown spreads and unresolved computed keys stay conservative. Literal propertyless primitives and proved child nullish spreads are no-ops. Unary plus is recognized only on a numeric literal under existing transparent wrappers. Void keys remain exact without suppressing operand effects. Select overloads using bounded array/callback identity from a single stable initializer chain and reuse collected lexical references. Parser-owned module/CommonJS facts, definite initialization, five wrapper-name exclusions, and eval/erased/transformed-scope guards govern proofs. Non-module block-function names conservatively block same-named var proofs. No named-object recovery, cross-statement evaluation or general interpreter is added. 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 <!-- Short answers are welcome. Complete applicable lines; mark unresolved facts as "unknown". Use "none" or "not applicable" only when established. --> - Semantic owner and earliest changed stage: Domain effective-property and child-argument identity readers; parser owns module/CommonJS/unknown context facts; graph projection retains unresolved stdio. - Contribution scope fit and linked maintainer decision: Existing static-analysis boundary; separate maintainer decision not applicable. - CLI and MCP/tool-catalog contract: Public schemas/catalog and internal worker IR remain unchanged. Unproved stdio retains candidate relations and unknown-value evidence. - Provider, bridge, target-format, or platform compatibility: JavaScript/TypeScript static analysis; verified macOS arm64 source checkout. - Evidence, artifact, provenance, or reconstruction contract: Retain child/source identities, complete Evidence, candidate/unknown endpoints and failed attempts. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Analyze selected fixtures as inert text; verification starts REA and self-owned Node controls. The MCP server's exit was observed after close. - 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 dependency, lockfile, package, release or committed generated-output change. 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. ## Evidence and regression coverage <!-- State whether evidence is executed, source-derived, or proposed. For fixes, show the original failure and explain how the regression would fail on the affected base revision when practical. Include the most useful proof inline; link long logs or artifacts, or put them in optional details. Documentation-only changes can use source, link, or rendered-document checks. --> - Tests added or updated: Both public adapters exercise effective properties, overloads, source ranges, env/argv facts, candidate/unknown stdio and graph endpoints. Focused tests cover shared RPC lookup, ordinary copied methods versus getter mutations, requested-key accessor/computed-key guards, the inline-spread depth boundary, narrow unary-plus numeric keys, parser contexts, stable initializers and reference reuse. - Base reproduction or other evidence: Node controls confirm an ordinary helper method is copied with zero invocations, while a getter executes once and can mutate the source stdio to pipe. Before the getter-only distinction, source-owner/shared-RPC regressions and both compiled adapters incorrectly reported the unrelated ordinary method as unknown; those regressions now pass. - User-visible CLI/MCP output (if applicable): An eight-case final-commit control reports `inherit/resolved` for nested ordinary methods and an unrelated setter-only member. A mutating getter, requested-key method/setter, unknown computed method key, nested unknown spread and the unchanged string-spread control stay `dynamic/candidate` with `unknown-value` evidence. Complete normalized CLI/MCP results match; graph endpoints, MCP ping and owned-server exit checks pass. - Remaining proof gaps: Inline lookup stops at its depth limit and does not follow named objects. String spreads and other primitive expressions remain conservative. Block-function names are conservative across the source; full Annex B strictness/copy eligibility is not modeled. Named nullish values, wrapper parameters and unproved initialization stay unknown. Ordinary .js/.ts sources whose sole module marker is `import.meta` retain unknown context. Alias, effect and array-content/count precision remains bounded; static facts do not prove runtime calls, completion or OS connections. For evidence-bearing changes: - [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 <!-- List only commands that actually ran, with observed results. Include the relevant real-provider or platform workflow, or explain why it was unavailable. Keep these results current after changes; a command without its result is incomplete. --> Verified commit: `c035bcc0c06f8cdeccfd21d62a8aba2c1cb90353`, macOS arm64, Node 24.18.0/npm 11.16.0 and locked dependencies. - `npm run check` — passed, including typecheck, lint, format, knip, metadata, module boundaries and architecture guards. - `vitest run src/domain/javascript/ src/application/javascript/ src/javascript/analysis/ tests/boundary/filesystem/referenceSourceShadowedRequire.test.ts` — 95 files, 2,325 tests passed. - `npm run test:focused -- tests/acceptance/applications/javascriptChildProcessStdioCli.test.ts tests/acceptance/applications/javascriptChildProcessArgumentsCli.test.ts tests/acceptance/applications/javascriptWindowOptionsCli.test.ts` — 3 files, 5 tests passed. - `npm run docs:check` — passed, including 5 README consistency tests. `node scripts/verify-test-discovery.mjs` discovered all 1,418 test files exactly once. - Compiled CLI and real stdio MCP — the eight-case output, complete normalized-result parity, graph, ping and cleanup checks passed. - Independent source review of this commit — no blockers. Nine independent method/getter, requested-key, computed/nested and property-precedence probes passed. - `npm test` — not run; full-suite coverage remains incomplete. GitHub CI and remote bot reviews have not established a pass for this commit. Full-suite, installed-package and external-provider verification remain unconfirmed. ## Compatibility, safety, and release <!-- Call out breaking changes, migrations, package effects, platform/provider limits, security/privacy/containment implications, and meaningful proof gaps. --> - Breaking changes or migration steps: No public schema migration. Unproved stdio is represented by candidate relations and explicit unknowns. - Real Hopper/Ghidra, browser, or OS coverage: macOS arm64 source-checkout CLI/stdio MCP and a self-owned Node control only. Linux/Windows, installed package, actual Electron/browsers, external engines and third-party clients are unverified on this commit. - Package or release metadata impact: None. - Security, privacy, process, or containment review: Static source analysis adds no execution/mutation/network authority. Performance was not benchmarked. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @Xinglan233 - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:12:30 +00:00

• closed this issue
• added the
  pull-request
  label

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

Subscribe

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#6183

No description provided.