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 #6937] [MERGED] fix(zip): validate trailing archive record candidates #7459

New issue
Closed
opened 2026-11-01 21:48:00 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:48:00 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: codex/fix-zip-comment-record-detection

📝 Commits (4)

  • 3e1bdc2 fix(zip): validate trailing archive record candidates
  • ba51d51 merge: synchronize upstream plist CI repair
  • 47898cb chore: sync upstream plist validation and lifecycle fixes
  • 95162ed chore: sync upstream native and launcher test contracts

📊 Changes

3 files changed (+71 additions, -46 deletions)

View changed files

📝 src/domain/zipPackageFormat.ts (+36 -39)
📝 tests/acceptance/applications/mobileDirectoryComponents.test.ts (+5 -3)
📝 tests/boundary/filesystem/zipDetection.test.ts (+30 -4)

📄 Description

Summary

Recognize a ZIP after leading script bytes when its legal archive comment contains an EOCD-like sequence. Validate candidate directories before accepting the final record candidate, so comment data cannot hide the real record.

Problem and expected behavior

The locator previously chose the last signature whose comment-length field reached EOF and stopped scanning. If that sequence was comment data, failed directory validation rejected the whole valid archive instead of trying the genuine earlier record. This is a newly reproduced format finding; no existing issue is linked.

Change and scope

Move the existing candidate validation into the existing backward scan and continue after an invalid candidate. The same 65,557-byte maximum tail window and single-disk, nonempty, non-Zip64 restrictions remain. No new archive family, extraction authority, allowance or parser abstraction.

Synchronization note: the normal pre-commit hook also simplifies one equivalent encrypted-ZIP fixture options expression in tests/acceptance/applications/mobileDirectoryComponents.test.ts; it does not add a product behavior change.

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: src/domain/zipPackageFormat.ts, trailing-ZIP detection before root classification and binary-target admission.
  • Contribution scope fit and linked maintainer decision: Ordinary correctness fix within existing boundaries; separate maintainer decision not applicable.
  • CLI and MCP/tool-catalog contract: Existing ZIP roots with leading bytes are recognized despite signature-like comment data. Public CLI/MCP schemas and supported archive families are unchanged.
  • Provider, bridge, target-format, or platform compatibility: See scope and platform verification below; no new provider.
  • Evidence, artifact, provenance, or reconstruction contract: Verified member identities and the explicit non-entry-byte limitation remain. Comments and script stubs are not invented as inventory entries.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Reads the already selected archive through the existing positional-read boundary. No source execution, extraction-policy or cleanup-ownership change.
  • 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; no generated output, package or installation 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: Expand the existing leading-byte matrix in tests/boundary/filesystem/zipDetection.test.ts for both offset conventions, with and without an EOCD-like legal comment. Preserve classifier, target admission and verified-member identity assertions plus the existing malformed/symlink controls.
  • Base reproduction or other evidence: On base cc18e9ad, both new comment cases fail: 2 failed, 23 passed, 1 existing Windows symlink skip. With the correction: 25 passed, the same 1 platform skip. An independent @zip.js/zip.js reader accepts the plain and commented fixtures and reads a.txt in both; the source locator changes from undefined to the correct leading byte count 17 for the commented input.
  • User-visible CLI/MCP output (if applicable): Root classification and parseBinaryTarget identify the commented script-prefixed fixture as ZIP; inventory members match the equivalent plain ZIP.
  • Remaining proof gaps: Synthetic valid ZIP fixtures on Windows and an independent ZIP reader. No real self-extracting executable was launched. Zip64, split and empty trailing archives remain outside this locator. No performance improvement claim.

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

