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 #4040] [MERGED] fix(browser): preserve frame identity across captures #6013

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4040
Author: @eco-null
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/23/2026
Merged by: @morluto

Base: main ← Head: codex/browser-evidence-fidelity

📝 Commits (10+)

  • a466628 fix(browser): preserve capture evidence fidelity
  • 33f048a fix(browser): align frame identity comparisons
  • 0e338dd chore(browser): resolve current main integration
  • 390046a fix(browser): retain historical frame evidence
  • 0d2a81b fix(electron): retain same-document script owners
  • ad2973f chore(browser): sync current main
  • d288065 chore(browser): integrate DOM admission updates
  • 1dcd7b1 fix(electron): bind frame proof to tree reads
  • 7801dae chore(browser): merge current main
  • cd66811 fix(browser): preserve frame identity proof

📊 Changes

21 files changed (+3961 additions, -171 deletions)

View changed files

📝 docs/electron-observation.md (+4 -1)
📝 src/browser/CdpAuthorizedMainFrame.ts (+12 -8)
📝 src/browser/CdpCaptureDocuments.test.ts (+130 -0)
📝 src/browser/CdpCaptureDocuments.ts (+86 -12)
📝 src/browser/CdpElectronInspection.test.ts (+567 -4)
📝 src/browser/CdpElectronInspection.ts (+395 -32)
📝 src/browser/CdpElectronScripts.ts (+2 -5)
📝 src/browser/CdpObservationSession.ts (+44 -20)
📝 src/browser/CdpScreenshot.ts (+55 -17)
📝 src/browser/CdpWebMcpDiscovery.ts (+81 -51)
📝 src/browser/execution/CdpRuntimeProtocol.ts (+1 -2)
📝 src/browser/execution/CdpRuntimeSession.ts (+44 -14)
➕ tests/boundary/browser/cdpAuthorizedMainFrameRetry.test.ts (+204 -0)
📝 tests/boundary/browser/cdpBrowserProvider.document_script.test.ts (+409 -5)
📝 tests/boundary/browser/cdpBrowserProvider.timelineEvents.test.ts (+298 -0)
📝 tests/boundary/browser/cdpElectronProvider.test.ts (+941 -0)
➕ tests/boundary/browser/cdpRuntimeFrameIdentity.test.ts (+168 -0)
📝 tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts (+148 -0)
➕ tests/boundary/browser/cdpWebMcpTransientIdentity.test.ts (+204 -0)
📝 tests/boundary/mcp/browserMcp.test.ts (+87 -0)

...and 1 more files

📄 Description

Summary

Preserve frame identity and lifecycle evidence across browser/Electron captures. Fixes #3878, fixes #3941, fixes #3910.

Problem and expected behavior

CDP splits base URL and fragment, while capture lifecycle can advance between reads. A single parsed identity/scope owner now feeds authorization, runtime, timeline, screenshot and WebMCP consumers. Electron uses a structurally valid ancestry graph separately from per-file admission and binds scripts to authorized frame generations.

Change and scope

Tree snapshots separate stable loader/parent document identity from URL observations. A URL-only child history/hash update retains generation authority; a changed loader/parent uses the shared descendant-generation invalidation. Explicit full-navigation event replay still requires matching observed URL, preserving unknown-frame controls. A tree-observed same-file reload cannot erase the previous loader identity and hide a delayed navigation event; main replacement returns target_changed, while child replacement retains historical proof and leaves newly unverified script attribution unknown.

One coupled outcome: preserve document identity and authorization across capture lifecycle. Integrated main 0b17cb621, including ASAR header admission and runtime setup/cleanup. No new target authority.

Independent fixes removed from this diff: PNG #6412 (merged); omitted-response accounting #6413 (merged). Offline HAR availability and dropped-WebMCP comparison are validated independent branches; GitHub rejected their PR creation with CreatePullRequest permission errors. Prepared comparisons: offline HAR and WebMCP comparison.

