morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #4351] [MERGED] fix(captures): scope HAR HTTP interpretation to entries #6195

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4351
Author: @To3akaRin
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: codex/rea-oct16-captures

📝 Commits (10+)

  • 12c6316 fix(captures): scope HAR HTTP interpretation to entries
  • d114dc9 Merge commit '974487f00f' into codex/rea-oct16-captures
  • 6f89888 test(snapshot): preserve Evidence-scoped native workflow unknowns
  • 058be4b Merge commit 'e8da7e1edd' into codex/rea-oct16-captures
  • b686ccc test(process): assert owned snapshot cancellation outcomes
  • 6c6e949 test(process): preserve snapshot race causes and owned cleanup
  • 1ff5013 test(cli): scope runtime cleanup provider injection
  • aa640ad test(artifacts): use valid ASAR bytes for signature control
  • ac46ab4 test(mcp): isolate snapshot filesystem fault injection
  • a62a070 Merge commit 'ba866a26ec' into codex/rea-oct16-captures

📊 Changes

5 files changed (+177 additions, -10 deletions)

View changed files

📝 docs/web-network-captures.md (+4 -0)
📝 src/browser/history/HarCapture.test.ts (+62 -1)
📝 src/browser/history/HarCapture.ts (+9 -8)
📝 tests/boundary/browser/historicalWebCapture.test.ts (+62 -1)
📝 tests/fixtures/historicalHar.ts (+40 -0)

📄 Description

Summary

Keep unknown HAR document fields opaque instead of applying entry-local HTTP interpretation to them.

Problem and expected behavior

A schema-admitted HAR document with a top-level response.content object containing encoding: "base64" and ordinary extension text was rejected as malformed HTTP content. Top-level request and response lookalikes could also lose header, cookie and URL text without an explicit sensitive-value declaration. The same objects nested under another extension key were preserved.

These fields belong to the document container, not log.entries. No matching issue was found after checking open and closed HAR/container/extension reports and related patches.

Change and scope

The existing HAR projection owner now selects an explicit validation, container or entry context. Only entry projection interprets authentication fields, transport URLs and base64 response content. Generic value/property exclusions and numeric sidecars retain their existing behavior in both evidence contexts. Document this ownership boundary.

Contract and boundary impact

  • Semantic owner and earliest changed stage: HarCapture.projectHar, before evidence projection.
  • Contribution scope fit and linked maintainer decision: ordinary offline evidence-correctness fix; no new provider or target authority. Separate scope decision not applicable.
  • CLI and MCP/tool-catalog contract: unchanged input/output schemas; previously rejected opaque fields are retained, and unrelated text is no longer removed.
  • Provider, bridge, target-format, or platform compatibility: existing HAR 1.2 profile and decoder lifecycle; no SAZ/qlog interpretation changes.
  • Evidence, artifact, provenance, or reconstruction contract: preserve original document fields and artifact identity; actual entry authentication exclusions and binary sidecars remain intact. Reinspect affected inputs to obtain corrected Evidence; historical Evidence is not rewritten.
  • Target selection, authority, upstream behavior, and cleanup details: existing selected-file read and bounded offline decoder process; no target requests or source-file mutation.
  • Generated metadata, package, or installation impact: none.

Expected effects:

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

Evidence and regression coverage

  • Base 42fc6c53: new source regression failed with HAR content declares base64 but its text is not valid canonical base64; the compiled CLI returned invalid_request at capture_path /response/content/text. Existing source/public tests passed in those runs.
  • Source controls distinguish container and entry handling of Authorization, cookies, URL userinfo and base64. Explicit sensitive text remains excluded in both contexts; an explicitly sensitive decoded body does not cause an opaque container string to be decoded or removed.
  • Compiled CLI and real stdio MCP produce identical Evidence for marked/unmarked inputs. The container retains its opaque text; actual entry credentials remain null and actual QUJD content retains its three-byte sidecar. Input bytes remain unchanged.
  • Synthetic HAR files exercise the real local decoder and public transports. No live-browser capture or exporter provenance is claimed.

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.

Current branch validation

The branch was reconciled with current main while preserving this PR's feature-specific patch; unrelated shared CI repairs have been superseded by upstream and are no longer part of the current diff. See the reconciliation and local verification report.

