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 #2605] [MERGED] fix(native): keep lipo path echoes out of FAT records #5289

New issue
Closed
opened 2026-10-31 01:05:28 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:05:28 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2605
Author: @FengCi0
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: fix/lipo-fat-path-framing

📝 Commits (4)

  • 552edbf fix(native): keep lipo path echoes out of FAT records
  • 013927f fix(native): use parsed lipo framing for container offsets
  • fc955d4 test(native): use explicit FAT fixtures for CLI regressions
  • 781e425 fix(native): resolve upstream lipo merge conflicts

📊 Changes

10 files changed (+347 additions, -106 deletions)

View changed files

📝 src/artifacts/MachOSliceArtifactReader.ts (+2 -2)
📝 src/native/NativeMacOSProvider.ts (+5 -2)
📝 src/native/NativeMachoInspection.ts (+7 -7)
📝 src/native/parsers/lipo.test.ts (+105 -10)
📝 src/native/parsers/lipo.ts (+38 -17)
📝 tests/boundary/cli/nativeMachoEchoedPathCli.test.ts (+68 -23)
📝 tests/boundary/providers/native/machoSliceReader.test.ts (+53 -1)
📝 tests/boundary/providers/native/nativeProvider.test.ts (+13 -10)
📝 tests/boundary/providers/native/nativeSelectedArchitecture.test.ts (+44 -28)
📝 tests/boundary/providers/native/nativeTextRobustness.test.ts (+12 -6)

📄 Description

Summary

I fixed FAT Mach-O filenames being parsed as architecture records. A filename containing a newline followed by architecture forged made REA report a third slice for a two-slice file, or reject the artifact because the lipo count disagreed with its FAT table.

I found this while checking native parsing and reproduced the producer behavior with system lipo and a generated two-slice fixture. No separate issue is linked for this focused correction. I checked related work: #2040 covers slice selection, and #2107 covers codesign path echoes; neither isolates lipo's FAT operand header.

Problem and expected behavior

lipo -detailed_info prints Fat header in: <path> with the filename unchanged. Splitting that header into lines lets filename text become slice metadata. Only the actual tool records should contribute architectures, thin/FAT framing and ranges. A filename containing Non-fat file: also caused the inspection consumer to use a zero container offset and project segment/entrypoint evidence onto the wrong bytes.

Change and scope

The lipo parser receives the exact operand and removes only a complete matching FAT header ending in LF or CRLF. Native inspection, architecture listing and the slice reader pass their own lipo operand. The parser returns the thin/FAT framing together with architectures. Inspection uses that fact for its container offset rather than rescanning the raw capture. Thin and headerless captures retain their existing behavior, including single-slice FAT and unknown offsets. The CLI regressions share their driver rather than duplicate it.

Contract and boundary impact

  • Semantic owner: parseLipoOutput, before record parsing; consumers reuse its framing and architecture facts.
  • Scope decision: not applicable; this corrects existing static metadata parsing.
  • CLI/MCP/catalog: no command or schema changes. Incorrect filename-derived slices disappear.
  • Compatibility: native macOS workflows; existing thin/FAT formats and unknown CPU text are preserved.
  • Evidence/provenance: raw captures, artifact bytes and identities are preserved; only derived records change.
  • Authority/cleanup: no added native commands or target execution. Temporary test resources use existing awaited cleanup.
  • Generated metadata, package and installation: no changes.

Expected effects of the correction:

  • Read existing files or captured data.

Existing native tool subprocesses are unchanged. The target samples are not executed; this adds no instrumentation, target mutation, network access or protection recovery.

Evidence and regression coverage

  • 11 parser cases cover embedded architecture/header tokens, multiline and CRLF paths, literal regex characters, common prefixes and compatibility.
  • A generated FAT fixture passes through the real system lipo and slice reader, retaining exactly the two declared ranges.
  • Real compiled inspect-macho and list-architectures CLI calls return the same facts for ordinary and multiline names, including a forged Non-fat file: line. Each CLI case compiles the existing C fixture for arm64 and x86_64, then checks multiple slices and a positive selected container offset before comparing filenames. This removes reliance on the host's /usr/bin/true being FAT.
  • LF/CRLF provider cases preserve the selected FAT slice offset and container-relative segment/entrypoint evidence; thin, single-slice FAT and unknown-offset controls remain covered.
  • Restoring the base parser makes five architecture regressions fail. Before the framing follow-up, both provider cases and the real CLI case fail with an incorrect zero container offset (the CLI observed 0 instead of 49152).
  • Observations, derived records and unknowns remain distinct.
  • Artifact identity and original provenance are preserved.
  • Existing incomplete and unavailable outcomes remain visible.

Validation performed

