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 #6876] [MERGED] fix(environment): match served items whose route repeats a separator #7428

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6876
Author: @mhamzasakhi
Created: 10/23/2026
Status: ✅ Merged
Merged: 10/23/2026
Merged by: @gensokyo-dev

Base: main ← Head: fix/environment-repeated-separator-item

📝 Commits (3)

  • f894861 fix(environment): match served items whose route repeats a separator
  • f194c2a fix(environment): keep repeated-separator collections writable
  • c463198 Merge branch 'main' into fix/environment-repeated-separator-item

📊 Changes

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

View changed files

📝 src/application/environment/environmentStateAnswer.test.ts (+62 -0)
📝 src/application/environment/environmentStateCallLines.ts (+6 -5)
📝 src/application/environment/environmentStateCollections.ts (+6 -1)

📄 Description

Summary

Fixes #6847. A served item read whose captured route repeats a path separator, such as GET /api//books/1, returned AnalysisInputError ("The state holds no /api//books entity 1 in /api/books.") even though the entity was correctly extracted into collection /api//books. The single-separator route /api/books/1 succeeds, and direct recorded replay of the double-separator route also succeeds.

Problem and expected behavior

segmentsOf (the owner used to split the held collection path) preserves internal empty segments, so /api//books becomes ["api", "", "books"]. callSegments instead split the tool's path_template itself and dropped empty literal segments with if (text !== "") …, producing ["api", "books", value]. collectionMatch compares by position, so the lengths matched but the segments did not, and the item was reported as missing.

Expected: a state item view finds the entity it extracted from the same recorded path, preserving the empty internal segment when matching.

Change and scope

  • callSegments now splits the template through segmentsOf, the same owner that splits the held collection path, instead of re-implementing a split that dropped empty segments. A repeated separator is preserved identically on both sides.
  • Param positions are unchanged: param indices are already defined over segmentsOf(path_template) (see environmentStateCheckedLines.ts, which builds param index sets with segmentsOf(tool.path_template).flatMap(...)), and the reproduction confirms the /api//books/{numeric} param index is 3, matching segmentsOf.
  • Single-separator routes are unaffected: with no empty segment, segmentsOf and the previous raw split agree.
  • Create path (review follow-up): preserving empty literal segments exposed createdCollection's missing-argument guard, which rejected any empty segment. A generated create to a repeated-separator collection, such as POST /api//books, was refused. The guard now rejects only an empty supplied parameter segment, so an empty literal (the repeated separator) stays writable while a missing path argument is still refused. Recorded-replay creates were never affected.
  • Not included: the broader path-handling findings tracked in #6726 and #6696 (closed). This change addresses only the call-side split that diverged from segmentsOf.

Contribution scope: an ordinary correctness fix within existing boundaries; a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: call-path segmentation in callSegments, consumed by collectionMatch at the state-answer boundary.

  • CLI and MCP/tool-catalog contract: no schema change. A served item whose route repeats a separator now returns its entity instead of a not-found refusal.

  • Provider, bridge, target-format, or platform compatibility: none.

  • Evidence, artifact, provenance, or reconstruction contract: unchanged; state extraction already stored these collections distinctly.

  • Generated metadata, package, or installation impact: none.

  • 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 to src/application/environment/environmentStateAnswer.test.ts:

    • "answers a state item whose route has a repeated path separator": serves two captured items, /api/books/1 and /api//books/1, and asserts the double-separator item answers from /api//books while the single-separator item stays distinct under /api/books.
    • "creates into a collection whose route has a repeated path separator" (review follow-up): a generated create to /api//books returns 201 from state instead of a missing-argument refusal.

  • Base reproduction (executed): with only environmentStateCallLines.ts reverted, the item test fails with the issue's AnalysisInputError. With only the environmentStateCollections.ts guard change reverted, the create test fails with needs every path argument to be non-empty.

  • Reproduction of the reported issue (executed): the issue's synthetic HAR probe returned answer.ok: false for /api//books/1 before the change and answer.ok: true after, with /api/books/1 succeeding throughout.

  • 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