Remote CI required passed on head 1dc55ffd. The PR readiness status also passed at the last readback. Earlier feature checks below remain historical evidence for their stated revisions.

Earlier feature validation

Node.js 24.18.0, npm 11.16.0, macOS arm64:

  • npm run test:focused -- src/browser/history/HarCapture.test.ts src/browser/history/QlogCapture.test.ts src/application/WebNetworkCaptureService.test.ts tests/boundary/browser/historicalWebCapture.test.ts tests/boundary/mcp/webNetworkCaptureMcp.test.ts — 5 files, 129 tests passed.
  • npm run test:local -- src/browser/history/HarCapture.test.ts after the additional decoded-literal control — 63 tests passed.
  • npm run check — passed, including typecheck, format, lint and architecture guards.
  • npm run docs:check — passed.
  • npm run verify:test-discovery — all 1,400 test files discovered exactly once.
  • npm run jscpd — passed; 3.23% duplicated lines against the checked-in 3.5% threshold.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; affected captures can be reinspected for corrected Evidence.
  • Real Hopper/Ghidra, browser, or OS coverage: offline HAR decoder and public CLI/stdio MCP on macOS; no live browser or external native engine.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: actual HAR entry authentication exclusion and explicit sensitive-value handling remain covered. No new execution, network or mutation authority. Existing traversal and resource budgets remain; no performance improvement claim or process-family memory measurement.

Author readiness

