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 #7073] [MERGED] fix(cli): preserve literal Markdown table facts #7623

New issue
Closed
opened 2026-11-03 13:39:11 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:11 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7073
Author: @Plastic-time
Created: 10/25/2026
Status: ✅ Merged
Merged: 10/25/2026
Merged by: @morluto

Base: main ← Head: codex/fix-markdown-table-literals-20261025

📝 Commits (3)

  • c346143 fix(cli): preserve literal Markdown table facts
  • 26b6fab test(cli): retain capacity diagnostics through Markdown escaping
  • 8f1fd0d fix(cli): keep intraword underscores readable in Markdown tables

📊 Changes

5 files changed (+137 additions, -15 deletions)

View changed files

📝 docs/cli.md (+4 -2)
📝 src/cli/cliOutputFormatter.ts (+16 -2)
📝 tests/boundary/cli/filteredArrayOutput.test.ts (+11 -10)
➕ tests/boundary/cli/markdownLiteralCells.test.ts (+105 -0)
📝 tests/boundary/cli/markdownNestedFacts.test.ts (+1 -1)

📄 Description

Summary

Markdown table output treats captured text such as __name__, backticks, link/image syntax, and strikethrough as markup. A rendered report can therefore change an Evidence key, value, or nested JSON fact even though JSON output retains the source.

Escape inline Markdown syntax at the existing table-cell owner. Table headers, key/value tables, object-row tables, and standalone reports all use that owner. No issue is linked because this was reproduced directly on main 8e6a9578. Related #7062 fixes headings; this change addresses table contents independently. A three-way merge with its current head is conflict-free.

Contract and boundary impact

  • Semantic owner: src/cli/cliOutputFormatter.ts#escapeTableCell; the existing backslash/pipe passes are replaced by one character escape pass before line-break rendering. Underscore runs between letters or digits cannot open or close emphasis, so they stay unescaped and identifiers such as source_index remain readable in raw Markdown.
  • Ordinary presentation fix; no new capability or maintainer scope decision required.
  • CLI: raw Markdown now includes escapes for inline syntax. For example, a cell containing __name__ renders as the literal __name__, rather than name in bold. JSON, saved Evidence, schemas and MCP output are unchanged.
  • Provider/platform, artifact identity, target authority, cleanup and package/generated metadata: unchanged.

Expected effects:

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

A compiled inspect-evidence-bundle --format md --filter-output records.0.normalized_result regression renders the result with the existing VitePress dependency and reads table text through parse5. It compares visible keys and values to the original data, including nested JSON, code/emphasis/strike/link/image syntax, existing backslashes, pipes, HTML/entities, empty text, zero, false and null. JSON output and the saved bundle are exact controls; standalone reports exercise the same data.

Applicable boundary cases: raw identity/normalization, missing/empty/scalar distinctions, and public output delivery. Existing delimiter/newline, failure-output and 150,000-row capacity regressions remain covered. No resource lifecycle changes.

  • Observed, derived and inferred claims remain distinguishable.
  • Artifact identity, source provenance and failed attempts remain preserved.
  • Unsupported or uncertain outcomes remain visible.

Validation performed

Windows x64, Node 24.22.1 / npm 11.16.0:

  • Unchanged upstream runtime plus the new regression: 105 existing tests passed; only the new rendered-text assertion failed. Captured __name__ became name, link markup displayed only its label, and image syntax became an image.
  • Final relevant CLI coverage: 196 passed, 1 platform skip across 11 files, including the rendered-text regression and large inventory page. After updating old raw-Markdown assertions, the affected 13-test subset was rerun and passed.
  • npm run check — passed, including architecture guards, reachability reporting and typed lint (0 errors).
  • npm run docs:check — passed, including 9 consistency tests.
  • lint-staged, npm run check:fast, and git diff --check — passed. Hook commands ran directly under Windows Node because the Git Bash Node shim failed before executing them.

Hosted CI on the initial c3461437 runtime change passed source tests, documentation, static checks, package build and the Linux native package baseline. Shard 1 failed six legacy raw-text assertions in tests/acceptance/cliFormattingCapacity.test.ts; the other seven shards were cancelled. This acceptance file was missing from the initial local selection.

Follow-up 26b6fab5 changed only those test assertions. It is superseded by 8f1fd0d: intraword underscores are no longer escaped, so diagnostic identifiers such as formatted_characters, target_unavailable and invalid_request appear unchanged and the original assertions in cliFormattingCapacity, analysisViewCli and filteredFailureOutput are restored exactly as on main. Boundary runs (__proto__, _name_, snake_case_) are still escaped.

  • Same-host upstream production source (8e6a9578) with the original capacity test: 22 passed, 1 Windows SIGPIPE skip. The initial PR reproduced all six Markdown assertion failures; one separate local fixture-cleanup EBUSY also occurred and did not recur in the baseline or fixed runs.
  • Fixed capacity, literal-cell, formatting-recovery, filtered-failure and update-alias files: 45 passed, 1 platform skip across five files.
  • npm run check, lint-staged, npm run check:fast and git diff --check passed again after the test correction.

