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 #2831] [MERGED] fix(source-maps): accept omitted names during browser collection #5421

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

📋 Pull Request Information

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

Base: main ← Head: fix/source-map-optional-names

📝 Commits (1)

  • 8fcf996 fix(source-maps): accept omitted names during browser collection

📊 Changes

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

View changed files

📝 src/javascript/sourceMaps/SourceMapFormat.ts (+0 -5)
📝 tests/boundary/browser/webSourceMapFetcher.test.ts (+98 -0)

📄 Description

Summary

Fixes #2826.

Collect valid HTTP source maps that omit the optional names field, preserving their original-source artifacts and mappings. Previously, adding only "names": [] changed collection from invalid to included.

Problem and expected behavior

{"version":3,"sources":["original.js"],"sourcesContent":["export const answer = 42;"],"mappings":"AAAA"} contains no named mapping and is valid without names under ECMA-426 section 9. Browser collection should include it with one original source and one mapping while retaining the exact fetched text. On the base revision, collection instead returns invalid, no map artifact, zero originals and zero mappings.

Change and scope

Remove the browser-only mandatory-names guard in the shared source-map format owner. Its existing leaf schema already supplies [] for omission and validates present values; its decoded mapping owner continues validating name indices. This applies equally to ordinary maps and embedded indexed leaves, without adding a second normalization rule. No unrelated source-map policy changes are included.

This is a routine format compatibility fix within existing contribution scope; a separate maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: SourceMapFormat.ts, structural validation after the collector receives a map.
  • Contribution scope fit and linked maintainer decision: existing source-map inspection; no new provider or execution capability.
  • CLI and MCP/tool-catalog contract: schemas and parameters are unchanged; valid omitted-names maps now contribute the existing artifact/source/mapping result fields.
  • Provider, bridge, target-format, or platform compatibility: version 3 regular/indexed source maps; no provider or bridge changes.
  • Evidence, artifact, provenance, or reconstruction contract: preserve exact fetched JSON, byte count, digest, resolved original sources, mapping coordinates, and recovered module edges. Invalid present names and out-of-range name indices remain invalid.
  • Target selection, authority, upstream behavior, and cleanup details: existing origin admission and HTTP resource cleanup are unchanged. The regression uses owned loopback fixtures and closes its servers.
  • Generated metadata, package, or installation impact: none; no contract or dependency changes.

Expected effects of the existing workflow:

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

The fix adds no new target interaction or network request; it changes admission of already-fetched map bytes.

Evidence and regression coverage

  • Tests added or updated: real-HTTP collector regressions for regular maps and indexed leaves with nonzero offsets; omitted names and explicit-empty controls; null, numeric, non-string-array values and a name-index reference into an omitted array remain rejected.
  • Base reproduction: at 9680da76c84a6833635dc7a5df607806d899f804, both new regular/indexed regressions fail because omission returns invalid; the other 73 tests in the file pass. After the fix, all 108 selected tests pass.
  • Observable result: the standalone production-collector HTTP reproduction changes {status:"invalid", artifactRetained:false, originalSources:0, mappings:0} to {status:"included", artifactRetained:true, originalSources:1, mappings:1}. The explicit-empty control remains included. This is executed collector evidence, not a full CLI/CDP journey.
  • Remaining proof gaps: no real Chrome capture/export run; the changed boundary is covered directly with real HTTP.

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/browser/webSourceMapFetcher.test.ts tests/boundary/browser/webSourceMapNestedCoordinates.test.ts src/javascript/sourceMaps/TraceSourceMap.test.ts — 108 tests passed.
  • Standalone issue reproduction through the compiled collector and real loopback HTTP — reproduced on the base and passed after the fix.
  • npm run check — attempted; blocked by unrelated base formatting in tests/fixtures/javaClassFile.ts and max-lines-per-function lint errors in tests/boundary/providers/ghidra/ghidraLauncher.test.ts, src/ghidra/GhidraFunctionValues.test.ts, and src/domain/webBundleAnalyzer.test.ts. The same formatting and lint failures were independently reproduced in a clean checkout of base 9680da7; those files are unchanged by this PR.
  • npm run typecheck, npm run knip, npm run verify:module-boundaries, npm run verify:architecture-guards, and npm run verify:test-discovery — passed; all 1,078 test files discovered exactly once.
  • node_modules/.bin/oxfmt --check src/javascript/sourceMaps/SourceMapFormat.ts tests/boundary/browser/webSourceMapFetcher.test.ts — passed.
  • node_modules/.bin/oxlint --deny-warnings src/javascript/sourceMaps/SourceMapFormat.ts tests/boundary/browser/webSourceMapFetcher.test.ts — zero errors or warnings.
  • git diff --check — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: Linux x64/WSL production HTTP boundary; full browser capture not run. Native analysis providers are not involved.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: existing allowed origins, fetch behavior, resource budgets, invalid-name validation, and server cleanup retained. The fixture JavaScript is parsed for dependency evidence and is not executed.

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.

Full-repository formatting/lint failures were independently reproduced on clean base 9680da7. After the separate passing checks above, the branch was pushed with HUSKY=0 for that push only.

Integration note

Related independent fix: #2829. Both PRs target main and fix separate issues. Their deletions touch adjacent validation blocks in SourceMapFormat.ts; a local three-way merge reports a textual conflict between them. Once either merges, the other needs a small rebase retaining both removals. There is no semantic dependency, and the regression additions merge cleanly.