Run on Ubuntu 24.04 x64 with Node 24.22.1:

  • npm run test:focused -- with every test file referencing environment state, callSegments, collectionMatch, answerFromState, createdCollection, environment-serve, segmentsOf or dyldPaths (47 files): 992 passed, 1 skipped, 0 failed.
  • npm run test:local -- src/application/environment/environmentStateAnswer.test.ts: 21 passed. With either fix reverted, its corresponding test fails.
  • npm run check:fast: passed. knip reports nothing for the touched module.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Only a previously failing served-item read begins succeeding; its collection extraction was already correct.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable (synthetic capture; no provider). Linux only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new reads, execution, or network access.

Independent verification on updated main

Head c4631987 integrates main af3b039d. Independent Linux validation passed 310 targeted domain/service/CLI/MCP tests and full npm run check. A real Chromium HAR of a local package-inventory application was imported through compiled CLI/stdio MCP, projected to state and served through HTTP MCP: repeated-separator item reads and generated creates succeeded, with ordinary-path collections isolated. Original capture/manifest/state Evidence remained identical. Review and measured resource observations include verification scope, timing variation and token-estimate limitations.

CI run 40018253228 failed with 14 test failures, all reproduced on its clean base af3b039d; seven remaining shards were cancelled. Static/build/native-package checks and the agentenv export/run lane passed. Main then advanced to 0929fa42: the unchanged PR was re-integrated there, and the same 310 tests, full check and real Chromium/CLI/MCP workflow passed again. Final baseline and latest-main verification.

Author readiness

