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 #3812] feat(experiments): prototype evidence-gated findings triage #5918

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3812
Author: @Lopesnextgen
Created: 10/15/2026
Status: 🔄 Open

Base: main ← Head: feat/findings-triage

📝 Commits (3)

  • 364882b feat(experiments): prototype evidence-gated findings triage
  • 6d42322 fix(experiments): keep triage fingerprints stable across builds
  • fb8127e fix(experiments): keep triage output owner-only and test cleanup

📊 Changes

16 files changed (+1639 additions, -0 deletions)

View changed files

➕ experiments/findings-triage/README.md (+265 -0)
➕ experiments/findings-triage/cli.mjs (+106 -0)
➕ experiments/findings-triage/cli.test.mjs (+135 -0)
➕ experiments/findings-triage/fixture/app/index.html (+21 -0)
➕ experiments/findings-triage/fixture/app/main.js (+29 -0)
➕ experiments/findings-triage/fixture/app/package.json (+6 -0)
➕ experiments/findings-triage/fixture/app/preload.js (+8 -0)
➕ experiments/findings-triage/fixture/bundle.ndjson (+1 -0)
➕ experiments/findings-triage/fixture/expected/advisories/notes-save-unchecked-path.md (+33 -0)
➕ experiments/findings-triage/fixture/expected/issues.json (+8 -0)
➕ experiments/findings-triage/fixture/expected/issues/insecure-web-preferences.md (+34 -0)
➕ experiments/findings-triage/fixture/expected/report.md (+113 -0)
➕ experiments/findings-triage/fixture/generate.mjs (+114 -0)
➕ experiments/findings-triage/fixture/triage.json (+68 -0)
➕ experiments/findings-triage/triage.mjs (+411 -0)
➕ experiments/findings-triage/triage.test.mjs (+287 -0)

📄 Description

Summary

Adds an isolated prototype under experiments/findings-triage/ that turns a finished REA investigation into a triage report. Every finding is classified as defect, suspect, acceptable or unknown. The validator refuses any verdict the cited Evidence cannot carry. Nothing is registered in the CLI, the MCP catalog or the package.

Refs #1142. That issue proposes evidence-gated Markdown reports from bundles (TraceBrief), and this draft covers the step that proposal leaves open: verdicts, remediation, the next probe and issue export.

Problem and expected behavior

A bundle records what REA observed and what remains unknown. It does not record which findings are defects in the target, which are fine, and what to do about each one. Analysts write that by hand today, and nothing checks the verdicts against the Evidence.

Inputs are an Evidence bundle from export_evidence_bundle and an analyst-written triage.json. validate reports every problem at once. render writes report.md, one issue body per public defect or suspect with an issues.json index for filing with gh, and one advisory draft per private finding.

Change and scope

  • The bundle is parsed with REA's own parseEvidenceBundle, which also authenticates Evidence IDs and unknown revisions, rather than a second parser.
  • defect and acceptable need at least one cited record that is observed or derived and not analyst-inference. record_unknown and update_unknown records are derived but only record intent.
  • A runtime-behavior defect or acceptable verdict needs that same record to carry controlled-replay or external-service authority. suspect and unknown may rest on static Evidence; that gap is what next_probe names.
  • Every residual unknown whose current revision is not resolved must be linked by a finding. Linking a resolved unknown, or settling a verdict on an open one, is an error.
  • Evidence strength is computed from the cited records, never authored.
  • Exported bodies carry only triage text, Evidence IDs, operations and limitations. They never include raw_result, parameters or environment, which hold local paths.
  • render creates a new directory with a non-recursive mkdir and exclusive writes. If a write fails, it removes that directory.

Not included: creating GitHub issues (the tool makes no network calls), any src/ integration, and any skill or doc change outside the experiment.

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: the experiment owns triage validation and rendering. Bundle parsing stays with src/domain/evidenceBundle.ts.
  • Contribution scope fit and linked maintainer decision: evidence reporting, which CONTRIBUTING lists as a supported contribution. Maintainer scope decision: pending (#1142).
  • CLI and MCP/tool-catalog contract: unchanged.
  • Provider, bridge, target-format, or platform compatibility: unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged. The experiment only reads exported bundles.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): fixture/generate.mjs starts the built REA MCP server, analyzes a copy of the self-owned sample app in an mkdtemp directory, and removes both the directory and the server on every path. The sample app is never executed.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none.

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.

render writes only a new output directory. The fixture generator starts REA's own MCP server as a child process; it does not launch the target.