Restored prior runtime error precedence: frame/loader or no-loader URL changes return target_changed before origin rejection. Same-document origin rejection retains the original detail text; regressions pin both behaviors. Superseded AST-only regressions were removed; upstream fixes are not claimed here.

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: CdpCaptureDocuments parsed identity/scope and Electron inventory/generation producers.
  • Contribution scope fit and linked maintainer decision: Ordinary fix within existing boundaries; new maintainer scope decision not applicable.
  • CLI and MCP/tool-catalog contract: Existing interfaces and schemas retained; observable correction described above.
  • Provider, bridge, target-format, or platform compatibility: Owner, provider and public CLI/MCP fixture regressions, including ancestry, malformed identity, origin policy, document replacement and cleanup.
  • Evidence, artifact, provenance, or reconstruction contract: Incomplete or rejected observations remain explicit; source evidence is retained.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Existing selection and authority unchanged.
  • 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): No build outputs committed; catalogs regenerated by normal checks.

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: Owner, provider and public CLI/MCP fixture regressions, including ancestry, malformed identity, origin policy, document replacement and cleanup.
  • Base reproduction or other evidence: The existing identity/lifecycle regressions retain prior red/green evidence in this PR history. This revision adds changed-origin/frame precedence and detail assertions; no fresh complete pre-fix replay was performed.
  • User-visible CLI/MCP output (if applicable): Compiled CLI and MCP retain the same reconstructed full URL including fragment; screenshot/runtime evidence matches it. Failed identity and scope remain explicit.
  • Remaining proof gaps: No real Chromium/Electron/live WebMCP replay, full suite or cross-platform run on this head. Historical engine runs do not establish current-head hosted CI.

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

  • Current conflict-resolution head 1b579209dc7c5cc7ac68824381c486b8fe6bb45a merges main 45a411e8f8314b844bc20aef57afb59991c4a637. Retained both frame-identity and upstream cleanup-failure MCP tests; reused the shared imports. No additional production edits.
  • macOS, Node 24.22.1/npm 11.16.0: npm ci --no-audit --no-fund, npm run check, normal pre-commit and pre-push (check:fast) passed. npm run test:focused -- src/browser/CdpCaptureDocuments.test.ts src/browser/CdpElectronInspection.test.ts tests/boundary/browser/cdpAuthorizedMainFrameRetry.test.ts tests/boundary/browser/cdpBrowserProvider.document_script.test.ts tests/boundary/browser/cdpBrowserProvider.timelineEvents.test.ts tests/boundary/browser/cdpElectronProvider.test.ts tests/boundary/browser/cdpRuntimeFrameIdentity.test.ts tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts tests/boundary/browser/cdpWebMcpTransientIdentity.test.ts tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/webRuntimeMcp.test.ts: full rerun passed 429 tests in 11 files (18.54s). Initial run passed 428/429: the screenshot root-replacement test returned target_changed instead of target_not_allowed; its isolated rerun passed 62/62, then the complete selection passed. The screenshot implementation, test, and fixture were unchanged by this merge; intermittent event-order behavior remains unmodified.
  • Current-head limitations: no real Chromium/Electron/live WebMCP, full suite, cross-platform, or fresh docs check run. Hosted CI is pending; CI results listed below refer to earlier heads.
  • Merged main 6dff37594c0bc942c9748b34a7a028d223e88a6d after #6412/#6413 landed. One conflict in screenshot identity tests: retained both upstream PNG tests/CRC fixtures and this PR's frame-identity tests. Other147 upstream-only files match main exactly; no PNG/network production change remains in this PR diff.
  • npm run test:focused -- src/browser/CdpCaptureDocuments.test.ts src/browser/CdpElectronInspection.test.ts tests/boundary/browser/cdpElectronProvider.test.ts tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/webRuntimeMcp.test.ts: 223 passed in6 files (42.18s), including compiled CLI/MCP checks, Electron reload/same-document and strict PNG capture regressions.
  • Full npm run check (6tasks15.123s plus architecture guards), npm run docs:check (9 README tests), normal pre-push (4.313s) passed. Merge commit tree matches the read-only-validated staged tree; mutating pre-commit fixes were not applied to unrelated upstream files. Windows, pinned Node24.18.0/npm11.16.0.
  • Earlier owner failure-first matrices (6red/23controls reload;5red/31controls URL-only),121pass/2Windows POSIX skips and real-engine runs are historical parent proof. No real Electron/Chromium/liveWebMCP/fullsuite/crossplatform local rerun on this merge head. Hosted CI for exact merge head 346093f9da86c4ea98ae289f1ccce42ab8a1554e completed successfully: CI39905535992, CI required SUCCESS, real-browser job SUCCESS. No specific real Electron/liveWebMCP replay or skipped-lane execution is claimed.
  • Parent 0a0e608c726c2eada431527fd11da15f605c0896 completed CI39869520659, including CI required and real-browser jobSUCCESS. That is not new merge-head CI proof.

