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 #4365] [CLOSED] fix(domain): stop reporting a named-versus-unnamed reference endpoint as a change #6206

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4365
Author: @Henglie
Created: 10/16/2026
Status: ❌ Closed

Base: main ← Head: fix/reference-endpoint-asymmetry

📝 Commits (3)

  • ca8e524 fix(domain): stop reporting a named-versus-unnamed reference endpoint as a change
  • 9b25ec1 fix(domain): match reference edges by identity, not by sort position
  • fd08c24 fix(domain): pair reference edges by perfect matching, not greedily

📊 Changes

4 files changed (+533 additions, -32 deletions)

View changed files

📝 src/domain/functionComparison.test.ts (+242 -0)
📝 src/domain/functionComparisonDimensions.ts (+52 -15)
📝 src/domain/functionComparisonNormalization.ts (+37 -17)
➕ src/domain/functionComparisonReferenceMatching.ts (+202 -0)

📄 Description

Summary

compare_functions reported references: changed when one record resolved a
reference target to a procedure name and the other left it unresolved, even
though no known reference kind or named target differed. The same false
endpoint-change conclusion appeared within one artifact when both records
identified the same target address and only one supplied a procedure record. In
verify_reconstruction the first result became a definite fail.

The reference comparison now distinguishes a known difference from a knowledge
asymmetry, and the edge-kind projection no longer carries endpoint identity.

Fixes #4210.

Problem and expected behavior

compareReferences compared the two endpoint projections with canonical JSON
equality and reported any difference as changed. A projection entry is a
procedure name when the record resolved one, an address when it did not and the
artifacts are the same, and null when it did not and the artifacts differ. So
"helper" against null, and "helper" against {address} at the same address,
both read as differing endpoints even though one side simply recorded less.

referenceKindProjection embedded the same endpoints in every row, so the
asymmetry also reached the edge-semantics comparison and produced a change
there.

Expected: a known endpoint difference stays a change, a resolved endpoint
against an unresolved one is neither a difference nor an equality, and the
edge-kind comparison decides kinds.

Change and scope

  • src/domain/functionComparisonNormalization.ts
    • referenceEndpoint keeps the address alongside a resolved name within one
      artifact, because there the address is the target's identity and the name is
      supplementary. Across artifacts an address still names nothing, so only a
      resolved name survives and an unresolved endpoint stays null.
    • referenceKindProjection no longer projects endpoints. Endpoint identity is
      compared on its own, and the projection now decides edge semantics only,
      which is what its reported limitation already claimed.
    • sorted became generic, so projections keep their inferred element type
      instead of erasing it to unknown[].
  • src/domain/functionComparisonDimensions.ts: compareReferences compares
    endpoint lists pairwise with compareEndpoint, which returns equal,
    changed or asymmetric. A known difference is still reported immediately;
    an unresolved endpoint on either side is an asymmetry; within one artifact the
    address decides and a resolved name is supplementary.
  • src/domain/functionComparison.test.ts: three tests — the reported
    mixed-record cases now resolve to unknown across artifacts and unchanged
    inside one artifact; a real address difference beside a named and an unnamed
    target stays changed; and different named targets stay changed.

No schema, tool contract, or output shape changes. This is a fix inside existing
boundaries, so no maintainer scope decision is required ("not applicable").

Contract and boundary impact

  • Semantic owner and earliest changed stage: the references dimension of
    compare_functions, and the references verdict that feeds
    verify_reconstruction.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: unchanged in shape. The observable
    difference is the references dimension status and, through it, the overall
    comparison status and the verify_reconstruction verdict for records whose
    reference targets are resolved on one side only. Reported left/right
    values for same-artifact comparisons now carry the address alongside a
    resolved name, which is more of the recorded evidence rather than less.
  • Provider, bridge, target-format, or platform compatibility: none; the change
    is in provider-neutral domain logic.
  • Evidence, artifact, provenance, or reconstruction contract: the asymmetry is
    reported as a limitation instead of being asserted as a difference, so a
    definite fail in verify_reconstruction is no longer produced from a
    missing record.
  • Target selection, authority, upstream behavior, and cleanup details: not
    applicable; no execution, no writes.
  • Generated metadata: none.