Synchronized with upstream b5c42dfc, including #6945, for six shared CI failures: two stale bound-target error expectations and four launcher/package fixture cases. The two source cases reproduce before synchronization (2 failed, 3 passed). After synchronization, all six previously failing cases pass; bound-target permissions and exact corrupted-catalog/CRLF/bytecode rejection assertions remain. Extended validation on the synchronized ZIP tree ran the complete metadata, MCP, TAR, plist and ZIP files: 231 passed, 22 existing platform skips, and one Windows-local catalog-recording timeout. An unchanged isolated rerun passed in 24 seconds; the original timeout remains recorded and does not establish whole-suite success. Real macOS plist CLI tests were skipped on Windows. The six plist boundary files still pass (64 passed, 3 existing platform skips). On this PR tree, 25 ZIP tests passed, with the existing Windows symlink case skipped; npm run check and npm run docs:check passed. Full new-head Linux CI must qualify the synchronized change.

Original fix baseline cc18e9ad; synchronized upstream b5c42dfc; current head 95162edd09.

  • npm run test:focused -- tests/boundary/filesystem/zipDetection.test.ts — 25 passed, 1 existing Windows symlink skip on the independent final branch.
  • Independent ZIP reader and source-locator probe — both valid fixtures readable, leading byte count preserved.
  • npm run check — all six tasks, module boundaries and architecture guards passed.
  • Formatting, git diff --check and normal commit/push hooks passed.
  • Local checks do not establish complete Linux CI success; consult the current-head Checks tab.

Compatibility, safety, and release

  • Breaking changes or migration steps: No migration. Invalid candidates now permit continued detection; the original supported-format and directory/local-header validation rules are retained.

  • Real Hopper/Ghidra, browser, or OS coverage: Pinned Node 24.22.1 on Windows x64, synthetic archive classification/admission/inventory. No executable or native provider run.

  • Package or release metadata impact: None.

  • Security, privacy, process, or containment review: Reads the already selected archive through the existing positional-read boundary. No source execution, extraction-policy or cleanup-ownership change.

Author readiness

