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 #5962] [CLOSED] fix(firmware): report a staging budget refusal as a resource constraint #7111

New issue
Closed
opened 2026-11-01 21:45:28 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:45:28 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5962
Author: @XiaoBinGan
Created: 10/21/2026
Status: ❌ Closed

Base: main ← Head: fix/firmware-staging-budget

📝 Commits (5)

  • e0a5874 fix(firmware): report a staging budget refusal as a resource constraint
  • 997a552 fix(firmware): explain staging budget hard ceilings
  • 3a7829b fix(firmware): classify staging bytes as capacity
  • 98b6997 Merge main into firmware staging budget
  • 746a64c chore: integrate firmware staging-budget fix with current main

📊 Changes

3 files changed (+147 additions, -5 deletions)

View changed files

📝 src/domain/firmware/firmwareAnalysis.ts (+4 -2)
➕ src/firmware/FirmwareFiles.test.ts (+100 -0)
📝 src/firmware/FirmwareFiles.ts (+43 -3)

📄 Description

Summary

inventoryFirmwareOutput refused an extraction that exceeded the caller-selected max_output_files or max_output_bytes staging budget with AnalysisOutputError, so an MCP caller received unreadable_output, category: "execution_failure" and rea doctor remediation for a deterministic allowance the caller can raise.

Fixes #5846

Problem and expected behavior

  • Smallest trigger: extract_firmware with max_output_files: 1 over the repository's synthetic Unblob producer, which stages rootfs/config (one directory and one regular file). The inventory counted two entries and threw Invalid analysis output for extract_firmware: Staging entry budget exceeded (1), projected as unreadable_output with doctor guidance.
  • Violated invariant: the firmware policy separates producer-report and staging allowances and documents caller-selected staging budgets; the error algebra classifies a bounded admission refusal as a resource constraint, and output errors describe failed output parsing. This refusal is a valid, deterministic budget decision.
  • Expected: keep refusing, identify the resource, report the exceeded allowance in limit details, and explain the actual recovery - raising that specific budget and rerunning with an absent output destination. details.reason keeps the observed text.

Change and scope

  • src/firmware/FirmwareFiles.ts: both staging overruns now throw AnalysisResourceConstraintError (entries: capacity, bytes: memory) with reported_limits.max_output_files / reported_limits.max_output_bytes, retryable: false, and a remediation that names the control, its supported maximum and the absent-destination retry.
  • src/firmware/FirmwareFiles.test.ts (new): covers both refusals and their projection, including the remediation text.
  • Not included: no change to the budgets themselves, to Unblob invocation, to the FirmwareCommand deadline path or to publication.

Contract and boundary impact

  • Semantic owner and earliest changed stage: firmware staging inventory enforcement.
  • Contribution scope fit and linked maintainer decision: not applicable - an ordinary fix inside an existing boundary.
  • CLI and MCP/tool-catalog contract: a staging-budget refusal now returns resource_constraint with reported_limits instead of unreadable_output; the input schema is unchanged.
  • Provider, bridge, target-format, or platform compatibility: none; the same function serves the provider and the command deadline path.
  • Evidence, artifact, provenance, or reconstruction contract: no extraction output is published when the budget is exceeded, as before.
  • Target selection, authority, upstream behavior, and cleanup details: unchanged; no extra process is launched and workspace cleanup keeps its existing path.
  • Generated metadata, package, or installation impact: none.

Expected effects (check known effects; use documentation-only on its own).

  • 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: src/firmware/FirmwareFiles.test.ts (2 cases).
  • Base reproduction: before the change both cases fail with Expected a resource constraint, received Error: Invalid analysis output for extract_firmware: Staging entry budget exceeded (1) and the byte equivalent; after the change they pass and project code: "resource_constraint" with details.reported_limits and the budget-specific remediation.
  • User-visible CLI/MCP output: the refusal now names max_output_files / max_output_bytes and the supported maximum instead of recommending rea doctor.
  • Remaining proof gaps: the tests stage a real directory tree but do not run Unblob; the original report exercised a mocked Linux admission on macOS, and no real Unblob or public CLI run is claimed.

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

  • npx vitest run src/firmware tests/boundary/firmware - 46 passed, 40 skipped.
  • npm run format:check - all matched files use the correct format.
  • npm run verify:test-discovery - all 1903 test files discovered exactly once.
  • npm run typecheck - no diagnostic in the changed files (the remaining errors in this checkout are pre-existing protobuf-module resolution failures).
  • npm run lint - 0 errors, module boundaries checked.