Compatibility, safety, and release

  • Breaking changes or migration steps: No schema migration; previously misclassified observations are corrected.
  • Real Hopper/Ghidra, browser, or OS coverage: No real Chromium/Electron/live WebMCP replay, full suite or cross-platform run on this head. Historical engine runs do not establish current-head hosted CI.
  • Package or release metadata impact: No dependency or release version change.
  • Security, privacy, process, or containment review: No expanded target authority; no bypass of workflow approval.

Author readiness

Human owner: @eco-null

  • 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/4040 **Author:** [@eco-null](https://github.com/eco-null) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/23/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/browser-evidence-fidelity` --- ### 📝 Commits (10+) - [`a466628`](https://github.com/morluto/rea/commit/a4666281f6569826382ed759dd1e38a6e2372d62) fix(browser): preserve capture evidence fidelity - [`33f048a`](https://github.com/morluto/rea/commit/33f048a2c218dd0c35442c968db46f25af9d20d6) fix(browser): align frame identity comparisons - [`0e338dd`](https://github.com/morluto/rea/commit/0e338dd2e0f9c0d8cf4a042695b3fb3c17853831) chore(browser): resolve current main integration - [`390046a`](https://github.com/morluto/rea/commit/390046a75c136ab8bd54d368256e3a991d1d9a56) fix(browser): retain historical frame evidence - [`0d2a81b`](https://github.com/morluto/rea/commit/0d2a81b1498e689cafa3a254d77fa1b5b5f518d0) fix(electron): retain same-document script owners - [`ad2973f`](https://github.com/morluto/rea/commit/ad2973f5e0642e8f8914abfbb27428c630dcbc13) chore(browser): sync current main - [`d288065`](https://github.com/morluto/rea/commit/d288065f5f95dadb7988ea576660b9b601cb3853) chore(browser): integrate DOM admission updates - [`1dcd7b1`](https://github.com/morluto/rea/commit/1dcd7b1bd56a437e9239925be5b621f7c72fa5f0) fix(electron): bind frame proof to tree reads - [`7801dae`](https://github.com/morluto/rea/commit/7801daec3b9429eb8ca9708dcee339cb714c9ce0) chore(browser): merge current main - [`cd66811`](https://github.com/morluto/rea/commit/cd66811ac07843ccb530df489c2daca1080dace8) fix(browser): preserve frame identity proof ### 📊 Changes **21 files changed** (+3961 additions, -171 deletions) <details> <summary>View changed files</summary> 📝 `docs/electron-observation.md` (+4 -1) 📝 `src/browser/CdpAuthorizedMainFrame.ts` (+12 -8) 📝 `src/browser/CdpCaptureDocuments.test.ts` (+130 -0) 📝 `src/browser/CdpCaptureDocuments.ts` (+86 -12) 📝 `src/browser/CdpElectronInspection.test.ts` (+567 -4) 📝 `src/browser/CdpElectronInspection.ts` (+395 -32) 📝 `src/browser/CdpElectronScripts.ts` (+2 -5) 📝 `src/browser/CdpObservationSession.ts` (+44 -20) 📝 `src/browser/CdpScreenshot.ts` (+55 -17) 📝 `src/browser/CdpWebMcpDiscovery.ts` (+81 -51) 📝 `src/browser/execution/CdpRuntimeProtocol.ts` (+1 -2) 📝 `src/browser/execution/CdpRuntimeSession.ts` (+44 -14) ➕ `tests/boundary/browser/cdpAuthorizedMainFrameRetry.test.ts` (+204 -0) 📝 `tests/boundary/browser/cdpBrowserProvider.document_script.test.ts` (+409 -5) 📝 `tests/boundary/browser/cdpBrowserProvider.timelineEvents.test.ts` (+298 -0) 📝 `tests/boundary/browser/cdpElectronProvider.test.ts` (+941 -0) ➕ `tests/boundary/browser/cdpRuntimeFrameIdentity.test.ts` (+168 -0) 📝 `tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts` (+148 -0) ➕ `tests/boundary/browser/cdpWebMcpTransientIdentity.test.ts` (+204 -0) 📝 `tests/boundary/mcp/browserMcp.test.ts` (+87 -0) _...and 1 more files_ </details> ### 📄 Description <!-- PR title: type(optional-scope): imperative outcome The title becomes the squash-merge commit subject and generated changelog entry. --> ## Summary Preserve frame identity and lifecycle evidence across browser/Electron captures. Fixes #3878, fixes #3941, fixes #3910. <!-- What user, agent, or maintainer problem does this solve? Link the issue with "Fixes #123" when applicable. Keep the prior behavior, expected contract, and new behavior understandable without private context. --> ## Problem and expected behavior CDP splits base URL and fragment, while capture lifecycle can advance between reads. A single parsed identity/scope owner now feeds authorization, runtime, timeline, screenshot and WebMCP consumers. Electron uses a structurally valid ancestry graph separately from per-file admission and binds scripts to authorized frame generations. <!-- For fixes, give the smallest trigger and violated invariant. For features, describe the use case and observable outcome. --> ## Change and scope Tree snapshots separate stable loader/parent document identity from URL observations. A URL-only child history/hash update retains generation authority; a changed loader/parent uses the shared descendant-generation invalidation. Explicit full-navigation event replay still requires matching observed URL, preserving unknown-frame controls. A tree-observed same-file reload cannot erase the previous loader identity and hide a delayed navigation event; main replacement returns target_changed, while child replacement retains historical proof and leaves newly unverified script attribution unknown. One coupled outcome: preserve document identity and authorization across capture lifecycle. Integrated main 0b17cb621, including ASAR header admission and runtime setup/cleanup. No new target authority. Independent fixes removed from this diff: PNG #6412 (merged); omitted-response accounting #6413 (merged). Offline HAR availability and dropped-WebMCP comparison are validated independent branches; GitHub rejected their PR creation with CreatePullRequest permission errors. Prepared comparisons: [offline HAR](https://github.com/morluto/rea/compare/main...eco-null:rea:codex/offline-network-availability) and [WebMCP comparison](https://github.com/morluto/rea/compare/main...eco-null:rea:codex/webmcp-dropped-comparison). Restored prior runtime error precedence: frame/loader or no-loader URL changes return target_changed before origin rejection. Same-document origin rejection retains the original detail text; regressions pin both behaviors. Superseded AST-only regressions were removed; upstream fixes are not claimed here. <!-- Explain the chosen approach, why it fits REA's architecture, and what is intentionally not included. --> 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 <!-- Short answers are welcome. Complete applicable lines; mark unresolved facts as "unknown". Use "none" or "not applicable" only when established. --> - Semantic owner and earliest changed stage: CdpCaptureDocuments parsed identity/scope and Electron inventory/generation producers. - Contribution scope fit and linked maintainer decision: Ordinary fix within existing boundaries; new maintainer scope decision not applicable. - CLI and MCP/tool-catalog contract: Existing interfaces and schemas retained; observable correction described above. - Provider, bridge, target-format, or platform compatibility: Owner, provider and public CLI/MCP fixture regressions, including ancestry, malformed identity, origin policy, document replacement and cleanup. - Evidence, artifact, provenance, or reconstruction contract: Incomplete or rejected observations remain explicit; source evidence is retained. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Existing selection and authority unchanged. - 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): No build outputs committed; catalogs regenerated by normal checks. 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. - [x] Launch or attach to a process. - [x] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [x] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage <!-- State whether evidence is executed, source-derived, or proposed. For fixes, show the original failure and explain how the regression would fail on the affected base revision when practical. Include the most useful proof inline; link long logs or artifacts, or put them in optional details. Documentation-only changes can use source, link, or rendered-document checks. --> - Tests added or updated: Owner, provider and public CLI/MCP fixture regressions, including ancestry, malformed identity, origin policy, document replacement and cleanup. - Base reproduction or other evidence: The existing identity/lifecycle regressions retain prior red/green evidence in this PR history. This revision adds changed-origin/frame precedence and detail assertions; no fresh complete pre-fix replay was performed. - User-visible CLI/MCP output (if applicable): Compiled CLI and MCP retain the same reconstructed full URL including fragment; screenshot/runtime evidence matches it. Failed identity and scope remain explicit. - Remaining proof gaps: No real Chromium/Electron/live WebMCP replay, full suite or cross-platform run on this head. Historical engine runs do not establish current-head hosted CI. 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 - Current conflict-resolution head `1b579209dc7c5cc7ac68824381c486b8fe6bb45a` merges main `45a411e8f8314b844bc20aef57afb59991c4a637`. Retained both frame-identity and upstream cleanup-failure MCP tests; reused the shared imports. No additional production edits. - macOS, Node 24.22.1/npm 11.16.0: `npm ci --no-audit --no-fund`, `npm run check`, normal pre-commit and pre-push (`check:fast`) passed. `npm run test:focused -- src/browser/CdpCaptureDocuments.test.ts src/browser/CdpElectronInspection.test.ts tests/boundary/browser/cdpAuthorizedMainFrameRetry.test.ts tests/boundary/browser/cdpBrowserProvider.document_script.test.ts tests/boundary/browser/cdpBrowserProvider.timelineEvents.test.ts tests/boundary/browser/cdpElectronProvider.test.ts tests/boundary/browser/cdpRuntimeFrameIdentity.test.ts tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts tests/boundary/browser/cdpWebMcpTransientIdentity.test.ts tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/webRuntimeMcp.test.ts`: full rerun passed 429 tests in 11 files (18.54s). Initial run passed 428/429: the screenshot root-replacement test returned `target_changed` instead of `target_not_allowed`; its isolated rerun passed 62/62, then the complete selection passed. The screenshot implementation, test, and fixture were unchanged by this merge; intermittent event-order behavior remains unmodified. - Current-head limitations: no real Chromium/Electron/live WebMCP, full suite, cross-platform, or fresh docs check run. Hosted CI is pending; CI results listed below refer to earlier heads. <!-- List only commands that actually ran, with observed results. Include the relevant real-provider or platform workflow, or explain why it was unavailable. Keep these results current after changes; a command without its result is incomplete. --> - Merged main `6dff37594c0bc942c9748b34a7a028d223e88a6d` after #6412/#6413 landed. One conflict in screenshot identity tests: retained both upstream PNG tests/CRC fixtures and this PR's frame-identity tests. Other147 upstream-only files match main exactly; no PNG/network production change remains in this PR diff. - `npm run test:focused -- src/browser/CdpCaptureDocuments.test.ts src/browser/CdpElectronInspection.test.ts tests/boundary/browser/cdpElectronProvider.test.ts tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/webRuntimeMcp.test.ts`: 223 passed in6 files (42.18s), including compiled CLI/MCP checks, Electron reload/same-document and strict PNG capture regressions. - Full `npm run check` (6tasks15.123s plus architecture guards), `npm run docs:check` (9 README tests), normal pre-push (4.313s) passed. Merge commit tree matches the read-only-validated staged tree; mutating pre-commit fixes were not applied to unrelated upstream files. Windows, pinned Node24.18.0/npm11.16.0. - Earlier owner failure-first matrices (6red/23controls reload;5red/31controls URL-only),121pass/2Windows POSIX skips and real-engine runs are historical parent proof. No real Electron/Chromium/liveWebMCP/fullsuite/crossplatform local rerun on this merge head. Hosted CI for exact merge head `346093f9da86c4ea98ae289f1ccce42ab8a1554e` completed successfully: [CI39905535992](https://github.com/morluto/rea/actions/runs/39905535992), [CI required SUCCESS](https://github.com/morluto/rea/actions/runs/39905535992/job/120260294833), [real-browser job SUCCESS](https://github.com/morluto/rea/actions/runs/39905535992/job/120256890690). No specific real Electron/liveWebMCP replay or skipped-lane execution is claimed. - Parent `0a0e608c726c2eada431527fd11da15f605c0896` completed [CI39869520659](https://github.com/morluto/rea/actions/runs/39869520659), including CI required and real-browser jobSUCCESS. That is not new merge-head CI proof. ## Compatibility, safety, and release <!-- Call out breaking changes, migrations, package effects, platform/provider limits, security/privacy/containment implications, and meaningful proof gaps. --> - Breaking changes or migration steps: No schema migration; previously misclassified observations are corrected. <!-- For ! / BREAKING CHANGE: show a previously valid call/configuration, its new behavior and migration, and why compatibility/deprecation cannot preserve it. Every release increments minor, including breaking changes; keep breaking markers and migration notes so callers can assess compatibility. See docs/releasing.md. --> - Real Hopper/Ghidra, browser, or OS coverage: No real Chromium/Electron/live WebMCP replay, full suite or cross-platform run on this head. Historical engine runs do not establish current-head hosted CI. - Package or release metadata impact: No dependency or release version change. - Security, privacy, process, or containment review: No expanded target authority; no bypass of workflow approval. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @eco-null - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:11:10 +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#6013
No description provided.