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 #6249] [CLOSED] fix(protobuf): preserve schema admission diagnostics #7226

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6249
Author: @wunianze666-netizen
Created: 10/22/2026
Status: ❌ Closed

Base: main ← Head: codex/protobuf-schema-diagnostics

📝 Commits (1)

  • f415732 fix(protobuf): preserve schema admission diagnostics

📊 Changes

5 files changed (+292 additions, -43 deletions)

View changed files

📝 docs/web-network-captures.md (+9 -0)
📝 src/browser/history/protobuf/ProtobufCapture.ts (+8 -19)
📝 src/browser/history/protobuf/ProtobufSchema.ts (+62 -15)
📝 src/browser/history/protobuf/ProtobufWire.test.ts (+106 -9)
📝 tests/acceptance/tools/protobufCapture.test.ts (+107 -0)

📄 Description

Status — 2026-10-24: superseded, not merged. Maintainer commit b3c3b21e fixed and closed #6118 on main. The core diagnostic distinction in this draft is therefore already covered by upstream's own admission result model.

I independently built unmodified main b5c42dfc2a8eddeffb8d37c669178fa04169f050 with pinned Node 24.22.1/npm 11.16.0. All 9 generated controls passed: valid descriptor, missing selected message and malformed descriptor through the production CLI plus full/compact production stdio MCP. Four retained views remained readable after deleting the generated capture/descriptor inputs; source SHA, original ordinal 0, parent Evidence, field-specific path/reason and safe wire reason were preserved. SDK-converted request/response schemas were checked. This is selected Windows public-adapter evidence, not a complete suite, live provider or whole-platform qualification.

Closing this draft as superseded instead of resolving conflicts by reintroducing the old implementation. Original head f415732d and branch/verification assets are retained. This PR has not been merged; no upstream adoption or co-authorship credit is claimed. No target traffic was replayed and no paid model was called.

Original PR description and historical verification

Summary

Fixes #6118. Preserve actionable Protobuf schema-admission diagnostics: an undefined selected message points to protobuf.schema.message_type (invalid_value); malformed or unresolved descriptor definitions point to protobuf.schema.descriptor_set_path (invalid_format). Both still return invalid_request and retain sanitized partial capture Evidence.

Problem and expected behavior

A valid descriptor with capture.Missing and corrupt descriptor bytes previously produced the same generic schema error. Callers could not tell whether to correct the selected type or replace the descriptor. Wire preflight also discarded its known byte offset/reason.

Change and scope

ProtobufSchema.read now returns the existing typed Result<ProtobufSchema, AnalysisInputError> for schema admission. The owning stage identifies the rejected field and retains wire facts or SDK causes internally. ProtobufCapture forwards this result, removing its blanket catch/reclassification. SDK exception text is not copied into public issues; shared byte-budget and cancellation failures remain outside SDK catches. An entry checkpoint also honors cancellation for empty descriptors.

Within the existing offline capture scope; no new provider, target execution or authority requiring a separate maintainer decision.

Contract and boundary impact

  • Semantic owner/earliest changed stage: descriptor-wire/SDK registry admission in ProtobufSchema, consumed by ProtobufCapture.
  • Scope/maintainer decision: correction within existing schema interpretation; separate decision not applicable.
  • CLI/MCP/tool-catalog: no new argument, tool or success schema. Both interfaces expose the corrected details.issues paths/reasons. Example: {path:["protobuf","schema","message_type"],reason:"invalid_value"}.
  • Provider/bridge/format/platform: existing FileDescriptorSet and HAR workflow; underlying protobuf-es 2.16.0 and framing remain unchanged.
  • Evidence/artifact/provenance: valid CLI/MCP Evidence IDs remain equal; failures preserve the original capture SHA and retained ordinal 0 in the generated controls.
  • Target selection/authority/cleanup: selected local files only; no acquisition, network retrieval, replay or cleanup-policy expansion.
  • Generated metadata/package/install: no dependency, version or installer change. No generated catalogs, binaries or build outputs committed.

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.

The verification harness starts REA's own CLI/MCP subprocesses and writes self-owned fixtures; the feature adds no target-process operation.

