[PR #6990] [MERGED] fix(apple): refuse unpaired surrogates in IPS JSON strings #7553

New issue

Closed

opened 2026-11-03 13:38:40 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-03 13:38:40 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6990
Author: @DeryFerd
Created: 10/24/2026
Status: ✅ Merged
Merged: 10/24/2026
Merged by: @morluto

Base: main ← Head: fix/apple-ips-unpaired-surrogates

---

📝 Commits (2)

• 3e67c75 fix(apple): refuse unpaired surrogates in IPS JSON strings
• f92ec17 fix(ci): merge main to restore the setup lint gate

📊 Changes

2 files changed (+63 additions, -7 deletions)

View changed files

📝 src/native/apple/losslessJson.test.ts (+29 -0)
📝 src/native/apple/losslessJson.ts (+34 -7)

📄 Description

Summary

The Apple IPS JSON reader now refuses strings that decode to text containing an unpaired surrogate. A crash report's strings come from the crashed process, so an escaped lone surrogate in procName, an exception message, or a symbol name previously flowed into Evidence as-is: malformed text under a coverage verdict of complete, with no refusal and no uncertainty marker. The reader now treats that like any other malformed input, and the report is refused with a typed format failure naming the reason.

No issue is linked because none exists. The report comes from reading this new parser against the way the rest of REA's text parsers already treat the same input, and the comparison is the argument for the change.

Problem and expected behavior

Smallest trigger: an .ips report whose JSON contains "procName": "test\uD800". The escape is valid JSON syntax, JSON.parse accepts it, and the decoded string carries U+D800 with no following low surrogate.

Before this change, parseString returned that text unchanged through two paths. The escaped path went through JSON.parse, which preserves lone surrogates in its result. The unescaped path returned the raw slice verbatim. Nothing in src/native/apple/ inspected the decoded text, so the report projected with complete coverage while carrying text that no Unicode consumer can render.

Expected behavior: text that is not valid Unicode is malformed input, the same way an invalid escape or an unterminated string is. The reader refuses it with a typed failure naming the problem, and the existing projection turns that into the usual format error for the report instead of Evidence with invalid strings.

Change and scope

parseString now validates the decoded value through requirePairedSurrogates before returning. The check walks the string once: a high surrogate must be followed by its low surrogate, and a low surrogate must follow a high one. Anything else is refused with "JSON string contains an unpaired surrogate".

Placing the check on the decoded value rather than inside the escape handler matters for two reasons. A valid emoji arrives as two separate escapes, so validating each escape in isolation would refuse well-formed text. And the unescaped path never calls the escape handler at all, so an escape-local check would miss raw text entirely. One check after decoding covers both.

consumeJson needs no change. A LosslessJsonFailure with the default reason already projects as an AppleIpsFormatFailure for the report, so the refusal travels through the existing path with the parser's own message.

Out of scope: a normalization mode that replaces lone surrogates with the replacement character while keeping the rest of the report. Refusing matches the nearest precedent in the codebase, the safetensors header reader, which rejects a model whose JSON contains an unpaired surrogate. Keeping malformed text out of Evidence is also the narrower change; a replacement mode would need a decision about where the substitution is recorded.

Contract and boundary impact

• Semantic owner and earliest changed stage: src/native/apple/losslessJson.ts owns IPS JSON text decoding; the check runs when a string is decoded, before shape projection or Evidence construction.
• Contribution scope fit and linked maintainer decision: routine fix inside an existing parser boundary, no target execution, injection, mutation, or protection recovery; not applicable.
• CLI and MCP/tool-catalog contract: none. No tool schema, description, or example change. A previously-succeeding report containing an escaped lone surrogate now returns a typed format failure.
• Provider, bridge, target-format, or platform compatibility: Apple IPS only, all platforms. Reports without unpaired surrogates, including ones using paired surrogate escapes, parse identically.
• Evidence, artifact, provenance, or reconstruction contract: the change removes one way for Evidence to carry invalid text under complete coverage. Artifact identity, provenance, and failed attempts are untouched.
• Target selection, authority, upstream behavior, and cleanup details: not applicable.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. No dependency, lockfile, catalog, or skill bundle change.

Expected effects (check known effects; use documentation-only on its own).

• 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: refuses JSON string escapes for unpaired surrogates in src/native/apple/losslessJson.test.ts. It asserts that a lone \ud800 escape and a trailing \udfff escape are refused with the named message, and that a paired \ud83d\ude00 escape still parses, which is the case an escape-local check would have broken.
• Base reproduction or other evidence: on the base revision the refusal case fails because the parser accepted the escape and returned the decoded string, while the paired case passes. That pair of outcomes is the defect and the non-regression in one run.
• User-visible CLI/MCP output (if applicable): a report containing an escaped lone surrogate now fails with the typed format error carrying "JSON string contains an unpaired surrogate" instead of returning Evidence whose strings are invalid Unicode.
• Remaining proof gaps: no real macOS crash report was decoded for this change; coverage is the reader boundary and its suite, which is where the defect lives. Whether Apple's own reporter ever emits such an escape is unknown, and the refusal does not depend on that.

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

CI follow-up at f92ec17f4 (2026-10-25), Node 24.22.1 / npm 11.16.0 on macOS:

• The failing Static checks job reported setupRegistrationPrewarm.test.ts: a 193-line function exceeded the 150-line test limit. This was inherited from main, and main fixed it in 2acdd5413.
• Merged current main c7ae27807 to include that fix. The PR's two-file IPS parser diff is unchanged.
• npm run check:fast (typecheck/lint) and npm run format:check: passed.
• Source tests for src/native/apple/losslessJson.test.ts and AppleIpsParser.test.ts: 58 passed.
• npm run test:focused -- tests/boundary/filesystem/setupRegistrationPrewarm.test.ts tests/acceptance/appleIpsCli.test.ts: 9 passed, including the public CLI/stdio MCP IPS coverage.
• Fresh GitHub CI is pending; these local checks do not establish a completed hosted run.

Earlier author validation:

• npx vitest run src/native/apple — 311 passed across 12 files, including the 44 AppleIpsParser cases, so no existing fixture or projection changes behavior.
• npx tsc -p .tmp-tsconfig.json --noEmit over losslessJson.ts, its test, and the shape consumer — exit 0.
• npx oxlint src/native/apple/losslessJson.ts src/native/apple/losslessJson.test.ts — 0 warnings, 0 errors.
• npx oxfmt --check on both files — all matched files use the correct format.
• npm run verify:module-boundaries — pass.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Reports without unpaired surrogates parse identically. A report that contains one previously produced Evidence with invalid text and now returns a typed format failure naming the reason, which is the corrected behavior rather than a removal. No ! marker is needed.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable. The change is inside the IPS text reader; no provider session, bridge, or OS process is involved.
• Package or release metadata impact: none. No dependency, lockfile, catalog, or skill bundle change.
• Security, privacy, process, or containment review: the change narrows what reaches Evidence, adds no input path, and does not alter token or credential handling.

Author readiness

Human owner: @DeryFerd

• 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. No owning document describes this reader's string validation, and docs/apple-ips.md documents tool behavior that does not change.
• User-visible CLI/MCP changes include representative output, quoted under Evidence and regression coverage.
• 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/6990 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/24/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/apple-ips-unpaired-surrogates` --- ### 📝 Commits (2) - [`3e67c75`](https://github.com/morluto/rea/commit/3e67c751020e6f530e3adeb6747ef33ffcc4453e) fix(apple): refuse unpaired surrogates in IPS JSON strings - [`f92ec17`](https://github.com/morluto/rea/commit/f92ec17f48ce5a679d5bc7af1966b0f3d7c1b080) fix(ci): merge main to restore the setup lint gate ### 📊 Changes **2 files changed** (+63 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `src/native/apple/losslessJson.test.ts` (+29 -0) 📝 `src/native/apple/losslessJson.ts` (+34 -7) </details> ### 📄 Description ## Summary The Apple IPS JSON reader now refuses strings that decode to text containing an unpaired surrogate. A crash report's strings come from the crashed process, so an escaped lone surrogate in `procName`, an exception message, or a symbol name previously flowed into Evidence as-is: malformed text under a coverage verdict of complete, with no refusal and no uncertainty marker. The reader now treats that like any other malformed input, and the report is refused with a typed format failure naming the reason. No issue is linked because none exists. The report comes from reading this new parser against the way the rest of REA's text parsers already treat the same input, and the comparison is the argument for the change. ## Problem and expected behavior Smallest trigger: an `.ips` report whose JSON contains `"procName": "test\uD800"`. The escape is valid JSON syntax, `JSON.parse` accepts it, and the decoded string carries U+D800 with no following low surrogate. Before this change, `parseString` returned that text unchanged through two paths. The escaped path went through `JSON.parse`, which preserves lone surrogates in its result. The unescaped path returned the raw slice verbatim. Nothing in `src/native/apple/` inspected the decoded text, so the report projected with complete coverage while carrying text that no Unicode consumer can render. Expected behavior: text that is not valid Unicode is malformed input, the same way an invalid escape or an unterminated string is. The reader refuses it with a typed failure naming the problem, and the existing projection turns that into the usual format error for the report instead of Evidence with invalid strings. ## Change and scope `parseString` now validates the decoded value through `requirePairedSurrogates` before returning. The check walks the string once: a high surrogate must be followed by its low surrogate, and a low surrogate must follow a high one. Anything else is refused with "JSON string contains an unpaired surrogate". Placing the check on the decoded value rather than inside the escape handler matters for two reasons. A valid emoji arrives as two separate escapes, so validating each escape in isolation would refuse well-formed text. And the unescaped path never calls the escape handler at all, so an escape-local check would miss raw text entirely. One check after decoding covers both. `consumeJson` needs no change. A `LosslessJsonFailure` with the default reason already projects as an `AppleIpsFormatFailure` for the report, so the refusal travels through the existing path with the parser's own message. Out of scope: a normalization mode that replaces lone surrogates with the replacement character while keeping the rest of the report. Refusing matches the nearest precedent in the codebase, the safetensors header reader, which rejects a model whose JSON contains an unpaired surrogate. Keeping malformed text out of Evidence is also the narrower change; a replacement mode would need a decision about where the substitution is recorded. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/native/apple/losslessJson.ts` owns IPS JSON text decoding; the check runs when a string is decoded, before shape projection or Evidence construction. - Contribution scope fit and linked maintainer decision: routine fix inside an existing parser boundary, no target execution, injection, mutation, or protection recovery; not applicable. - CLI and MCP/tool-catalog contract: none. No tool schema, description, or example change. A previously-succeeding report containing an escaped lone surrogate now returns a typed format failure. - Provider, bridge, target-format, or platform compatibility: Apple IPS only, all platforms. Reports without unpaired surrogates, including ones using paired surrogate escapes, parse identically. - Evidence, artifact, provenance, or reconstruction contract: the change removes one way for Evidence to carry invalid text under complete coverage. Artifact identity, provenance, and failed attempts are untouched. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. No dependency, lockfile, catalog, or skill bundle change. Expected effects (check known effects; use documentation-only on its own). - [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 or updated: `refuses JSON string escapes for unpaired surrogates` in `src/native/apple/losslessJson.test.ts`. It asserts that a lone `\ud800` escape and a trailing `\udfff` escape are refused with the named message, and that a paired `\ud83d\ude00` escape still parses, which is the case an escape-local check would have broken. - Base reproduction or other evidence: on the base revision the refusal case fails because the parser accepted the escape and returned the decoded string, while the paired case passes. That pair of outcomes is the defect and the non-regression in one run. - User-visible CLI/MCP output (if applicable): a report containing an escaped lone surrogate now fails with the typed format error carrying "JSON string contains an unpaired surrogate" instead of returning Evidence whose strings are invalid Unicode. - Remaining proof gaps: no real macOS crash report was decoded for this change; coverage is the reader boundary and its suite, which is where the defect lives. Whether Apple's own reporter ever emits such an escape is unknown, and the refusal does not depend on that. 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 CI follow-up at `f92ec17f4` (2026-10-25), Node 24.22.1 / npm 11.16.0 on macOS: - The failing Static checks job reported `setupRegistrationPrewarm.test.ts`: a 193-line function exceeded the 150-line test limit. This was inherited from main, and main fixed it in `2acdd5413`. - Merged current main `c7ae27807` to include that fix. The PR's two-file IPS parser diff is unchanged. - `npm run check:fast` (typecheck/lint) and `npm run format:check`: passed. - Source tests for `src/native/apple/losslessJson.test.ts` and `AppleIpsParser.test.ts`: **58 passed**. - `npm run test:focused -- tests/boundary/filesystem/setupRegistrationPrewarm.test.ts tests/acceptance/appleIpsCli.test.ts`: **9 passed**, including the public CLI/stdio MCP IPS coverage. - Fresh GitHub CI is pending; these local checks do not establish a completed hosted run. Earlier author validation: - `npx vitest run src/native/apple` — 311 passed across 12 files, including the 44 `AppleIpsParser` cases, so no existing fixture or projection changes behavior. - `npx tsc -p .tmp-tsconfig.json --noEmit` over `losslessJson.ts`, its test, and the shape consumer — exit 0. - `npx oxlint src/native/apple/losslessJson.ts src/native/apple/losslessJson.test.ts` — 0 warnings, 0 errors. - `npx oxfmt --check` on both files — all matched files use the correct format. - `npm run verify:module-boundaries` — pass. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Reports without unpaired surrogates parse identically. A report that contains one previously produced Evidence with invalid text and now returns a typed format failure naming the reason, which is the corrected behavior rather than a removal. No `!` marker is needed. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. The change is inside the IPS text reader; no provider session, bridge, or OS process is involved. - Package or release metadata impact: none. No dependency, lockfile, catalog, or skill bundle change. - Security, privacy, process, or containment review: the change narrows what reaches Evidence, adds no input path, and does not alter token or credential handling. ## Author readiness Human owner: @DeryFerd - [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. No owning document describes this reader's string validation, and `docs/apple-ips.md` documents tool behavior that does not change. - [x] User-visible CLI/MCP changes include representative output, quoted under Evidence and regression coverage. - [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-11-03 13:38:40 +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#7553

No description provided.