Human owner: @mhamzasakhi

  • 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/6876 **Author:** [@mhamzasakhi](https://github.com/mhamzasakhi) **Created:** 10/23/2026 **Status:** ✅ Merged **Merged:** 10/23/2026 **Merged by:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Base:** `main` ← **Head:** `fix/environment-repeated-separator-item` --- ### 📝 Commits (3) - [`f894861`](https://github.com/morluto/rea/commit/f894861f165826fff7b49038ea682638f4880df7) fix(environment): match served items whose route repeats a separator - [`f194c2a`](https://github.com/morluto/rea/commit/f194c2a74fc1a5ab9fc8ba62986b6081736520fc) fix(environment): keep repeated-separator collections writable - [`c463198`](https://github.com/morluto/rea/commit/c463198726902753d79b8a8c2559dde27ef54af2) Merge branch 'main' into fix/environment-repeated-separator-item ### 📊 Changes **3 files changed** (+74 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `src/application/environment/environmentStateAnswer.test.ts` (+62 -0) 📝 `src/application/environment/environmentStateCallLines.ts` (+6 -5) 📝 `src/application/environment/environmentStateCollections.ts` (+6 -1) </details> ### 📄 Description ## Summary Fixes #6847. A served item read whose captured route repeats a path separator, such as `GET /api//books/1`, returned `AnalysisInputError` ("The state holds no /api//books entity 1 in /api/books.") even though the entity was correctly extracted into collection `/api//books`. The single-separator route `/api/books/1` succeeds, and direct recorded replay of the double-separator route also succeeds. ## Problem and expected behavior `segmentsOf` (the owner used to split the held collection path) preserves internal empty segments, so `/api//books` becomes `["api", "", "books"]`. `callSegments` instead split the tool's `path_template` itself and dropped empty literal segments with `if (text !== "") …`, producing `["api", "books", value]`. `collectionMatch` compares by position, so the lengths matched but the segments did not, and the item was reported as missing. Expected: a state item view finds the entity it extracted from the same recorded path, preserving the empty internal segment when matching. ## Change and scope - `callSegments` now splits the template through `segmentsOf`, the same owner that splits the held collection path, instead of re-implementing a split that dropped empty segments. A repeated separator is preserved identically on both sides. - Param positions are unchanged: param indices are already defined over `segmentsOf(path_template)` (see `environmentStateCheckedLines.ts`, which builds param index sets with `segmentsOf(tool.path_template).flatMap(...)`), and the reproduction confirms the `/api//books/{numeric}` param index is `3`, matching `segmentsOf`. - Single-separator routes are unaffected: with no empty segment, `segmentsOf` and the previous raw split agree. - Create path (review follow-up): preserving empty literal segments exposed `createdCollection`'s missing-argument guard, which rejected any empty segment. A generated create to a repeated-separator collection, such as `POST /api//books`, was refused. The guard now rejects only an empty *supplied* parameter segment, so an empty literal (the repeated separator) stays writable while a missing path argument is still refused. Recorded-replay creates were never affected. - Not included: the broader path-handling findings tracked in #6726 and #6696 (closed). This change addresses only the call-side split that diverged from `segmentsOf`. Contribution scope: an ordinary correctness fix within existing boundaries; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: call-path segmentation in `callSegments`, consumed by `collectionMatch` at the state-answer boundary. - CLI and MCP/tool-catalog contract: no schema change. A served item whose route repeats a separator now returns its entity instead of a not-found refusal. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: unchanged; state extraction already stored these collections distinctly. - Generated metadata, package, or installation impact: none. - [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 to `src/application/environment/environmentStateAnswer.test.ts`: - "answers a state item whose route has a repeated path separator": serves two captured items, `/api/books/1` and `/api//books/1`, and asserts the double-separator item answers from `/api//books` while the single-separator item stays distinct under `/api/books`. - "creates into a collection whose route has a repeated path separator" (review follow-up): a generated create to `/api//books` returns 201 from state instead of a missing-argument refusal. - Base reproduction (executed): with only `environmentStateCallLines.ts` reverted, the item test fails with the issue's `AnalysisInputError`. With only the `environmentStateCollections.ts` guard change reverted, the create test fails with `needs every path argument to be non-empty`. - Reproduction of the reported issue (executed): the issue's synthetic HAR probe returned `answer.ok: false` for `/api//books/1` before the change and `answer.ok: true` after, with `/api/books/1` succeeding throughout. - [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 Run on Ubuntu 24.04 x64 with Node 24.22.1: - `npm run test:focused --` with every test file referencing environment state, `callSegments`, `collectionMatch`, `answerFromState`, `createdCollection`, `environment-serve`, `segmentsOf` or `dyldPaths` (47 files): 992 passed, 1 skipped, 0 failed. - `npm run test:local -- src/application/environment/environmentStateAnswer.test.ts`: 21 passed. With either fix reverted, its corresponding test fails. - `npm run check:fast`: passed. `knip` reports nothing for the touched module. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Only a previously failing served-item read begins succeeding; its collection extraction was already correct. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (synthetic capture; no provider). Linux only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new reads, execution, or network access. ## Independent verification on updated main Head `c4631987` integrates main `af3b039d`. Independent Linux validation passed 310 targeted domain/service/CLI/MCP tests and full `npm run check`. A real Chromium HAR of a local package-inventory application was imported through compiled CLI/stdio MCP, projected to state and served through HTTP MCP: repeated-separator item reads and generated creates succeeded, with ordinary-path collections isolated. Original capture/manifest/state Evidence remained identical. [Review and measured resource observations](https://github.com/morluto/rea/pull/6876#pullrequestreview-5634063144) include verification scope, timing variation and token-estimate limitations. CI run [40018253228](https://github.com/morluto/rea/actions/runs/40018253228) failed with 14 test failures, all reproduced on its clean base `af3b039d`; seven remaining shards were cancelled. Static/build/native-package checks and the agentenv export/run lane passed. Main then advanced to `0929fa42`: the unchanged PR was re-integrated there, and the same 310 tests, full check and real Chromium/CLI/MCP workflow passed again. [Final baseline and latest-main verification](https://github.com/morluto/rea/pull/6876#issuecomment-6374183028). ## Author readiness Human owner: @mhamzasakhi - [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. - [ ] 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:47:47 +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#7428
No description provided.