Expected effects:

  • 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: three in src/domain/functionComparison.test.ts, inside the
    existing "function comparison unnamed reference endpoints" group.
  • Base reproduction: reverting functionComparisonDimensions.ts and
    functionComparisonNormalization.ts fails
    does not report a change when one record names the target and the other does not; restoring them passes. I ran both directions.
  • The other two added tests are controls and pass either way by design: a real
    address difference beside a named and an unnamed target stays changed, and
    different named targets stay changed. They exist so the fix cannot be
    widened into "report everything as unknown".
  • Regression coverage: functionComparison (58),
    reconstructionVerification.functionSources (69),
    staticRuntimeCorrelation (7), and the MCP boundary suites
    comparisonUnknownsMcp (3), functionComparisonCoverageMcp (1),
    functionComparisonMcp (8) and functionCallDirectionsMcp (1) — 147 passed.
    Those boundary suites compile the runtime, so the type change is covered by a
    real build.
  • Remaining proof gaps: the issue's reproduction drives the public MCP tool
    with inline Evidence; the regression here is at the comparison domain boundary
    the tool calls, and the MCP boundary suites exercise the same path. I did not
    re-run the issue's exact fixture script.

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

  • npm run test:focused -- src/domain/functionComparison.test.ts — 58 passed;
    the mixed-record test fails when the fix is reverted.
  • npm run test:focused -- src/domain/functionComparison.test.ts src/domain/reconstructionVerification.functionSources.test.ts src/domain/staticRuntimeCorrelation.test.ts tests/boundary/mcp/comparisonUnknownsMcp.test.ts tests/boundary/mcp/functionComparisonCoverageMcp.test.ts tests/boundary/mcp/functionComparisonMcp.test.ts tests/boundary/mcp/functionCallDirectionsMcp.test.ts — 147 passed.
  • npx tsc --noEmit — no errors in the changed files.
  • npx oxlint src/domain/ — 0 errors.
  • npx oxfmt <changed files> — applied.

Not run, and not claimed as passing: npm run check:fast (its deps:check
pre-step fails in this environment) and npm run test:acceptance. Expected to
be covered by CI.

Compatibility, safety, and release

  • Breaking changes or migration steps: none in shape. Two verdicts change from
    changed/fail to unknown, and one from changed to unchanged inside a
    single artifact; all three were false endpoints differences. Same-artifact
    reference projections gain the address next to a resolved name.
  • Real Hopper/Ghidra, browser, or OS coverage: not required; no provider engine
    is involved.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: comparison logic only; no
    new reads, writes or execution.

Author readiness

