[PR #6753] [CLOSED] fix(environment): preserve astral token boundaries #7406

New issue

Closed

opened 2026-11-01 21:47:38 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:47:38 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6753
Author: @gongfpp
Created: 10/23/2026
Status: ❌ Closed

Base: main ← Head: fix/environment-unicode-delimiters-6635

---

📝 Commits (1)

• 56fae12 fix(environment): preserve astral token boundaries

📊 Changes

3 files changed (+99 additions, -6 deletions)

View changed files

📝 src/domain/analysisView/environmentStateWriteValues.test.ts (+12 -0)
📝 src/domain/analysisView/environmentStateWriteValues.ts (+5 -5)
📝 tests/boundary/mcp/environmentServeWritesMcp.test.ts (+82 -1)

📄 Description

Summary

Fixes #6635. Preserve astral Unicode words when rebuilding delimited identifiers in captured environment state.

Problem and expected behavior

delimitedOffsets checked one UTF-16 code unit on either side of a match. Half of an astral letter or number does not match the existing Unicode letter/number predicate, so a token inside 𐐀3𐐁 or 𝟙3𝟚 was incorrectly eligible for replacement. A later served create could silently change those strings to contain the new entity id.

Complete neighboring code points must determine word boundaries; returned offsets must remain UTF-16 indices for existing slice-based consumers. Emoji and path punctuation must remain valid delimiters.

Change and scope

Inspect at most two UTF-16 units per neighbor with anchored versions of the existing Unicode letter/number predicate. Preserve empty-token handling, accepted-match stepping, and rejected overlapping-match search. Remove the superseded single-unit helper; existing consumers require no changes.

This is a narrow correction at the shared producer, not a state-target redesign or a new provider. PR #6385 has adjacent consumer/test work but does not change this helper; this PR does not alter its consumers or shared fixtures.

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: delimitedOffsets in environmentStateWriteValues.ts, before template inference/replacement.
• Contribution scope fit and linked maintainer decision: not applicable; ordinary correctness fix within existing captured-state reconstruction boundaries. No new execution, injection, or target-mutation capability.
• CLI and MCP/tool-catalog contract: no schema, command, or catalog changes; existing served create/read tools now preserve Unicode words correctly.
• Provider, bridge, target-format, or platform compatibility: no new dependency or platform requirement; offsets remain UTF-16.
• Evidence, artifact, provenance, or reconstruction contract: existing capture identities and provenance unchanged; only incorrectly inferred token boundaries are corrected.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged. Boundary tests use synthetic captures, the compiled local CLI, a loopback MCP server, and the existing managed-process/temporary-directory fixtures; no external target or browser is required.
• 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): none; generated artifacts checked, not committed.

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.

Process/network effects above describe the existing local CLI/MCP verification workflow, not new target interaction. The test server contacts only its loopback client.

Evidence and regression coverage

• Tests added or updated: twelve delimiter-table cases covering astral letters/numbers on both sides, mixed rejected/accepted matches, UTF-16 offsets after emoji, astral tokens, and ASCII/path controls. Existing overlap and empty-token cases retained.
• Base reproduction or other evidence: applied only the final two test-file changes to a detached 2bcd7e6d13f0a8118d6619718254255e84f75d86 worktree. The two-file run failed with 9 failures (8 delimiter cases plus the served MCP regression), demonstrating that the final fixture reaches the bug rather than merely failing to expose a tool.
• User-visible CLI/MCP output (if applicable): the added boundary test starts the compiled rea environment-serve, connects the real MCP SDK client, and creates/reads ids 3 and 4. For id 4, letter: "𐐀3𐐁", digit: "𝟙3𝟚", and the one-sided Unicode words remain unchanged, while emoji: "😀4😀" and path: "/books/4" update. Create/read return status 201/200 and state-backed typed results. The affected base instead rewrites the Unicode words with id 4.
• Remaining proof gaps: synthetic captured-state workflow, not a live browser/provider capture. The full test suite and other operating systems were not run locally. Independent review was static; runtime evidence comes from the executed tests below.

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

Executed on macOS with Node 24.22.1 and npm 11.16.0, on head 56fae12c175cf285a051d3426134a59081a78d35 rebased onto main 5f702dd6ccd9e8e505e224854b91678439c3b41f:

• npm run test:focused -- src/domain/analysisView/environmentStateWriteValues.test.ts src/domain/analysisView/environmentStateWriteExplain.test.ts src/domain/analysisView/environmentStateWriteApply.test.ts src/domain/analysisView/environmentStateWrites.test.ts src/application/environment/environmentStateWriteAnswer.test.ts tests/boundary/mcp/environmentServeWritesMcp.test.ts — 420 passed, including both real CLI/MCP boundary tests.
• npm run check:fast — typecheck and lint passed.
• npm run docs:check — generated metadata/document facts/license checks passed; README consistency 9 passed.
• git diff --check — passed; worktree clean after commit/rebase.

