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 #4117] [MERGED] fix(verifiers): align WABT operation timeout #6067

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4117
Author: @N0zoM1z0
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/15/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/windows-wabt-mcp-timeout-4109

📝 Commits (5)

  • 5423ae0 fix(verifiers): align WABT MCP request timeout
  • 3318d80 Merge remote-tracking branch 'origin/main' into fix/windows-wabt-mcp-timeout-4109
  • ecd04ee fix(verifiers): bound packaged WABT workflow
  • fbc2685 Merge remote-tracking branch 'origin/main' into fix/windows-wabt-mcp-timeout-4109
  • 8ca19d1 Merge remote-tracking branch 'origin/main' into fix/windows-wabt-mcp-timeout-4109

📊 Changes

3 files changed (+18 additions, -6 deletions)

View changed files

➕ scripts/lib/wabt-verifier-timeouts.mjs (+4 -0)
📝 scripts/verify-packaged-wasm-artifact.mjs (+6 -1)
📝 scripts/verify-wasm-artifact.mjs (+8 -5)

📄 Description

Summary

The real Windows WABT verifier gave equivalent CLI and MCP inspections different fixed deadlines, so MCP expired at the SDK default 60 seconds and a later malformed CLI case could expire at 120 seconds. This change gives every WABT inspection one 240-second operation budget across both transports and gives the complete packaged workflow a shared 15-minute aggregate budget, preserving all parity, malformed-input, retained Evidence, residue, and cleanup checks.

Fixes #4109.

Problem and expected behavior

On an ordinary two-core Windows run, the verifier reached the production MCP inspection and failed with typed REQUEST_TIMEOUT at 60 seconds. Enabling the existing Node compile cache reproduced it. A 120-second MCP-only candidate passed that boundary, then the equivalent malformed CLI path reached its separate 120-second deadline and retained a workspace residue. Equivalent verifier operations need one budget large enough for the measured bounded workload.

Change and scope

  • Define one 240-second WABT verifier operation budget and one 15-minute aggregate workflow budget in a single verifier-owned module.
  • Apply the operation budget to public CLI artifact inspection and every MCP tool call, including bundle and malformed-input paths.
  • Apply the aggregate budget to the packaged wrapper so it cannot terminate one valid operation or skip child cleanup. The 15-minute limit covers the measured 647-second completed Windows workflow with about 39% margin.
  • Keep tool preflight, provider limits, fixtures, retries, cleanup, output, and product contracts unchanged.

Contribution scope: verifier-only correction for existing read-only WASM artifact analysis. No provider capability or authority changes; no maintainer scope decision is required.

