[PR #2907] [CLOSED] fix(reference): reconcile excluded symlink identities #5488

New issue

Closed

opened 2026-10-31 01:07:02 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:07:02 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2907
Author: @Adkid-Zephyr
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: fix/reference-excluded-symlink

---

📝 Commits (10+)

• 62ec3db fix(reference): retain links to excluded source paths
• 1786fdd fix(reference): require exact excluded symlink targets
• b1f097b fix(reference): preserve excluded directory coverage
• 3da27cf fix(reference): distinguish omitted paths from escape facts
• 333e32c Merge remote-tracking branch 'origin/main' into fix/reference-excluded-symlink
• 3cd5f6c fix(reference): preserve specific exclusion identity
• 162fd65 fix(reference): validate exclusion kinds and index ancestors
• 49da456 Merge remote-tracking branch 'origin/main' into fix/reference-excluded-symlink
• 4d3e6d9 fix(reference): compare exclusion kinds by filesystem spelling
• 8bac307 Merge remote-tracking branch 'origin/main' into fix/reference-excluded-symlink

📊 Changes

5 files changed (+291 additions, -41 deletions)

View changed files

📝 src/domain/referenceSourceGraph.test.ts (+139 -0)
📝 src/domain/referenceSourceGraph.ts (+36 -26)
➕ src/domain/referenceSourcePathIdentity.test.ts (+40 -0)
📝 src/domain/referenceSourcePathIdentity.ts (+46 -13)
📝 tests/boundary/filesystem/referenceSourceImport.test.ts (+30 -2)

📄 Description

Summary

Fixes #2651. Thanks to @coygeek for the original report.

Validate excluded symlink targets without conflating distinct filesystem spellings or repeatedly walking and normalizing long path prefixes. Current main supplies the exclusion-kind metadata and missing-target handling; this PR preserves those behaviors and completes graph consistency and identity checks.

Problem and expected behavior

A source tree may contain an excluded directory café and a different file cafe\u0301. Their recorded filesystem identities must not be conflated when checking entry kinds. Symbolic-reference lookup can still use an unambiguous Unicode fallback.

An internal target must also agree with the recorded facts: an escape is not an omission, an excluded file cannot establish subtree coverage, and directory evidence cannot contradict an inventoried file at the same exact path. Unknown kind remains unknown.

Change and scope

• Compare exclusion/inventory kinds by exact recorded spelling.
• Match recorded prefixes through lazy exact/canonical component indexes. Normalize each query once and retain unknown identity when a prefix is ambiguous.
• Validate every applicable excluded prefix: only directory evidence covers descendants; exact omissions keep their existing meaning. Escape facts never supply internal-target coverage.
• Skip exclusion lookup for already-inventoried targets. Remove the superseded parent-walking API and preserve upstream missing-target, literal-path, and exclusion-kind behavior.

Contract and boundary impact

• Semantic owners: historical-source graph validation and reference-path identity.
• Contribution scope: ordinary static source-import correctness; no new provider or capability requiring a separate scope decision.
• CLI/MCP: the current-main graph shape and exclusion-kind schema remain unchanged. New checks reject contradictory graph facts while preserving valid imported source metadata and partial inventories.
• Evidence: exact source spellings, exclusion reasons/patterns, hashes, and unknowns remain preserved. Existing graph commitments are not rewritten.
• Platform coverage: macOS source/CLI tests; Linux filename-coexistence fixture is included for CI. No real analysis engine or paid API is involved.

Expected operation effects:

• 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

The original source-import failure and later review findings were reproduced before their corrections. Coverage includes distinct NFC/NFD filesystem names, exact kind conflicts, unknown kind, legacy omissions, directory descendants, escapes, mixed exclusion kinds, sibling boundaries, and source preservation.

A small 128-component query made 128 normalization calls with the original parent walker and one with the component index. This is a resource-work regression, not an end-to-end latency, token, CPU, or memory improvement claim.

• 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

Pinned Node 24.18.0 / npm 11.16.0; head 1092f12d includes main 500e3239 and preserves maintainer commits:

• All 26 reference-source suites through npm run test:focused — 139 passed, 3 skipped. One skip is the new Linux filesystem-coexistence test; its platform-independent graph regression passed locally.
• npm run check — passed, including architecture guards.
• npm run docs:check — passed, including 5 consistency tests.
• npm run verify:test-discovery — 1,244 files discovered exactly once.
• git diff --check — passed.

The eight suites implicated in the preceding CI run were also rerun after incorporating upstream #3080 and the README-fact isolation fix: 117 passed (injected IDA protocol fixture, no real provider). The full suite and actual Linux coexistence case remain for current-head CI. Local test results do not claim CI or maintainer approval.

Compatibility, safety, and release

No new graph field relative to current main, provider, package entrypoint, or installation behavior. Static import remains read-only. Tests use self-created fixtures. Main's general exclusion-kind and missing-target behavior is retained rather than replaced by the earlier narrower representation.

Implementation, regression tests, conflict resolution, and self-review were assisted by OpenAI Codex.

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 coverage.
• I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/2907 **Author:** [@Adkid-Zephyr](https://github.com/Adkid-Zephyr) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/reference-excluded-symlink` --- ### 📝 Commits (10+) - [`62ec3db`](https://github.com/morluto/rea/commit/62ec3db8bd5a071e28ca8058274fc2d695f06fc3) fix(reference): retain links to excluded source paths - [`1786fdd`](https://github.com/morluto/rea/commit/1786fdd0019ee35ddc697e1996236875711e00a4) fix(reference): require exact excluded symlink targets - [`b1f097b`](https://github.com/morluto/rea/commit/b1f097bcc2a96dc918fea83037ee07ded5e528f7) fix(reference): preserve excluded directory coverage - [`3da27cf`](https://github.com/morluto/rea/commit/3da27cf4fc977e130ff71a78cbd16a5be40be7ad) fix(reference): distinguish omitted paths from escape facts - [`333e32c`](https://github.com/morluto/rea/commit/333e32c4f927ddb329eacf4056ecda15e6d08ae6) Merge remote-tracking branch 'origin/main' into fix/reference-excluded-symlink - [`3cd5f6c`](https://github.com/morluto/rea/commit/3cd5f6c2790770f3daba3fa0180219b8f803eaa0) fix(reference): preserve specific exclusion identity - [`162fd65`](https://github.com/morluto/rea/commit/162fd6537e78b07b5c15684d61c171540ec0a58c) fix(reference): validate exclusion kinds and index ancestors - [`49da456`](https://github.com/morluto/rea/commit/49da456b905fc5cb983535440ad82b076a34cf54) Merge remote-tracking branch 'origin/main' into fix/reference-excluded-symlink - [`4d3e6d9`](https://github.com/morluto/rea/commit/4d3e6d98fdfe4a306b708fa5ed3ae9b1f75e8dfa) fix(reference): compare exclusion kinds by filesystem spelling - [`8bac307`](https://github.com/morluto/rea/commit/8bac3070e10de1666268e9e461abecb9fc0024e3) Merge remote-tracking branch 'origin/main' into fix/reference-excluded-symlink ### 📊 Changes **5 files changed** (+291 additions, -41 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/referenceSourceGraph.test.ts` (+139 -0) 📝 `src/domain/referenceSourceGraph.ts` (+36 -26) ➕ `src/domain/referenceSourcePathIdentity.test.ts` (+40 -0) 📝 `src/domain/referenceSourcePathIdentity.ts` (+46 -13) 📝 `tests/boundary/filesystem/referenceSourceImport.test.ts` (+30 -2) </details> ### 📄 Description ## Summary Fixes #2651. Thanks to @coygeek for the original report. Validate excluded symlink targets without conflating distinct filesystem spellings or repeatedly walking and normalizing long path prefixes. Current main supplies the exclusion-kind metadata and missing-target handling; this PR preserves those behaviors and completes graph consistency and identity checks. ## Problem and expected behavior A source tree may contain an excluded directory `café` and a different file `cafe\u0301`. Their recorded filesystem identities must not be conflated when checking entry kinds. Symbolic-reference lookup can still use an unambiguous Unicode fallback. An internal target must also agree with the recorded facts: an escape is not an omission, an excluded file cannot establish subtree coverage, and directory evidence cannot contradict an inventoried file at the same exact path. Unknown kind remains unknown. ## Change and scope - Compare exclusion/inventory kinds by exact recorded spelling. - Match recorded prefixes through lazy exact/canonical component indexes. Normalize each query once and retain unknown identity when a prefix is ambiguous. - Validate every applicable excluded prefix: only directory evidence covers descendants; exact omissions keep their existing meaning. Escape facts never supply internal-target coverage. - Skip exclusion lookup for already-inventoried targets. Remove the superseded parent-walking API and preserve upstream missing-target, literal-path, and exclusion-kind behavior. ## Contract and boundary impact - Semantic owners: historical-source graph validation and reference-path identity. - Contribution scope: ordinary static source-import correctness; no new provider or capability requiring a separate scope decision. - CLI/MCP: the current-main graph shape and exclusion-kind schema remain unchanged. New checks reject contradictory graph facts while preserving valid imported source metadata and partial inventories. - Evidence: exact source spellings, exclusion reasons/patterns, hashes, and unknowns remain preserved. Existing graph commitments are not rewritten. - Platform coverage: macOS source/CLI tests; Linux filename-coexistence fixture is included for CI. No real analysis engine or paid API is involved. Expected operation effects: - [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 The original source-import failure and later review findings were reproduced before their corrections. Coverage includes distinct NFC/NFD filesystem names, exact kind conflicts, unknown kind, legacy omissions, directory descendants, escapes, mixed exclusion kinds, sibling boundaries, and source preservation. A small 128-component query made 128 normalization calls with the original parent walker and one with the component index. This is a resource-work regression, not an end-to-end latency, token, CPU, or memory improvement claim. - [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 Pinned Node 24.18.0 / npm 11.16.0; head `1092f12d` includes main `500e3239` and preserves maintainer commits: - All 26 reference-source suites through `npm run test:focused` — **139 passed, 3 skipped**. One skip is the new Linux filesystem-coexistence test; its platform-independent graph regression passed locally. - `npm run check` — passed, including architecture guards. - `npm run docs:check` — passed, including 5 consistency tests. - `npm run verify:test-discovery` — 1,244 files discovered exactly once. - `git diff --check` — passed. The eight suites implicated in the preceding CI run were also rerun after incorporating upstream #3080 and the README-fact isolation fix: **117 passed** (injected IDA protocol fixture, no real provider). The full suite and actual Linux coexistence case remain for current-head CI. Local test results do not claim CI or maintainer approval. ## Compatibility, safety, and release No new graph field relative to current main, provider, package entrypoint, or installation behavior. Static import remains read-only. Tests use self-created fixtures. Main's general exclusion-kind and missing-target behavior is retained rather than replaced by the earlier narrower representation. Implementation, regression tests, conflict resolution, and self-review were assisted by OpenAI Codex. ## 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 coverage. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:07:02 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-03 13:39:23 +00:00

[PR #7116] [CLOSED] feat(browser): validate browser scenarios with --dry-run before launching #7652

bsakaguchi referenced this issue 2026-11-03 13:39:34 +00:00

[PR #7149] [CLOSED] feat(cli): validate a browser scenario without launching a browser #7676

bsakaguchi referenced this issue 2026-11-05 01:47:56 +00:00

[PR #7343] [MERGED] feat(cli): validate browser scenarios offline #7825

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

No description provided.