Current-head CI status

CI 39967057574 on 56fae12c175cf285a051d3426134a59081a78d35 finished failure, not green. Its Source tests report four failures: environment bundle discovery-budget fixture, repeated-query exactness fixture, webpack:// source-map resolution, and ELF note remediation text. I ran those same four suites on the unmodified exact parent 5f702dd6ccd9e8e505e224854b91678439c3b41f (Node 24.22.1/npm 11.16.0): the same four cases fail, 36 controls pass. These are upstream production/test-contract conflicts; this Unicode delimiter PR does not include unrelated fixes. The existing base CI is separate evidence, not claimed successful. Built-test attribution is now complete for the observed failures: only shard 5 actually failed, with the two javascriptIndirectLoaderOwners.test.ts require.resolve CLI/MCP cases (resolved expected, unavailable observed). The unmodified exact parent shard 5 independently failed the same two cases, at the same assertion and with identical totals (2 failed / 1879 passed / 35 skipped). Shards 3/4/6/8 were cancelled by matrix fail-fast, not four additional demonstrated regressions; cancelled coverage is not claimed passed. Portable tests and CI required are downstream failures. The current-head CI remains red; no unrelated source, loader-ownership or CI-policy changes are bundled here. Baseline coordination is needed before claiming full qualification.

Compatibility, safety, and release

• Breaking changes or migration steps: none; preserve the documented Unicode letter/number boundary rule and existing UTF-16 offset contract.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable to this pure producer fix; no such provider exercised. Real compiled CLI/MCP exercised locally on macOS.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: no new authority or external service access; synthetic data only. No speculative security expansion or unrelated cleanup.

Author readiness

Human owner: @gongfpp