Evidence and regression coverage

  • Tests added or updated: triage.test.mjs and cli.test.mjs, 36 tests.
    • Each rule fails on a minimal mutation of the real fixture.
    • Analyst-inference-only citations are covered, and so is basis and runtime authority split across two records.
    • Revision-head logic.
    • Finding-ID path safety: separators, device names and non-ASCII case folding.
    • Ordering, and the absence of local paths and raw results in rendered files.
    • CLI exit codes, --json, refusal of an existing --out, malformed JSON, and tampered or unparseable bundles.
    • An owner-only output directory, and its removal after a write fails mid-render.
  • Base reproduction or other evidence: fixture/bundle.ndjson is real output of analyze_javascript_application, record_unknown and update_unknown over fixture/app/, kept as REA serialized it. One unknown is resolved, so revision history is exercised. Against the pre-fix validator, the new tests for analyst-inference basis, split runtime authority, static suspects and unknowns, and ID safety fail.
  • User-visible CLI/MCP output (if applicable): see fixture/expected/report.md, issues/insecure-web-preferences.md and advisories/notes-save-unchecked-path.md.
  • Remaining proof gaps:
    • Only the static JavaScript provider and the unknown registry produced fixture Evidence. The runtime-authority rule is covered by in-memory records, not a real capture.
    • The gh filing loop in the README has not been run.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