Human owner: @To3akaRin

  • 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/4351 **Author:** [@To3akaRin](https://github.com/To3akaRin) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/rea-oct16-captures` --- ### 📝 Commits (10+) - [`12c6316`](https://github.com/morluto/rea/commit/12c6316e091cdf2dcee1d735f73a96d268b093bc) fix(captures): scope HAR HTTP interpretation to entries - [`d114dc9`](https://github.com/morluto/rea/commit/d114dc946c6c3f9cb505f168d68e7fcb4e611642) Merge commit '974487f00f2d68912c7c2c9e033a2760a343a82e' into codex/rea-oct16-captures - [`6f89888`](https://github.com/morluto/rea/commit/6f8988823710d5888d2497e1d390e2d24f24ed62) test(snapshot): preserve Evidence-scoped native workflow unknowns - [`058be4b`](https://github.com/morluto/rea/commit/058be4b76513e7e89b77e0a0e29a34f902c1ce71) Merge commit 'e8da7e1edd075feec0e6beedec93d5645fed8125' into codex/rea-oct16-captures - [`b686ccc`](https://github.com/morluto/rea/commit/b686ccc93320b235d110476fb7d4f0d2edbe1038) test(process): assert owned snapshot cancellation outcomes - [`6c6e949`](https://github.com/morluto/rea/commit/6c6e94949a129d23a0feb01f47f490370590d280) test(process): preserve snapshot race causes and owned cleanup - [`1ff5013`](https://github.com/morluto/rea/commit/1ff50134db510a221a4f1543dd9c4bc98546264a) test(cli): scope runtime cleanup provider injection - [`aa640ad`](https://github.com/morluto/rea/commit/aa640ada742809c1e999befd7d1e9c3a65d603f1) test(artifacts): use valid ASAR bytes for signature control - [`ac46ab4`](https://github.com/morluto/rea/commit/ac46ab4d3e2af791150a12d75b05b99fdd891a74) test(mcp): isolate snapshot filesystem fault injection - [`a62a070`](https://github.com/morluto/rea/commit/a62a0704713a7dbc21f11abcd439efcd185c357e) Merge commit 'ba866a26ecbe179a717e746cbc0d1605ae616ad5' into codex/rea-oct16-captures ### 📊 Changes **5 files changed** (+177 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `docs/web-network-captures.md` (+4 -0) 📝 `src/browser/history/HarCapture.test.ts` (+62 -1) 📝 `src/browser/history/HarCapture.ts` (+9 -8) 📝 `tests/boundary/browser/historicalWebCapture.test.ts` (+62 -1) 📝 `tests/fixtures/historicalHar.ts` (+40 -0) </details> ### 📄 Description ## Summary Keep unknown HAR document fields opaque instead of applying entry-local HTTP interpretation to them. ## Problem and expected behavior A schema-admitted HAR document with a top-level `response.content` object containing `encoding: "base64"` and ordinary extension text was rejected as malformed HTTP content. Top-level `request` and `response` lookalikes could also lose header, cookie and URL text without an explicit sensitive-value declaration. The same objects nested under another extension key were preserved. These fields belong to the document container, not `log.entries`. No matching issue was found after checking open and closed HAR/container/extension reports and related patches. ## Change and scope The existing HAR projection owner now selects an explicit validation, container or entry context. Only entry projection interprets authentication fields, transport URLs and base64 response content. Generic value/property exclusions and numeric sidecars retain their existing behavior in both evidence contexts. Document this ownership boundary. ## Contract and boundary impact - Semantic owner and earliest changed stage: `HarCapture.projectHar`, before evidence projection. - Contribution scope fit and linked maintainer decision: ordinary offline evidence-correctness fix; no new provider or target authority. Separate scope decision not applicable. - CLI and MCP/tool-catalog contract: unchanged input/output schemas; previously rejected opaque fields are retained, and unrelated text is no longer removed. - Provider, bridge, target-format, or platform compatibility: existing HAR 1.2 profile and decoder lifecycle; no SAZ/qlog interpretation changes. - Evidence, artifact, provenance, or reconstruction contract: preserve original document fields and artifact identity; actual entry authentication exclusions and binary sidecars remain intact. Reinspect affected inputs to obtain corrected Evidence; historical Evidence is not rewritten. - Target selection, authority, upstream behavior, and cleanup details: existing selected-file read and bounded offline decoder process; no target requests or source-file mutation. - Generated metadata, package, or installation impact: none. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. Existing isolated offline decoder only. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Base `42fc6c53`: new source regression failed with `HAR content declares base64 but its text is not valid canonical base64`; the compiled CLI returned `invalid_request` at `capture_path /response/content/text`. Existing source/public tests passed in those runs. - Source controls distinguish container and entry handling of Authorization, cookies, URL userinfo and base64. Explicit sensitive text remains excluded in both contexts; an explicitly sensitive decoded body does not cause an opaque container string to be decoded or removed. - Compiled CLI and real stdio MCP produce identical Evidence for marked/unmarked inputs. The container retains its opaque text; actual entry credentials remain null and actual `QUJD` content retains its three-byte sidecar. Input bytes remain unchanged. - Synthetic HAR files exercise the real local decoder and public transports. No live-browser capture or exporter provenance is claimed. 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. ## Current branch validation The branch was reconciled with current main while preserving this PR's feature-specific patch; unrelated shared CI repairs have been superseded by upstream and are no longer part of the current diff. See the [reconciliation and local verification report](https://github.com/morluto/rea/pull/4351#issuecomment-6307225917). Remote [CI required](https://github.com/morluto/rea/actions/runs/39538189321/job/119023225834) passed on head `1dc55ffd`. The PR readiness status also passed at the last readback. Earlier feature checks below remain historical evidence for their stated revisions. ## Earlier feature validation Node.js 24.18.0, npm 11.16.0, macOS arm64: - `npm run test:focused -- src/browser/history/HarCapture.test.ts src/browser/history/QlogCapture.test.ts src/application/WebNetworkCaptureService.test.ts tests/boundary/browser/historicalWebCapture.test.ts tests/boundary/mcp/webNetworkCaptureMcp.test.ts` — 5 files, 129 tests passed. - `npm run test:local -- src/browser/history/HarCapture.test.ts` after the additional decoded-literal control — 63 tests passed. - `npm run check` — passed, including typecheck, format, lint and architecture guards. - `npm run docs:check` — passed. - `npm run verify:test-discovery` — all 1,400 test files discovered exactly once. - `npm run jscpd` — passed; 3.23% duplicated lines against the checked-in 3.5% threshold. ## Compatibility, safety, and release - Breaking changes or migration steps: none; affected captures can be reinspected for corrected Evidence. - Real Hopper/Ghidra, browser, or OS coverage: offline HAR decoder and public CLI/stdio MCP on macOS; no live browser or external native engine. - Package or release metadata impact: none. - Security, privacy, process, or containment review: actual HAR entry authentication exclusion and explicit sensitive-value handling remain covered. No new execution, network or mutation authority. Existing traversal and resource budgets remain; no performance improvement claim or process-family memory measurement. ## Author readiness Human owner: @To3akaRin - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:12:35 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/procedure-reference-stacked
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#6195
No description provided.