Contract and boundary impact

  • Semantic owner and earliest changed stage: real WABT verification request supervision.
  • CLI and MCP/tool-catalog contract: unchanged.
  • Provider, bridge, target-format, or platform compatibility: unchanged; only verifier operation and aggregate wait policy changes.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • 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

  • Base reproductions: default and compile-cache Windows runs both failed at the SDK's 60-second MCP timeout and cleaned to Job0.

  • Intermediate 120-second candidate passed the original MCP failure, then retained a later malformed CLI timeout and workspace residue instead of hiding either fact.

  • Final real run passed all 42 WABT 1.0.42 cases: seven normal CLI/MCP schema, Evidence, identity, hash/bytes, WAT, section, glue/candidate, and retained-bundle comparisons plus both malformed inputs and their retained failed Evidence for every fixture.

  • Review follow-up on exact head ecd04eea840385caeb7b595c827845b6ff8c6c88: an ordinary-user Windows continuation from the extracted-package entrypoint passed the same 42 cases through the packaged wrapper in 363.28 seconds, exceeding the old 180-second cap, with empty stderr and Job0.

  • Full pack/install verification exposed four independent existing Windows verifier defects: npm command-script launching (#4125), CRLF tar-member parsing (#4128), child extraction into a leased private root (#4134), and transient installed-tree cleanup (#4136). Each is recorded separately. The continuation used explicit test-only bypasses for those prerequisites; it directly verifies this PR's nested timeout and cleanup path, but does not claim the full pack/install lane passed.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm run check:fast — passed on final head fbc268555adbf00c68c4cb38aaed16a8ff78abf3.
  • npm run test:focused -- tests/boundary/mcp/wasmArtifactMcp.test.ts src/wasm/WabtArtifactProvider.test.ts src/wasm/WabtOutput.test.ts — 42/42 passed on the final head.
  • Exact-head CI on fbc268555adbf00c68c4cb38aaed16a8ff78abf3 — all required checks passed, including five test shards, source/static/build/package, Windows capability/package, native package baselines, Portable tests, the required aggregator, and Greptile review. The latest-main merge changed only JavaScript tool-effect contracts/docs/tests; a machine diff confirms every WABT and package-verifier input used by the Windows run is unchanged.
  • Ordinary-user Windows candidate 5423ae0734c89c825cf06603187db45cbf9e55e7 — 42/42 real verifier cases passed; 647.28 s Job wall, 667.84 s observer wall, 148.91 sampled CPU seconds, 1,145,798,656-byte Job peak, 1,175,539,712-byte sampled working-set peak, 2 LP, BelowNormal, 2 GiB, 631 output bytes, empty stderr, and Job0.
  • Exact-head Windows packaged-timeout continuation — 42/42 passed; 363.28 s Job wall / 366.17 s observer wall / 98.30 sampled CPU seconds / 942,870,528-byte Job peak / 968,450,048-byte sampled working-set peak / 9,761,697,792-byte minimum host free memory, with 2 LP, BelowNormal, 2 GiB, 631 output bytes, empty stderr, and Job0.

The completed final workload is broader than the failing reproductions, and the compile-cache reproduction was slower than the default failure. No speedup or cache benefit is claimed. Agent-token cost was not measured; the verifier's output shape and size are unchanged.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: real WABT on Windows; no Hopper, Ghidra, or browser path is affected.
  • Security, privacy, process, or containment review: no new authority; existing private input staging, child temp ownership, residue checks, and Job cleanup remain intact.

Author readiness

Human owner: @N0zoM1z0

  • 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/4117 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/15/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/windows-wabt-mcp-timeout-4109` --- ### 📝 Commits (5) - [`5423ae0`](https://github.com/morluto/rea/commit/5423ae073cb3ad68df7a3a2246aa2824abad9556) fix(verifiers): align WABT MCP request timeout - [`3318d80`](https://github.com/morluto/rea/commit/3318d802e2494dfdf8fa01976d716a811591bdc2) Merge remote-tracking branch 'origin/main' into fix/windows-wabt-mcp-timeout-4109 - [`ecd04ee`](https://github.com/morluto/rea/commit/ecd04eea840385caeb7b595c827845b6ff8c6c88) fix(verifiers): bound packaged WABT workflow - [`fbc2685`](https://github.com/morluto/rea/commit/fbc268555adbf00c68c4cb38aaed16a8ff78abf3) Merge remote-tracking branch 'origin/main' into fix/windows-wabt-mcp-timeout-4109 - [`8ca19d1`](https://github.com/morluto/rea/commit/8ca19d1511c8f90dc4238068915aaecc75e4ae60) Merge remote-tracking branch 'origin/main' into fix/windows-wabt-mcp-timeout-4109 ### 📊 Changes **3 files changed** (+18 additions, -6 deletions) <details> <summary>View changed files</summary> ➕ `scripts/lib/wabt-verifier-timeouts.mjs` (+4 -0) 📝 `scripts/verify-packaged-wasm-artifact.mjs` (+6 -1) 📝 `scripts/verify-wasm-artifact.mjs` (+8 -5) </details> ### 📄 Description ## Summary The real Windows WABT verifier gave equivalent CLI and MCP inspections different fixed deadlines, so MCP expired at the SDK default 60 seconds and a later malformed CLI case could expire at 120 seconds. This change gives every WABT inspection one 240-second operation budget across both transports and gives the complete packaged workflow a shared 15-minute aggregate budget, preserving all parity, malformed-input, retained Evidence, residue, and cleanup checks. Fixes #4109. ## Problem and expected behavior On an ordinary two-core Windows run, the verifier reached the production MCP inspection and failed with typed `REQUEST_TIMEOUT` at 60 seconds. Enabling the existing Node compile cache reproduced it. A 120-second MCP-only candidate passed that boundary, then the equivalent malformed CLI path reached its separate 120-second deadline and retained a workspace residue. Equivalent verifier operations need one budget large enough for the measured bounded workload. ## Change and scope - Define one 240-second WABT verifier operation budget and one 15-minute aggregate workflow budget in a single verifier-owned module. - Apply the operation budget to public CLI artifact inspection and every MCP tool call, including bundle and malformed-input paths. - Apply the aggregate budget to the packaged wrapper so it cannot terminate one valid operation or skip child cleanup. The 15-minute limit covers the measured 647-second completed Windows workflow with about 39% margin. - Keep tool preflight, provider limits, fixtures, retries, cleanup, output, and product contracts unchanged. Contribution scope: verifier-only correction for existing read-only WASM artifact analysis. No provider capability or authority changes; no maintainer scope decision is required. ## Contract and boundary impact - Semantic owner and earliest changed stage: real WABT verification request supervision. - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: unchanged; only verifier operation and aggregate wait policy changes. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Generated metadata, package, or installation impact: none. Expected effects: - [x] 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 - Base reproductions: default and compile-cache Windows runs both failed at the SDK's 60-second MCP timeout and cleaned to Job0. - Intermediate 120-second candidate passed the original MCP failure, then retained a later malformed CLI timeout and workspace residue instead of hiding either fact. - Final real run passed all 42 WABT 1.0.42 cases: seven normal CLI/MCP schema, Evidence, identity, hash/bytes, WAT, section, glue/candidate, and retained-bundle comparisons plus both malformed inputs and their retained failed Evidence for every fixture. - Review follow-up on exact head `ecd04eea840385caeb7b595c827845b6ff8c6c88`: an ordinary-user Windows continuation from the extracted-package entrypoint passed the same 42 cases through the packaged wrapper in 363.28 seconds, exceeding the old 180-second cap, with empty stderr and Job0. - Full pack/install verification exposed four independent existing Windows verifier defects: npm command-script launching (#4125), CRLF tar-member parsing (#4128), child extraction into a leased private root (#4134), and transient installed-tree cleanup (#4136). Each is recorded separately. The continuation used explicit test-only bypasses for those prerequisites; it directly verifies this PR's nested timeout and cleanup path, but does not claim the full pack/install lane passed. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run check:fast` — passed on final head `fbc268555adbf00c68c4cb38aaed16a8ff78abf3`. - `npm run test:focused -- tests/boundary/mcp/wasmArtifactMcp.test.ts src/wasm/WabtArtifactProvider.test.ts src/wasm/WabtOutput.test.ts` — 42/42 passed on the final head. - Exact-head CI on `fbc268555adbf00c68c4cb38aaed16a8ff78abf3` — all required checks passed, including five test shards, source/static/build/package, Windows capability/package, native package baselines, Portable tests, the required aggregator, and Greptile review. The latest-main merge changed only JavaScript tool-effect contracts/docs/tests; a machine diff confirms every WABT and package-verifier input used by the Windows run is unchanged. - Ordinary-user Windows candidate `5423ae0734c89c825cf06603187db45cbf9e55e7` — 42/42 real verifier cases passed; 647.28 s Job wall, 667.84 s observer wall, 148.91 sampled CPU seconds, 1,145,798,656-byte Job peak, 1,175,539,712-byte sampled working-set peak, 2 LP, BelowNormal, 2 GiB, 631 output bytes, empty stderr, and Job0. - Exact-head Windows packaged-timeout continuation — 42/42 passed; 363.28 s Job wall / 366.17 s observer wall / 98.30 sampled CPU seconds / 942,870,528-byte Job peak / 968,450,048-byte sampled working-set peak / 9,761,697,792-byte minimum host free memory, with 2 LP, BelowNormal, 2 GiB, 631 output bytes, empty stderr, and Job0. The completed final workload is broader than the failing reproductions, and the compile-cache reproduction was slower than the default failure. No speedup or cache benefit is claimed. Agent-token cost was not measured; the verifier's output shape and size are unchanged. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: real WABT on Windows; no Hopper, Ghidra, or browser path is affected. - Security, privacy, process, or containment review: no new authority; existing private input staging, child temp ownership, residue checks, and Job cleanup remain intact. ## Author readiness Human owner: @N0zoM1z0 - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:11:36 +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#6067
No description provided.