🔄 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/2831 **Author:** [@shoyann](https://github.com/shoyann) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/source-map-optional-names` --- ### 📝 Commits (1) - [`8fcf996`](https://github.com/morluto/rea/commit/8fcf996b16d1566475db6851634332bc260e007e) fix(source-maps): accept omitted names during browser collection ### 📊 Changes **2 files changed** (+98 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `src/javascript/sourceMaps/SourceMapFormat.ts` (+0 -5) 📝 `tests/boundary/browser/webSourceMapFetcher.test.ts` (+98 -0) </details> ### 📄 Description ## Summary Fixes #2826. Collect valid HTTP source maps that omit the optional `names` field, preserving their original-source artifacts and mappings. Previously, adding only `"names": []` changed collection from `invalid` to `included`. ## Problem and expected behavior `{"version":3,"sources":["original.js"],"sourcesContent":["export const answer = 42;"],"mappings":"AAAA"}` contains no named mapping and is valid without `names` under [ECMA-426 section 9](https://tc39.es/ecma426/#sec-source-map-format). Browser collection should include it with one original source and one mapping while retaining the exact fetched text. On the base revision, collection instead returns `invalid`, no map artifact, zero originals and zero mappings. ## Change and scope Remove the browser-only mandatory-`names` guard in the shared source-map format owner. Its existing leaf schema already supplies `[]` for omission and validates present values; its decoded mapping owner continues validating name indices. This applies equally to ordinary maps and embedded indexed leaves, without adding a second normalization rule. No unrelated source-map policy changes are included. This is a routine format compatibility fix within existing [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope); a separate maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `SourceMapFormat.ts`, structural validation after the collector receives a map. - Contribution scope fit and linked maintainer decision: existing source-map inspection; no new provider or execution capability. - CLI and MCP/tool-catalog contract: schemas and parameters are unchanged; valid omitted-`names` maps now contribute the existing artifact/source/mapping result fields. - Provider, bridge, target-format, or platform compatibility: version 3 regular/indexed source maps; no provider or bridge changes. - Evidence, artifact, provenance, or reconstruction contract: preserve exact fetched JSON, byte count, digest, resolved original sources, mapping coordinates, and recovered module edges. Invalid present `names` and out-of-range name indices remain invalid. - Target selection, authority, upstream behavior, and cleanup details: existing origin admission and HTTP resource cleanup are unchanged. The regression uses owned loopback fixtures and closes its servers. - Generated metadata, package, or installation impact: none; no contract or dependency changes. Expected effects of the existing workflow: - [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. - [x] 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. The fix adds no new target interaction or network request; it changes admission of already-fetched map bytes. ## Evidence and regression coverage - Tests added or updated: real-HTTP collector regressions for regular maps and indexed leaves with nonzero offsets; omitted names and explicit-empty controls; null, numeric, non-string-array values and a name-index reference into an omitted array remain rejected. - Base reproduction: at `9680da76c84a6833635dc7a5df607806d899f804`, both new regular/indexed regressions fail because omission returns `invalid`; the other 73 tests in the file pass. After the fix, all 108 selected tests pass. - Observable result: the standalone production-collector HTTP reproduction changes `{status:"invalid", artifactRetained:false, originalSources:0, mappings:0}` to `{status:"included", artifactRetained:true, originalSources:1, mappings:1}`. The explicit-empty control remains included. This is executed collector evidence, not a full CLI/CDP journey. - Remaining proof gaps: no real Chrome capture/export run; the changed boundary is covered directly with real HTTP. 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/browser/webSourceMapFetcher.test.ts tests/boundary/browser/webSourceMapNestedCoordinates.test.ts src/javascript/sourceMaps/TraceSourceMap.test.ts` — 108 tests passed. - Standalone issue reproduction through the compiled collector and real loopback HTTP — reproduced on the base and passed after the fix. - `npm run check` — attempted; blocked by unrelated base formatting in `tests/fixtures/javaClassFile.ts` and max-lines-per-function lint errors in `tests/boundary/providers/ghidra/ghidraLauncher.test.ts`, `src/ghidra/GhidraFunctionValues.test.ts`, and `src/domain/webBundleAnalyzer.test.ts`. The same formatting and lint failures were independently reproduced in a clean checkout of base `9680da7`; those files are unchanged by this PR. - `npm run typecheck`, `npm run knip`, `npm run verify:module-boundaries`, `npm run verify:architecture-guards`, and `npm run verify:test-discovery` — passed; all 1,078 test files discovered exactly once. - `node_modules/.bin/oxfmt --check src/javascript/sourceMaps/SourceMapFormat.ts tests/boundary/browser/webSourceMapFetcher.test.ts` — passed. - `node_modules/.bin/oxlint --deny-warnings src/javascript/sourceMaps/SourceMapFormat.ts tests/boundary/browser/webSourceMapFetcher.test.ts` — zero errors or warnings. - `git diff --check` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: Linux x64/WSL production HTTP boundary; full browser capture not run. Native analysis providers are not involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: existing allowed origins, fetch behavior, resource budgets, invalid-name validation, and server cleanup retained. The fixture JavaScript is parsed for dependency evidence and is not executed. ## 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. Full-repository formatting/lint failures were independently reproduced on clean base `9680da7`. After the separate passing checks above, the branch was pushed with `HUSKY=0` for that push only. ## Integration note Related independent fix: #2829. Both PRs target `main` and fix separate issues. Their deletions touch adjacent validation blocks in `SourceMapFormat.ts`; a local three-way merge reports a textual conflict between them. Once either merges, the other needs a small rebase retaining both removals. There is no semantic dependency, and the regression additions merge cleanly. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:06:30 +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#5421
No description provided.