Evidence and regression coverage

  • Fixed baseline: main 26356dc34a74e38b68eb2acb4befb126176ed978, package 6.7.0.

  • Before the production change, the three new CLI/MCP cases selected by test name had one valid case pass and two error-path cases fail on the incorrect issue paths. The other 21 cases were skipped in that selected baseline run, not counted as passed.

  • After the change, all 24 capture acceptance cases pass through the compiled CLI and production stdio MCP, including valid/missing/malformed descriptor cases, retained views after failure, source identity, byte-budget refusal, credential exclusions and schema round trips.

  • Producer tests preserve malformed unknown-field rejection with the original byte-16 overflowing-varint cause, SDK decoding/registry failures, empty descriptor versus missing type, leading-dot lookup, registry expansion budget and exact caller cancellation reasons.

  • Current-head code CI 39723699187 passed for f415732d. Source and all eight portable-shard logs executed merge b22decce070262030bb0368eaf524b878c785ed9 against main bd5d189a8f8aeea669bcb93e68af6c046b567939. Raw logs confirm 21 wire/schema, 2 capture, 5 trailer, 13 failure-projection, 24 CLI/production-stdio acceptance and one MCP-contract checks.

  • Source/static/docs/build, eight portable shards, Windows native artifact build, selected Linux package baseline and controlled browser/web-network lanes passed. These are remote selected-lane results, not a new local rerun or full Windows/provider qualification.

  • Remaining gaps: no complete local repository suite, external customer capture or downstream-recovery frequency measurement; no local macOS/Linux run or comparative performance benchmark. Generated local controls and controlled CI fixture lanes do not establish customer adoption. Human initial-readiness declarations remain pending.

  • 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

Windows x64, Node 24.18.0/npm 11.16.0. npm was invoked via the pinned Node/npm-cli entry.

  • node scripts/run-development-tests.mjs focused src/browser/history/protobuf/ProtobufWire.test.ts src/browser/history/protobuf/ProtobufCapture.test.ts src/browser/history/protobuf/ProtobufBodyTrailer.test.ts src/browser/history/CaptureFailures.test.ts tests/acceptance/tools/protobufCapture.test.ts tests/boundary/mcp/webNetworkCaptureMcp.test.ts tests/conformance/readmeConsistency.test.ts — 71 passed, zero skipped, including 24 production CLI/stdio acceptance cases and SDK-converted schema checks.
  • npm run check — passed typecheck, lint/module, format, metadata and architecture checks.
  • npm run docs:check — generated checks and five fresh consistency controls passed; these repeat the same documentation file rather than add five distinct tests to the 71.
  • node scripts/verify-test-discovery.mjs — all 1,967 test files discovered exactly once.
  • node scripts/check-dependency-install.mjs and node scripts/verify-windows-native-artifact.mjs — passed. Official 6.7.0 native artifact from main ancestor 87c8086f has matching native/build/verification source relative to the frozen baseline; this is component qualification, not full Windows-provider support.

Compatibility, safety, and release

  • Breaking changes/migration: valid success behavior and inputs unchanged. Invalid schema requests intentionally receive more specific correction paths/reasons; error code/category and partial-observation behavior remain stable.
  • Real tool/OS: Windows public CLI and production stdio over generated offline inputs. No Ghidra/Hopper, live browser, capture or request replay.
  • Package/release metadata: unchanged; no release or deployment.
  • Privacy/containment: owned wire diagnostics and correction guidance only; raw SDK exception text stays in the internal cause. No unbounded list of available message types, descriptor content or credentials added to public correction messages.
  • No token, speed, memory or customer-adoption benefit measured or claimed.

Author readiness

Human owner: @wunianze666-netizen

