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 #2863] [CLOSED] fix(saz): accept U+FFFD in well-formed metadata #5447

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2863
Author: @Dragolone
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: fix/saz-metadata-replacement-character

📝 Commits (7)

  • cda4251 fix(saz): accept U+FFFD in well-formed metadata
  • c6d8672 fix(comparison): recheck historical calls-only changes (#2223)
  • 50c5cd5 fix(ci): isolate Linux Hopper process fixture inventory
  • bfc44c2 fix(android): make DEX descriptor pattern portable
  • 7d68747 Merge upstream main into fix/saz-metadata-replacement-character
  • d2d4f8a Merge branch 'main' into fix/saz-metadata-replacement-character
  • da429f3 Merge branch 'main' into fix/saz-metadata-replacement-character

📊 Changes

2 files changed (+33 additions, -1 deletions)

View changed files

➕ src/browser/history/SazMetadata.test.ts (+24 -0)
📝 src/browser/history/SazMetadata.ts (+9 -1)

📄 Description

Summary

A SAZ capture is rejected as invalid input when any raw/N_m.xml metadata member contains U+FFFD (REPLACEMENT CHARACTER), even though the XML is well-formed.

xmldom 0.9.12 emits a warning ("Unicode replacement character detected, source encoding issues?") whenever the source text contains U+FFFD (lib/sax.js, start of parse). decodeSazMetadata treats every onError report, warnings included, as a well-formedness failure. U+FFFD is a legal XML Char ([#xE000-#xFFFD]). The decoder already uses a fatal TextDecoder, so a U+FFFD that reaches the parser was encoded in the source. It cannot be a decoding artifact, which is the case the warning is about.

Related: #2601 asks for the opposite direction in the same handler, rejecting &, NUL and surrogate references that are currently accepted. This PR does not change that behavior and does not conflict with it; it only stops rejecting one legal character. No issue covers this case: I searched for "SAZ metadata", "replacement character", "U+FFFD", "xmldom warning" and "Fiddler".

Problem and expected behavior

Smallest trigger: metadata <Session SID="1"><SessionFlags><SessionFlag N="ui-comments" V="caf�"/></SessionFlags></Session> (with a real U+FFFD) in an otherwise ordinary archive.

  • Before: rea inspect-web-network-capture fffd.saz saz --json reports {"category": "invalid_input", "code": "invalid_request"}, and decodeSazMetadata throws "SAZ metadata is not well-formed XML."
  • After: total_records: 1, with the attribute value retained as caf�.

Expected per docs/web-network-captures.md: malformed metadata fails validation; well-formed metadata is projected.

Change and scope

The onError handler ignores only the warning whose message starts with "Unicode replacement character detected". Every other warning, error or fatal error still sets parseFailed, so malformed XML is still rejected. That includes documents that also contain U+FFFD, and xmldom reports some of them only as warnings: unquoted attributes, attributes without separating whitespace, mismatched elements.

Not included: the stricter checks requested in #2601.

Contribution scope: an ordinary format-inspection correctness fix within existing boundaries; a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: decodeSazMetadata in src/browser/history/SazMetadata.ts.
  • Contribution scope fit and linked maintainer decision: in scope (format inspection); not applicable.
  • CLI and MCP/tool-catalog contract: no schema change; affected captures now succeed instead of failing as invalid input.
  • Provider, bridge, target-format, or platform compatibility: depends on xmldom's warning text; the dependency is pinned (0.9.12), and the new test fails if that message changes.
  • Evidence, artifact, provenance, or reconstruction contract: none; the character is retained verbatim.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: 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: new src/browser/history/SazMetadata.test.ts:
    • "retains U+FFFD in well-formed metadata as an ordinary XML character" (an attribute and a text node);
    • "still rejects malformed metadata that also contains U+FFFD" for an unquoted attribute, attributes without separating whitespace, and a mismatched element.
  • Base reproduction: on 94072364c the first test fails with "SAZ metadata is not well-formed XML."; the rejection cases pass on both base and fix.
  • User-visible CLI output (rea inspect-web-network-capture fffd.saz saz --json): before {"category": "invalid_input", "code": "invalid_request"}, after normalized_result.total_records = 1.
  • Remaining proof gaps: I have not seen a Fiddler-produced SAZ with U+FFFD in metadata; the fixture is synthetic.

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

macOS (Apple silicon), Node 24.19.0.

  • npx vitest run src/browser/history/SazMetadata.test.ts on the base — the retention test fails, the three rejection tests pass.
  • npx vitest run src/browser/history/ with the fix — 6 files, 103 tests passed.
  • npm run build:cached && npx vitest run tests/boundary/browser/sazWebCapture.test.ts — 13 passed, 1 skipped.
  • rea inspect-web-network-capture before/after as above.
  • npm run verify:test-discovery — "Discovered all 1089 test files exactly once."
  • npm run typecheck — passed.
  • npx oxfmt --check and npx oxlint on both changed files — passed, no errors.
  • npm run verify:module-boundaries — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no change to DTD or entity handling; malformed XML stays rejected.

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/2863 **Author:** [@Dragolone](https://github.com/Dragolone) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/saz-metadata-replacement-character` --- ### 📝 Commits (7) - [`cda4251`](https://github.com/morluto/rea/commit/cda4251ad6fbb13d5090664655ed4b7fccdad2d2) fix(saz): accept U+FFFD in well-formed metadata - [`c6d8672`](https://github.com/morluto/rea/commit/c6d86721f64c2fbbed4cdf30a6f4bc8eb7779bde) fix(comparison): recheck historical calls-only changes (#2223) - [`50c5cd5`](https://github.com/morluto/rea/commit/50c5cd57c345c172a00d87103f6488435d28fe0a) fix(ci): isolate Linux Hopper process fixture inventory - [`bfc44c2`](https://github.com/morluto/rea/commit/bfc44c228ecc9a32a508f09c093d734051ad4647) fix(android): make DEX descriptor pattern portable - [`7d68747`](https://github.com/morluto/rea/commit/7d68747bce26b6963250bd1d982b6e73f42dd1bb) Merge upstream main into fix/saz-metadata-replacement-character - [`d2d4f8a`](https://github.com/morluto/rea/commit/d2d4f8acd2b67e34b7076287fda9f1c8e96c5b56) Merge branch 'main' into fix/saz-metadata-replacement-character - [`da429f3`](https://github.com/morluto/rea/commit/da429f35c24e1182fb0fedfaff20393f52c52d62) Merge branch 'main' into fix/saz-metadata-replacement-character ### 📊 Changes **2 files changed** (+33 additions, -1 deletions) <details> <summary>View changed files</summary> ➕ `src/browser/history/SazMetadata.test.ts` (+24 -0) 📝 `src/browser/history/SazMetadata.ts` (+9 -1) </details> ### 📄 Description ## Summary A SAZ capture is rejected as invalid input when any `raw/N_m.xml` metadata member contains U+FFFD (REPLACEMENT CHARACTER), even though the XML is well-formed. xmldom 0.9.12 emits a `warning` ("Unicode replacement character detected, source encoding issues?") whenever the source text contains U+FFFD (`lib/sax.js`, start of `parse`). `decodeSazMetadata` treats every `onError` report, warnings included, as a well-formedness failure. U+FFFD is a legal XML `Char` (`[#xE000-#xFFFD]`). The decoder already uses a fatal `TextDecoder`, so a U+FFFD that reaches the parser was encoded in the source. It cannot be a decoding artifact, which is the case the warning is about. Related: #2601 asks for the opposite direction in the same handler, rejecting `&`, NUL and surrogate references that are currently accepted. This PR does not change that behavior and does not conflict with it; it only stops rejecting one legal character. No issue covers this case: I searched for "SAZ metadata", "replacement character", "U+FFFD", "xmldom warning" and "Fiddler". ## Problem and expected behavior Smallest trigger: metadata `<Session SID="1"><SessionFlags><SessionFlag N="ui-comments" V="caf�"/></SessionFlags></Session>` (with a real U+FFFD) in an otherwise ordinary archive. - Before: `rea inspect-web-network-capture fffd.saz saz --json` reports `{"category": "invalid_input", "code": "invalid_request"}`, and `decodeSazMetadata` throws "SAZ metadata is not well-formed XML." - After: `total_records: 1`, with the attribute value retained as `caf�`. Expected per `docs/web-network-captures.md`: malformed metadata fails validation; well-formed metadata is projected. ## Change and scope The `onError` handler ignores only the `warning` whose message starts with "Unicode replacement character detected". Every other warning, error or fatal error still sets `parseFailed`, so malformed XML is still rejected. That includes documents that also contain U+FFFD, and xmldom reports some of them only as warnings: unquoted attributes, attributes without separating whitespace, mismatched elements. Not included: the stricter checks requested in #2601. Contribution scope: an ordinary format-inspection correctness fix within existing boundaries; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `decodeSazMetadata` in `src/browser/history/SazMetadata.ts`. - Contribution scope fit and linked maintainer decision: in scope (format inspection); not applicable. - CLI and MCP/tool-catalog contract: no schema change; affected captures now succeed instead of failing as invalid input. - Provider, bridge, target-format, or platform compatibility: depends on xmldom's warning text; the dependency is pinned (0.9.12), and the new test fails if that message changes. - Evidence, artifact, provenance, or reconstruction contract: none; the character is retained verbatim. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: 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: new `src/browser/history/SazMetadata.test.ts`: - "retains U+FFFD in well-formed metadata as an ordinary XML character" (an attribute and a text node); - "still rejects malformed metadata that also contains U+FFFD" for an unquoted attribute, attributes without separating whitespace, and a mismatched element. - Base reproduction: on `94072364c` the first test fails with "SAZ metadata is not well-formed XML."; the rejection cases pass on both base and fix. - User-visible CLI output (`rea inspect-web-network-capture fffd.saz saz --json`): before `{"category": "invalid_input", "code": "invalid_request"}`, after `normalized_result.total_records = 1`. - Remaining proof gaps: I have not seen a Fiddler-produced SAZ with U+FFFD in metadata; the fixture is synthetic. 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 macOS (Apple silicon), Node 24.19.0. - `npx vitest run src/browser/history/SazMetadata.test.ts` on the base — the retention test fails, the three rejection tests pass. - `npx vitest run src/browser/history/` with the fix — 6 files, 103 tests passed. - `npm run build:cached && npx vitest run tests/boundary/browser/sazWebCapture.test.ts` — 13 passed, 1 skipped. - `rea inspect-web-network-capture` before/after as above. - `npm run verify:test-discovery` — "Discovered all 1089 test files exactly once." - `npm run typecheck` — passed. - `npx oxfmt --check` and `npx oxlint` on both changed files — passed, no errors. - `npm run verify:module-boundaries` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no change to DTD or entity handling; malformed XML stays rejected. ## 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. --- <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:42 +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#5447
No description provided.