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 #1920] [CLOSED] fix(javascript): admit deferred semantic graphs after later sources #4910

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1920
Author: @jimpablo
Created: 10/11/2026
Status: ❌ Closed

Base: main ← Head: fix/javascript-parent-admission

📝 Commits (2)

  • 93df06e fix(javascript): admit deferred semantic graphs after later sources
  • 40096c1 fix(javascript): reserve only the next static checkpoint

📊 Changes

5 files changed (+365 additions, -64 deletions)

View changed files

📝 src/application/javascript/JavaScriptArtifactAnalysis.ts (+28 -1)
📝 src/domain/javascript/javascriptSourceAnalysis.ts (+14 -0)
📝 src/javascript/analysis/JavaScriptAnalysisTransfer.ts (+4 -1)
📝 src/javascript/analysis/JavaScriptAnalysisWorker.ts (+189 -62)
➕ tests/boundary/cli/javascriptAdmissionBudget.test.ts (+130 -0)

📄 Description

Summary

Fixes #1911. Fixes #1847.

On current main, the original #1847 worker-heap exhaustion no longer reproduces for the two generated wrappers (maintainer check at 898d5096, and this host did not see exhausted its heap). Directory analysis of the reduced two-file fixture from that investigation still drops the earlier file's completed semantic graph: the parent reserves 80% of its result budget whenever any later source remains, then the recovery text tells the caller to raise the worker heap.

This change reserves only the next static checkpoint (8 MiB, charged at the existing six-byte retention expansion), not one full checkpoint for every later file. A graph that fits once that reserve shrinks is kept and admitted after the later sources are analyzed. If the parent budget cannot start semantic analysis, the diagnostic names parent admission instead of the worker heap.

Problem and expected behavior

a-large.mjs (800 generated functions, objects, and bindings; 86,180 bytes) plus z-tiny.mjs (export const tiny = 1;) parses with 17,609 AST nodes and zero parse failures. Under NODE_OPTIONS=--max-old-space-size=512, the worker heap stays at the default 1,024 MiB and completes, but the parent reports:

Semantic graph for a-large.mjs exceeds the parent's remaining result budget; static and module facts were retained

with parent_result_budget_bytes=197848196, graph_transfer_bytes=17946120, graph_records=24007, and remediation that says to review worker memory. No method_0 semantic node is returned.

After this change the same command keeps syntax evidence and returns the semantic graph (12,005 nodes, 8,002 relations, including method_0) without truncation and without a worker-heap failure.

Change and scope

  • #futureStaticReserve replaces the 80% parent-budget reserve.
  • Graphs blocked only by that future-static reserve stay on the private runtime and are admitted by admitDeferredSemanticGraphs after later sources reduce the reserve. Graphs that still do not fit are rejected with the parent-admission error.
  • Worker heapMb default stays 1024. No MCP catalog, skill, or generated-doc change.

Contract and boundary impact

  • Semantic owner and earliest changed stage: parent result admission in JavaScriptAnalysisWorker, after the worker checkpoint.
  • CLI and MCP/tool-catalog contract: none. Same analyze / analyze-javascript-application result shape; admission failures now include parent_admission_budget_bytes and future_static_reserve_bytes, and their remediation no longer blames the worker heap.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: a semantic graph that was previously omitted is now retained when it fits the resource-derived budget. Observations, unknowns, and syntax facts are unchanged.
  • Process execution, authorization, cleanup, or containment impact: deferred transfer records stay in the existing private runtime until admission or close.
  • Generated metadata, package, or installation impact: none.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/cli/javascriptAdmissionBudget.test.ts runs rea analyze through the compiled CLI, which spawns the production JavaScript analysis worker. The parent process is limited with NODE_OPTIONS=--max-old-space-size. The tests do not pass max_heap_mb, so the worker stays at the default 1024 MiB. Coverage is one later file, ten later files (both must retain method_0), and a 320 MiB parent that still rejects the graph while naming the parent admission budget.
  • Base reproduction: before the change, the fixture exited 0 with a partial semantic graph (5 nodes, 2 relations), the admission error above, and worker-memory remediation. Captured locally; not the reporter's Linux cgroup.
  • User-visible CLI output: two runs of analyze-javascript-application --artifact-format directory --json on a-large.mjs plus ten later modules, parent old space 512 MiB, both exited 0 with parsed_javascript_files=11, parse_failures=0, visited_ast_nodes=17672, truncated=false, 12,041 semantic nodes, 8,020 relations, and method_0 retained.
  • Remaining proof gaps: the unattached 439,680-byte and 438,705-byte wrappers were not executed here. The Linux x86_64 one-CPU / 3 GiB process-tree limit was not executed on this macOS arm64 host.

