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 #5368] feat(browser): wake or classify discarded CDP page targets before inspection #6900

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5368
Author: @aryankeluskar
Created: 10/20/2026
Status: 🔄 Open

Base: main ← Head: agent/wake-discarded-browser-targets

📝 Commits (1)

  • a18dd3e feat(browser): wake or classify discarded CDP page targets before inspection

📊 Changes

21 files changed (+984 additions, -2 deletions)

View changed files

📝 src/application/BrowserEvidence.ts (+15 -0)
📝 src/application/BrowserObservationPort.ts (+6 -0)
📝 src/application/BrowserObservationService.ts (+27 -0)
📝 src/browser/CdpBrowserProvider.ts (+357 -1)
➕ src/browser/CdpBrowserProviderTargetWake.test.ts (+255 -0)
📝 src/browser/CdpTargetSession.ts (+2 -1)
📝 src/cli/browserCommands.ts (+83 -0)
📝 src/cliCommandNames.ts (+1 -0)
📝 src/contracts/browserToolContracts.ts (+31 -0)
📝 src/contracts/toolEffects.ts (+7 -0)
📝 src/domain/browserObservation.ts (+30 -0)
📝 src/domain/browserObservationErrors.ts (+1 -0)
📝 src/domain/browserObservationSchemas.ts (+31 -0)
📝 src/server/registerBrowserTools.ts (+16 -0)
📝 tests/boundary/mcp/browserMcp.test.ts (+53 -0)
📝 tests/boundary/mcp/lateAbortApplicationEvidenceMcp.test.ts (+3 -0)
📝 tests/boundary/mcp/observationPartialEvidenceDelivery.test.ts (+1 -0)
📝 tests/fixtures/fakeCdpBrowser.ts (+53 -0)
📝 tests/fixtures/fakeCdpBrowserResults.ts (+1 -0)
📝 tests/fixtures/fakeCdpBrowserTypes.ts (+10 -0)

...and 1 more files

📄 Description

Summary

Implements the wake/classify prototype proposed in #5360: a bounded
wake_browser_targets browser operation (CLI: wake-browser-targets) that
classifies selected CDP page targets as awake, awake_after_reload, or
unknown before inspection, with explicit per-target failure reasons, so
browser tools stop dying on Page.enable response-deadline errors after a
session restore.

Discussion and the original failure report live in #5360. This PR does not
close it: real discarded-target revival is verified in the fake CDP lane and
left as a recorded proof gap (NOT_ENOUGH_INFO in the issue) until a live
discarded target can be exercised.

Problem and expected behavior