Compatibility, safety, and release

  • Breaking changes or migration steps: callers that matched unreadable_output for a staging overrun now receive resource_constraint; both keep the same reason text.
  • Real Unblob coverage: none claimed.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @XiaoBinGan

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

Maintainer blocker verification

Both staging refusals use schema-owned maxima and one remediation owner: below the cap callers may increase the selected budget up to the supported maximum; at the cap the message recommends a smaller firmware range/image and a fresh absent output destination. It no longer recommends an impossible increase above the schema ceiling.

Regular-file sizes measure retained staging capacity, not observed process memory. The byte-budget refusal therefore reports capacity, matching entry-budget refusal, with non-retryability and the actual configured limit. Four focused FirmwareFiles tests and npm run check:fast passed on Node 24.18.0/npm 11.16.0, including serialized resource classification and cap-specific recovery guidance. No real Unblob extraction or public CLI was executed in this pass.

Current follow-up evidence

Merged main 82e4e032 to resolve the actual firmware contract conflict, retaining main's staging semantics and the schema-owned capacity/remediation fix. The combined tree passed 4 FirmwareFiles tests, 11 report-file boundary tests and check:fast; the 36 firmware integration cases were skipped by host configuration. No real extraction/provider result is claimed. The fork push was a verified fast-forward; this update establishes local combined-tree checks, not completed hosted CI.