All run on Linux x64 with Node 24.21.0. The pinned 24.18.0 was not used.

  • node --test experiments/findings-triage/*.test.mjs: 36 passed, 0 failed.
  • node experiments/findings-triage/cli.mjs render on the fixture, then diff -r against fixture/expected/: identical.
  • node experiments/findings-triage/fixture/generate.mjs: exit 0, 5 records and 4 unknown revisions. No temp directory or server process was left behind.
  • npx oxlint experiments/findings-triage: 0 warnings, 0 errors.
  • npx oxfmt --check experiments/findings-triage: clean.
  • npx jscpd experiments/findings-triage: 0 clones.
  • Pre-commit lint-staged and npm run check:fast: passed.
  • experiments/ is outside tsconfig.json, so the typecheck does not cover these .mjs files. This folder is covered by oxlint and the node --test suites only.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: none. Linux only; macOS and Windows were not run.
  • Package or release metadata impact: none. experiments/ is not packaged.
  • Security, privacy, process, or containment review:
    • No network access.
    • Output never overwrites existing paths and is created owner-only (0700).
    • Finding IDs are restricted before being used as file names.
    • Private findings are kept out of issues.json.
    • The fixture bundle holds only a temporary path for the sample app; no user or host identifiers.

Author readiness

Human owner: @Lopesnextgen

  • 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/3812 **Author:** [@Lopesnextgen](https://github.com/Lopesnextgen) **Created:** 10/15/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/findings-triage` --- ### 📝 Commits (3) - [`364882b`](https://github.com/morluto/rea/commit/364882b353e8d1520870d44ea059bac8cec7173b) feat(experiments): prototype evidence-gated findings triage - [`6d42322`](https://github.com/morluto/rea/commit/6d42322e8332cd2e029ad3497fdfe594fd6041cd) fix(experiments): keep triage fingerprints stable across builds - [`fb8127e`](https://github.com/morluto/rea/commit/fb8127ec1525cec3615608b4d3e297f5bc9e4dc1) fix(experiments): keep triage output owner-only and test cleanup ### 📊 Changes **16 files changed** (+1639 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `experiments/findings-triage/README.md` (+265 -0) ➕ `experiments/findings-triage/cli.mjs` (+106 -0) ➕ `experiments/findings-triage/cli.test.mjs` (+135 -0) ➕ `experiments/findings-triage/fixture/app/index.html` (+21 -0) ➕ `experiments/findings-triage/fixture/app/main.js` (+29 -0) ➕ `experiments/findings-triage/fixture/app/package.json` (+6 -0) ➕ `experiments/findings-triage/fixture/app/preload.js` (+8 -0) ➕ `experiments/findings-triage/fixture/bundle.ndjson` (+1 -0) ➕ `experiments/findings-triage/fixture/expected/advisories/notes-save-unchecked-path.md` (+33 -0) ➕ `experiments/findings-triage/fixture/expected/issues.json` (+8 -0) ➕ `experiments/findings-triage/fixture/expected/issues/insecure-web-preferences.md` (+34 -0) ➕ `experiments/findings-triage/fixture/expected/report.md` (+113 -0) ➕ `experiments/findings-triage/fixture/generate.mjs` (+114 -0) ➕ `experiments/findings-triage/fixture/triage.json` (+68 -0) ➕ `experiments/findings-triage/triage.mjs` (+411 -0) ➕ `experiments/findings-triage/triage.test.mjs` (+287 -0) </details> ### 📄 Description ## Summary Adds an isolated prototype under `experiments/findings-triage/` that turns a finished REA investigation into a triage report. Every finding is classified as `defect`, `suspect`, `acceptable` or `unknown`. The validator refuses any verdict the cited Evidence cannot carry. Nothing is registered in the CLI, the MCP catalog or the package. Refs #1142. That issue proposes evidence-gated Markdown reports from bundles (TraceBrief), and this draft covers the step that proposal leaves open: verdicts, remediation, the next probe and issue export. ## Problem and expected behavior A bundle records what REA observed and what remains unknown. It does not record which findings are defects in the target, which are fine, and what to do about each one. Analysts write that by hand today, and nothing checks the verdicts against the Evidence. Inputs are an Evidence bundle from `export_evidence_bundle` and an analyst-written `triage.json`. `validate` reports every problem at once. `render` writes `report.md`, one issue body per public `defect` or `suspect` with an `issues.json` index for filing with `gh`, and one advisory draft per private finding. ## Change and scope - The bundle is parsed with REA's own `parseEvidenceBundle`, which also authenticates Evidence IDs and unknown revisions, rather than a second parser. - `defect` and `acceptable` need at least one cited record that is `observed` or `derived` and not `analyst-inference`. `record_unknown` and `update_unknown` records are derived but only record intent. - A `runtime-behavior` defect or acceptable verdict needs that same record to carry `controlled-replay` or `external-service` authority. `suspect` and `unknown` may rest on static Evidence; that gap is what `next_probe` names. - Every residual unknown whose current revision is not resolved must be linked by a finding. Linking a resolved unknown, or settling a verdict on an open one, is an error. - Evidence strength is computed from the cited records, never authored. - Exported bodies carry only triage text, Evidence IDs, operations and limitations. They never include `raw_result`, `parameters` or `environment`, which hold local paths. - `render` creates a new directory with a non-recursive `mkdir` and exclusive writes. If a write fails, it removes that directory. Not included: creating GitHub issues (the tool makes no network calls), any `src/` integration, and any skill or doc change outside the experiment. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: the experiment owns triage validation and rendering. Bundle parsing stays with `src/domain/evidenceBundle.ts`. - Contribution scope fit and linked maintainer decision: evidence reporting, which CONTRIBUTING lists as a supported contribution. Maintainer scope decision: pending (#1142). - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: unchanged. - Evidence, artifact, provenance, or reconstruction contract: unchanged. The experiment only reads exported bundles. - Target selection, authority, upstream behavior, and cleanup details (if applicable): `fixture/generate.mjs` starts the built REA MCP server, analyzes a copy of the self-owned sample app in an `mkdtemp` directory, and removes both the directory and the server on every path. The sample app is never executed. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. `render` writes only a new output directory. The fixture generator starts REA's own MCP server as a child process; it does not launch the target. ## Evidence and regression coverage - Tests added or updated: `triage.test.mjs` and `cli.test.mjs`, 36 tests. - Each rule fails on a minimal mutation of the real fixture. - Analyst-inference-only citations are covered, and so is basis and runtime authority split across two records. - Revision-head logic. - Finding-ID path safety: separators, device names and non-ASCII case folding. - Ordering, and the absence of local paths and raw results in rendered files. - CLI exit codes, `--json`, refusal of an existing `--out`, malformed JSON, and tampered or unparseable bundles. - An owner-only output directory, and its removal after a write fails mid-render. - Base reproduction or other evidence: `fixture/bundle.ndjson` is real output of `analyze_javascript_application`, `record_unknown` and `update_unknown` over `fixture/app/`, kept as REA serialized it. One unknown is resolved, so revision history is exercised. Against the pre-fix validator, the new tests for analyst-inference basis, split runtime authority, static suspects and unknowns, and ID safety fail. - User-visible CLI/MCP output (if applicable): see `fixture/expected/report.md`, `issues/insecure-web-preferences.md` and `advisories/notes-save-unchecked-path.md`. - Remaining proof gaps: - Only the static JavaScript provider and the unknown registry produced fixture Evidence. The runtime-authority rule is covered by in-memory records, not a real capture. - The `gh` filing loop in the README has not been run. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed All run on Linux x64 with Node 24.21.0. The pinned 24.18.0 was not used. - `node --test experiments/findings-triage/*.test.mjs`: 36 passed, 0 failed. - `node experiments/findings-triage/cli.mjs render` on the fixture, then `diff -r` against `fixture/expected/`: identical. - `node experiments/findings-triage/fixture/generate.mjs`: exit 0, 5 records and 4 unknown revisions. No temp directory or server process was left behind. - `npx oxlint experiments/findings-triage`: 0 warnings, 0 errors. - `npx oxfmt --check experiments/findings-triage`: clean. - `npx jscpd experiments/findings-triage`: 0 clones. - Pre-commit `lint-staged` and `npm run check:fast`: passed. - `experiments/` is outside `tsconfig.json`, so the typecheck does not cover these `.mjs` files. This folder is covered by oxlint and the `node --test` suites only. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: none. Linux only; macOS and Windows were not run. - Package or release metadata impact: none. `experiments/` is not packaged. - Security, privacy, process, or containment review: - No network access. - Output never overwrites existing paths and is created owner-only (`0700`). - Finding IDs are restricted before being used as file names. - Private findings are kept out of `issues.json`. - The fixture bundle holds only a temporary path for the sample app; no user or host identifiers. ## Author readiness Human owner: @Lopesnextgen - [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>
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#5918
No description provided.