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 #7059] [MERGED] fix(apple): keep the recorded image name and frame symbol offset of IPS reports #7613

New issue
Closed
opened 2026-11-03 13:39:07 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:07 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7059
Author: @Adolanium
Created: 10/25/2026
Status: ✅ Merged
Merged: 10/25/2026
Merged by: @morluto

Base: main ← Head: fix/ips-image-name-symbol-location

📝 Commits (2)

  • 30e90c4 fix(apple): keep the recorded image name and frame symbol offset of IPS reports
  • aba1bc7 fix(apple): count frame symbol offsets in the integer text check

📊 Changes

6 files changed (+94 additions, -2 deletions)

View changed files

📝 docs/apple-ips.md (+3 -1)
📝 src/application/binaryDiagnostics/AppleIpsService.test.ts (+43 -0)
📝 src/domain/native/appleIps.ts (+8 -1)
📝 src/native/apple/AppleIpsJsonShape.ts (+2 -0)
📝 src/native/apple/AppleIpsParser.test.ts (+33 -0)
📝 src/native/apple/AppleIpsParser.ts (+5 -0)

📄 Description

Summary

Fixes #7060.

inspect_recorded_crash drops two documented .ips fields: each binary image's name and each frame's symbolLocation. docs/apple-ips.md says documented body fields are reproduced and undocumented keys stay in unlisted_keys, but neither happens for these two: the parser shapes did not list them, so they were syntax-checked and discarded. A symbolicated frame showed __pthread_kill without its + 8, and every image lost its binary name. Both are now kept.

Problem and expected behavior

Apple's JSON crash report reference lists name ("The binary name") under binary images and symbolLocation ("The number of bytes from the executing instruction's entry point") under frames. ReportCrash writes both in ordinary reports; the existing fixture already contains them. Nothing in the result recorded either value, and no unlisted_keys entry showed they existed.

Expected: images[].name and frames[].symbol_location (a recorded integer, like the other integer fields), with type mismatches recorded the same way as for other fields.

Change and scope

  • src/native/apple/AppleIpsJsonShape.ts: usedImages rows list name; frame rows list symbolLocation.
  • src/native/apple/AppleIpsParser.ts: reads them with the existing read.text / read.integer readers.
  • src/domain/native/appleIps.ts: imageSchema.name: string | null and frameSchema.symbol_location: RecordedInteger | null.
  • docs/apple-ips.md names both fields.

Not included: no other IPS fields; recorded_symbol is unchanged and symbol_location sits next to it.

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.

Contribution scope: not applicable. This is a fix inside the existing Apple crash report parser, restoring fields its documentation says it reproduces.

Contract and boundary impact

  • Semantic owner and earliest changed stage: the IPS JSON shapes in AppleIpsJsonShape.ts.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: inspect_recorded_crash output gains images[].name and threads[].frames[].symbol_location, both nullable. Existing fields are unchanged.
  • Provider, bridge, target-format, or platform compatibility: Apple .ips crash reports (bug_type 309).
  • Evidence, artifact, provenance, or reconstruction contract: two recorded producer facts are no longer discarded.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • 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): the generated tool catalog reflects the two output fields; no package change.

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

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

Evidence and regression coverage

  • Tests added or updated: src/native/apple/AppleIpsParser.test.ts, "keeps the recorded image name and symbol offset": on the existing ReportCrash-shaped fixture, image names are ["rea-crash-fixture", null], the faulting frame keeps symbol_location 12 next to rea_fixture_fault, an inline frame keeps 0, coverage stays complete, and a string symbolLocation gives null with a type mismatch at body.threads[0].frames[0].symbolLocation.
  • Base reproduction or other evidence: with the three source files from upstream/main 4ed33efb0 and the new test, the test fails. Before the new assertions, all existing tests passed with the fields dropped, so nothing covered them.
  • User-visible CLI/MCP output (if applicable): images[].name and frames[].symbol_location in inspect_recorded_crash results.
  • Remaining proof gaps: the fixture is synthetic, modelled on ReportCrash output; no real macOS crash report was parsed.

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

On Linux (WSL Ubuntu, Node 24.22.1) at 30e90c435 (on upstream/main 4ed33efb0), after npm ci and npm run build:cached:

  • npx tsc -p . --noEmit passed.
  • On the same change at the previous base f62a2baad: npx oxfmt --check on the changed files clean, node scripts/ci/static-check-report.mjs lint 0 errors, npm run docs:check passed. The rebase onto the current base was clean.
  • npx vitest run src/native/apple src/domain/native tests/boundary/native tests/acceptance/appleIpsCli.test.ts: 555 passed, in two runs.
  • npx vitest run tests/boundary/mcp after npm run mcp-catalog:generate (one earlier run on the previous base): 1991 passed, 10 skipped, 1 failed, "advertises portable NUL escapes and patterns that compile in all JS modes". That test fails the same way on the base without this change.
  • The negative check above failed the new test.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; two nullable output fields are added.
  • Real Hopper/Ghidra, browser, or OS coverage: Linux only; no macOS.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the image name is already part of the recorded image path; no new data source.

Author readiness

