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 #4924] test(http3): verify reset and partial-response capture semantics #6675

New issue
Open
opened 2026-11-01 21:42:14 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:42:14 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4924
Author: @LuisTaffelli
Created: 10/18/2026
Status: 🔄 Open

Base: main ← Head: test/http3-origin-reset

📝 Commits (3)

  • 71942b2 test(http3): verify reset and partial-response capture semantics
  • 7bd6b09 test(jadx): retain protocol fixture lifetime until owned cleanup
  • c755d26 docs(http3): record reinspection against the refreshed runtime

📊 Changes

11 files changed (+1432 additions, -167 deletions)

View changed files

📝 docs/http3-capture-lab.md (+172 -5)
📝 scripts/fixtures/http3-lab.py (+88 -6)
📝 scripts/fixtures/http3-lab.test.py (+73 -2)
📝 scripts/fixtures/observe-mitmproxy-http3.py (+12 -2)
📝 scripts/lib/http3-capture-assertions.mjs (+67 -45)
📝 scripts/lib/http3-capture-assertions.test.mjs (+291 -100)
➕ scripts/lib/http3-capture-fixtures.mjs (+312 -0)
➕ scripts/lib/http3-reset-assertions.mjs (+320 -0)
📝 scripts/verify-http3-network-captures.mjs (+60 -4)
➕ tests/evaluation/http3CaptureAssertions.test.ts (+33 -0)
📝 tests/fixtures/android/jadx-mcp.mjs (+4 -3)

📄 Description

Summary

Verify native HTTP/3 capture semantics and recovery on the original connections after origin cancellation, both before response headers and after a streamed partial response. Follow-up to merged #1997; no separate issue is linked because this extends that existing optional lab.

Problem and expected behavior

Status 200 and a declared content-length do not establish a complete response or recovered body bytes. The lab must distinguish bytes observed at endpoints from bytes retained in captures, preserve incomplete exchanges, and prove recovery independently on each connection leg.

Change and scope

  • --with-origin-reset cancels before headers. --with-partial-reset sends 21 of 32 declared bytes, waits for client receipt, then cancels. Both require H3_REQUEST_CANCELLED and same-connection recovery; stream IDs remain local to each leg.
  • Shared assertions own HTTP field interpretation. Requested missing scenarios fail before analysis. A discovered evaluation test rejects failing and empty assertion suites in ordinary CI.
  • A separate CI repair keeps the synthetic JADX protocol fixture alive until its verified cleanup owner stops it. The explicit RPC-disconnect fault still exits. JADX production code is unchanged.

Contract and boundary impact

  • Semantic owner: optional lab producer, shared capture assertions and verifier; the CI repair belongs to the synthetic process fixture.
  • Scope and maintainer decision: existing self-owned loopback boundaries from #1997 and a test-fixture correction; separate advance scope decision not applicable.
  • CLI/MCP contract: no schema or product-tool changes; complete delivery defaults remain unchanged. Only the optional verifier gains scenario flags.
  • Compatibility: mitmproxy 12.2.3, aioquic 1.2.0, Linux reverse mode, QUIC v1. Earlier normal/fallback and before-headers captures remain inspectable.
  • Evidence/provenance: original capture hashes, exact fields/bytes, nulls, errors and retained session Evidence are checked through CLI/MCP. Endpoint receipt is distinct from stored body evidence.
  • Authority/cleanup: generated loopback endpoints, private files, explicit test CAs and existing owned-process supervision. Partial responses stream with body storage disabled; cleanup attempts all acquired resources.
  • Metadata/package/install: no dependencies, installers, public metadata or release changes. Lab scripts and test fixtures are outside the package file allowlist.

Expected effects of running the optional lab:

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

These effects are the lab's Python/addon/proxy/client code, private generated files and loopback traffic; host trust and routes are unchanged.

Evidence and regression coverage

Fresh traffic and reinspection passed for nine native records. The partial response retains status_code: 200, content: null, timestamp_end: null and the producer error. The 21-byte prefix is endpoint evidence, not a captured body. Recovery bodies were 42/50 bytes.

Suppressing receipt produced a failed attempt without success output, cleanup failures or live owned descendants/groups. This was a controlled fault. Source/capture hashes, versions, run IDs and the refreshed-runtime reinspection are in the lab evidence; raw captures and keys remain private.

  • 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

  • CI 39088666739 on c755d268230e5d82bad8ba14936876058852585b — passed all 36 jobs, including all five test shards, their aggregate, Windows capability/package verification and CI required.
  • npm run check and npm run docs:check — passed after the final documentation update; docs checks include five README consistency tests.
  • Focused plist, keyed-archive and HTTP/3 evaluation tests — 54 passed on the rebased runtime, including the formerly failing archive case and the HTTP/3 assertion gate.
  • node --test scripts/lib/http3-capture-assertions.test.mjs scripts/lib/http3-verifier-lifecycle.test.mjs — 65 passed. Pinned aioquic Python producer tests — six passed.
  • Ten affected Android/JADX boundary and MCP files — 116 passed after the fixture repair, covering cleanup retry, disconnect, cancellation, startup and archive ownership.
  • Real fresh-traffic verifier, then --inspect-existing --with-origin-reset --with-partial-reset — passed CLI/MCP schemas, bytes, identity, reset/recovery, retained Evidence and cleanup. The updated-runtime reinspection run was a3a1c38e-d4cf-4cef-97cb-c76743866c40 (2026-10-18 01:31 UTC); its five lab source hashes and four capture digests match the original evidence. Reinspection adds no traffic or scenario coverage.