Human owner: @ShuaixinHuang

  • 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/6937 **Author:** [@ShuaixinHuang](https://github.com/ShuaixinHuang) **Created:** 10/24/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/fix-zip-comment-record-detection` --- ### 📝 Commits (4) - [`3e1bdc2`](https://github.com/morluto/rea/commit/3e1bdc2dbf4f16e0cd9e3ccd652cb877bd4ec19b) fix(zip): validate trailing archive record candidates - [`ba51d51`](https://github.com/morluto/rea/commit/ba51d515d458e38dbc97d29236dccb140bd3c24b) merge: synchronize upstream plist CI repair - [`47898cb`](https://github.com/morluto/rea/commit/47898cb95065222916c88e533c565837d4a6b221) chore: sync upstream plist validation and lifecycle fixes - [`95162ed`](https://github.com/morluto/rea/commit/95162edd0924708460edbd9faa23322aed4a3903) chore: sync upstream native and launcher test contracts ### 📊 Changes **3 files changed** (+71 additions, -46 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/zipPackageFormat.ts` (+36 -39) 📝 `tests/acceptance/applications/mobileDirectoryComponents.test.ts` (+5 -3) 📝 `tests/boundary/filesystem/zipDetection.test.ts` (+30 -4) </details> ### 📄 Description ## Summary Recognize a ZIP after leading script bytes when its legal archive comment contains an EOCD-like sequence. Validate candidate directories before accepting the final record candidate, so comment data cannot hide the real record. ## Problem and expected behavior The locator previously chose the last signature whose comment-length field reached EOF and stopped scanning. If that sequence was comment data, failed directory validation rejected the whole valid archive instead of trying the genuine earlier record. This is a newly reproduced format finding; no existing issue is linked. ## Change and scope Move the existing candidate validation into the existing backward scan and continue after an invalid candidate. The same 65,557-byte maximum tail window and single-disk, nonempty, non-Zip64 restrictions remain. No new archive family, extraction authority, allowance or parser abstraction. Synchronization note: the normal pre-commit hook also simplifies one equivalent encrypted-ZIP fixture options expression in `tests/acceptance/applications/mobileDirectoryComponents.test.ts`; it does not add a product behavior change. 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: `src/domain/zipPackageFormat.ts`, trailing-ZIP detection before root classification and binary-target admission. - Contribution scope fit and linked maintainer decision: Ordinary correctness fix within existing boundaries; separate maintainer decision not applicable. - CLI and MCP/tool-catalog contract: Existing ZIP roots with leading bytes are recognized despite signature-like comment data. Public CLI/MCP schemas and supported archive families are unchanged. - Provider, bridge, target-format, or platform compatibility: See scope and platform verification below; no new provider. - Evidence, artifact, provenance, or reconstruction contract: Verified member identities and the explicit non-entry-byte limitation remain. Comments and script stubs are not invented as inventory entries. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Reads the already selected archive through the existing positional-read boundary. No source execution, extraction-policy or cleanup-ownership change. - 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; no generated output, package or installation 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: Expand the existing leading-byte matrix in tests/boundary/filesystem/zipDetection.test.ts for both offset conventions, with and without an EOCD-like legal comment. Preserve classifier, target admission and verified-member identity assertions plus the existing malformed/symlink controls. - Base reproduction or other evidence: On base cc18e9ad, both new comment cases fail: 2 failed, 23 passed, 1 existing Windows symlink skip. With the correction: 25 passed, the same 1 platform skip. An independent @zip.js/zip.js reader accepts the plain and commented fixtures and reads a.txt in both; the source locator changes from undefined to the correct leading byte count 17 for the commented input. - User-visible CLI/MCP output (if applicable): Root classification and parseBinaryTarget identify the commented script-prefixed fixture as ZIP; inventory members match the equivalent plain ZIP. - Remaining proof gaps: Synthetic valid ZIP fixtures on Windows and an independent ZIP reader. No real self-extracting executable was launched. Zip64, split and empty trailing archives remain outside this locator. No performance improvement claim. 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 Synchronized with upstream `b5c42dfc`, including #6945, for six shared CI failures: two stale bound-target error expectations and four launcher/package fixture cases. The two source cases reproduce before synchronization (2 failed, 3 passed). After synchronization, all six previously failing cases pass; bound-target permissions and exact corrupted-catalog/CRLF/bytecode rejection assertions remain. Extended validation on the synchronized ZIP tree ran the complete metadata, MCP, TAR, plist and ZIP files: 231 passed, 22 existing platform skips, and one Windows-local catalog-recording timeout. An unchanged isolated rerun passed in 24 seconds; the original timeout remains recorded and does not establish whole-suite success. Real macOS plist CLI tests were skipped on Windows. The six plist boundary files still pass (64 passed, 3 existing platform skips). On this PR tree, 25 ZIP tests passed, with the existing Windows symlink case skipped; `npm run check` and `npm run docs:check` passed. Full new-head Linux CI must qualify the synchronized change. Original fix baseline cc18e9ad; synchronized upstream b5c42dfc; current head 95162edd0924708460edbd9faa23322aed4a3903. - `npm run test:focused -- tests/boundary/filesystem/zipDetection.test.ts` — 25 passed, 1 existing Windows symlink skip on the independent final branch. - Independent ZIP reader and source-locator probe — both valid fixtures readable, leading byte count preserved. - `npm run check` — all six tasks, module boundaries and architecture guards passed. - Formatting, git diff --check and normal commit/push hooks passed. - Local checks do not establish complete Linux CI success; consult the current-head Checks tab. ## Compatibility, safety, and release - Breaking changes or migration steps: No migration. Invalid candidates now permit continued detection; the original supported-format and directory/local-header validation rules are retained. - Real Hopper/Ghidra, browser, or OS coverage: Pinned Node 24.22.1 on Windows x64, synthetic archive classification/admission/inventory. No executable or native provider run. - Package or release metadata impact: None. - Security, privacy, process, or containment review: Reads the already selected archive through the existing positional-read boundary. No source execution, extraction-policy or cleanup-ownership change. ## Author readiness Human owner: @ShuaixinHuang - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:48:00 +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#7459
No description provided.