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 #7177] feat(artifacts): add dry-run plan for artifact extraction #7694

New issue
Open
opened 2026-11-03 13:39:43 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:43 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7177
Author: @hannesstrydom664-hash
Created: 10/25/2026
Status: 🔄 Open

Base: main ← Head: feat/artifact-extraction-dry-run-5489

📝 Commits (10+)

  • 777b04a feat(artifacts): add dry-run extraction plan without destination writes (#5489)
  • 47f478c fix(artifacts): address dry-run extraction plan review feedback (#5489)
  • 93c3ab3 fix(artifacts): preserve unknown mount case sensitivity and use destination case folding in dry-run (#5489)
  • 74029e0 fix(artifacts): handle hardlinked entries and leave non-ASCII case folds unresolved in dry-run (#5489)
  • 77f9884 fix(artifacts): bound case-sensitivity probes and observe Windows directories (#5489)
  • 545c4e3 fix(artifacts): verify dry-run directory freshness, over-limit paths, and case-probe close ownership
  • 20ae0c4 fix(artifacts): resolve canonical output path limits and full Unicode case folds in dry-run plan
  • a0bf542 fix(artifacts): revalidate unpacked ASAR companions and qualify unresolved collision limitation in dry-run
  • 8f417b4 fix(artifacts): reconcile non-file entries against the inventory snapshot in dry-run
  • 041f0ef fix(artifacts): scope non-file reconciliation to active reader and verify entry kinds

📊 Changes

17 files changed (+3916 additions, -134 deletions)

View changed files

📝 docs/mcp-contracts.md (+18 -0)
📝 docs/node-sea.md (+1 -0)
📝 src/application/environment/environmentBundleTool.ts (+18 -0)
📝 src/artifacts/ArtifactPaths.test.ts (+55 -0)
📝 src/artifacts/ArtifactPaths.ts (+99 -20)
📝 src/artifacts/ArtifactProvider.ts (+8 -0)
📝 src/artifacts/SafeOutputTree.ts (+180 -19)
➕ src/artifacts/extraction/ArtifactExtraction.sourceGuard.test.ts (+128 -0)
📝 src/artifacts/extraction/ArtifactExtraction.test.ts (+1521 -3)
📝 src/artifacts/extraction/ArtifactExtraction.ts (+1071 -58)
➕ src/artifacts/extraction/DryRunPlanCache.ts (+383 -0)
📝 src/cli/artifactCommands.ts (+65 -4)
📝 src/contracts/artifactToolContracts.ts (+124 -22)
📝 src/domain/artifactGraph.ts (+58 -0)
📝 src/firmware/FirmwareFiles.ts (+5 -5)
📝 src/firmware/FirmwareProvider.ts (+3 -3)
📝 tests/boundary/providers/native/artifactProvider.extraction.test.ts (+179 -0)

📄 Description

Summary

Fixes #5489

Adds a dry-run planning mode (dry_run: true / --dry-run) to extract_artifact so agents and operators can inspect what an extraction will materialize, verify destination admission and path-collision rules, and review labeled byte estimates before touching disk.

Problem and expected behavior

  • Smallest trigger: Call extract_artifact (or CLI rea extract-artifact) when evaluating an archive or application package before deciding whether to materialize files on disk.
  • Violated invariant: Previously, extract_artifact always staged and moved extracted entries into output_root, providing no dry-run mode to validate destination path safety (Windows/POSIX reserved characters, NFC collisions, prefix collisions) and inspect planned vs. unsupported/unresolved entries without writing to disk.
  • Expected behavior: When dry_run: true (or --dry-run) is passed, extract_artifact validates output_root admission via SafeOutputTree.checkDestination(input.outputRoot), traverses selected entries using the same normalizeDestinationPath and ArtifactPathRegistry rules as real extraction, creates zero destination directories/files or sidecar manifests, and returns a structured plan alongside dry_run: true.

Change and scope

Follow the contribution scope.
Scoped enhancement implementing issue #5489 (feat(artifacts): add dry-run plan for artifact extraction).

  • src/domain/artifactGraph.ts: Add artifactExtractionPlanEntrySchema, artifactExtractionPlanTotalsSchema, and artifactExtractionPlanSchema, plus dry_run and plan fields on artifactExtractionResultSchema. Each non-root inventory occurrence is classified as "planned", "unsupported" (directories, logical metadata declarations, or nested archive members not expanded during single-container extraction), or "unresolved" (symlinks), with byte totals explicitly labeled via byte_totals_basis: "declared-and-observed-content-estimates" and byte_totals_note.
  • src/artifacts/SafeOutputTree.ts & src/artifacts/extraction/ArtifactExtraction.ts: Export normalizeDestinationPath(relativePath, platform) so dry-run planning applies the exact same Windows/POSIX destination path rules (\, :, U+0001-U+001F, NFC normalization, and ArtifactPathRegistry prefix/collision checks) as SafeOutputTree.prototype.write(). When dryRun: true, extractArtifact validates the destination via SafeOutputTree.checkDestination(input.outputRoot) and walks reader.entries(signal, traversal) via planSelectedEntries() without creating outputRoot, staging directories, or sidecar files.
  • src/contracts/artifactToolContracts.ts, src/cli/artifactCommands.ts, src/artifacts/ArtifactProvider.ts: Add dry_run?: boolean to artifactExtractionInputSchema and --dry-run to the CLI extract-artifact command, forwarding dryRun and platform through ArtifactProvider.
  • src/artifacts/extraction/ArtifactExtraction.test.ts & tests/boundary/providers/native/artifactProvider.extraction.test.ts: Add unit and provider boundary tests covering dry-run plans, zero destination writes, and parity of path-collision/invalid-name refusals between dry-run and real extraction.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/domain/artifactGraph.ts and src/artifacts/extraction/ArtifactExtraction.ts.
  • Contribution scope fit and linked maintainer decision: Implements #5489 (feat(artifacts): add dry-run plan for artifact extraction).
  • CLI and MCP/tool-catalog contract: Adds optional dry_run?: boolean to extract_artifact input and --dry-run to rea extract-artifact, and optional dry_run?: boolean + plan?: ArtifactExtractionPlan to artifactExtractionResultSchema.
  • Provider, bridge, target-format, or platform compatibility: Preserves platform-specific destination validation (win32 vs POSIX) across both dry-run and real extraction.
  • Evidence, artifact, provenance, or reconstruction contract: Dry-run results report created: false and bytes_written: 0 on selected entries while preserving verified inventory artifact_id and sha256 values and explicitly labeling byte estimates.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): SafeOutputTree.checkDestination runs before planning, and no staging directory or destination root is created when dryRun: true.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: Updated generated catalog metadata if applicable.

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:
    • src/artifacts/extraction/ArtifactExtraction.test.ts
    • tests/boundary/providers/native/artifactProvider.extraction.test.ts
  • Base reproduction or other evidence:
    • Executed: Verified on safe archive fixtures containing regular files, directories, and symlinks that dryRun: true produces plan.entries (planned, unsupported, unresolved) and plan.totals while leaving output_root nonexistent on disk, and rejects NFC path collisions and Windows : ADS names identically to dryRun: false.
  • User-visible CLI/MCP output (if applicable):
    • extract_artifact with dry_run: true returns dry_run: true and plan: { destination_root, entries, totals: { planned_files, unsupported_entries, unresolved_links, observed_bytes_estimate, declared_bytes_estimate, byte_totals_basis, byte_totals_note } }.
  • Remaining proof gaps: None.

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

  • npx vitest run src/artifacts/extraction/ArtifactExtraction.test.ts tests/boundary/providers/native/artifactProvider.extraction.test.ts — passed (39/39 tests).
  • npm run typecheck — passed (tsc --noEmit, 0 errors).
  • npm run format:check — passed (oxfmt --check .).
  • npm run lint — passed (oxlint 0 warnings/0 errors; verify:module-boundaries passed).
  • npm run verify:test-discovery — passed.
  • npm run verify:architecture-guards — passed.
  • npm run scan:todos — passed.
  • npm run jscpd — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: None (dry_run is optional and defaults to false).
  • Real Hopper/Ghidra, browser, or OS coverage: Tested with both POSIX and win32 platform normalization rules in ArtifactExtraction.test.ts.
  • Package or release metadata impact: None.
  • Security, privacy, process, or containment review: Ensures dry-run never writes to or creates output_root while enforcing identical path-traversal and collision checks.

Author readiness

Human owner: @hannesstrydom664-hash

  • 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/7177 **Author:** [@hannesstrydom664-hash](https://github.com/hannesstrydom664-hash) **Created:** 10/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/artifact-extraction-dry-run-5489` --- ### 📝 Commits (10+) - [`777b04a`](https://github.com/morluto/rea/commit/777b04a6eb016b39ba0b9c310cac2c16668a8174) feat(artifacts): add dry-run extraction plan without destination writes (#5489) - [`47f478c`](https://github.com/morluto/rea/commit/47f478c625e52cd4f7814acb251c954ceef51717) fix(artifacts): address dry-run extraction plan review feedback (#5489) - [`93c3ab3`](https://github.com/morluto/rea/commit/93c3ab39534cdeb61e3359d0cb0963e42b80cb5a) fix(artifacts): preserve unknown mount case sensitivity and use destination case folding in dry-run (#5489) - [`74029e0`](https://github.com/morluto/rea/commit/74029e0f77de522f450b7078f1b902fd582f89f4) fix(artifacts): handle hardlinked entries and leave non-ASCII case folds unresolved in dry-run (#5489) - [`77f9884`](https://github.com/morluto/rea/commit/77f98841b2c931597e48b88bc3fd262604046c42) fix(artifacts): bound case-sensitivity probes and observe Windows directories (#5489) - [`545c4e3`](https://github.com/morluto/rea/commit/545c4e3e70149edb29e6d9f6a8d53d8e31005298) fix(artifacts): verify dry-run directory freshness, over-limit paths, and case-probe close ownership - [`20ae0c4`](https://github.com/morluto/rea/commit/20ae0c47c010736af97dd55f0694d537a8d0d620) fix(artifacts): resolve canonical output path limits and full Unicode case folds in dry-run plan - [`a0bf542`](https://github.com/morluto/rea/commit/a0bf542f77136c5b7d672990fbd84049e977c3eb) fix(artifacts): revalidate unpacked ASAR companions and qualify unresolved collision limitation in dry-run - [`8f417b4`](https://github.com/morluto/rea/commit/8f417b44a03871b057a33107428cfc1b25b73319) fix(artifacts): reconcile non-file entries against the inventory snapshot in dry-run - [`041f0ef`](https://github.com/morluto/rea/commit/041f0efa4d820c99f6297f5487b99e91c7034ed0) fix(artifacts): scope non-file reconciliation to active reader and verify entry kinds ### 📊 Changes **17 files changed** (+3916 additions, -134 deletions) <details> <summary>View changed files</summary> 📝 `docs/mcp-contracts.md` (+18 -0) 📝 `docs/node-sea.md` (+1 -0) 📝 `src/application/environment/environmentBundleTool.ts` (+18 -0) 📝 `src/artifacts/ArtifactPaths.test.ts` (+55 -0) 📝 `src/artifacts/ArtifactPaths.ts` (+99 -20) 📝 `src/artifacts/ArtifactProvider.ts` (+8 -0) 📝 `src/artifacts/SafeOutputTree.ts` (+180 -19) ➕ `src/artifacts/extraction/ArtifactExtraction.sourceGuard.test.ts` (+128 -0) 📝 `src/artifacts/extraction/ArtifactExtraction.test.ts` (+1521 -3) 📝 `src/artifacts/extraction/ArtifactExtraction.ts` (+1071 -58) ➕ `src/artifacts/extraction/DryRunPlanCache.ts` (+383 -0) 📝 `src/cli/artifactCommands.ts` (+65 -4) 📝 `src/contracts/artifactToolContracts.ts` (+124 -22) 📝 `src/domain/artifactGraph.ts` (+58 -0) 📝 `src/firmware/FirmwareFiles.ts` (+5 -5) 📝 `src/firmware/FirmwareProvider.ts` (+3 -3) 📝 `tests/boundary/providers/native/artifactProvider.extraction.test.ts` (+179 -0) </details> ### 📄 Description ## Summary Fixes #5489 Adds a dry-run planning mode (`dry_run: true` / `--dry-run`) to `extract_artifact` so agents and operators can inspect what an extraction will materialize, verify destination admission and path-collision rules, and review labeled byte estimates before touching disk. ## Problem and expected behavior - **Smallest trigger:** Call `extract_artifact` (or CLI `rea extract-artifact`) when evaluating an archive or application package before deciding whether to materialize files on disk. - **Violated invariant:** Previously, `extract_artifact` always staged and moved extracted entries into `output_root`, providing no dry-run mode to validate destination path safety (Windows/POSIX reserved characters, NFC collisions, prefix collisions) and inspect planned vs. unsupported/unresolved entries without writing to disk. - **Expected behavior:** When `dry_run: true` (or `--dry-run`) is passed, `extract_artifact` validates `output_root` admission via `SafeOutputTree.checkDestination(input.outputRoot)`, traverses selected entries using the same `normalizeDestinationPath` and `ArtifactPathRegistry` rules as real extraction, creates zero destination directories/files or sidecar manifests, and returns a structured `plan` alongside `dry_run: true`. ## Change and scope Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Scoped enhancement implementing issue #5489 (`feat(artifacts): add dry-run plan for artifact extraction`). - `src/domain/artifactGraph.ts`: Add `artifactExtractionPlanEntrySchema`, `artifactExtractionPlanTotalsSchema`, and `artifactExtractionPlanSchema`, plus `dry_run` and `plan` fields on `artifactExtractionResultSchema`. Each non-root inventory occurrence is classified as `"planned"`, `"unsupported"` (directories, logical metadata declarations, or nested archive members not expanded during single-container extraction), or `"unresolved"` (symlinks), with byte totals explicitly labeled via `byte_totals_basis: "declared-and-observed-content-estimates"` and `byte_totals_note`. - `src/artifacts/SafeOutputTree.ts` & `src/artifacts/extraction/ArtifactExtraction.ts`: Export `normalizeDestinationPath(relativePath, platform)` so dry-run planning applies the exact same Windows/POSIX destination path rules (`\`, `:`, `U+0001-U+001F`, NFC normalization, and `ArtifactPathRegistry` prefix/collision checks) as `SafeOutputTree.prototype.write()`. When `dryRun: true`, `extractArtifact` validates the destination via `SafeOutputTree.checkDestination(input.outputRoot)` and walks `reader.entries(signal, traversal)` via `planSelectedEntries()` without creating `outputRoot`, staging directories, or sidecar files. - `src/contracts/artifactToolContracts.ts`, `src/cli/artifactCommands.ts`, `src/artifacts/ArtifactProvider.ts`: Add `dry_run?: boolean` to `artifactExtractionInputSchema` and `--dry-run` to the CLI `extract-artifact` command, forwarding `dryRun` and `platform` through `ArtifactProvider`. - `src/artifacts/extraction/ArtifactExtraction.test.ts` & `tests/boundary/providers/native/artifactProvider.extraction.test.ts`: Add unit and provider boundary tests covering dry-run plans, zero destination writes, and parity of path-collision/invalid-name refusals between dry-run and real extraction. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/domain/artifactGraph.ts` and `src/artifacts/extraction/ArtifactExtraction.ts`. - Contribution scope fit and linked maintainer decision: Implements #5489 (`feat(artifacts): add dry-run plan for artifact extraction`). - CLI and MCP/tool-catalog contract: Adds optional `dry_run?: boolean` to `extract_artifact` input and `--dry-run` to `rea extract-artifact`, and optional `dry_run?: boolean` + `plan?: ArtifactExtractionPlan` to `artifactExtractionResultSchema`. - Provider, bridge, target-format, or platform compatibility: Preserves platform-specific destination validation (`win32` vs POSIX) across both dry-run and real extraction. - Evidence, artifact, provenance, or reconstruction contract: Dry-run results report `created: false` and `bytes_written: 0` on selected entries while preserving verified inventory `artifact_id` and `sha256` values and explicitly labeling byte estimates. - Target selection, authority, upstream behavior, and cleanup details (if applicable): `SafeOutputTree.checkDestination` runs before planning, and no staging directory or destination root is created when `dryRun: true`. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: Updated generated catalog metadata if applicable. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: - `src/artifacts/extraction/ArtifactExtraction.test.ts` - `tests/boundary/providers/native/artifactProvider.extraction.test.ts` - Base reproduction or other evidence: - Executed: Verified on safe archive fixtures containing regular files, directories, and symlinks that `dryRun: true` produces `plan.entries` (`planned`, `unsupported`, `unresolved`) and `plan.totals` while leaving `output_root` nonexistent on disk, and rejects NFC path collisions and Windows `:` ADS names identically to `dryRun: false`. - User-visible CLI/MCP output (if applicable): - `extract_artifact` with `dry_run: true` returns `dry_run: true` and `plan: { destination_root, entries, totals: { planned_files, unsupported_entries, unresolved_links, observed_bytes_estimate, declared_bytes_estimate, byte_totals_basis, byte_totals_note } }`. - Remaining proof gaps: None. 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 - `npx vitest run src/artifacts/extraction/ArtifactExtraction.test.ts tests/boundary/providers/native/artifactProvider.extraction.test.ts` — passed (`39/39` tests). - `npm run typecheck` — passed (`tsc --noEmit`, 0 errors). - `npm run format:check` — passed (`oxfmt --check .`). - `npm run lint` — passed (`oxlint` 0 warnings/0 errors; `verify:module-boundaries` passed). - `npm run verify:test-discovery` — passed. - `npm run verify:architecture-guards` — passed. - `npm run scan:todos` — passed. - `npm run jscpd` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: None (`dry_run` is optional and defaults to `false`). - Real Hopper/Ghidra, browser, or OS coverage: Tested with both POSIX and `win32` platform normalization rules in `ArtifactExtraction.test.ts`. - Package or release metadata impact: None. - Security, privacy, process, or containment review: Ensures dry-run never writes to or creates `output_root` while enforcing identical path-traversal and collision checks. ## Author readiness Human owner: @hannesstrydom664-hash - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#7694
No description provided.