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 #6971] [MERGED] fix(firmware): stop recommending a raise at the staging budget ceiling #7484

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6971
Author: @XiaoBinGan
Created: 10/24/2026
Status: ✅ Merged
Merged: 10/24/2026
Merged by: @baron

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

📝 Commits (1)

  • 4c89ef5 fix(firmware): stop recommending a raise at the staging budget ceiling

📊 Changes

3 files changed (+90 additions, -3 deletions)

View changed files

📝 src/domain/firmware/firmwareAnalysis.ts (+6 -2)
📝 src/firmware/FirmwareFiles.ts (+26 -1)
➕ src/firmware/FirmwareStagingBudget.test.ts (+58 -0)

📄 Description

Summary

The firmware staging-budget refusal told callers to raise max_output_bytes or max_output_files
"within its schema maximum". At the schema ceiling that recovery does not exist, so the one case
where the selected value cannot grow received advice that cannot be followed.

Part of the contract described in #5846, which already returns a nonretryable resource constraint
naming the selected limit. This change only corrects the recovery text at the ceiling and pins the
schema maxima to named constants.

Problem and expected behavior

Smallest trigger: extract_firmware with max_output_files at its schema maximum (100000) on a
staging tree that still exceeds it, or max_output_bytes at 536870912. Both refusals keep their
resource_constraint / capacity classification and reported_limits, but the remediation says
"Increase max_output_files within its schema maximum if the larger extraction is required" — and no
larger value is accepted.

Expected: below the ceiling the remediation names the remaining room and the control to change. At
the ceiling it states that a further raise is not supported and points at a smaller firmware byte
range, which is the recovery that actually exists.

Change and scope

  • src/domain/firmware/firmwareAnalysis.ts: the two schema maxima become MAX_FIRMWARE_STAGING_BYTES
    and MAX_FIRMWARE_STAGING_ENTRIES, and the schema's .max() calls use them, so the accepted range
    and the advice cannot drift apart.
  • src/firmware/FirmwareFiles.ts: firmwareStagingBudgetRemediation selects the below-ceiling or
    at-ceiling wording from the selected value; firmwareStagingLimit uses it.

Intentionally not included: the classification itself (resource_constraint, capacity,
reported_limits, retryable: false) is unchanged — it is already correct on the base revision. No
budget default, extraction behavior, Unblob invocation or deadline path changes.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block integration. Link the
required maintainer scope decision for new providers or capabilities involving target execution,
injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state
"not applicable".

Not applicable — this is an ordinary fix inside the existing firmware admission boundary.

Contract and boundary impact

  • Semantic owner and earliest changed stage: firmware staging-budget enforcement in
    inventoryFirmwareOutput; the earliest changed stage is the refusal's remediation text, not the
    refusal.
  • Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not
    applicable.
  • CLI and MCP/tool-catalog contract: unchanged schemas, codes, categories and reported_limits. Only
    the remediation.action string for this refusal changes, which is the reported defect.
  • Provider, bridge, target-format, or platform compatibility: none; the same helper serves the
    provider path and the command deadline path.
  • Evidence, artifact, provenance, or reconstruction contract: no extraction output is published when
    a budget is exceeded, as before.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged; no
    extra process is launched and workspace cleanup keeps its existing path.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI
    generates and validates ignored catalogs and skills/; edit authored instructions in
    .agents/skills/reverse-engineer-anything/ and never commit build outputs): none.

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

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: src/firmware/FirmwareStagingBudget.test.ts — a budget below its ceiling
    offers the room and the control, both budgets at their ceilings state that a further raise is not
    supported and point at a smaller range, and the selected value and ceiling are named in both cases.
  • Base reproduction or other evidence: on the base revision firmwareStagingBudgetRemediation does
    not exist and the single-form remediation says "Increase within its schema maximum" for
    every selected value. Verified red → green: restoring that single form makes all four new cases
    fail; the change makes them pass.
  • User-visible CLI/MCP output (if applicable): for extract_firmware at the entry ceiling the
    remediation.action now reads "The staging entry budget, which counts extracted directories and
    links, reached its supported maximum (max_output_files=100000; maximum 100000). Raising
    max_output_files further is not supported. Select a smaller firmware byte range or analyze a
    smaller image. analysis_timeout_ms does not raise this staging allowance." Below the ceiling it
    reads "…was exceeded (max_output_files=1; supported maximum 100000). Increase max_output_files up to
    100000 if the larger extraction is required, or select a materially narrower firmware byte range."
  • Remaining proof gaps: the remediation strings are covered by module tests, not by an end-to-end
    extract_firmware MCP call. The 39 firmware integration cases are skipped by host configuration on
    this machine, and no real Unblob extraction was run.

For evidence-bearing changes:

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

Validation performed

  • node node_modules/vitest/vitest.mjs run src/firmware tests/boundary/firmware --maxWorkers=1 — 81
    passed, 52 skipped (10 files; the skips are host-gated firmware integration and workspace recovery).
  • npx tsc --noEmit -p . — no errors.
  • npx oxfmt <changed files> — formatted.
  • npm run verify:module-boundaries — 2898 source files checked, no violations.
  • Red → green on src/firmware/FirmwareStagingBudget.test.ts: 4 failed with the previous single-form
    remediation, 4 passed with the change.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The failure classification and reported_limits are
    unchanged; only the recovery sentence changes, and only where the previous sentence recommended an
    unsupported value.
  • Real Hopper/Ghidra, browser, or OS coverage: no analysis engine involved.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no target execution and no new data exposure.

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.