For evidence-bearing changes:

  • 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

  • npm run test:focused -- tests/boundary/cli/javascriptAdmissionBudget.test.ts — 3 tests passed (Node 24.18.0), including ten later sources and the 320 MiB rejection.
  • npm run test:focused -- tests/boundary/javascript/javascriptSourceAnalysisWorker.test.ts — 7 tests passed in the same earlier focused run.
  • npm run check — exit 0.
  • npm run build:cached — exit 0.
  • NODE_OPTIONS=--max-old-space-size=512 node scripts/rea.mjs analyze-javascript-application <fixture> --artifact-format directory --json — exit 0, twice, with the same retained semantic graph.
  • npm run docs:check — not applicable; no generated catalog or docs contract change.
  • Real Hopper/Ghidra/IDA — not applicable.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Callers that only read parent_result_budget_bytes still receive it. Admission failures add parent_admission_budget_bytes and future_static_reserve_bytes.
  • Real Hopper/Ghidra, browser, or OS coverage: JavaScript CLI/worker only, macOS arm64, Node 24.18.0. Worker old space remained 1024 MiB.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: deferred records stay inside the existing private runtime root and are removed on admission, rejection, or close.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

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

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1920 **Author:** [@jimpablo](https://github.com/jimpablo) **Created:** 10/11/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/javascript-parent-admission` --- ### 📝 Commits (2) - [`93df06e`](https://github.com/morluto/rea/commit/93df06eacb6ef73b095cf02185830390fc92dd18) fix(javascript): admit deferred semantic graphs after later sources - [`40096c1`](https://github.com/morluto/rea/commit/40096c16a72c94b4fc5bf15f20597032b9e853bc) fix(javascript): reserve only the next static checkpoint ### 📊 Changes **5 files changed** (+365 additions, -64 deletions) <details> <summary>View changed files</summary> 📝 `src/application/javascript/JavaScriptArtifactAnalysis.ts` (+28 -1) 📝 `src/domain/javascript/javascriptSourceAnalysis.ts` (+14 -0) 📝 `src/javascript/analysis/JavaScriptAnalysisTransfer.ts` (+4 -1) 📝 `src/javascript/analysis/JavaScriptAnalysisWorker.ts` (+189 -62) ➕ `tests/boundary/cli/javascriptAdmissionBudget.test.ts` (+130 -0) </details> ### 📄 Description ## Summary Fixes #1911. Fixes #1847. On current main, the original #1847 worker-heap exhaustion no longer reproduces for the two generated wrappers (maintainer check at `898d5096`, and this host did not see `exhausted its heap`). Directory analysis of the reduced two-file fixture from that investigation still drops the earlier file's completed semantic graph: the parent reserves 80% of its result budget whenever any later source remains, then the recovery text tells the caller to raise the worker heap. This change reserves only the next static checkpoint (8 MiB, charged at the existing six-byte retention expansion), not one full checkpoint for every later file. A graph that fits once that reserve shrinks is kept and admitted after the later sources are analyzed. If the parent budget cannot start semantic analysis, the diagnostic names parent admission instead of the worker heap. ## Problem and expected behavior `a-large.mjs` (800 generated functions, objects, and bindings; 86,180 bytes) plus `z-tiny.mjs` (`export const tiny = 1;`) parses with 17,609 AST nodes and zero parse failures. Under `NODE_OPTIONS=--max-old-space-size=512`, the worker heap stays at the default 1,024 MiB and completes, but the parent reports: `Semantic graph for a-large.mjs exceeds the parent's remaining result budget; static and module facts were retained` with `parent_result_budget_bytes=197848196`, `graph_transfer_bytes=17946120`, `graph_records=24007`, and remediation that says to review worker memory. No `method_0` semantic node is returned. After this change the same command keeps syntax evidence and returns the semantic graph (12,005 nodes, 8,002 relations, including `method_0`) without truncation and without a worker-heap failure. ## Change and scope - `#futureStaticReserve` replaces the 80% parent-budget reserve. - Graphs blocked only by that future-static reserve stay on the private runtime and are admitted by `admitDeferredSemanticGraphs` after later sources reduce the reserve. Graphs that still do not fit are rejected with the parent-admission error. - Worker `heapMb` default stays 1024. No MCP catalog, skill, or generated-doc change. ## Contract and boundary impact - Semantic owner and earliest changed stage: parent result admission in `JavaScriptAnalysisWorker`, after the worker checkpoint. - CLI and MCP/tool-catalog contract: none. Same `analyze` / `analyze-javascript-application` result shape; admission failures now include `parent_admission_budget_bytes` and `future_static_reserve_bytes`, and their remediation no longer blames the worker heap. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: a semantic graph that was previously omitted is now retained when it fits the resource-derived budget. Observations, unknowns, and syntax facts are unchanged. - Process execution, authorization, cleanup, or containment impact: deferred transfer records stay in the existing private runtime until admission or close. - Generated metadata, package, or installation impact: none. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/cli/javascriptAdmissionBudget.test.ts` runs `rea analyze` through the compiled CLI, which spawns the production JavaScript analysis worker. The parent process is limited with `NODE_OPTIONS=--max-old-space-size`. The tests do not pass `max_heap_mb`, so the worker stays at the default 1024 MiB. Coverage is one later file, ten later files (both must retain `method_0`), and a 320 MiB parent that still rejects the graph while naming the parent admission budget. - Base reproduction: before the change, the fixture exited 0 with a partial semantic graph (5 nodes, 2 relations), the admission error above, and worker-memory remediation. Captured locally; not the reporter's Linux cgroup. - User-visible CLI output: two runs of `analyze-javascript-application --artifact-format directory --json` on `a-large.mjs` plus ten later modules, parent old space 512 MiB, both exited 0 with `parsed_javascript_files=11`, `parse_failures=0`, `visited_ast_nodes=17672`, `truncated=false`, 12,041 semantic nodes, 8,020 relations, and `method_0` retained. - Remaining proof gaps: the unattached 439,680-byte and 438,705-byte wrappers were not executed here. The Linux x86_64 one-CPU / 3 GiB process-tree limit was not executed on this macOS arm64 host. For evidence-bearing changes: - [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 - `npm run test:focused -- tests/boundary/cli/javascriptAdmissionBudget.test.ts` — 3 tests passed (Node 24.18.0), including ten later sources and the 320 MiB rejection. - `npm run test:focused -- tests/boundary/javascript/javascriptSourceAnalysisWorker.test.ts` — 7 tests passed in the same earlier focused run. - `npm run check` — exit 0. - `npm run build:cached` — exit 0. - `NODE_OPTIONS=--max-old-space-size=512 node scripts/rea.mjs analyze-javascript-application <fixture> --artifact-format directory --json` — exit 0, twice, with the same retained semantic graph. - `npm run docs:check` — not applicable; no generated catalog or docs contract change. - Real Hopper/Ghidra/IDA — not applicable. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Callers that only read `parent_result_budget_bytes` still receive it. Admission failures add `parent_admission_budget_bytes` and `future_static_reserve_bytes`. - Real Hopper/Ghidra, browser, or OS coverage: JavaScript CLI/worker only, macOS arm64, Node 24.18.0. Worker old space remained 1024 MiB. - Package or release metadata impact: none. - Security, privacy, process, or containment review: deferred records stay inside the existing private runtime root and are removed on admission, rejection, or close. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 00:56:40 +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#4910
No description provided.