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 #5886] [MERGED] test(ci): keep module mocks in isolated test projects #7102

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5886
Author: @kaoru0822-kitauji
Created: 10/21/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @kaoru0822-kitauji

Base: main ← Head: test/isolate-module-mocks

📝 Commits (4)

  • 3f8c78c test(ci): keep module mocks in isolated test projects
  • eb1e835 test(pe): share one compiled CLI process across PE resource inspections
  • dfb2ac6 Merge remote-tracking branch 'origin/main' into test/isolate-module-mocks
  • 4738cd2 Merge remote-tracking branch 'origin/main' into test/isolate-module-mocks

📊 Changes

2 files changed (+46 additions, -5 deletions)

View changed files

📝 tests/boundary/filesystem/ciTestProjects.test.ts (+41 -0)
📝 tests/process-global/directAnalysisStatFailure.test.ts (+5 -5)

📄 Description

What broke: module-mocking tests in Vitest projects with isolate: false (one module graph shared per worker) pass or fail depending on file scheduling. This made the environmentExport.test.ts source tests fail intermittently on hosted runs (e.g. PRs #5852 and #5874) until c324d31b4 removed those mocks.
Fix: a guard test requires every tracked test using vi.mock/vi.doMock to belong to an isolated project. The last shared-graph case, DirectAnalysisStatFailure.test.ts, moves to process-global, where the repository already keeps module-mocking workflow tests.
Risk: low. Test layout only; no product code changes. The moved test now runs with the built lane.

Summary

c324d31b4 fixed the observed environmentExport failures by removing those mocks. This PR prevents the same class of failure from returning and moves the one remaining file that breaks the rule. No issue is filed for this CI failure, so none is linked.

Problem and expected behavior

In a project with isolate: false, vi.mock takes effect only if no earlier file in the same worker already loaded the mocked module. The services, domain, composition, conformance, evaluation, cli-boundary and mcp-boundary projects share their graph for speed. vitest.config.ts already notes that "module mocks belong in process-global", but nothing enforced it.

The rule should hold mechanically: a mock's effect should never depend on which file ran first.

Change and scope

An earlier revision also moved the PE resource acceptance test onto the shared compiled CLI process. Main's 905cbaf23 (#5795) made the same startup reduction while keeping independent wrapper processes for PE32/PE32+, so that part was dropped in favour of main's version.

  • tests/boundary/filesystem/ciTestProjects.test.ts: new test module isolation check. It loads vitest.config.ts the same way the existing worker-policy check does to read each project's isolate. It then uses projectForTest to map every tracked *.test.ts that calls vi.mock( or vi.doMock( to its project. The check fails, naming the files, when one belongs to a shared-graph project.
  • src/application/DirectAnalysisStatFailure.test.ts → tests/process-global/directAnalysisStatFailure.test.ts, with only its relative imports rewritten. It mocks node:fs/promises in services.
  • Not included: rewriting that test without mocks (as c324d31b4 did for environment export), or changing any project's isolation policy.
  • Scope decision: not applicable (test infrastructure only).

Contract and boundary impact

  • Semantic owner and earliest changed stage: test-project policy (scripts/lib/test-projects.mjs ownership plus vitest.config.ts isolation).
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, package, or installation impact: none.

Expected 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

  • Tests added or updated: the guard above; the moved test is otherwise unchanged.
  • Base reproduction (executed, macOS arm64, on 5eebe2fdf before c324d31b4): npx vitest run --project services --maxWorkers=1 --sequence.shuffle --sequence.seed=<1|2|3> src/application/environment/ failed the same four environmentExport.test.ts cases as hosted CI. These were the manifest/evidence snapshot-change refusals and the two heap-admission refusals; they passed when run alone.
  • Guard verification (executed): with environmentExport.test.ts temporarily moved back under services, the guard failed and listed exactly src/application/environment/environmentExport.test.ts. With the final layout it passes.
  • DirectAnalysisStatFailure (executed): in its old location, four shuffled single-worker services runs (seeds 1–4) all passed. It is a latent case under the rule, not an observed flake.
  • Remaining proof gaps: the guard detects vi.mock(/vi.doMock( call text only, not mocks set up through helpers in other modules.

Validation performed

  • npm run test:focused -- tests/process-global/directAnalysisStatFailure.test.ts tests/boundary/filesystem/ciTestProjects.test.ts — 2 files, 19 tests passed
  • npx vitest run --project services — 118 files passed (1732 tests, 2 skipped)
  • npm run check:fast — passed
  • npm run format:check — passed

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS arm64 locally; hosted Linux via CI.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none needed (tests only).

Author readiness

Human owner: @kaoru0822-kitauji

  • 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.

🤖 Generated with Claude Code

🔄 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/5886 **Author:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Base:** `main` ← **Head:** `test/isolate-module-mocks` --- ### 📝 Commits (4) - [`3f8c78c`](https://github.com/morluto/rea/commit/3f8c78c78497ead35f225f712a79eaf8c5aa8168) test(ci): keep module mocks in isolated test projects - [`eb1e835`](https://github.com/morluto/rea/commit/eb1e8355ec420e6c6ad697393f3644974a3e5568) test(pe): share one compiled CLI process across PE resource inspections - [`dfb2ac6`](https://github.com/morluto/rea/commit/dfb2ac6c5e8ba9fbf0d5c443927f836cc5ab982c) Merge remote-tracking branch 'origin/main' into test/isolate-module-mocks - [`4738cd2`](https://github.com/morluto/rea/commit/4738cd2b61eabd761a86b6f6c120e7f3b357cc25) Merge remote-tracking branch 'origin/main' into test/isolate-module-mocks ### 📊 Changes **2 files changed** (+46 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `tests/boundary/filesystem/ciTestProjects.test.ts` (+41 -0) 📝 `tests/process-global/directAnalysisStatFailure.test.ts` (+5 -5) </details> ### 📄 Description **What broke:** module-mocking tests in Vitest projects with `isolate: false` (one module graph shared per worker) pass or fail depending on file scheduling. This made the `environmentExport.test.ts` source tests fail intermittently on hosted runs (e.g. PRs #5852 and #5874) until c324d31b4 removed those mocks. **Fix:** a guard test requires every tracked test using `vi.mock`/`vi.doMock` to belong to an isolated project. The last shared-graph case, `DirectAnalysisStatFailure.test.ts`, moves to `process-global`, where the repository already keeps module-mocking workflow tests. **Risk:** low. Test layout only; no product code changes. The moved test now runs with the built lane. ## Summary c324d31b4 fixed the observed `environmentExport` failures by removing those mocks. This PR prevents the same class of failure from returning and moves the one remaining file that breaks the rule. No issue is filed for this CI failure, so none is linked. ## Problem and expected behavior In a project with `isolate: false`, `vi.mock` takes effect only if no earlier file in the same worker already loaded the mocked module. The `services`, `domain`, `composition`, `conformance`, `evaluation`, `cli-boundary` and `mcp-boundary` projects share their graph for speed. `vitest.config.ts` already notes that "module mocks belong in process-global", but nothing enforced it. The rule should hold mechanically: a mock's effect should never depend on which file ran first. ## Change and scope An earlier revision also moved the PE resource acceptance test onto the shared compiled CLI process. Main's 905cbaf23 (#5795) made the same startup reduction while keeping independent wrapper processes for PE32/PE32+, so that part was dropped in favour of main's version. - `tests/boundary/filesystem/ciTestProjects.test.ts`: new `test module isolation` check. It loads `vitest.config.ts` the same way the existing worker-policy check does to read each project's `isolate`. It then uses `projectForTest` to map every tracked `*.test.ts` that calls `vi.mock(` or `vi.doMock(` to its project. The check fails, naming the files, when one belongs to a shared-graph project. - `src/application/DirectAnalysisStatFailure.test.ts` → `tests/process-global/directAnalysisStatFailure.test.ts`, with only its relative imports rewritten. It mocks `node:fs/promises` in `services`. - Not included: rewriting that test without mocks (as c324d31b4 did for environment export), or changing any project's isolation policy. - Scope decision: not applicable (test infrastructure only). ## Contract and boundary impact - Semantic owner and earliest changed stage: test-project policy (`scripts/lib/test-projects.mjs` ownership plus `vitest.config.ts` isolation). - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. Expected 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. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: the guard above; the moved test is otherwise unchanged. - Base reproduction (executed, macOS arm64, on 5eebe2fdf before c324d31b4): `npx vitest run --project services --maxWorkers=1 --sequence.shuffle --sequence.seed=<1|2|3> src/application/environment/` failed the same four `environmentExport.test.ts` cases as hosted CI. These were the manifest/evidence snapshot-change refusals and the two heap-admission refusals; they passed when run alone. - Guard verification (executed): with `environmentExport.test.ts` temporarily moved back under `services`, the guard failed and listed exactly `src/application/environment/environmentExport.test.ts`. With the final layout it passes. - `DirectAnalysisStatFailure` (executed): in its old location, four shuffled single-worker `services` runs (seeds 1–4) all passed. It is a latent case under the rule, not an observed flake. - Remaining proof gaps: the guard detects `vi.mock(`/`vi.doMock(` call text only, not mocks set up through helpers in other modules. ## Validation performed - `npm run test:focused -- tests/process-global/directAnalysisStatFailure.test.ts tests/boundary/filesystem/ciTestProjects.test.ts` — 2 files, 19 tests passed - `npx vitest run --project services` — 118 files passed (1732 tests, 2 skipped) - `npm run check:fast` — passed - `npm run format:check` — passed ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: macOS arm64 locally; hosted Linux via CI. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none needed (tests only). ## Author readiness Human owner: @kaoru0822-kitauji - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:45:24 +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#7102
No description provided.