Human owner: @Adolanium

  • 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/7059 **Author:** [@Adolanium](https://github.com/Adolanium) **Created:** 10/25/2026 **Status:** ✅ Merged **Merged:** 10/25/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/ips-image-name-symbol-location` --- ### 📝 Commits (2) - [`30e90c4`](https://github.com/morluto/rea/commit/30e90c435f4703288f5cb9983eefd0801332167d) fix(apple): keep the recorded image name and frame symbol offset of IPS reports - [`aba1bc7`](https://github.com/morluto/rea/commit/aba1bc735ea6ac3dc91293dc69ff62d3e789e712) fix(apple): count frame symbol offsets in the integer text check ### 📊 Changes **6 files changed** (+94 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/apple-ips.md` (+3 -1) 📝 `src/application/binaryDiagnostics/AppleIpsService.test.ts` (+43 -0) 📝 `src/domain/native/appleIps.ts` (+8 -1) 📝 `src/native/apple/AppleIpsJsonShape.ts` (+2 -0) 📝 `src/native/apple/AppleIpsParser.test.ts` (+33 -0) 📝 `src/native/apple/AppleIpsParser.ts` (+5 -0) </details> ### 📄 Description ## Summary Fixes #7060. `inspect_recorded_crash` drops two documented `.ips` fields: each binary image's `name` and each frame's `symbolLocation`. `docs/apple-ips.md` says documented body fields are reproduced and undocumented keys stay in `unlisted_keys`, but neither happens for these two: the parser shapes did not list them, so they were syntax-checked and discarded. A symbolicated frame showed `__pthread_kill` without its `+ 8`, and every image lost its binary name. Both are now kept. ## Problem and expected behavior Apple's JSON crash report reference lists `name` ("The binary name") under binary images and `symbolLocation` ("The number of bytes from the executing instruction's entry point") under frames. ReportCrash writes both in ordinary reports; the existing fixture already contains them. Nothing in the result recorded either value, and no `unlisted_keys` entry showed they existed. Expected: `images[].name` and `frames[].symbol_location` (a recorded integer, like the other integer fields), with type mismatches recorded the same way as for other fields. ## Change and scope - `src/native/apple/AppleIpsJsonShape.ts`: `usedImages` rows list `name`; frame rows list `symbolLocation`. - `src/native/apple/AppleIpsParser.ts`: reads them with the existing `read.text` / `read.integer` readers. - `src/domain/native/appleIps.ts`: `imageSchema.name: string | null` and `frameSchema.symbol_location: RecordedInteger | null`. - `docs/apple-ips.md` names both fields. Not included: no other IPS fields; `recorded_symbol` is unchanged and `symbol_location` sits next to it. 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. Contribution scope: not applicable. This is a fix inside the existing Apple crash report parser, restoring fields its documentation says it reproduces. ## Contract and boundary impact - Semantic owner and earliest changed stage: the IPS JSON shapes in `AppleIpsJsonShape.ts`. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: `inspect_recorded_crash` output gains `images[].name` and `threads[].frames[].symbol_location`, both nullable. Existing fields are unchanged. - Provider, bridge, target-format, or platform compatibility: Apple `.ips` crash reports (`bug_type` 309). - Evidence, artifact, provenance, or reconstruction contract: two recorded producer facts are no longer discarded. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - 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): the generated tool catalog reflects the two output fields; no package change. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/native/apple/AppleIpsParser.test.ts`, "keeps the recorded image name and symbol offset": on the existing ReportCrash-shaped fixture, image names are `["rea-crash-fixture", null]`, the faulting frame keeps `symbol_location` 12 next to `rea_fixture_fault`, an inline frame keeps 0, coverage stays `complete`, and a string `symbolLocation` gives `null` with a type mismatch at `body.threads[0].frames[0].symbolLocation`. - Base reproduction or other evidence: with the three source files from upstream/main 4ed33efb0 and the new test, the test fails. Before the new assertions, all existing tests passed with the fields dropped, so nothing covered them. - User-visible CLI/MCP output (if applicable): `images[].name` and `frames[].symbol_location` in `inspect_recorded_crash` results. - Remaining proof gaps: the fixture is synthetic, modelled on ReportCrash output; no real macOS crash report was parsed. 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 On Linux (WSL Ubuntu, Node 24.22.1) at 30e90c435 (on upstream/main 4ed33efb0), after `npm ci` and `npm run build:cached`: - `npx tsc -p . --noEmit` passed. - On the same change at the previous base f62a2baad: `npx oxfmt --check` on the changed files clean, `node scripts/ci/static-check-report.mjs lint` 0 errors, `npm run docs:check` passed. The rebase onto the current base was clean. - `npx vitest run src/native/apple src/domain/native tests/boundary/native tests/acceptance/appleIpsCli.test.ts`: 555 passed, in two runs. - `npx vitest run tests/boundary/mcp` after `npm run mcp-catalog:generate` (one earlier run on the previous base): 1991 passed, 10 skipped, 1 failed, "advertises portable NUL escapes and patterns that compile in all JS modes". That test fails the same way on the base without this change. - The negative check above failed the new test. ## Compatibility, safety, and release - Breaking changes or migration steps: none; two nullable output fields are added. - Real Hopper/Ghidra, browser, or OS coverage: Linux only; no macOS. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the image name is already part of the recorded image path; no new data source. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @Adolanium - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-03 13:39:07 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7613
No description provided.