Head 8f1fd0d (Windows x64, Node 24.20.0 with --engine-strict=false; Windows addon restored from rea-agents@6.7.0 per native/windows/README.md):

  • All 13 test files that exercise Markdown CLI output: 227 passed, 2 skipped, including the literal-cell regression extended with x__y__z _a_b_ 中_文 snake_case_ (raw output keeps intraword underscores; rendered cells match the source).
  • npm run typecheck, oxlint, oxfmt --check, lint-staged (pre-commit) and npm run check:fast (pre-push) passed.

The 26b6fab5 shard 8 failures (cdpSvgXlinkHref headless Chrome timeout, javascriptAnalysisResources MCP heap budget) do not reach cliOutputFormatter, which only the CLI uses. Latest-head hosted CI is pending. Greptile rated the initial runtime change 5/5 with no inline findings. The Codex review attempt did not complete and published no actionable inline comments. macOS and external analysis providers were not exercised. An initial sandboxed multi-file run lost Vite's temporary files; normal-host baseline and fixed runs completed without that runner error.

Compatibility, safety, and release

Rendered table facts retain their supplied inline syntax. Raw Markdown consumers will see additional escapes for inline syntax at word boundaries; intraword underscores are unchanged; programmatic consumers can use JSON. Heading and non-table scalar rendering are outside this change. No dependency, schema, migration or release-metadata change.

Author readiness

Human owner: @Plastic-time

  • 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

  • Concrete problem, focused outcome and conventional title.
  • Scope, owning boundary, source preservation and representative output documented.
  • Relevant tests and docs updated; no generated artifacts, secrets or unrelated cleanup.
  • Latest-head required CI and human readiness confirmed.