The complete local deterministic suite was not run; the remote result above is the CI evidence for this revision.

CI repairs and earlier failure limits

Rebased onto upstream 1accac27c36d98fb432e32a4a45fe75c78480773 / #4930 to consume the independently reproduced plist-format and keyed-archive expectation repairs.

The next CI run exposed a synthetic JADX cleanup race. Its original 48-test integration file passed locally, so no deterministic local reproduction of that complete failure is claimed. A separate EOF experiment confirmed that the fixture exited without its cleanup owner in tool-error mode; after the repair it stayed alive until explicitly stopped. All five remote test shards passed subsequently.

An earlier Windows curated run exceeded a 15-second webModuleCli deadline despite complete JSON output. Its cause remains unestablished; the Linux test passed but does not establish Windows behavior. The latest Windows lane passed without changing that test or deadline. GitHub refused an isolated rerun because repository admin rights were required; the documentation update triggered fresh CI from the owned branch.

Compatibility, safety, and release

  • No breaking change, migration, package metadata change or release request.
  • New reset scenarios were verified in private Linux user/mount/network/PID namespaces with loopback and no default routes; they share the host kernel/filesystem. These resets were not rerun in the pinned VM.
  • Buffered partial responses, storing streamed bodies, other reset codes, client cancellation, real-browser HTTP/3 and QUIC v2 remain unverified. No performance claim is made.
  • Generated test CAs are passed explicitly. Raw captures, certificates and keys remain outside Git.

Author readiness