AI-assisted implementation and verification. The human owner's initial review declaration remains pending; this PR is a draft.

  • 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 within the existing offline parsing boundary.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs and contracts 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/6249 **Author:** [@wunianze666-netizen](https://github.com/wunianze666-netizen) **Created:** 10/22/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `codex/protobuf-schema-diagnostics` --- ### 📝 Commits (1) - [`f415732`](https://github.com/morluto/rea/commit/f415732d61aa9aefd177949f3b45344c62e0274a) fix(protobuf): preserve schema admission diagnostics ### 📊 Changes **5 files changed** (+292 additions, -43 deletions) <details> <summary>View changed files</summary> 📝 `docs/web-network-captures.md` (+9 -0) 📝 `src/browser/history/protobuf/ProtobufCapture.ts` (+8 -19) 📝 `src/browser/history/protobuf/ProtobufSchema.ts` (+62 -15) 📝 `src/browser/history/protobuf/ProtobufWire.test.ts` (+106 -9) 📝 `tests/acceptance/tools/protobufCapture.test.ts` (+107 -0) </details> ### 📄 Description > **Status — 2026-10-24: superseded, not merged.** Maintainer commit [b3c3b21e](https://github.com/morluto/rea/commit/b3c3b21e43cab4e71b460d08829d8c6e4e9b9c21) fixed and [closed #6118](https://github.com/morluto/rea/issues/6118#issuecomment-6376018562) on main. The core diagnostic distinction in this draft is therefore already covered by upstream's own admission result model. > > I independently built unmodified main `b5c42dfc2a8eddeffb8d37c669178fa04169f050` with pinned Node 24.22.1/npm 11.16.0. All 9 generated controls passed: valid descriptor, missing selected message and malformed descriptor through the production CLI plus full/compact production stdio MCP. Four retained views remained readable after deleting the generated capture/descriptor inputs; source SHA, original ordinal 0, parent Evidence, field-specific path/reason and safe wire reason were preserved. SDK-converted request/response schemas were checked. This is selected Windows public-adapter evidence, not a complete suite, live provider or whole-platform qualification. > > Closing this draft as superseded instead of resolving conflicts by reintroducing the old implementation. Original head `f415732d` and branch/verification assets are retained. This PR has not been merged; no upstream adoption or co-authorship credit is claimed. No target traffic was replayed and no paid model was called. <details> <summary>Original PR description and historical verification</summary> ## Summary Fixes #6118. Preserve actionable Protobuf schema-admission diagnostics: an undefined selected message points to `protobuf.schema.message_type` (`invalid_value`); malformed or unresolved descriptor definitions point to `protobuf.schema.descriptor_set_path` (`invalid_format`). Both still return `invalid_request` and retain sanitized partial capture Evidence. ## Problem and expected behavior A valid descriptor with `capture.Missing` and corrupt descriptor bytes previously produced the same generic schema error. Callers could not tell whether to correct the selected type or replace the descriptor. Wire preflight also discarded its known byte offset/reason. ## Change and scope `ProtobufSchema.read` now returns the existing typed `Result<ProtobufSchema, AnalysisInputError>` for schema admission. The owning stage identifies the rejected field and retains wire facts or SDK causes internally. `ProtobufCapture` forwards this result, removing its blanket catch/reclassification. SDK exception text is not copied into public issues; shared byte-budget and cancellation failures remain outside SDK catches. An entry checkpoint also honors cancellation for empty descriptors. Within the [existing offline capture scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope); no new provider, target execution or authority requiring a separate maintainer decision. ## Contract and boundary impact - Semantic owner/earliest changed stage: descriptor-wire/SDK registry admission in `ProtobufSchema`, consumed by `ProtobufCapture`. - Scope/maintainer decision: correction within existing schema interpretation; separate decision not applicable. - CLI/MCP/tool-catalog: no new argument, tool or success schema. Both interfaces expose the corrected `details.issues` paths/reasons. Example: `{path:["protobuf","schema","message_type"],reason:"invalid_value"}`. - Provider/bridge/format/platform: existing FileDescriptorSet and HAR workflow; underlying protobuf-es 2.16.0 and framing remain unchanged. - Evidence/artifact/provenance: valid CLI/MCP Evidence IDs remain equal; failures preserve the original capture SHA and retained ordinal 0 in the generated controls. - Target selection/authority/cleanup: selected local files only; no acquisition, network retrieval, replay or cleanup-policy expansion. - Generated metadata/package/install: no dependency, version or installer change. No generated catalogs, binaries or build outputs committed. Expected effects: - [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. The verification harness starts REA's own CLI/MCP subprocesses and writes self-owned fixtures; the feature adds no target-process operation. ## Evidence and regression coverage - Fixed baseline: main `26356dc34a74e38b68eb2acb4befb126176ed978`, package 6.7.0. - Before the production change, the three new CLI/MCP cases selected by test name had one valid case pass and two error-path cases fail on the incorrect issue paths. The other 21 cases were skipped in that selected baseline run, not counted as passed. - After the change, all 24 capture acceptance cases pass through the compiled CLI and production stdio MCP, including valid/missing/malformed descriptor cases, retained views after failure, source identity, byte-budget refusal, credential exclusions and schema round trips. - Producer tests preserve malformed unknown-field rejection with the original byte-16 overflowing-varint cause, SDK decoding/registry failures, empty descriptor versus missing type, leading-dot lookup, registry expansion budget and exact caller cancellation reasons. - [Current-head code CI 39723699187](https://github.com/morluto/rea/actions/runs/39723699187) **passed** for `f415732d`. Source and all eight portable-shard logs executed merge `b22decce070262030bb0368eaf524b878c785ed9` against main `bd5d189a8f8aeea669bcb93e68af6c046b567939`. Raw logs confirm 21 wire/schema, 2 capture, 5 trailer, 13 failure-projection, 24 CLI/production-stdio acceptance and one MCP-contract checks. - Source/static/docs/build, eight portable shards, Windows native artifact build, selected Linux package baseline and controlled browser/web-network lanes passed. These are remote selected-lane results, not a new local rerun or full Windows/provider qualification. - Remaining gaps: no complete local repository suite, external customer capture or downstream-recovery frequency measurement; no local macOS/Linux run or comparative performance benchmark. Generated local controls and controlled CI fixture lanes do not establish customer adoption. Human initial-readiness declarations remain pending. - [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 Windows x64, Node 24.18.0/npm 11.16.0. npm was invoked via the pinned Node/npm-cli entry. - `node scripts/run-development-tests.mjs focused src/browser/history/protobuf/ProtobufWire.test.ts src/browser/history/protobuf/ProtobufCapture.test.ts src/browser/history/protobuf/ProtobufBodyTrailer.test.ts src/browser/history/CaptureFailures.test.ts tests/acceptance/tools/protobufCapture.test.ts tests/boundary/mcp/webNetworkCaptureMcp.test.ts tests/conformance/readmeConsistency.test.ts` — **71 passed, zero skipped**, including 24 production CLI/stdio acceptance cases and SDK-converted schema checks. - `npm run check` — passed typecheck, lint/module, format, metadata and architecture checks. - `npm run docs:check` — generated checks and five fresh consistency controls passed; these repeat the same documentation file rather than add five distinct tests to the 71. - `node scripts/verify-test-discovery.mjs` — all 1,967 test files discovered exactly once. - `node scripts/check-dependency-install.mjs` and `node scripts/verify-windows-native-artifact.mjs` — passed. Official 6.7.0 native artifact from main ancestor `87c8086f` has matching native/build/verification source relative to the frozen baseline; this is component qualification, not full Windows-provider support. ## Compatibility, safety, and release - Breaking changes/migration: valid success behavior and inputs unchanged. Invalid schema requests intentionally receive more specific correction paths/reasons; error code/category and partial-observation behavior remain stable. - Real tool/OS: Windows public CLI and production stdio over generated offline inputs. No Ghidra/Hopper, live browser, capture or request replay. - Package/release metadata: unchanged; no release or deployment. - Privacy/containment: owned wire diagnostics and correction guidance only; raw SDK exception text stays in the internal cause. No unbounded list of available message types, descriptor content or credentials added to public correction messages. - No token, speed, memory or customer-adoption benefit measured or claimed. ## Author readiness Human owner: @wunianze666-netizen AI-assisted implementation and verification. The human owner's initial review declaration remains pending; this PR is a draft. - [ ] 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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved within the existing offline parsing boundary. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs and contracts are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:46:19 +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#7226
No description provided.