With pinned Node 24.18.0 and npm 11.16.0 on macOS arm64:

  • npm run test:focused -- src/native/parsers/lipo.test.ts tests/boundary/providers/native/nativeTextRobustness.test.ts tests/boundary/providers/native/nativeProvider.test.ts tests/boundary/providers/native/machoSliceReader.test.ts tests/boundary/cli/nativeMachoEchoedPathCli.test.ts tests/boundary/providers/native/artifactProvider.machOSlices.test.ts tests/boundary/providers/native/nativeSelectedArchitecture.test.ts — 88 tests passed across seven files before the CLI fixture follow-up.
  • npm run test:focused -- tests/boundary/cli/nativeMachoEchoedPathCli.test.ts — all four CLI cases passed with the generated universal fixture.
  • Negative fixture experiment: compiling only arm64 makes the FAT precondition fail (1 architecture is not greater than 1), confirming thin fixtures cannot silently pass.
  • npm run check — passed, including typecheck, runtime compilation, lint, format, knip, metadata and architecture checks.
  • npm run verify:test-discovery — all 1023 files discovered once.
  • git diff --check — passed.

Compatibility, safety, and release

No breaking changes or migration. Real Apple metadata tools and compiled CLI coverage ran on macOS; Hopper/Ghidra and other host workflows were not run. No package, release metadata or execution-authority changes. Full deterministic coverage remains with CI.

Before merge

  • Concrete problem and one focused outcome.
  • Existing contribution boundaries preserved; no new provider or execution capability.
  • Conventional title and reason for no separate issue stated.
  • Regression and compatibility coverage included.
  • No owning schema or generated metadata change needed.
  • Representative CLI behavior recorded above.
  • Final diff checked for unrelated changes, secrets and unsupported claims.

Summary by CodeRabbit

  • Bug Fixes

    • Improved macOS architecture and slice detection for filenames containing text that resembles Mach-O metadata.
    • Prevented echoed filename text from being interpreted as architecture records, load commands, or symbols.
    • Improved slice offset reporting for thin and universal binaries across supported lipo output formats.

  • Tests

    • Expanded coverage for metadata-like filenames, including newline characters, and for thin and universal binary output formats.