🔄 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/5962 **Author:** [@XiaoBinGan](https://github.com/XiaoBinGan) **Created:** 10/21/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/firmware-staging-budget` --- ### 📝 Commits (5) - [`e0a5874`](https://github.com/morluto/rea/commit/e0a5874367b505018306e6b165fe0d36c97ed2a9) fix(firmware): report a staging budget refusal as a resource constraint - [`997a552`](https://github.com/morluto/rea/commit/997a55297dc9a0df35da0509e77d0b0c3ebaccae) fix(firmware): explain staging budget hard ceilings - [`3a7829b`](https://github.com/morluto/rea/commit/3a7829bad8c53b2175661be4367450c5e8ac75c3) fix(firmware): classify staging bytes as capacity - [`98b6997`](https://github.com/morluto/rea/commit/98b6997386391dcf923f837bfb7552d9cea0a816) Merge main into firmware staging budget - [`746a64c`](https://github.com/morluto/rea/commit/746a64c9a2a5f2d64430a1dcab7c42663c58bb01) chore: integrate firmware staging-budget fix with current main ### 📊 Changes **3 files changed** (+147 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/firmware/firmwareAnalysis.ts` (+4 -2) ➕ `src/firmware/FirmwareFiles.test.ts` (+100 -0) 📝 `src/firmware/FirmwareFiles.ts` (+43 -3) </details> ### 📄 Description ## Summary `inventoryFirmwareOutput` refused an extraction that exceeded the caller-selected `max_output_files` or `max_output_bytes` staging budget with `AnalysisOutputError`, so an MCP caller received `unreadable_output`, `category: "execution_failure"` and `rea doctor` remediation for a deterministic allowance the caller can raise. Fixes #5846 ## Problem and expected behavior - Smallest trigger: `extract_firmware` with `max_output_files: 1` over the repository's synthetic Unblob producer, which stages `rootfs/config` (one directory and one regular file). The inventory counted two entries and threw `Invalid analysis output for extract_firmware: Staging entry budget exceeded (1)`, projected as `unreadable_output` with doctor guidance. - Violated invariant: the firmware policy separates producer-report and staging allowances and documents caller-selected staging budgets; the error algebra classifies a bounded admission refusal as a resource constraint, and output errors describe failed output parsing. This refusal is a valid, deterministic budget decision. - Expected: keep refusing, identify the resource, report the exceeded allowance in limit details, and explain the actual recovery - raising that specific budget and rerunning with an absent output destination. `details.reason` keeps the observed text. ## Change and scope - `src/firmware/FirmwareFiles.ts`: both staging overruns now throw `AnalysisResourceConstraintError` (entries: `capacity`, bytes: `memory`) with `reported_limits.max_output_files` / `reported_limits.max_output_bytes`, `retryable: false`, and a remediation that names the control, its supported maximum and the absent-destination retry. - `src/firmware/FirmwareFiles.test.ts` (new): covers both refusals and their projection, including the remediation text. - Not included: no change to the budgets themselves, to Unblob invocation, to the `FirmwareCommand` deadline path or to publication. ## Contract and boundary impact - Semantic owner and earliest changed stage: firmware staging inventory enforcement. - Contribution scope fit and linked maintainer decision: not applicable - an ordinary fix inside an existing boundary. - CLI and MCP/tool-catalog contract: a staging-budget refusal now returns `resource_constraint` with `reported_limits` instead of `unreadable_output`; the input schema is unchanged. - Provider, bridge, target-format, or platform compatibility: none; the same function serves the provider and the command deadline path. - Evidence, artifact, provenance, or reconstruction contract: no extraction output is published when the budget is exceeded, as before. - Target selection, authority, upstream behavior, and cleanup details: unchanged; no extra process is launched and workspace cleanup keeps its existing path. - Generated metadata, package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). - [ ] Read existing files or captured data. - [x] 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: `src/firmware/FirmwareFiles.test.ts` (2 cases). - Base reproduction: before the change both cases fail with `Expected a resource constraint, received Error: Invalid analysis output for extract_firmware: Staging entry budget exceeded (1)` and the byte equivalent; after the change they pass and project `code: "resource_constraint"` with `details.reported_limits` and the budget-specific remediation. - User-visible CLI/MCP output: the refusal now names `max_output_files` / `max_output_bytes` and the supported maximum instead of recommending `rea doctor`. - Remaining proof gaps: the tests stage a real directory tree but do not run Unblob; the original report exercised a mocked Linux admission on macOS, and no real Unblob or public CLI run is claimed. 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 - `npx vitest run src/firmware tests/boundary/firmware` - 46 passed, 40 skipped. - `npm run format:check` - all matched files use the correct format. - `npm run verify:test-discovery` - all 1903 test files discovered exactly once. - `npm run typecheck` - no diagnostic in the changed files (the remaining errors in this checkout are pre-existing protobuf-module resolution failures). - `npm run lint` - 0 errors, module boundaries checked. ## Compatibility, safety, and release - Breaking changes or migration steps: callers that matched `unreadable_output` for a staging overrun now receive `resource_constraint`; both keep the same reason text. - Real Unblob coverage: none claimed. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @XiaoBinGan - [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] 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. <!-- maintainer-blocker-review --> ### Maintainer blocker verification Both staging refusals use schema-owned maxima and one remediation owner: below the cap callers may increase the selected budget up to the supported maximum; at the cap the message recommends a smaller firmware range/image and a fresh absent output destination. It no longer recommends an impossible increase above the schema ceiling. Regular-file sizes measure retained staging capacity, not observed process memory. The byte-budget refusal therefore reports `capacity`, matching entry-budget refusal, with non-retryability and the actual configured limit. Four focused `FirmwareFiles` tests and `npm run check:fast` passed on Node 24.18.0/npm 11.16.0, including serialized resource classification and cap-specific recovery guidance. No real Unblob extraction or public CLI was executed in this pass. <!-- current-blocker-followup --> ### Current follow-up evidence Merged main `82e4e032` to resolve the actual firmware contract conflict, retaining main's staging semantics and the schema-owned capacity/remediation fix. The combined tree passed 4 `FirmwareFiles` tests, 11 report-file boundary tests and `check:fast`; the 36 firmware integration cases were skipped by host configuration. No real extraction/provider result is claimed. The fork push was a verified fast-forward; this update establishes local combined-tree checks, not completed hosted CI. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:45:28 +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#7111
No description provided.