Human owner: @LuisTaffelli

  • 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/4924 **Author:** [@LuisTaffelli](https://github.com/LuisTaffelli) **Created:** 10/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `test/http3-origin-reset` --- ### 📝 Commits (3) - [`71942b2`](https://github.com/morluto/rea/commit/71942b2617770fd57e2c5e6bb9c3ecbd3348fe82) test(http3): verify reset and partial-response capture semantics - [`7bd6b09`](https://github.com/morluto/rea/commit/7bd6b09ffd52db8369c3ba48dba9cd4b94b413c6) test(jadx): retain protocol fixture lifetime until owned cleanup - [`c755d26`](https://github.com/morluto/rea/commit/c755d268230e5d82bad8ba14936876058852585b) docs(http3): record reinspection against the refreshed runtime ### 📊 Changes **11 files changed** (+1432 additions, -167 deletions) <details> <summary>View changed files</summary> 📝 `docs/http3-capture-lab.md` (+172 -5) 📝 `scripts/fixtures/http3-lab.py` (+88 -6) 📝 `scripts/fixtures/http3-lab.test.py` (+73 -2) 📝 `scripts/fixtures/observe-mitmproxy-http3.py` (+12 -2) 📝 `scripts/lib/http3-capture-assertions.mjs` (+67 -45) 📝 `scripts/lib/http3-capture-assertions.test.mjs` (+291 -100) ➕ `scripts/lib/http3-capture-fixtures.mjs` (+312 -0) ➕ `scripts/lib/http3-reset-assertions.mjs` (+320 -0) 📝 `scripts/verify-http3-network-captures.mjs` (+60 -4) ➕ `tests/evaluation/http3CaptureAssertions.test.ts` (+33 -0) 📝 `tests/fixtures/android/jadx-mcp.mjs` (+4 -3) </details> ### 📄 Description ## Summary Verify native HTTP/3 capture semantics and recovery on the original connections after origin cancellation, both before response headers and after a streamed partial response. Follow-up to merged #1997; no separate issue is linked because this extends that existing optional lab. ## Problem and expected behavior Status 200 and a declared content-length do not establish a complete response or recovered body bytes. The lab must distinguish bytes observed at endpoints from bytes retained in captures, preserve incomplete exchanges, and prove recovery independently on each connection leg. ## Change and scope - `--with-origin-reset` cancels before headers. `--with-partial-reset` sends 21 of 32 declared bytes, waits for client receipt, then cancels. Both require `H3_REQUEST_CANCELLED` and same-connection recovery; stream IDs remain local to each leg. - Shared assertions own HTTP field interpretation. Requested missing scenarios fail before analysis. A discovered evaluation test rejects failing and empty assertion suites in ordinary CI. - A separate CI repair keeps the synthetic JADX protocol fixture alive until its verified cleanup owner stops it. The explicit RPC-disconnect fault still exits. JADX production code is unchanged. ## Contract and boundary impact - Semantic owner: optional lab producer, shared capture assertions and verifier; the CI repair belongs to the synthetic process fixture. - Scope and maintainer decision: existing self-owned loopback boundaries from #1997 and a test-fixture correction; separate advance scope decision not applicable. - CLI/MCP contract: no schema or product-tool changes; complete delivery defaults remain unchanged. Only the optional verifier gains scenario flags. - Compatibility: mitmproxy 12.2.3, aioquic 1.2.0, Linux reverse mode, QUIC v1. Earlier normal/fallback and before-headers captures remain inspectable. - Evidence/provenance: original capture hashes, exact fields/bytes, nulls, errors and retained session Evidence are checked through CLI/MCP. Endpoint receipt is distinct from stored body evidence. - Authority/cleanup: generated loopback endpoints, private files, explicit test CAs and existing owned-process supervision. Partial responses stream with body storage disabled; cleanup attempts all acquired resources. - Metadata/package/install: no dependencies, installers, public metadata or release changes. Lab scripts and test fixtures are outside the package file allowlist. Expected effects of running the optional lab: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [x] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. - [x] 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. These effects are the lab's Python/addon/proxy/client code, private generated files and loopback traffic; host trust and routes are unchanged. ## Evidence and regression coverage Fresh traffic and reinspection passed for nine native records. The partial response retains `status_code: 200`, `content: null`, `timestamp_end: null` and the producer error. The 21-byte prefix is endpoint evidence, not a captured body. Recovery bodies were 42/50 bytes. Suppressing receipt produced a failed attempt without success output, cleanup failures or live owned descendants/groups. This was a controlled fault. Source/capture hashes, versions, run IDs and the refreshed-runtime reinspection are in [the lab evidence](https://github.com/LuisTaffelli/rea/blob/c755d268230e5d82bad8ba14936876058852585b/docs/http3-capture-lab.md#verified-reset-snapshot-2026-10-17); raw captures and keys remain private. - [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 - [CI 39088666739](https://github.com/morluto/rea/actions/runs/39088666739) on `c755d268230e5d82bad8ba14936876058852585b` — passed all 36 jobs, including all five test shards, their aggregate, Windows capability/package verification and `CI required`. - `npm run check` and `npm run docs:check` — passed after the final documentation update; docs checks include five README consistency tests. - Focused plist, keyed-archive and HTTP/3 evaluation tests — 54 passed on the rebased runtime, including the formerly failing archive case and the HTTP/3 assertion gate. - `node --test scripts/lib/http3-capture-assertions.test.mjs scripts/lib/http3-verifier-lifecycle.test.mjs` — 65 passed. Pinned aioquic Python producer tests — six passed. - Ten affected Android/JADX boundary and MCP files — 116 passed after the fixture repair, covering cleanup retry, disconnect, cancellation, startup and archive ownership. - Real fresh-traffic verifier, then `--inspect-existing --with-origin-reset --with-partial-reset` — passed CLI/MCP schemas, bytes, identity, reset/recovery, retained Evidence and cleanup. The updated-runtime reinspection run was `a3a1c38e-d4cf-4cef-97cb-c76743866c40` (2026-10-18 01:31 UTC); its five lab source hashes and four capture digests match the original evidence. Reinspection adds no traffic or scenario coverage. The complete local deterministic suite was not run; the remote result above is the CI evidence for this revision. <details> <summary>CI repairs and earlier failure limits</summary> Rebased onto upstream `1accac27c36d98fb432e32a4a45fe75c78480773` / #4930 to consume the independently reproduced plist-format and keyed-archive expectation repairs. The next CI run exposed a synthetic JADX cleanup race. Its original 48-test integration file passed locally, so no deterministic local reproduction of that complete failure is claimed. A separate EOF experiment confirmed that the fixture exited without its cleanup owner in `tool-error` mode; after the repair it stayed alive until explicitly stopped. All five remote test shards passed subsequently. An earlier Windows curated run exceeded a 15-second `webModuleCli` deadline despite complete JSON output. Its cause remains unestablished; the Linux test passed but does not establish Windows behavior. The latest Windows lane passed without changing that test or deadline. GitHub refused an isolated rerun because repository admin rights were required; the documentation update triggered fresh CI from the owned branch. </details> ## Compatibility, safety, and release - No breaking change, migration, package metadata change or release request. - New reset scenarios were verified in private Linux user/mount/network/PID namespaces with loopback and no default routes; they share the host kernel/filesystem. These resets were not rerun in the pinned VM. - Buffered partial responses, storing streamed bodies, other reset codes, client cancellation, real-browser HTTP/3 and QUIC v2 remain unverified. No performance claim is made. - Generated test CAs are passed explicitly. Raw captures, certificates and keys remain outside Git. ## Author readiness Human owner: @LuisTaffelli - [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>
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#6675
No description provided.