🔄 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/2605 **Author:** [@FengCi0](https://github.com/FengCi0) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/lipo-fat-path-framing` --- ### 📝 Commits (4) - [`552edbf`](https://github.com/morluto/rea/commit/552edbfea3594aa107f5ea69a90e77d7d37dce19) fix(native): keep lipo path echoes out of FAT records - [`013927f`](https://github.com/morluto/rea/commit/013927ff5d7bbeaf0e67847fb1d6237d75edce57) fix(native): use parsed lipo framing for container offsets - [`fc955d4`](https://github.com/morluto/rea/commit/fc955d42e19450e95f926d8d4bdcbb78c292377e) test(native): use explicit FAT fixtures for CLI regressions - [`781e425`](https://github.com/morluto/rea/commit/781e425081fc821d4ba2a43918f81d23d9b2a659) fix(native): resolve upstream lipo merge conflicts ### 📊 Changes **10 files changed** (+347 additions, -106 deletions) <details> <summary>View changed files</summary> 📝 `src/artifacts/MachOSliceArtifactReader.ts` (+2 -2) 📝 `src/native/NativeMacOSProvider.ts` (+5 -2) 📝 `src/native/NativeMachoInspection.ts` (+7 -7) 📝 `src/native/parsers/lipo.test.ts` (+105 -10) 📝 `src/native/parsers/lipo.ts` (+38 -17) 📝 `tests/boundary/cli/nativeMachoEchoedPathCli.test.ts` (+68 -23) 📝 `tests/boundary/providers/native/machoSliceReader.test.ts` (+53 -1) 📝 `tests/boundary/providers/native/nativeProvider.test.ts` (+13 -10) 📝 `tests/boundary/providers/native/nativeSelectedArchitecture.test.ts` (+44 -28) 📝 `tests/boundary/providers/native/nativeTextRobustness.test.ts` (+12 -6) </details> ### 📄 Description ## Summary I fixed FAT Mach-O filenames being parsed as architecture records. A filename containing a newline followed by `architecture forged` made REA report a third slice for a two-slice file, or reject the artifact because the lipo count disagreed with its FAT table. I found this while checking native parsing and reproduced the producer behavior with system lipo and a generated two-slice fixture. No separate issue is linked for this focused correction. I checked related work: #2040 covers slice selection, and #2107 covers codesign path echoes; neither isolates lipo's FAT operand header. ## Problem and expected behavior `lipo -detailed_info` prints `Fat header in: <path>` with the filename unchanged. Splitting that header into lines lets filename text become slice metadata. Only the actual tool records should contribute architectures, thin/FAT framing and ranges. A filename containing `Non-fat file:` also caused the inspection consumer to use a zero container offset and project segment/entrypoint evidence onto the wrong bytes. ## Change and scope The lipo parser receives the exact operand and removes only a complete matching FAT header ending in LF or CRLF. Native inspection, architecture listing and the slice reader pass their own lipo operand. The parser returns the thin/FAT framing together with architectures. Inspection uses that fact for its container offset rather than rescanning the raw capture. Thin and headerless captures retain their existing behavior, including single-slice FAT and unknown offsets. The CLI regressions share their driver rather than duplicate it. ## Contract and boundary impact - Semantic owner: `parseLipoOutput`, before record parsing; consumers reuse its framing and architecture facts. - Scope decision: not applicable; this corrects existing static metadata parsing. - CLI/MCP/catalog: no command or schema changes. Incorrect filename-derived slices disappear. - Compatibility: native macOS workflows; existing thin/FAT formats and unknown CPU text are preserved. - Evidence/provenance: raw captures, artifact bytes and identities are preserved; only derived records change. - Authority/cleanup: no added native commands or target execution. Temporary test resources use existing awaited cleanup. - Generated metadata, package and installation: no changes. Expected effects of the correction: - [x] Read existing files or captured data. Existing native tool subprocesses are unchanged. The target samples are not executed; this adds no instrumentation, target mutation, network access or protection recovery. ## Evidence and regression coverage - 11 parser cases cover embedded architecture/header tokens, multiline and CRLF paths, literal regex characters, common prefixes and compatibility. - A generated FAT fixture passes through the real system lipo and slice reader, retaining exactly the two declared ranges. - Real compiled `inspect-macho` and `list-architectures` CLI calls return the same facts for ordinary and multiline names, including a forged `Non-fat file:` line. Each CLI case compiles the existing C fixture for arm64 and x86_64, then checks multiple slices and a positive selected container offset before comparing filenames. This removes reliance on the host's `/usr/bin/true` being FAT. - LF/CRLF provider cases preserve the selected FAT slice offset and container-relative segment/entrypoint evidence; thin, single-slice FAT and unknown-offset controls remain covered. - Restoring the base parser makes five architecture regressions fail. Before the framing follow-up, both provider cases and the real CLI case fail with an incorrect zero container offset (the CLI observed 0 instead of 49152). - [x] Observations, derived records and unknowns remain distinct. - [x] Artifact identity and original provenance are preserved. - [x] Existing incomplete and unavailable outcomes remain visible. ## Validation performed With pinned Node 24.18.0 and npm 11.16.0 on macOS arm64: - `npm run test:focused -- src/native/parsers/lipo.test.ts tests/boundary/providers/native/nativeTextRobustness.test.ts tests/boundary/providers/native/nativeProvider.test.ts tests/boundary/providers/native/machoSliceReader.test.ts tests/boundary/cli/nativeMachoEchoedPathCli.test.ts tests/boundary/providers/native/artifactProvider.machOSlices.test.ts tests/boundary/providers/native/nativeSelectedArchitecture.test.ts` — 88 tests passed across seven files before the CLI fixture follow-up. - `npm run test:focused -- tests/boundary/cli/nativeMachoEchoedPathCli.test.ts` — all four CLI cases passed with the generated universal fixture. - Negative fixture experiment: compiling only arm64 makes the FAT precondition fail (`1` architecture is not greater than `1`), confirming thin fixtures cannot silently pass. - `npm run check` — passed, including typecheck, runtime compilation, lint, format, knip, metadata and architecture checks. - `npm run verify:test-discovery` — all 1023 files discovered once. - `git diff --check` — passed. ## Compatibility, safety, and release No breaking changes or migration. Real Apple metadata tools and compiled CLI coverage ran on macOS; Hopper/Ghidra and other host workflows were not run. No package, release metadata or execution-authority changes. Full deterministic coverage remains with CI. ## Before merge - [x] Concrete problem and one focused outcome. - [x] Existing contribution boundaries preserved; no new provider or execution capability. - [x] Conventional title and reason for no separate issue stated. - [x] Regression and compatibility coverage included. - [x] No owning schema or generated metadata change needed. - [x] Representative CLI behavior recorded above. - [x] Final diff checked for unrelated changes, secrets and unsupported claims. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved macOS architecture and slice detection for filenames containing text that resembles Mach-O metadata. * Prevented echoed filename text from being interpreted as architecture records, load commands, or symbols. * Improved slice offset reporting for thin and universal binaries across supported `lipo` output formats. * **Tests** * Expanded coverage for metadata-like filenames, including newline characters, and for thin and universal binary output formats. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:05:28 +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#5289
No description provided.