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 #5453] [MERGED] fix(browser): read SAZ archives with zero-byte HTTP members #6930

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5453
Author: @amyanger
Created: 10/20/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @morluto

Base: main ← Head: fix/5411-empty-saz-member

📝 Commits (1)

  • 4f17b4f fix(browser): read SAZ archives with zero-byte HTTP members

📊 Changes

4 files changed (+62 additions, -13 deletions)

View changed files

📝 docs/web-network-captures.md (+2 -0)
📝 src/browser/history/NodeCaptureAdapter.ts (+1 -1)
📝 src/browser/history/SazCapture.ts (+19 -12)
📝 tests/boundary/browser/sazWebCapture.test.ts (+40 -0)

📄 Description

Summary

Fixes #5411.

Fiddler writes a zero-byte raw/NN_s.txt (or _c.txt) when a session never got that message. inspect_web_network_capture passed those bytes to the HTTP decoder, which threw "SAZ HTTP message has no header/body separator", so the whole archive was rejected and no session could be read, even with --record. A zero-byte HTTP member is now reported like a missing one: the request or response is null, the member stays in location.members, and the record carries a limitation saying the stored member was empty. The SAZ capture-level limitation now says absent and zero-byte HTTP members are null.

Problem and expected behavior

Smallest trigger: a SAZ archive with one valid raw/1_c.txt and a zero-byte raw/1_s.txt. On base the CLI returns invalid_request / invalid_format for the whole archive. The documented contract already says "Missing members remain null, distinct from empty bodies", and a missing _s.txt already works. A zero-byte member has no start line, so it is not an HTTP message with an empty body; it is the absence of a recorded message.

Change and scope

decodeSazCapture in src/browser/history/SazCapture.ts owns the meaning of each archive member, so the fix lives there. When a _c.txt or _s.txt member is zero bytes, the decoder leaves request or response as null and adds a per-record limitation. The limitation states only that the stored member is empty. It does not claim the server never answered, because a zero-byte member could also come from an interrupted write. NodeCaptureAdapter.ts updates the SAZ capture-level limitation to match. decodeSazHttp is unchanged, so a non-empty member without a header/body separator is still rejected as malformed. The declared-size and stream-length checks still run before this branch. Empty _w.txt and _g.txt members were already accepted as zero-length opaque bytes and are unchanged.

Precedent: HAR (HarCapture.ts) and qlog (QlogCapture.ts) already report fixed per-record limitation sentences. The limitation text does not name the member path, so it cannot bypass the coordinate exclusion that applies when a member path contains an explicitly sensitive literal. Record limitations also pass through the service's redactText.