🔄 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/7073 **Author:** [@Plastic-time](https://github.com/Plastic-time) **Created:** 10/25/2026 **Status:** ✅ Merged **Merged:** 10/25/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/fix-markdown-table-literals-20261025` --- ### 📝 Commits (3) - [`c346143`](https://github.com/morluto/rea/commit/c346143723049bc540a18fd3b612904329e1a77b) fix(cli): preserve literal Markdown table facts - [`26b6fab`](https://github.com/morluto/rea/commit/26b6fab5bc7ad99527a61d391ef3660d52f42e0a) test(cli): retain capacity diagnostics through Markdown escaping - [`8f1fd0d`](https://github.com/morluto/rea/commit/8f1fd0d53b0a2ec7d6eb35f552d5f2f6c966ff5c) fix(cli): keep intraword underscores readable in Markdown tables ### 📊 Changes **5 files changed** (+137 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `docs/cli.md` (+4 -2) 📝 `src/cli/cliOutputFormatter.ts` (+16 -2) 📝 `tests/boundary/cli/filteredArrayOutput.test.ts` (+11 -10) ➕ `tests/boundary/cli/markdownLiteralCells.test.ts` (+105 -0) 📝 `tests/boundary/cli/markdownNestedFacts.test.ts` (+1 -1) </details> ### 📄 Description ## Summary Markdown table output treats captured text such as `__name__`, backticks, link/image syntax, and strikethrough as markup. A rendered report can therefore change an Evidence key, value, or nested JSON fact even though JSON output retains the source. Escape inline Markdown syntax at the existing table-cell owner. Table headers, key/value tables, object-row tables, and standalone reports all use that owner. No issue is linked because this was reproduced directly on main `8e6a9578`. Related #7062 fixes headings; this change addresses table contents independently. A three-way merge with its current head is conflict-free. ## Contract and boundary impact - Semantic owner: `src/cli/cliOutputFormatter.ts#escapeTableCell`; the existing backslash/pipe passes are replaced by one character escape pass before line-break rendering. Underscore runs between letters or digits cannot open or close emphasis, so they stay unescaped and identifiers such as `source_index` remain readable in raw Markdown. - Ordinary presentation fix; no new capability or maintainer scope decision required. - CLI: raw Markdown now includes escapes for inline syntax. For example, a cell containing `__name__` renders as the literal `__name__`, rather than `name` in bold. JSON, saved Evidence, schemas and MCP output are unchanged. - Provider/platform, artifact identity, target authority, cleanup and package/generated metadata: unchanged. Expected effects: - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage A compiled `inspect-evidence-bundle --format md --filter-output records.0.normalized_result` regression renders the result with the existing VitePress dependency and reads table text through parse5. It compares visible keys and values to the original data, including nested JSON, code/emphasis/strike/link/image syntax, existing backslashes, pipes, HTML/entities, empty text, zero, false and null. JSON output and the saved bundle are exact controls; standalone reports exercise the same data. Applicable boundary cases: raw identity/normalization, missing/empty/scalar distinctions, and public output delivery. Existing delimiter/newline, failure-output and 150,000-row capacity regressions remain covered. No resource lifecycle changes. - [x] Observed, derived and inferred claims remain distinguishable. - [x] Artifact identity, source provenance and failed attempts remain preserved. - [x] Unsupported or uncertain outcomes remain visible. ## Validation performed Windows x64, Node 24.22.1 / npm 11.16.0: - Unchanged upstream runtime plus the new regression: **105 existing tests passed; only the new rendered-text assertion failed**. Captured `__name__` became `name`, link markup displayed only its label, and image syntax became an image. - Final relevant CLI coverage: **196 passed, 1 platform skip across 11 files**, including the rendered-text regression and large inventory page. After updating old raw-Markdown assertions, the affected 13-test subset was rerun and passed. - `npm run check` — passed, including architecture guards, reachability reporting and typed lint (0 errors). - `npm run docs:check` — passed, including 9 consistency tests. - `lint-staged`, `npm run check:fast`, and `git diff --check` — passed. Hook commands ran directly under Windows Node because the Git Bash Node shim failed before executing them. Hosted CI on the initial `c3461437` runtime change passed source tests, documentation, static checks, package build and the Linux native package baseline. Shard 1 failed six legacy raw-text assertions in `tests/acceptance/cliFormattingCapacity.test.ts`; the other seven shards were cancelled. This acceptance file was missing from the initial local selection. Follow-up `26b6fab5` changed only those test assertions. It is superseded by `8f1fd0d`: intraword underscores are no longer escaped, so diagnostic identifiers such as `formatted_characters`, `target_unavailable` and `invalid_request` appear unchanged and the original assertions in `cliFormattingCapacity`, `analysisViewCli` and `filteredFailureOutput` are restored exactly as on main. Boundary runs (`__proto__`, `_name_`, `snake_case_`) are still escaped. - Same-host upstream production source (`8e6a9578`) with the original capacity test: **22 passed, 1 Windows SIGPIPE skip**. The initial PR reproduced all six Markdown assertion failures; one separate local fixture-cleanup EBUSY also occurred and did not recur in the baseline or fixed runs. - Fixed capacity, literal-cell, formatting-recovery, filtered-failure and update-alias files: **45 passed, 1 platform skip across five files**. - `npm run check`, `lint-staged`, `npm run check:fast` and `git diff --check` passed again after the test correction. Head `8f1fd0d` (Windows x64, Node 24.20.0 with `--engine-strict=false`; Windows addon restored from `rea-agents@6.7.0` per `native/windows/README.md`): - All 13 test files that exercise Markdown CLI output: **227 passed, 2 skipped**, including the literal-cell regression extended with `x__y__z _a_b_ 中_文 snake_case_` (raw output keeps intraword underscores; rendered cells match the source). - `npm run typecheck`, `oxlint`, `oxfmt --check`, `lint-staged` (pre-commit) and `npm run check:fast` (pre-push) passed. The `26b6fab5` shard 8 failures (`cdpSvgXlinkHref` headless Chrome timeout, `javascriptAnalysisResources` MCP heap budget) do not reach `cliOutputFormatter`, which only the CLI uses. Latest-head hosted CI is pending. Greptile rated the initial runtime change 5/5 with no inline findings. The Codex review attempt did not complete and published no actionable inline comments. macOS and external analysis providers were not exercised. An initial sandboxed multi-file run lost Vite's temporary files; normal-host baseline and fixed runs completed without that runner error. ## Compatibility, safety, and release Rendered table facts retain their supplied inline syntax. Raw Markdown consumers will see additional escapes for inline syntax at word boundaries; intraword underscores are unchanged; programmatic consumers can use JSON. Heading and non-table scalar rendering are outside this change. No dependency, schema, migration or release-metadata change. ## Author readiness Human owner: @Plastic-time - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] Concrete problem, focused outcome and conventional title. - [x] Scope, owning boundary, source preservation and representative output documented. - [x] Relevant tests and docs updated; no generated artifacts, secrets or unrelated cleanup. - [ ] Latest-head required CI and human readiness confirmed. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-03 13:39:11 +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#7623
No description provided.