Human owner: @Henglie

  • 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/4365 **Author:** [@Henglie](https://github.com/Henglie) **Created:** 10/16/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/reference-endpoint-asymmetry` --- ### 📝 Commits (3) - [`ca8e524`](https://github.com/morluto/rea/commit/ca8e5240bf3a3a66e325be389d3f3c69dbd03772) fix(domain): stop reporting a named-versus-unnamed reference endpoint as a change - [`9b25ec1`](https://github.com/morluto/rea/commit/9b25ec1a1aa433c6b98f8747215e748760509bb7) fix(domain): match reference edges by identity, not by sort position - [`fd08c24`](https://github.com/morluto/rea/commit/fd08c245ab1e5a23adfdacda6970caba17b47308) fix(domain): pair reference edges by perfect matching, not greedily ### 📊 Changes **4 files changed** (+533 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/functionComparison.test.ts` (+242 -0) 📝 `src/domain/functionComparisonDimensions.ts` (+52 -15) 📝 `src/domain/functionComparisonNormalization.ts` (+37 -17) ➕ `src/domain/functionComparisonReferenceMatching.ts` (+202 -0) </details> ### 📄 Description ## Summary `compare_functions` reported `references: changed` when one record resolved a reference target to a procedure name and the other left it unresolved, even though no known reference kind or named target differed. The same false endpoint-change conclusion appeared within one artifact when both records identified the same target address and only one supplied a procedure record. In `verify_reconstruction` the first result became a definite `fail`. The reference comparison now distinguishes a known difference from a knowledge asymmetry, and the edge-kind projection no longer carries endpoint identity. Fixes #4210. ## Problem and expected behavior `compareReferences` compared the two endpoint projections with canonical JSON equality and reported any difference as `changed`. A projection entry is a procedure name when the record resolved one, an address when it did not and the artifacts are the same, and `null` when it did not and the artifacts differ. So "helper" against `null`, and "helper" against `{address}` at the same address, both read as differing endpoints even though one side simply recorded less. `referenceKindProjection` embedded the same endpoints in every row, so the asymmetry also reached the edge-semantics comparison and produced a change there. Expected: a known endpoint difference stays a change, a resolved endpoint against an unresolved one is neither a difference nor an equality, and the edge-kind comparison decides kinds. ## Change and scope - `src/domain/functionComparisonNormalization.ts` - `referenceEndpoint` keeps the address alongside a resolved name within one artifact, because there the address is the target's identity and the name is supplementary. Across artifacts an address still names nothing, so only a resolved name survives and an unresolved endpoint stays `null`. - `referenceKindProjection` no longer projects endpoints. Endpoint identity is compared on its own, and the projection now decides edge semantics only, which is what its reported limitation already claimed. - `sorted` became generic, so projections keep their inferred element type instead of erasing it to `unknown[]`. - `src/domain/functionComparisonDimensions.ts`: `compareReferences` compares endpoint lists pairwise with `compareEndpoint`, which returns `equal`, `changed` or `asymmetric`. A known difference is still reported immediately; an unresolved endpoint on either side is an asymmetry; within one artifact the address decides and a resolved name is supplementary. - `src/domain/functionComparison.test.ts`: three tests — the reported mixed-record cases now resolve to `unknown` across artifacts and `unchanged` inside one artifact; a real address difference beside a named and an unnamed target stays `changed`; and different named targets stay `changed`. No schema, tool contract, or output shape changes. This is a fix inside existing boundaries, so no maintainer scope decision is required ("not applicable"). ## Contract and boundary impact - Semantic owner and earliest changed stage: the `references` dimension of `compare_functions`, and the `references` verdict that feeds `verify_reconstruction`. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: unchanged in shape. The observable difference is the `references` dimension status and, through it, the overall comparison status and the `verify_reconstruction` verdict for records whose reference targets are resolved on one side only. Reported `left`/`right` values for same-artifact comparisons now carry the address alongside a resolved name, which is more of the recorded evidence rather than less. - Provider, bridge, target-format, or platform compatibility: none; the change is in provider-neutral domain logic. - Evidence, artifact, provenance, or reconstruction contract: the asymmetry is reported as a limitation instead of being asserted as a difference, so a definite `fail` in `verify_reconstruction` is no longer produced from a missing record. - Target selection, authority, upstream behavior, and cleanup details: not applicable; no execution, no writes. - Generated metadata: none. Expected effects: - [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 - Tests added: three in `src/domain/functionComparison.test.ts`, inside the existing "function comparison unnamed reference endpoints" group. - Base reproduction: reverting `functionComparisonDimensions.ts` and `functionComparisonNormalization.ts` fails `does not report a change when one record names the target and the other does not`; restoring them passes. I ran both directions. - The other two added tests are controls and pass either way by design: a real address difference beside a named and an unnamed target stays `changed`, and different named targets stay `changed`. They exist so the fix cannot be widened into "report everything as unknown". - Regression coverage: `functionComparison` (58), `reconstructionVerification.functionSources` (69), `staticRuntimeCorrelation` (7), and the MCP boundary suites `comparisonUnknownsMcp` (3), `functionComparisonCoverageMcp` (1), `functionComparisonMcp` (8) and `functionCallDirectionsMcp` (1) — 147 passed. Those boundary suites compile the runtime, so the type change is covered by a real build. - Remaining proof gaps: the issue's reproduction drives the public MCP tool with inline Evidence; the regression here is at the comparison domain boundary the tool calls, and the MCP boundary suites exercise the same path. I did not re-run the issue's exact fixture script. 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 - `npm run test:focused -- src/domain/functionComparison.test.ts` — 58 passed; the mixed-record test fails when the fix is reverted. - `npm run test:focused -- src/domain/functionComparison.test.ts src/domain/reconstructionVerification.functionSources.test.ts src/domain/staticRuntimeCorrelation.test.ts tests/boundary/mcp/comparisonUnknownsMcp.test.ts tests/boundary/mcp/functionComparisonCoverageMcp.test.ts tests/boundary/mcp/functionComparisonMcp.test.ts tests/boundary/mcp/functionCallDirectionsMcp.test.ts` — 147 passed. - `npx tsc --noEmit` — no errors in the changed files. - `npx oxlint src/domain/` — 0 errors. - `npx oxfmt <changed files>` — applied. Not run, and not claimed as passing: `npm run check:fast` (its `deps:check` pre-step fails in this environment) and `npm run test:acceptance`. Expected to be covered by CI. ## Compatibility, safety, and release - Breaking changes or migration steps: none in shape. Two verdicts change from `changed`/`fail` to `unknown`, and one from `changed` to `unchanged` inside a single artifact; all three were false endpoints differences. Same-artifact reference projections gain the address next to a resolved name. - Real Hopper/Ghidra, browser, or OS coverage: not required; no provider engine is involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: comparison logic only; no new reads, writes or execution. ## Author readiness Human owner: @Henglie - [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. - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:12:41 +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#6206
No description provided.