Not included: an empty _m.xml still rejects the archive through decodeSazMetadata. The issue does not cover it and I have not seen one from a real producer. The experiment note experiments/analysis-efficiency/saz-selection-workflows.md records the old failure as a baseline observation and is left as historical record.

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".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: SAZ archive member decoding in src/browser/history/SazCapture.ts.
  • Contribution scope fit and linked maintainer decision: not applicable, a decoding fix within the existing capture boundary.
  • CLI and MCP/tool-catalog contract: no schema change. Archives that were rejected now return records; record limitations is an existing string[].
  • Provider, bridge, target-format, or platform compatibility: SAZ only. Other capture formats are untouched.
  • Evidence, artifact, provenance, or reconstruction contract: archives that already decoded produce identical output. Only previously rejected archives gain output.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • 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. docs/web-network-captures.md gains one sentence.

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: tests/boundary/browser/sazWebCapture.test.ts, "reports zero-byte SAZ HTTP members as null instead of rejecting the archive". It runs the public CLI on a synthetic archive with an empty _s.txt in one session, an empty _c.txt and an empty _w.txt in another, then checks null request/response, retained members, the exact limitations, that the empty WebSocket member stays retained without a limitation, and --record 0 selection.
  • Base reproduction or other evidence (executed): the final test file run against base aa314ab68 fails only the new test, with the issue's error: {"code":"invalid_request",...,"issues":[{"path":["capture_path",""],"reason":"invalid_format","message":"SAZ HTTP message has no header/body separator."}]}. Result: 1 failed, 16 passed, 1 skipped.
  • Mutation check (executed on the final diff, each mutant rebuilt and run against the SAZ boundary file in a separate worktree): disabling the zero-length branch, dropping the limitation, inverting the request flag passed to decodeSazHttp, not recognizing _c.txt, widening the HTTP-only branch to _w.txt, and emitting limitations: []. All 6 mutants fail at least one test. The capture-level limitation sentence is static text with no test asserting it, before or after this change.
  • User-visible CLI/MCP output (executed, real archive): x49_mp_cs21.saz from Microsoft's Xbox Live Trace Analyzer at ad880ff0, sha256 97cdca8b…7f6, as pinned in experiments/analysis-efficiency/corpus.json.
    • Base: rea inspect-web-network-capture x49_mp_cs21.saz saz --json returns the invalid_format error above.
    • Branch: exit 0, 103 of 103 records. Only ordinal 98 (session 099) carries a limitation: members raw/099_c.txt, raw/099_m.xml, raw/099_s.txt, request method POST, response: null, limitation "The stored response member is empty (zero bytes); the response is reported as null.". --record 99 --record 0 also exits 0.
  • Adversarial review (read-only agent): no consumer breakage found. It checked the record schema, redactText on record limitations, coordinate exclusion, route-template and environment-manifest handling of null request/response, protobuf pointer checks, duplicate and case-variant members, and the size checks. Its two notes, the empty _m.xml case and the historical experiment note, are covered under scope above.
  • Remaining proof gaps: the MCP path was not exercised separately for this case. It shares WebNetworkCaptureService with the CLI, and existing tests cover CLI and MCP equality for SAZ.

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

All on Node from .nvmrc, macOS arm64, base aa314ab682e4bcd1e050a1e073bc90930660807f.

  • npm run test:focused -- tests/boundary/browser/sazWebCapture.test.ts tests/evaluation/sazWorkflowSemantics.test.ts src/browser/history/SazMetadata.test.ts src/browser/history/NodeCaptureAdapter.test.ts src/domain/webNetworkCapture.test.ts src/domain/analysisView/webNetworkCaptureView.test.ts: 6 files passed, 93 passed, 1 skipped
  • npm run check:fast: passed
  • npm run test:changed -- --base aa314ab68…: 2 passed. It selects only source-level tests; the boundary file above covers the decoder.
  • npm run check: passed
  • npm run docs:check: passed
  • /code-review high on the uncommitted diff: 7 findings, each checked by hand.
    • Fixed: the SAZ capture-level limitation still said only absent members are null.
    • Fixed: the per-record limitation claimed "no response was recorded", which a zero-byte member does not prove. It now states only that the member is empty.
    • Fixed: the _c/_s suffix checks were repeated in two chains. They are now one branch.
    • Not changed: an empty _m.xml still rejects the archive. It is outside this issue, and the real archive's empty session has a non-empty _m.xml.
    • Not changed: no structured "empty" flag in reported. location.members already shows the member exists, and adding a field would change the reported schema.
    • Not changed: limitation order follows ZIP member order. Record ordinals already follow ZIP order, so this matches the existing contract.
    • Not changed: no extra test for a session where both HTTP members are empty. That path uses the same branch twice, and the mutants above are already killed.

The skipped test is "reports SAZ unavailable when its runtime cannot enforce decoder memory", which is gated on runtimes without a memory bound and skips on base as well.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Previously rejected archives now decode.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; SAZ decoding is local file parsing. Exercised on a real Fiddler v4.6 archive as above.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the limitation text is fixed and names no path or value. Sensitive-literal exclusion of member coordinates is unchanged.

Author readiness

