[PR #5303] fix(javascript): keep var reads before their declarator unknown #6865

New issue

Open

opened 2026-11-01 21:43:39 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:43:39 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5303
Author: @darshjoshi
Created: 10/19/2026
Status: 🔄 Open

Base: main ← Head: fix/5302-var-read-before-initializer

---

📝 Commits (3)

• ab8578e fix(javascript): keep var reads before their declarator unknown
• db88f85 test(javascript): cover var reads before their declarator in export shapes
• 9ae2561 test(javascript): pin var reads inside nested functions keeping their literal

📊 Changes

2 files changed (+63 additions, -3 deletions)

View changed files

📝 src/domain/javascript/javascriptSemanticValues.ts (+8 -3)
📝 tests/boundary/filesystem/javascriptExportShapeComparison.test.ts (+55 -0)

📄 Description

Summary

Fixes #5302.

compare_javascript_export_shapes reported a definite literal for a field that reads a var before its declarator runs. At runtime the field is undefined: the declaration is hoisted, but the initializer has not executed yet.

Problem and expected behavior

Smallest trigger: return { kind: "k", a: v }; var v = 1; reports /a as literal 1, while Node returns a: undefined. The same happens with an alias, as in var w = v; var v = 1; return { kind: "k", a: w };.

The broken invariant comes from the export return-shape docs: "Rebound values are evaluated at their read position."

Change and scope

In evaluateExpression, an identifier was checked at its read position through semanticBindingAtRead only when its binding had an assignment definition. A var whose only write is its declarator initializer skipped that check, so evaluateBinding used the initializer no matter where the read was.

var bindings now go through semanticBindingAtRead too. When the order is proven, it drops initializers that do not come before the read, and the read becomes unknown. When the order cannot be proven, for example in reads from nested functions, the declarator value is kept as before. Treating those reads as unknown would make common bundle patterns such as var x = require(...) read inside functions lose precision. Assignment-bearing bindings behave exactly as before.

Not included: modelling the read as a definite undefined. It stays conservative and unknown.

The open PR #4173 edits the same identifier check to add read-order checks for let/const bindings, and it excludes var. This change is independent of it, and whichever lands second needs a small merge.

Follow the contribution scope. Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

• Semantic owner and earliest changed stage: JavaScript semantic value lattice (src/domain/javascript/javascriptSemanticValues.ts), identifier evaluation
• Contribution scope fit and linked maintainer decision: not applicable, an ordinary fix within existing static-analysis boundaries
• CLI and MCP/tool-catalog contract: no schema change. Affected reads now report unknown instead of a wrong literal.
• Provider, bridge, target-format, or platform compatibility: none
• Evidence, artifact, provenance, or reconstruction contract: none beyond the corrected value
• Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable
• Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

• 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: tests/boundary/filesystem/javascriptExportShapeComparison.test.ts, new block "JavaScript export hoisted var reads". It has the two bug shapes plus a control showing that a read after the declarator still reports literal 1.
• Base reproduction or other evidence: executed. With only the source file restored to b4938aed, both new cases fail (expected [ { …(11) } ] to deeply equal [ ObjectContaining{…} ]; the control passes). With the fix, all 51 tests in the file pass (52 with the nested-function test added in 9ae25617). The CLI reproduction from #5302 printed added /a {"availability":"literal","value":1} before the fix and no literal for /a after it.
• Differential check: 93 straight-line probes run through the CLI, with each literal claim compared against calling the export in Node. Before: 3 wrong literals, all of them this bug (2 distinct shapes, one of which appears in both probe sets). After: 0 wrong literals, and every previously correct literal is still reported. Two redeclaration cases now resolve correctly (var a = 1; var a = 2; gives 2, matching Node).
• User-visible CLI/MCP output (if applicable): the change for /a reports "right": {"availability": "unknown", ...} instead of {"availability": "literal", "value": 1}.
• Remaining proof gaps: the differential covers straight-line function bodies. Reads from closures called before the declarator keep the existing behavior.

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

Node 24.18.0, npm 11.16.0, macOS arm64:

• npm run test:focused -- tests/boundary/filesystem/javascriptExportShapeComparison.test.ts: 52 passed (after 9ae25617)
• node scripts/run-development-tests.mjs changed --base upstream/main (this is test:changed with origin pointing at my fork): 135 files, 3314 tests passed
• npm run check: passed. That covers typecheck, lint:built (0 errors), format:check, knip, metadata:check and architecture guards. javascriptSemanticValues.ts has the same lint warnings as on main.

Compatibility, safety, and release

• Breaking changes or migration steps: none
• Real Hopper/Ghidra, browser, or OS coverage: not applicable (pure static analysis); macOS only
• Package or release metadata impact: none
• Security, privacy, process, or containment review: no new effects

Author readiness

Human owner: @darshjoshi

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

---

_{🔄 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/5303 **Author:** [@darshjoshi](https://github.com/darshjoshi) **Created:** 10/19/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/5302-var-read-before-initializer` --- ### 📝 Commits (3) - [`ab8578e`](https://github.com/morluto/rea/commit/ab8578e895fd3180c9fa54ae91796556d0067926) fix(javascript): keep var reads before their declarator unknown - [`db88f85`](https://github.com/morluto/rea/commit/db88f851e047d9a0e146f744a0091d40065a76fe) test(javascript): cover var reads before their declarator in export shapes - [`9ae2561`](https://github.com/morluto/rea/commit/9ae256176ce75d63ab96701d7e41690010f58ff5) test(javascript): pin var reads inside nested functions keeping their literal ### 📊 Changes **2 files changed** (+63 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/javascript/javascriptSemanticValues.ts` (+8 -3) 📝 `tests/boundary/filesystem/javascriptExportShapeComparison.test.ts` (+55 -0) </details> ### 📄 Description ## Summary Fixes #5302. `compare_javascript_export_shapes` reported a definite literal for a field that reads a `var` before its declarator runs. At runtime the field is `undefined`: the declaration is hoisted, but the initializer has not executed yet. ## Problem and expected behavior Smallest trigger: `return { kind: "k", a: v }; var v = 1;` reports `/a` as literal `1`, while Node returns `a: undefined`. The same happens with an alias, as in `var w = v; var v = 1; return { kind: "k", a: w };`. The broken invariant comes from the [export return-shape docs](https://github.com/morluto/rea/blob/main/docs/javascript-application-workflows.md#export-return-shape-comparison): "Rebound values are evaluated at their read position." ## Change and scope In `evaluateExpression`, an identifier was checked at its read position through `semanticBindingAtRead` only when its binding had an `assignment` definition. A `var` whose only write is its declarator initializer skipped that check, so `evaluateBinding` used the initializer no matter where the read was. `var` bindings now go through `semanticBindingAtRead` too. When the order is proven, it drops initializers that do not come before the read, and the read becomes unknown. When the order cannot be proven, for example in reads from nested functions, the declarator value is kept as before. Treating those reads as unknown would make common bundle patterns such as `var x = require(...)` read inside functions lose precision. Assignment-bearing bindings behave exactly as before. Not included: modelling the read as a definite `undefined`. It stays conservative and unknown. The open PR #4173 edits the same identifier check to add read-order checks for `let`/`const` bindings, and it excludes `var`. This change is independent of it, and whichever lands second needs a small merge. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: JavaScript semantic value lattice (`src/domain/javascript/javascriptSemanticValues.ts`), identifier evaluation - Contribution scope fit and linked maintainer decision: not applicable, an ordinary fix within existing static-analysis boundaries - CLI and MCP/tool-catalog contract: no schema change. Affected reads now report unknown instead of a wrong literal. - Provider, bridge, target-format, or platform compatibility: none - Evidence, artifact, provenance, or reconstruction contract: none beyond the corrected value - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/javascriptExportShapeComparison.test.ts`, new block "JavaScript export hoisted var reads". It has the two bug shapes plus a control showing that a read after the declarator still reports literal `1`. - Base reproduction or other evidence: executed. With only the source file restored to `b4938aed`, both new cases fail (`expected [ { …(11) } ] to deeply equal [ ObjectContaining{…} ]`; the control passes). With the fix, all 51 tests in the file pass (52 with the nested-function test added in 9ae25617). The CLI reproduction from #5302 printed `added /a {"availability":"literal","value":1}` before the fix and no literal for `/a` after it. - Differential check: 93 straight-line probes run through the CLI, with each literal claim compared against calling the export in Node. Before: 3 wrong literals, all of them this bug (2 distinct shapes, one of which appears in both probe sets). After: 0 wrong literals, and every previously correct literal is still reported. Two redeclaration cases now resolve correctly (`var a = 1; var a = 2;` gives `2`, matching Node). - User-visible CLI/MCP output (if applicable): the change for `/a` reports `"right": {"availability": "unknown", ...}` instead of `{"availability": "literal", "value": 1}`. - Remaining proof gaps: the differential covers straight-line function bodies. Reads from closures called before the declarator keep the existing behavior. 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 Node 24.18.0, npm 11.16.0, macOS arm64: - `npm run test:focused -- tests/boundary/filesystem/javascriptExportShapeComparison.test.ts`: 52 passed (after 9ae25617) - `node scripts/run-development-tests.mjs changed --base upstream/main` (this is `test:changed` with `origin` pointing at my fork): 135 files, 3314 tests passed - `npm run check`: passed. That covers typecheck, lint:built (0 errors), format:check, knip, metadata:check and architecture guards. `javascriptSemanticValues.ts` has the same lint warnings as on main. ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: not applicable (pure static analysis); macOS only - Package or release metadata impact: none - Security, privacy, process, or containment review: no new effects ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @darshjoshi - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] 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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi added the

pull-request

label 2026-11-01 21:43:39 +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

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#6865

No description provided.