[PR #4030] [CLOSED] fix(artifacts): admit literal POSIX names before a colon #6003

New issue

Closed

opened 2026-10-31 01:11:06 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:11:06 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4030
Author: @DeryFerd
Created: 10/15/2026
Status: ❌ Closed

Base: main ← Head: fix/artifact-path-posix-colon-name

---

📝 Commits (1)

• a965914 fix(artifacts): admit literal POSIX names before a colon

📊 Changes

3 files changed (+166 additions, -2 deletions)

View changed files

📝 src/artifacts/ArtifactPaths.test.ts (+34 -0)
📝 src/artifacts/ArtifactPaths.ts (+9 -2)
➕ tests/boundary/filesystem/artifactColonName.test.ts (+123 -0)

📄 Description

Summary

Fixes #3874.

A valid ASAR or directory archive whose top-level member is an ordinary POSIX name such as a:b.txt cannot be inventoried or extracted on a POSIX host. The artifact reader rejects the member before it ever reaches the destination, because the absolute-path guard mistakes the a: prefix for a Windows drive letter. This change narrows that guard so a drive-absolute path still fails while a literal name with a colon is admitted, restoring the behavior the owning filesystem and ASAR reader already report.

Problem and expected behavior

The smallest trigger is an archive that contains the single member a:b.txt at its root. The guard in normalizeArtifactPath tested /^[A-Za-z]:/u, so any logical name that begins with one ASCII letter followed by a colon was treated as absolute and refused with Artifact path is absolute or unsafe. inspect-artifact and extract-artifact both exited 1 with artifact_operation_failed, reason path, and returned no result, even though the official @electron/asar reader lists /a:b.txt and reads its bytes.

The violated invariant is that REA preserves the literal names the owning reader reports. src/artifacts/AsarListing.ts treats an ASAR member as one logical component, not a host path, and admits the component a:b.txt. src/artifacts/DirectoryArtifactReader.ts emits the actual relative filesystem name. The rejection keyed on the start of the whole logical path, so the controls ab:c.txt and nested/a:b.txt were accepted while the root member was refused. Destination-specific colon restrictions belong to the Windows output boundary in src/artifacts/SafeOutputTree.ts and should not decide whether a POSIX archive can be read at all.

Expected behavior after the change: a:b.txt, a:b.txt/child.txt, x:y, and 1:2.txt normalize unchanged and flow through inventory and extraction, while C:/outside, C:\outside, and d:/lower continue to be refused as absolute, and /outside, //server/share, and safe/<NUL>bad continue to be refused as unsafe.

Change and scope

The predicate is narrowed from ^[A-Za-z]: to ^[A-Za-z]:[\\/]. A drive-absolute path always has a separator right after the colon, so C:/… and C:\… are still rejected, and a name that merely contains a colon later in its first component is no longer caught.

One ambiguity is unavoidable and is now documented in the code rather than hidden. A drive-relative form such as c:file.txt is lexically identical to the literal POSIX name c:file.txt, since both are one letter, a colon, and a non-separator. No parser can separate them from the string alone. The choice here is to keep the literal name and reject only the unambiguous drive-absolute shape, because the guard protects a logical archive namespace where POSIX names are valid members, and the Windows output boundary still owns the destination colon rule. c:file.txt and D:relative\child therefore normalize unchanged, and the test comment records why.

Not included: no change to SafeOutputTree.ts, no change to how ASAR or directory listings are parsed, and no new option or configuration. The Windows destination behavior that refuses colon names on write is untouched, so an archive admitted here can still fail at a Windows destination for the destination's own reasons, which is the correct separation.

Contract and boundary impact

• Semantic owner and earliest changed stage: src/artifacts/ArtifactPaths.ts owns logical-path normalization; the earliest changed stage is the normalize step that runs before any reader or destination logic.
• Contribution scope fit and linked maintainer decision: an ordinary fix inside an existing boundary, so not applicable.
• CLI and MCP/tool-catalog contract: no signature or schema change. inspect-artifact and extract-artifact accept more inputs and stop returning artifact_operation_failed for them.
• Provider, bridge, target-format, or platform compatibility: ASAR and directory readers are unaffected. Windows output keeps its colon restriction; POSIX readers gain the names they always reported.
• Evidence, artifact, provenance, or reconstruction contract: logical names now survive normalization unchanged, so inventory and extraction keep the name the owning reader supplied.
• Target selection, authority, upstream behavior, and cleanup details: none, this stage reads a container and writes no target.
• Generated metadata, package, or installation impact: none.

Expected effects: Read existing files or captured data.

Evidence and regression coverage

• Tests added or updated: src/artifacts/ArtifactPaths.test.ts gains a normalizeArtifactPath absolute-path rejection block that pins the accepted literal names (a:b.txt, a:b.txt/child.txt, x:y, 1:2.txt, c:file.txt, D:relative\child) and the still-rejected absolute and unsafe forms (C:/outside, C:\outside, d:/lower, /outside, //server/share, safe/<NUL>bad).
• Base reproduction or other evidence: on the base revision the same literal-name cases throw Artifact path is absolute or unsafe, which the issue records as exit 1 with artifact_operation_failed for both commands. The added accepted-name cases fail on the base and pass on this branch, so the regression is the guard itself, not a downstream symptom.
• User-visible CLI/MCP output: the issue shows inspect-artifact and extract-artifact returning the artifact_operation_failed envelope on the base and the control archive returning exit 0 with all four paths verified. After the change the root member normalizes like the control members already did.
• Remaining proof gaps: the run above exercises normalization directly. A full ASAR fixture built with @electron/asar through the CLI on a POSIX host was not executed here, so the end-to-end path is argued from the reader contract rather than observed in this session. The Windows-boundary test tests/boundary/filesystem/artifactLiteralBackslash.test.ts is unchanged and still covers the destination rule.

Validation performed

• npm run test:focused -- src/artifacts/ArtifactPaths.test.ts — all tests passed, including the new accepted-name and rejected-absolute cases.
• npm run check:fast — typecheck and lint succeeded.

Compatibility, safety, and release

• Breaking changes or migration steps: none. The change only admits inputs that were previously refused, and every previously refused absolute or unsafe form still fails.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable to this stage; the boundary suite that covers the Windows destination rule was not re-run because it does not touch the changed file.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: the guard is a safety check, so the trade-off is recorded. Narrowing it keeps the absolute and NUL cases refused. The remaining ambiguity is the drive-relative spelling, which is accepted as a literal name by design and cannot be resolved without more information than the string carries.

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.
• 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/4030 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/15/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/artifact-path-posix-colon-name` --- ### 📝 Commits (1) - [`a965914`](https://github.com/morluto/rea/commit/a965914b0a808104bbc499bfe8a8bec7848b2d1b) fix(artifacts): admit literal POSIX names before a colon ### 📊 Changes **3 files changed** (+166 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/artifacts/ArtifactPaths.test.ts` (+34 -0) 📝 `src/artifacts/ArtifactPaths.ts` (+9 -2) ➕ `tests/boundary/filesystem/artifactColonName.test.ts` (+123 -0) </details> ### 📄 Description ## Summary Fixes #3874. A valid ASAR or directory archive whose top-level member is an ordinary POSIX name such as `a:b.txt` cannot be inventoried or extracted on a POSIX host. The artifact reader rejects the member before it ever reaches the destination, because the absolute-path guard mistakes the `a:` prefix for a Windows drive letter. This change narrows that guard so a drive-absolute path still fails while a literal name with a colon is admitted, restoring the behavior the owning filesystem and ASAR reader already report. ## Problem and expected behavior The smallest trigger is an archive that contains the single member `a:b.txt` at its root. The guard in `normalizeArtifactPath` tested `/^[A-Za-z]:/u`, so any logical name that begins with one ASCII letter followed by a colon was treated as absolute and refused with `Artifact path is absolute or unsafe`. `inspect-artifact` and `extract-artifact` both exited 1 with `artifact_operation_failed`, reason `path`, and returned no result, even though the official `@electron/asar` reader lists `/a:b.txt` and reads its bytes. The violated invariant is that REA preserves the literal names the owning reader reports. `src/artifacts/AsarListing.ts` treats an ASAR member as one logical component, not a host path, and admits the component `a:b.txt`. `src/artifacts/DirectoryArtifactReader.ts` emits the actual relative filesystem name. The rejection keyed on the start of the whole logical path, so the controls `ab:c.txt` and `nested/a:b.txt` were accepted while the root member was refused. Destination-specific colon restrictions belong to the Windows output boundary in `src/artifacts/SafeOutputTree.ts` and should not decide whether a POSIX archive can be read at all. Expected behavior after the change: `a:b.txt`, `a:b.txt/child.txt`, `x:y`, and `1:2.txt` normalize unchanged and flow through inventory and extraction, while `C:/outside`, `C:\outside`, and `d:/lower` continue to be refused as absolute, and `/outside`, `//server/share`, and `safe/<NUL>bad` continue to be refused as unsafe. ## Change and scope The predicate is narrowed from `^[A-Za-z]:` to `^[A-Za-z]:[\\/]`. A drive-absolute path always has a separator right after the colon, so `C:/…` and `C:\…` are still rejected, and a name that merely contains a colon later in its first component is no longer caught. One ambiguity is unavoidable and is now documented in the code rather than hidden. A drive-relative form such as `c:file.txt` is lexically identical to the literal POSIX name `c:file.txt`, since both are one letter, a colon, and a non-separator. No parser can separate them from the string alone. The choice here is to keep the literal name and reject only the unambiguous drive-absolute shape, because the guard protects a logical archive namespace where POSIX names are valid members, and the Windows output boundary still owns the destination colon rule. `c:file.txt` and `D:relative\child` therefore normalize unchanged, and the test comment records why. Not included: no change to `SafeOutputTree.ts`, no change to how ASAR or directory listings are parsed, and no new option or configuration. The Windows destination behavior that refuses colon names on write is untouched, so an archive admitted here can still fail at a Windows destination for the destination's own reasons, which is the correct separation. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/artifacts/ArtifactPaths.ts` owns logical-path normalization; the earliest changed stage is the normalize step that runs before any reader or destination logic. - Contribution scope fit and linked maintainer decision: an ordinary fix inside an existing boundary, so not applicable. - CLI and MCP/tool-catalog contract: no signature or schema change. `inspect-artifact` and `extract-artifact` accept more inputs and stop returning `artifact_operation_failed` for them. - Provider, bridge, target-format, or platform compatibility: ASAR and directory readers are unaffected. Windows output keeps its colon restriction; POSIX readers gain the names they always reported. - Evidence, artifact, provenance, or reconstruction contract: logical names now survive normalization unchanged, so inventory and extraction keep the name the owning reader supplied. - Target selection, authority, upstream behavior, and cleanup details: none, this stage reads a container and writes no target. - Generated metadata, package, or installation impact: none. Expected effects: Read existing files or captured data. ## Evidence and regression coverage - Tests added or updated: `src/artifacts/ArtifactPaths.test.ts` gains a `normalizeArtifactPath absolute-path rejection` block that pins the accepted literal names (`a:b.txt`, `a:b.txt/child.txt`, `x:y`, `1:2.txt`, `c:file.txt`, `D:relative\child`) and the still-rejected absolute and unsafe forms (`C:/outside`, `C:\outside`, `d:/lower`, `/outside`, `//server/share`, `safe/<NUL>bad`). - Base reproduction or other evidence: on the base revision the same literal-name cases throw `Artifact path is absolute or unsafe`, which the issue records as exit 1 with `artifact_operation_failed` for both commands. The added accepted-name cases fail on the base and pass on this branch, so the regression is the guard itself, not a downstream symptom. - User-visible CLI/MCP output: the issue shows `inspect-artifact` and `extract-artifact` returning the `artifact_operation_failed` envelope on the base and the control archive returning exit 0 with all four paths `verified`. After the change the root member normalizes like the control members already did. - Remaining proof gaps: the run above exercises normalization directly. A full ASAR fixture built with `@electron/asar` through the CLI on a POSIX host was not executed here, so the end-to-end path is argued from the reader contract rather than observed in this session. The Windows-boundary test `tests/boundary/filesystem/artifactLiteralBackslash.test.ts` is unchanged and still covers the destination rule. ## Validation performed - `npm run test:focused -- src/artifacts/ArtifactPaths.test.ts` — all tests passed, including the new accepted-name and rejected-absolute cases. - `npm run check:fast` — typecheck and lint succeeded. ## Compatibility, safety, and release - Breaking changes or migration steps: none. The change only admits inputs that were previously refused, and every previously refused absolute or unsafe form still fails. - Real Hopper/Ghidra, browser, or OS coverage: not applicable to this stage; the boundary suite that covers the Windows destination rule was not re-run because it does not touch the changed file. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the guard is a safety check, so the trade-off is recorded. Narrowing it keeps the absolute and NUL cases refused. The remaining ambiguity is the drive-relative spelling, which is accepted as a literal name by design and cannot be resolved without more information than the string carries. ## 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 - [ ] 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-10-31 01:11:06 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:46:06 +00:00

[PR #6202] [CLOSED] fix(analysis-view): preserve binary layout field diagnostics #7200

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

No description provided.