After a browser restart with restored tabs, Chromium can drop a tab's renderer
while list_browser_targets still reports the steady CDP target entry. Any
tool that then opens the target waits out the fixed 20 s command budget; the
observed failure on this base is
CDP command Page.enable exceeded its 20000 ms response deadline.
(see #5360).

Expected behavior: wake_browser_targets reports which selections are
responsive (awake), which were revived after one caller-opted reload
(awake_after_reload), and which remain unknown with a machine-readable
failure_reason (target_not_found | target_not_allowed | protocol_error
| disconnected | timeout), all within caller-set deadlines instead of the
fixed 20 s.

Change and scope

  • Input schema wakeBrowserTargetsInputSchema: cdp_endpoint,
    allowed_origins, target_ids (≥1; duplicates classified once),
    probe_deadline_ms (default 2000), wake_deadline_ms (default 10000),
    revive (none default | reload).
  • Probe: Page.enable raced against the probe deadline; late replies are
    consumed and cannot leak a rejection into a later run.
  • Revival: for a probe failure only, the caller-opted Page.reload is sent
    (its ack bounded by the probe deadline) and the target is re-probed within
    the wake deadline; the default revive: none never navigates anything.
  • Per-target sessions reuse the existing ownership path (authorizeCdpTarget,
    page-socket or shared-browser-socket attach); shared sockets detach between
    selections and release once after the last.
  • Out of scope: revive: "activate" (raised in #5360; browser-socket
    activation complexity — flagged there as possibly cut) and any live
    discarded-tab revival proof (see gaps below).

Follow the contribution scope.
The work stays inside the existing CDP browser-provider boundary; no new
provider. The reload effect mutates page navigation state only on explicit
caller opt-in — that scope decision is pending (draft); see #5360.

Contract and boundary impact

  • Semantic owner and earliest changed stage: browser observation (domain) —
    src/domain/browserObservation.ts input schema; downstream per tool contract.
  • Contribution scope fit and linked maintainer decision: prototype inside the
    existing browser boundary; the reload-mutation scope decision is pending,
    discussed in #5360.
  • CLI and MCP/tool-catalog contract: wake-browser-targets CLI command and
    wake_browser_targets MCP tool with input/output schemas, examples, and a
    declared effect audit (mutatesTarget: true, mutatesSession: true,
    accessesNetwork: true, mayDiscardData: true, idempotent: false).
  • Provider, bridge, target-format, or platform compatibility: CDP browser
    provider only; BrowserObservationPort.wakeTargets added (recording and
    boundary test fakes updated).
  • Evidence, artifact, provenance, or reconstruction contract: predicate
    rea.browser-target-wake; parameters carry target_ids, both deadlines,
    and revive; output schema browserTargetWakeSchema.
  • Target selection, authority, upstream behavior, and cleanup details
    (if applicable): per-target authorization with allowed_origins; bounded
    probes with late replies consumed; pre-aborted and mid-loop cancellation
    surfaces as AnalysisCancelledError; owner cleanup retains resources whose
    cleanup failed.
  • Generated metadata (docs/public/product-catalog.json), package, or
    installation impact: none tracked; CI generates and validates ignored
    catalogs; authored .agents/skills/reverse-engineer-anything/
    instructions unchanged.

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. — only page
    navigation state via the caller-opted Page.reload; the default
    revive=none changes nothing (counter-asserted in tests).
  • Contact network services. — the caller-selected loopback CDP endpoint.
  • 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:
    • src/browser/CdpBrowserProviderTargetWake.test.ts (9): awake
      classification without reload; discarded target → unknown/timeout
      with zero reloads (proved by fixture counter); reload revival →
      awake_after_reload; revival missing the wake deadline → unknown +
      reload_sent: true; target_not_found; target_not_allowed; duplicate
      selections deduped with a limitation; mixed selections classified in
      input order; pre-aborted cancellation stays explicit.
    • Fake CDP fixture: per-target discarded simulation
      (discardedTargetIds, discardedReviveDelayMs, Page.reload ack case,
      reload counter).
    • MCP boundary segment in tests/boundary/mcp/browserMcp.test.ts:
      wake_browser_targets registered, probe-only unknown, revived
      awake_after_reload, and no navigation during classify-only wake.
  • Base reproduction or other evidence: the deadline failure string recorded in
    #5360 was observed on this base against a restored Brave session before the
    change.
  • User-visible CLI/MCP output (if applicable): real-lane output below.
  • Remaining proof gaps: live revival of a genuinely discarded target is
    unmeasured (no discarded tab existed at prototype time; NOT_ENOUGH_INFO in
    #5360); the fixture models browser-process reload-ack and delayed-renderer
    behavior; revive: "activate" is not implemented.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable. — measured
    statuses in tests; fixture behavior declared as simulation.
  • Artifact identity, source provenance, and failed attempts remain
    preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain
    visible. — unknown is a first-class result; limitation strings report
    stale selections.

Validation performed

  • npm run check — typecheck, lint:built, format:check, knip,
    metadata:check, verify:architecture-guards: all green (fixed a knip unused
    export and a max-lines-per-function lint error on the way).
  • npm run verify:test-discovery — all 1715 test files discovered exactly once.
  • npm run test:fast (source group) — 689 files, 11024 passed, 15 skipped.
  • npx vitest run --project mcp-boundary tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/toolSchemaValidity.test.ts tests/boundary/mcp/electronMcp.test.ts tests/boundary/mcp/webBundleContainmentMcp.test.ts —
    29 passed (after npm run test:prepare; the same slice fails identically
    on the pristine base without generated artifacts).
  • npx vitest run --project cli-boundary tests/boundary/cli/browserCli.test.ts tests/boundary/cli/browserRedirectShapeCompleteness.test.ts —
    12 passed.
  • npm run docs:check — green.
  • npm run test:prepare, npm run build:cached — green; no tracked
    generated diffs.
  • Live real-provider lane (Brave 155.1.97.59 / Chrome 155.0.8059.85, all tabs
    awake), new CLI against http://127.0.0.1:9222:
    • node scripts/rea.mjs wake-browser-targets http://127.0.0.1:9222 04550BCE1A699B8A1E38E1CA5DA4ABF8 --json →
      "status": "awake", "elapsed_ms": 1, "reload_sent": false with the
      probe-only limitation string.
    • same with --revive reload → still awake, reload_sent: false (the
      opt-in reload only fires on probe failure).
    • node scripts/rea.mjs wake-browser-targets http://127.0.0.1:9222 00000000000000000000000000000000 --json →
      unknown + "failure_reason": "target_not_found".

Compatibility, safety, and release

  • Breaking changes or migration steps: none; additive tool and an additive
    required method on the provider port (internal interface; bundled test
    fakes updated).
  • Real Hopper/Ghidra, browser, or OS coverage: live awake, authorization, and
    cancellation paths on Brave/Chrome 155 (macOS); discarded/revival path via
    the fake CDP lane.
  • Package or release metadata impact: none tracked.
  • Security, privacy, process, or containment review: loopback-only endpoint
    schema unchanged; no JavaScript evaluation, no storage access, no
    configuration change; navigation only on explicit revive: reload;
    origin authorization enforced per selection.

Author readiness

Human owner:

  • 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/5368 **Author:** [@aryankeluskar](https://github.com/aryankeluskar) **Created:** 10/20/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `agent/wake-discarded-browser-targets` --- ### 📝 Commits (1) - [`a18dd3e`](https://github.com/morluto/rea/commit/a18dd3e7a6c5ea0a1fb5440544d340dd0f19edbe) feat(browser): wake or classify discarded CDP page targets before inspection ### 📊 Changes **21 files changed** (+984 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/application/BrowserEvidence.ts` (+15 -0) 📝 `src/application/BrowserObservationPort.ts` (+6 -0) 📝 `src/application/BrowserObservationService.ts` (+27 -0) 📝 `src/browser/CdpBrowserProvider.ts` (+357 -1) ➕ `src/browser/CdpBrowserProviderTargetWake.test.ts` (+255 -0) 📝 `src/browser/CdpTargetSession.ts` (+2 -1) 📝 `src/cli/browserCommands.ts` (+83 -0) 📝 `src/cliCommandNames.ts` (+1 -0) 📝 `src/contracts/browserToolContracts.ts` (+31 -0) 📝 `src/contracts/toolEffects.ts` (+7 -0) 📝 `src/domain/browserObservation.ts` (+30 -0) 📝 `src/domain/browserObservationErrors.ts` (+1 -0) 📝 `src/domain/browserObservationSchemas.ts` (+31 -0) 📝 `src/server/registerBrowserTools.ts` (+16 -0) 📝 `tests/boundary/mcp/browserMcp.test.ts` (+53 -0) 📝 `tests/boundary/mcp/lateAbortApplicationEvidenceMcp.test.ts` (+3 -0) 📝 `tests/boundary/mcp/observationPartialEvidenceDelivery.test.ts` (+1 -0) 📝 `tests/fixtures/fakeCdpBrowser.ts` (+53 -0) 📝 `tests/fixtures/fakeCdpBrowserResults.ts` (+1 -0) 📝 `tests/fixtures/fakeCdpBrowserTypes.ts` (+10 -0) _...and 1 more files_ </details> ### 📄 Description ## Summary Implements the wake/classify prototype proposed in #5360: a bounded `wake_browser_targets` browser operation (CLI: `wake-browser-targets`) that classifies selected CDP page targets as `awake`, `awake_after_reload`, or `unknown` before inspection, with explicit per-target failure reasons, so browser tools stop dying on `Page.enable` response-deadline errors after a session restore. Discussion and the original failure report live in #5360. This PR does not close it: real discarded-target revival is verified in the fake CDP lane and left as a recorded proof gap (NOT_ENOUGH_INFO in the issue) until a live discarded target can be exercised. ## Problem and expected behavior After a browser restart with restored tabs, Chromium can drop a tab's renderer while `list_browser_targets` still reports the steady CDP target entry. Any tool that then opens the target waits out the fixed 20 s command budget; the observed failure on this base is `CDP command Page.enable exceeded its 20000 ms response deadline.` (see #5360). Expected behavior: `wake_browser_targets` reports which selections are responsive (`awake`), which were revived after one caller-opted reload (`awake_after_reload`), and which remain `unknown` with a machine-readable `failure_reason` (`target_not_found` | `target_not_allowed` | `protocol_error` | `disconnected` | `timeout`), all within caller-set deadlines instead of the fixed 20 s. ## Change and scope - Input schema `wakeBrowserTargetsInputSchema`: `cdp_endpoint`, `allowed_origins`, `target_ids` (≥1; duplicates classified once), `probe_deadline_ms` (default 2000), `wake_deadline_ms` (default 10000), `revive` (`none` default | `reload`). - Probe: `Page.enable` raced against the probe deadline; late replies are consumed and cannot leak a rejection into a later run. - Revival: for a probe failure only, the caller-opted `Page.reload` is sent (its ack bounded by the probe deadline) and the target is re-probed within the wake deadline; the default `revive: none` never navigates anything. - Per-target sessions reuse the existing ownership path (`authorizeCdpTarget`, page-socket or shared-browser-socket attach); shared sockets detach between selections and release once after the last. - Out of scope: `revive: "activate"` (raised in #5360; browser-socket activation complexity — flagged there as possibly cut) and any live discarded-tab revival proof (see gaps below). Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). The work stays inside the existing CDP browser-provider boundary; no new provider. The reload effect mutates page navigation state only on explicit caller opt-in — that scope decision is pending (draft); see #5360. ## Contract and boundary impact - Semantic owner and earliest changed stage: browser observation (domain) — `src/domain/browserObservation.ts` input schema; downstream per tool contract. - Contribution scope fit and linked maintainer decision: prototype inside the existing browser boundary; the reload-mutation scope decision is pending, discussed in #5360. - CLI and MCP/tool-catalog contract: `wake-browser-targets` CLI command and `wake_browser_targets` MCP tool with input/output schemas, examples, and a declared effect audit (`mutatesTarget: true`, `mutatesSession: true`, `accessesNetwork: true`, `mayDiscardData: true`, `idempotent: false`). - Provider, bridge, target-format, or platform compatibility: CDP browser provider only; `BrowserObservationPort.wakeTargets` added (recording and boundary test fakes updated). - Evidence, artifact, provenance, or reconstruction contract: predicate `rea.browser-target-wake`; parameters carry `target_ids`, both deadlines, and `revive`; output schema `browserTargetWakeSchema`. - Target selection, authority, upstream behavior, and cleanup details (if applicable): per-target authorization with `allowed_origins`; bounded probes with late replies consumed; pre-aborted and mid-loop cancellation surfaces as `AnalysisCancelledError`; owner cleanup retains resources whose cleanup failed. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none tracked; CI generates and validates ignored catalogs; authored `.agents/skills/reverse-engineer-anything/` instructions unchanged. 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. - [x] Change process memory, registers, files, or configuration. — only page navigation state via the caller-opted `Page.reload`; the default `revive=none` changes nothing (counter-asserted in tests). - [x] Contact network services. — the caller-selected loopback CDP endpoint. - [ ] 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: - `src/browser/CdpBrowserProviderTargetWake.test.ts` (9): awake classification without reload; discarded target → `unknown`/`timeout` with zero reloads (proved by fixture counter); reload revival → `awake_after_reload`; revival missing the wake deadline → `unknown` + `reload_sent: true`; `target_not_found`; `target_not_allowed`; duplicate selections deduped with a limitation; mixed selections classified in input order; pre-aborted cancellation stays explicit. - Fake CDP fixture: per-target discarded simulation (`discardedTargetIds`, `discardedReviveDelayMs`, `Page.reload` ack case, reload counter). - MCP boundary segment in `tests/boundary/mcp/browserMcp.test.ts`: `wake_browser_targets` registered, probe-only `unknown`, revived `awake_after_reload`, and no navigation during classify-only wake. - Base reproduction or other evidence: the deadline failure string recorded in #5360 was observed on this base against a restored Brave session before the change. - User-visible CLI/MCP output (if applicable): real-lane output below. - Remaining proof gaps: live revival of a genuinely discarded target is unmeasured (no discarded tab existed at prototype time; NOT_ENOUGH_INFO in #5360); the fixture models browser-process reload-ack and delayed-renderer behavior; `revive: "activate"` is not implemented. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. — measured statuses in tests; fixture behavior declared as simulation. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. — `unknown` is a first-class result; limitation strings report stale selections. ## Validation performed - `npm run check` — typecheck, lint:built, format:check, knip, metadata:check, verify:architecture-guards: all green (fixed a knip unused export and a max-lines-per-function lint error on the way). - `npm run verify:test-discovery` — all 1715 test files discovered exactly once. - `npm run test:fast` (source group) — 689 files, 11024 passed, 15 skipped. - `npx vitest run --project mcp-boundary tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/toolSchemaValidity.test.ts tests/boundary/mcp/electronMcp.test.ts tests/boundary/mcp/webBundleContainmentMcp.test.ts` — 29 passed (after `npm run test:prepare`; the same slice fails identically on the pristine base without generated artifacts). - `npx vitest run --project cli-boundary tests/boundary/cli/browserCli.test.ts tests/boundary/cli/browserRedirectShapeCompleteness.test.ts` — 12 passed. - `npm run docs:check` — green. - `npm run test:prepare`, `npm run build:cached` — green; no tracked generated diffs. - Live real-provider lane (Brave 155.1.97.59 / Chrome 155.0.8059.85, all tabs awake), new CLI against <http://127.0.0.1:9222>: - `node scripts/rea.mjs wake-browser-targets http://127.0.0.1:9222 04550BCE1A699B8A1E38E1CA5DA4ABF8 --json` → `"status": "awake", "elapsed_ms": 1, "reload_sent": false` with the probe-only limitation string. - same with `--revive reload` → still `awake`, `reload_sent: false` (the opt-in reload only fires on probe failure). - `node scripts/rea.mjs wake-browser-targets http://127.0.0.1:9222 00000000000000000000000000000000 --json` → `unknown` + `"failure_reason": "target_not_found"`. ## Compatibility, safety, and release - Breaking changes or migration steps: none; additive tool and an additive required method on the provider port (internal interface; bundled test fakes updated). - Real Hopper/Ghidra, browser, or OS coverage: live awake, authorization, and cancellation paths on Brave/Chrome 155 (macOS); discarded/revival path via the fake CDP lane. - Package or release metadata impact: none tracked. - Security, privacy, process, or containment review: loopback-only endpoint schema unchanged; no JavaScript evaluation, no storage access, no configuration change; navigation only on explicit `revive: reload`; origin authorization enforced per selection. ## 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: <!-- @GitHub-handle --> - [ ] 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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6900
No description provided.