🔄 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/6971 **Author:** [@XiaoBinGan](https://github.com/XiaoBinGan) **Created:** 10/24/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@baron](https://github.com/baron) **Base:** `main` ← **Head:** `fix/firmware-staging-ceiling` --- ### 📝 Commits (1) - [`4c89ef5`](https://github.com/morluto/rea/commit/4c89ef55dcf92bcf6f2ed1f992c278d6eba67c35) fix(firmware): stop recommending a raise at the staging budget ceiling ### 📊 Changes **3 files changed** (+90 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/firmware/firmwareAnalysis.ts` (+6 -2) 📝 `src/firmware/FirmwareFiles.ts` (+26 -1) ➕ `src/firmware/FirmwareStagingBudget.test.ts` (+58 -0) </details> ### 📄 Description ## Summary The firmware staging-budget refusal told callers to raise `max_output_bytes` or `max_output_files` "within its schema maximum". At the schema ceiling that recovery does not exist, so the one case where the selected value cannot grow received advice that cannot be followed. Part of the contract described in #5846, which already returns a nonretryable resource constraint naming the selected limit. This change only corrects the recovery text at the ceiling and pins the schema maxima to named constants. ## Problem and expected behavior Smallest trigger: `extract_firmware` with `max_output_files` at its schema maximum (`100000`) on a staging tree that still exceeds it, or `max_output_bytes` at `536870912`. Both refusals keep their `resource_constraint` / `capacity` classification and `reported_limits`, but the remediation says "Increase max_output_files within its schema maximum if the larger extraction is required" — and no larger value is accepted. Expected: below the ceiling the remediation names the remaining room and the control to change. At the ceiling it states that a further raise is not supported and points at a smaller firmware byte range, which is the recovery that actually exists. ## Change and scope - `src/domain/firmware/firmwareAnalysis.ts`: the two schema maxima become `MAX_FIRMWARE_STAGING_BYTES` and `MAX_FIRMWARE_STAGING_ENTRIES`, and the schema's `.max()` calls use them, so the accepted range and the advice cannot drift apart. - `src/firmware/FirmwareFiles.ts`: `firmwareStagingBudgetRemediation` selects the below-ceiling or at-ceiling wording from the selected value; `firmwareStagingLimit` uses it. Intentionally not included: the classification itself (`resource_constraint`, `capacity`, `reported_limits`, `retryable: false`) is unchanged — it is already correct on the base revision. No budget default, extraction behavior, Unblob invocation or deadline path changes. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Not applicable — this is an ordinary fix inside the existing firmware admission boundary. ## Contract and boundary impact - Semantic owner and earliest changed stage: firmware staging-budget enforcement in `inventoryFirmwareOutput`; the earliest changed stage is the refusal's remediation text, not the refusal. - Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: unchanged schemas, codes, categories and `reported_limits`. Only the `remediation.action` string for this refusal changes, which is the reported defect. - Provider, bridge, target-format, or platform compatibility: none; the same helper serves the provider path and the command deadline path. - Evidence, artifact, provenance, or reconstruction contract: no extraction output is published when a budget is exceeded, as before. - Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged; no extra process is launched and workspace cleanup keeps its existing path. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/firmware/FirmwareStagingBudget.test.ts` — a budget below its ceiling offers the room and the control, both budgets at their ceilings state that a further raise is not supported and point at a smaller range, and the selected value and ceiling are named in both cases. - Base reproduction or other evidence: on the base revision `firmwareStagingBudgetRemediation` does not exist and the single-form remediation says "Increase <budget> within its schema maximum" for every selected value. Verified red → green: restoring that single form makes all four new cases fail; the change makes them pass. - User-visible CLI/MCP output (if applicable): for `extract_firmware` at the entry ceiling the `remediation.action` now reads "The staging entry budget, which counts extracted directories and links, reached its supported maximum (max_output_files=100000; maximum 100000). Raising max_output_files further is not supported. Select a smaller firmware byte range or analyze a smaller image. analysis_timeout_ms does not raise this staging allowance." Below the ceiling it reads "…was exceeded (max_output_files=1; supported maximum 100000). Increase max_output_files up to 100000 if the larger extraction is required, or select a materially narrower firmware byte range." - Remaining proof gaps: the remediation strings are covered by module tests, not by an end-to-end `extract_firmware` MCP call. The 39 firmware integration cases are skipped by host configuration on this machine, and no real Unblob extraction was run. 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 - `node node_modules/vitest/vitest.mjs run src/firmware tests/boundary/firmware --maxWorkers=1` — 81 passed, 52 skipped (10 files; the skips are host-gated firmware integration and workspace recovery). - `npx tsc --noEmit -p .` — no errors. - `npx oxfmt <changed files>` — formatted. - `npm run verify:module-boundaries` — 2898 source files checked, no violations. - Red → green on `src/firmware/FirmwareStagingBudget.test.ts`: 4 failed with the previous single-form remediation, 4 passed with the change. ## Compatibility, safety, and release - Breaking changes or migration steps: none. The failure classification and `reported_limits` are unchanged; only the recovery sentence changes, and only where the previous sentence recommended an unsupported value. - Real Hopper/Ghidra, browser, or OS coverage: no analysis engine involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no target execution and no new data exposure. ## 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 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:48:09 +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#7484
No description provided.