• 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/6753 **Author:** [@gongfpp](https://github.com/gongfpp) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/environment-unicode-delimiters-6635` --- ### 📝 Commits (1) - [`56fae12`](https://github.com/morluto/rea/commit/56fae12c175cf285a051d3426134a59081a78d35) fix(environment): preserve astral token boundaries ### 📊 Changes **3 files changed** (+99 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/analysisView/environmentStateWriteValues.test.ts` (+12 -0) 📝 `src/domain/analysisView/environmentStateWriteValues.ts` (+5 -5) 📝 `tests/boundary/mcp/environmentServeWritesMcp.test.ts` (+82 -1) </details> ### 📄 Description ## Summary Fixes #6635. Preserve astral Unicode words when rebuilding delimited identifiers in captured environment state. ## Problem and expected behavior `delimitedOffsets` checked one UTF-16 code unit on either side of a match. Half of an astral letter or number does not match the existing Unicode letter/number predicate, so a token inside `𐐀3𐐁` or `𝟙3𝟚` was incorrectly eligible for replacement. A later served create could silently change those strings to contain the new entity id. Complete neighboring code points must determine word boundaries; returned offsets must remain UTF-16 indices for existing slice-based consumers. Emoji and path punctuation must remain valid delimiters. ## Change and scope Inspect at most two UTF-16 units per neighbor with anchored versions of the existing Unicode letter/number predicate. Preserve empty-token handling, accepted-match stepping, and rejected overlapping-match search. Remove the superseded single-unit helper; existing consumers require no changes. This is a narrow correction at the shared producer, not a state-target redesign or a new provider. PR #6385 has adjacent consumer/test work but does not change this helper; this PR does not alter its consumers or shared fixtures. 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: `delimitedOffsets` in `environmentStateWriteValues.ts`, before template inference/replacement. - Contribution scope fit and linked maintainer decision: not applicable; ordinary correctness fix within existing captured-state reconstruction boundaries. No new execution, injection, or target-mutation capability. - CLI and MCP/tool-catalog contract: no schema, command, or catalog changes; existing served create/read tools now preserve Unicode words correctly. - Provider, bridge, target-format, or platform compatibility: no new dependency or platform requirement; offsets remain UTF-16. - Evidence, artifact, provenance, or reconstruction contract: existing capture identities and provenance unchanged; only incorrectly inferred token boundaries are corrected. - Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged. Boundary tests use synthetic captures, the compiled local CLI, a loopback MCP server, and the existing managed-process/temporary-directory fixtures; no external target or browser is required. - 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): none; generated artifacts checked, not committed. 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. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [x] 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. Process/network effects above describe the existing local CLI/MCP verification workflow, not new target interaction. The test server contacts only its loopback client. ## Evidence and regression coverage - Tests added or updated: twelve delimiter-table cases covering astral letters/numbers on both sides, mixed rejected/accepted matches, UTF-16 offsets after emoji, astral tokens, and ASCII/path controls. Existing overlap and empty-token cases retained. - Base reproduction or other evidence: applied only the final two test-file changes to a detached `2bcd7e6d13f0a8118d6619718254255e84f75d86` worktree. The two-file run failed with **9 failures** (8 delimiter cases plus the served MCP regression), demonstrating that the final fixture reaches the bug rather than merely failing to expose a tool. - User-visible CLI/MCP output (if applicable): the added boundary test starts the compiled `rea environment-serve`, connects the real MCP SDK client, and creates/reads ids 3 and 4. For id 4, `letter: "𐐀3𐐁"`, `digit: "𝟙3𝟚"`, and the one-sided Unicode words remain unchanged, while `emoji: "😀4😀"` and `path: "/books/4"` update. Create/read return status 201/200 and state-backed typed results. The affected base instead rewrites the Unicode words with id 4. - Remaining proof gaps: synthetic captured-state workflow, not a live browser/provider capture. The full test suite and other operating systems were not run locally. Independent review was static; runtime evidence comes from the executed tests below. 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 Executed on macOS with Node **24.22.1** and npm **11.16.0**, on head `56fae12c175cf285a051d3426134a59081a78d35` rebased onto main `5f702dd6ccd9e8e505e224854b91678439c3b41f`: - `npm run test:focused -- src/domain/analysisView/environmentStateWriteValues.test.ts src/domain/analysisView/environmentStateWriteExplain.test.ts src/domain/analysisView/environmentStateWriteApply.test.ts src/domain/analysisView/environmentStateWrites.test.ts src/application/environment/environmentStateWriteAnswer.test.ts tests/boundary/mcp/environmentServeWritesMcp.test.ts` — **420 passed**, including both real CLI/MCP boundary tests. - `npm run check:fast` — typecheck and lint passed. - `npm run docs:check` — generated metadata/document facts/license checks passed; README consistency **9 passed**. - `git diff --check` — passed; worktree clean after commit/rebase. ### Current-head CI status CI [39967057574](https://github.com/morluto/rea/actions/runs/39967057574) on `56fae12c175cf285a051d3426134a59081a78d35` finished **failure**, not green. Its [Source tests](https://github.com/morluto/rea/actions/runs/39967057574/job/120460486845) report four failures: environment bundle discovery-budget fixture, repeated-query exactness fixture, `webpack://` source-map resolution, and ELF note remediation text. I ran those same four suites on the **unmodified exact parent** `5f702dd6ccd9e8e505e224854b91678439c3b41f` (Node 24.22.1/npm 11.16.0): **the same four cases fail, 36 controls pass**. These are upstream production/test-contract conflicts; this Unicode delimiter PR does not include unrelated fixes. The existing [base CI](https://github.com/morluto/rea/actions/runs/39966102793) is separate evidence, not claimed successful. Built-test attribution is now complete for the observed failures: only [shard 5](https://github.com/morluto/rea/actions/runs/39967057574/job/120460882736) actually failed, with the two `javascriptIndirectLoaderOwners.test.ts` require.resolve CLI/MCP cases (`resolved` expected, `unavailable` observed). The **unmodified exact parent** [shard 5](https://github.com/morluto/rea/actions/runs/39966102793/job/120470561053) independently failed the **same two cases**, at the same assertion and with identical totals (2 failed / 1879 passed / 35 skipped). Shards 3/4/6/8 were **cancelled by matrix fail-fast**, not four additional demonstrated regressions; cancelled coverage is not claimed passed. Portable tests and CI required are downstream failures. The current-head CI remains red; no unrelated source, loader-ownership or CI-policy changes are bundled here. Baseline coordination is needed before claiming full qualification. ## Compatibility, safety, and release - Breaking changes or migration steps: none; preserve the documented Unicode letter/number boundary rule and existing UTF-16 offset contract. - Real Hopper/Ghidra, browser, or OS coverage: not applicable to this pure producer fix; no such provider exercised. Real compiled CLI/MCP exercised locally on macOS. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new authority or external service access; synthetic data only. No speculative security expansion or unrelated cleanup. ## Author readiness Human owner: @gongfpp - [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 - [ ] 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.}

bsakaguchi 2026-11-01 21:47:38 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-03 00:29:32 +00:00

[GH-ISSUE #5653] [Tracker] New issue intake by area (October 2026) #3423

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

No description provided.