Human owner: @amyanger

  • 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/5453 **Author:** [@amyanger](https://github.com/amyanger) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/5411-empty-saz-member` --- ### 📝 Commits (1) - [`4f17b4f`](https://github.com/morluto/rea/commit/4f17b4f8a5f5fb8ebafa293368bcaf69d3a30b4f) fix(browser): read SAZ archives with zero-byte HTTP members ### 📊 Changes **4 files changed** (+62 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `docs/web-network-captures.md` (+2 -0) 📝 `src/browser/history/NodeCaptureAdapter.ts` (+1 -1) 📝 `src/browser/history/SazCapture.ts` (+19 -12) 📝 `tests/boundary/browser/sazWebCapture.test.ts` (+40 -0) </details> ### 📄 Description ## Summary Fixes #5411. Fiddler writes a zero-byte `raw/NN_s.txt` (or `_c.txt`) when a session never got that message. `inspect_web_network_capture` passed those bytes to the HTTP decoder, which threw "SAZ HTTP message has no header/body separator", so the whole archive was rejected and no session could be read, even with `--record`. A zero-byte HTTP member is now reported like a missing one: the request or response is `null`, the member stays in `location.members`, and the record carries a limitation saying the stored member was empty. The SAZ capture-level limitation now says absent and zero-byte HTTP members are null. ## Problem and expected behavior Smallest trigger: a SAZ archive with one valid `raw/1_c.txt` and a zero-byte `raw/1_s.txt`. On base the CLI returns `invalid_request` / `invalid_format` for the whole archive. The documented contract already says "Missing members remain null, distinct from empty bodies", and a missing `_s.txt` already works. A zero-byte member has no start line, so it is not an HTTP message with an empty body; it is the absence of a recorded message. ## Change and scope `decodeSazCapture` in `src/browser/history/SazCapture.ts` owns the meaning of each archive member, so the fix lives there. When a `_c.txt` or `_s.txt` member is zero bytes, the decoder leaves `request` or `response` as `null` and adds a per-record limitation. The limitation states only that the stored member is empty. It does not claim the server never answered, because a zero-byte member could also come from an interrupted write. `NodeCaptureAdapter.ts` updates the SAZ capture-level limitation to match. `decodeSazHttp` is unchanged, so a non-empty member without a header/body separator is still rejected as malformed. The declared-size and stream-length checks still run before this branch. Empty `_w.txt` and `_g.txt` members were already accepted as zero-length opaque bytes and are unchanged. Precedent: HAR (`HarCapture.ts`) and qlog (`QlogCapture.ts`) already report fixed per-record limitation sentences. The limitation text does not name the member path, so it cannot bypass the coordinate exclusion that applies when a member path contains an explicitly sensitive literal. Record limitations also pass through the service's `redactText`. Not included: an empty `_m.xml` still rejects the archive through `decodeSazMetadata`. The issue does not cover it and I have not seen one from a real producer. The experiment note `experiments/analysis-efficiency/saz-selection-workflows.md` records the old failure as a baseline observation and is left as historical record. 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". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: SAZ archive member decoding in `src/browser/history/SazCapture.ts`. - Contribution scope fit and linked maintainer decision: not applicable, a decoding fix within the existing capture boundary. - CLI and MCP/tool-catalog contract: no schema change. Archives that were rejected now return records; record `limitations` is an existing `string[]`. - Provider, bridge, target-format, or platform compatibility: SAZ only. Other capture formats are untouched. - Evidence, artifact, provenance, or reconstruction contract: archives that already decoded produce identical output. Only previously rejected archives gain output. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - 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. `docs/web-network-captures.md` gains one sentence. 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: `tests/boundary/browser/sazWebCapture.test.ts`, "reports zero-byte SAZ HTTP members as null instead of rejecting the archive". It runs the public CLI on a synthetic archive with an empty `_s.txt` in one session, an empty `_c.txt` and an empty `_w.txt` in another, then checks null request/response, retained members, the exact limitations, that the empty WebSocket member stays retained without a limitation, and `--record 0` selection. - Base reproduction or other evidence (executed): the final test file run against base `aa314ab68` fails only the new test, with the issue's error: `{"code":"invalid_request",...,"issues":[{"path":["capture_path",""],"reason":"invalid_format","message":"SAZ HTTP message has no header/body separator."}]}`. Result: 1 failed, 16 passed, 1 skipped. - Mutation check (executed on the final diff, each mutant rebuilt and run against the SAZ boundary file in a separate worktree): disabling the zero-length branch, dropping the limitation, inverting the request flag passed to `decodeSazHttp`, not recognizing `_c.txt`, widening the HTTP-only branch to `_w.txt`, and emitting `limitations: []`. All 6 mutants fail at least one test. The capture-level limitation sentence is static text with no test asserting it, before or after this change. - User-visible CLI/MCP output (executed, real archive): `x49_mp_cs21.saz` from Microsoft's Xbox Live Trace Analyzer at `ad880ff0`, sha256 `97cdca8b…7f6`, as pinned in `experiments/analysis-efficiency/corpus.json`. - Base: `rea inspect-web-network-capture x49_mp_cs21.saz saz --json` returns the `invalid_format` error above. - Branch: exit 0, 103 of 103 records. Only ordinal 98 (session `099`) carries a limitation: members `raw/099_c.txt`, `raw/099_m.xml`, `raw/099_s.txt`, request method `POST`, `response: null`, limitation `"The stored response member is empty (zero bytes); the response is reported as null."`. `--record 99 --record 0` also exits 0. - Adversarial review (read-only agent): no consumer breakage found. It checked the record schema, `redactText` on record limitations, coordinate exclusion, route-template and environment-manifest handling of null request/response, protobuf pointer checks, duplicate and case-variant members, and the size checks. Its two notes, the empty `_m.xml` case and the historical experiment note, are covered under scope above. - Remaining proof gaps: the MCP path was not exercised separately for this case. It shares `WebNetworkCaptureService` with the CLI, and existing tests cover CLI and MCP equality for SAZ. 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 All on Node from `.nvmrc`, macOS arm64, base `aa314ab682e4bcd1e050a1e073bc90930660807f`. - `npm run test:focused -- tests/boundary/browser/sazWebCapture.test.ts tests/evaluation/sazWorkflowSemantics.test.ts src/browser/history/SazMetadata.test.ts src/browser/history/NodeCaptureAdapter.test.ts src/domain/webNetworkCapture.test.ts src/domain/analysisView/webNetworkCaptureView.test.ts`: 6 files passed, 93 passed, 1 skipped - `npm run check:fast`: passed - `npm run test:changed -- --base aa314ab68…`: 2 passed. It selects only source-level tests; the boundary file above covers the decoder. - `npm run check`: passed - `npm run docs:check`: passed - `/code-review high` on the uncommitted diff: 7 findings, each checked by hand. - Fixed: the SAZ capture-level limitation still said only absent members are null. - Fixed: the per-record limitation claimed "no response was recorded", which a zero-byte member does not prove. It now states only that the member is empty. - Fixed: the `_c`/`_s` suffix checks were repeated in two chains. They are now one branch. - Not changed: an empty `_m.xml` still rejects the archive. It is outside this issue, and the real archive's empty session has a non-empty `_m.xml`. - Not changed: no structured "empty" flag in `reported`. `location.members` already shows the member exists, and adding a field would change the reported schema. - Not changed: limitation order follows ZIP member order. Record ordinals already follow ZIP order, so this matches the existing contract. - Not changed: no extra test for a session where both HTTP members are empty. That path uses the same branch twice, and the mutants above are already killed. The skipped test is "reports SAZ unavailable when its runtime cannot enforce decoder memory", which is gated on runtimes without a memory bound and skips on base as well. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Previously rejected archives now decode. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; SAZ decoding is local file parsing. Exercised on a real Fiddler v4.6 archive as above. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the limitation text is fixed and names no path or value. Sensitive-literal exclusion of member coordinates is unchanged. ## Author readiness Human owner: @amyanger - [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-11-01 21:44: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#6930
No description provided.