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 #5784] [MERGED] perf(test): reuse one compiled CLI for the remaining hot command files #7058

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

📋 Pull Request Information

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

Base: main ← Head: cursor/ci-queue-shard-wins-d342

📝 Commits (1)

  • b98f734 perf(test): reuse one compiled CLI for the remaining hot command files

📊 Changes

6 files changed (+98 additions, -73 deletions)

View changed files

📝 docs/testing.md (+7 -2)
📝 tests/acceptance/applications/applicationWorkflowCli.test.ts (+25 -23)
📝 tests/acceptance/goBinaryCli.test.ts (+16 -16)
📝 tests/acceptance/il2cppMetadataCli.test.ts (+16 -16)
📝 tests/boundary/cli/dylibResolutionCli.test.ts (+20 -16)
📝 tests/support/cli/cliFixture.ts (+14 -0)

📄 Description

Summary

The slowest remaining acceptance commands still started a compiled CLI process for every call, after the shared JavaScript session (#5676) and the warm export-binding CLI (#5679). Go binary, IL2CPP metadata, dylib resolution, and application-workflow JSON commands now reuse one compiled process per file. Assertions are unchanged.

Human owner: @morluto.

Problem and expected behavior

On fast main run 39542179402 (3a0e91dd, after #5676 and before #5679), these files were still among the longest built modules: goBinaryCli.test.ts 76.0s, applicationWorkflowCli.test.ts 69.5s, il2cppMetadataCli.test.ts 42.9s, and dylibResolutionCli.test.ts 40.9s. Each cli.run or execFile(scripts/rea.mjs) paid process startup again. Commands with stdin or an explicit deadline still need a fresh process. These calls have neither.

Change and scope

runFileCli sends a cliTest command through the existing file-scoped session. Go, IL2CPP, and dylib-resolution tests use it. Application workflow keeps its own session so a non-zero status whose stdout is JSON is still returned as that document, matching the previous execFile catch path. The session restarts when the environment changes, after 32 commands, or at a 1 GiB resident set, and the file closes it afterward.

Not included: shard-count changes, cancel-in-progress on main, or moving setup commands that pass timeoutMs. Eight fast shards already sit on the ten-minute job budget (slowest built shard execution on that run was 547s). Main keeps the in-progress feedback run so a burst of pushes cannot cancel every attempt. Vitest already forces maxWorkers: 1 when fileParallelism is false, so the process-boundary lane is already serial in the sequencer.

No separate issue is linked. This continues the standing CI wall-time work already landed in #5676 and #5679.

Contribution scope: not applicable. This is test harness work inside existing CLI/MCP checks.

Contract and boundary impact

  • Semantic owner and earliest changed stage: the acceptance and boundary tests own the reused CLI child. Command results still come from the compiled CLI runtime.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: none. Production commands are unchanged.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none. The same JSON results are still required.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): the shared child is closed with the file. A different environment, the command limit, or the resident-set limit starts another owned process. Stdin and explicit deadlines stay on a fresh process.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

Expected effects: test-only. No product target interaction.

Evidence and regression coverage

  • Tests added or updated: the four files above call the shared session. No assertions were removed. tests/support/cli/cliFixture.ts adds runFileCli. docs/testing.md records both reuse paths.
  • Base reproduction or other evidence: warm local vitest runs on Node 24.18.0, no coverage. Before: Go 39.65s, application workflow 46.08s, IL2CPP 35.32s, dylib resolution 21.15s. After: 14.15s, 21.01s, 20.38s, and 2.17s. All four passed before and after. tests/boundary/cli/sharedJavaScriptCliSession.test.ts passed.
  • User-visible CLI/MCP output (if applicable): none. There is no public CLI or MCP projection change, so no representative command output is included.
  • Remaining proof gaps: GitHub Actions has not run this head. The local ratio is not a measured CI shard wall time. These files share eight shards and two workers, so the uncontended shard critical path should drop by tens of seconds of module time, not by the sum of the file times. Runner queue is a separate, larger delay and is unchanged.

Validation performed

  • node node_modules/vitest/vitest.mjs run --project acceptance tests/acceptance/goBinaryCli.test.ts — passed, warm 39.65s then 14.15s.
  • node node_modules/vitest/vitest.mjs run --project acceptance tests/acceptance/applications/applicationWorkflowCli.test.ts — passed, warm 46.08s then 21.01s.
  • node node_modules/vitest/vitest.mjs run --project acceptance tests/acceptance/il2cppMetadataCli.test.ts — passed, 35.32s then 20.38s.
  • node node_modules/vitest/vitest.mjs run --project cli-boundary tests/boundary/cli/dylibResolutionCli.test.ts — passed, 21.15s then 2.17s.
  • node node_modules/vitest/vitest.mjs run --project cli-boundary tests/boundary/cli/sharedJavaScriptCliSession.test.ts — passed.
  • npm run check:fast — passed (typecheck and lint, 24.2s).

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. These tests use local fixtures and the compiled CLI.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the test child is still owned and closed with the file. No new product authority.

Author readiness

Human owner: @morluto

  • 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.
Open in Web Open in Cursor 

🔄 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/5784 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/ci-queue-shard-wins-d342` --- ### 📝 Commits (1) - [`b98f734`](https://github.com/morluto/rea/commit/b98f734517e0662d0a26f02c40df66da08f59cb6) perf(test): reuse one compiled CLI for the remaining hot command files ### 📊 Changes **6 files changed** (+98 additions, -73 deletions) <details> <summary>View changed files</summary> 📝 `docs/testing.md` (+7 -2) 📝 `tests/acceptance/applications/applicationWorkflowCli.test.ts` (+25 -23) 📝 `tests/acceptance/goBinaryCli.test.ts` (+16 -16) 📝 `tests/acceptance/il2cppMetadataCli.test.ts` (+16 -16) 📝 `tests/boundary/cli/dylibResolutionCli.test.ts` (+20 -16) 📝 `tests/support/cli/cliFixture.ts` (+14 -0) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary The slowest remaining acceptance commands still started a compiled CLI process for every call, after the shared JavaScript session (#5676) and the warm export-binding CLI (#5679). Go binary, IL2CPP metadata, dylib resolution, and application-workflow JSON commands now reuse one compiled process per file. Assertions are unchanged. Human owner: @morluto. ## Problem and expected behavior On fast main run `39542179402` (`3a0e91dd`, after #5676 and before #5679), these files were still among the longest built modules: `goBinaryCli.test.ts` 76.0s, `applicationWorkflowCli.test.ts` 69.5s, `il2cppMetadataCli.test.ts` 42.9s, and `dylibResolutionCli.test.ts` 40.9s. Each `cli.run` or `execFile(scripts/rea.mjs)` paid process startup again. Commands with stdin or an explicit deadline still need a fresh process. These calls have neither. ## Change and scope `runFileCli` sends a `cliTest` command through the existing file-scoped session. Go, IL2CPP, and dylib-resolution tests use it. Application workflow keeps its own session so a non-zero status whose stdout is JSON is still returned as that document, matching the previous `execFile` catch path. The session restarts when the environment changes, after 32 commands, or at a 1 GiB resident set, and the file closes it afterward. Not included: shard-count changes, cancel-in-progress on main, or moving setup commands that pass `timeoutMs`. Eight fast shards already sit on the ten-minute job budget (slowest built shard execution on that run was 547s). Main keeps the in-progress feedback run so a burst of pushes cannot cancel every attempt. Vitest already forces `maxWorkers: 1` when `fileParallelism` is false, so the process-boundary lane is already serial in the sequencer. No separate issue is linked. This continues the standing CI wall-time work already landed in #5676 and #5679. Contribution scope: not applicable. This is test harness work inside existing CLI/MCP checks. ## Contract and boundary impact - Semantic owner and earliest changed stage: the acceptance and boundary tests own the reused CLI child. Command results still come from the compiled CLI runtime. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none. Production commands are unchanged. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. The same JSON results are still required. - Target selection, authority, upstream behavior, and cleanup details (if applicable): the shared child is closed with the file. A different environment, the command limit, or the resident-set limit starts another owned process. Stdin and explicit deadlines stay on a fresh process. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects: test-only. No product target interaction. ## Evidence and regression coverage - Tests added or updated: the four files above call the shared session. No assertions were removed. `tests/support/cli/cliFixture.ts` adds `runFileCli`. `docs/testing.md` records both reuse paths. - Base reproduction or other evidence: warm local vitest runs on Node 24.18.0, no coverage. Before: Go 39.65s, application workflow 46.08s, IL2CPP 35.32s, dylib resolution 21.15s. After: 14.15s, 21.01s, 20.38s, and 2.17s. All four passed before and after. `tests/boundary/cli/sharedJavaScriptCliSession.test.ts` passed. - User-visible CLI/MCP output (if applicable): none. There is no public CLI or MCP projection change, so no representative command output is included. - Remaining proof gaps: GitHub Actions has not run this head. The local ratio is not a measured CI shard wall time. These files share eight shards and two workers, so the uncontended shard critical path should drop by tens of seconds of module time, not by the sum of the file times. Runner queue is a separate, larger delay and is unchanged. ## Validation performed - `node node_modules/vitest/vitest.mjs run --project acceptance tests/acceptance/goBinaryCli.test.ts` — passed, warm 39.65s then 14.15s. - `node node_modules/vitest/vitest.mjs run --project acceptance tests/acceptance/applications/applicationWorkflowCli.test.ts` — passed, warm 46.08s then 21.01s. - `node node_modules/vitest/vitest.mjs run --project acceptance tests/acceptance/il2cppMetadataCli.test.ts` — passed, 35.32s then 20.38s. - `node node_modules/vitest/vitest.mjs run --project cli-boundary tests/boundary/cli/dylibResolutionCli.test.ts` — passed, 21.15s then 2.17s. - `node node_modules/vitest/vitest.mjs run --project cli-boundary tests/boundary/cli/sharedJavaScriptCliSession.test.ts` — passed. - `npm run check:fast` — passed (typecheck and lint, 24.2s). ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. These tests use local fixtures and the compiled CLI. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the test child is still owned and closed with the file. No new product authority. ## Author readiness Human owner: @morluto - [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. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-ac6d4d10-cdbc-5a68-a6b1-e326f171d342?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-ac6d4d10-cdbc-5a68-a6b1-e326f171d342&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <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:02 +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#7058
No description provided.