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 #5863] [MERGED] feat(firmware): make analysis deadlines recoverable per call #7092

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5863
Author: @gensokyo-dev
Created: 10/21/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @gensokyo-dev

Base: main ← Head: feat/20261021-firmware-timeout-recovery

📝 Commits (6)

  • 3b2aea4 feat(firmware): make analysis deadlines recoverable per call
  • 59d3a9e fix(firmware): classify cancellation during launcher admission
  • c93e6f6 fix(errors): retain one command capture through repeated cleanup
  • 320a4a4 fix(firmware): retain interruptions observed during command cleanup
  • ef70dba test(errors): assert canonical output ownership in cleanup consumers
  • 272f9fb test(errors): verify capture ownership across decoder cleanup consumers

📊 Changes

23 files changed (+843 additions, -118 deletions)

View changed files

📝 docs/firmware-analysis.md (+12 -1)
📝 src/application/binary/AnalysisClientCleanup.test.ts (+14 -3)
📝 src/application/firmware/FirmwareAnalysisService.test.ts (+129 -47)
📝 src/application/firmware/FirmwareAnalysisService.ts (+17 -0)
📝 src/cli/firmwareCommands.ts (+12 -2)
📝 src/contracts/firmware/firmwareToolContracts.ts (+1 -1)
📝 src/domain/analysisErrorCleanup.test.ts (+62 -2)
📝 src/domain/analysisErrorCleanup.ts (+8 -2)
📝 src/domain/analysisErrorProjection.ts (+11 -1)
📝 src/domain/firmware/firmwareAnalysis.ts (+21 -6)
📝 src/firmware/FirmwareCommand.test.ts (+97 -2)
📝 src/firmware/FirmwareCommand.ts (+67 -26)
📝 src/firmware/FirmwareDeadline.test.ts (+56 -0)
📝 src/firmware/FirmwareFailures.ts (+5 -1)
📝 src/firmware/FirmwareProvider.ts (+7 -2)
📝 src/firmware/FirmwarePublication.ts (+2 -0)
📝 src/firmware/FirmwareRelease.ts (+1 -1)
📝 src/sqlite/SqliteDatabaseFailures.ts (+8 -8)
📝 tests/boundary/binaryDiagnostics/pwntoolsLayoutProvider.test.ts (+17 -1)
📝 tests/composition/directAnalysisCleanup.test.ts (+15 -3)

...and 3 more files

📄 Description

Summary

Fixes #5851. Firmware agents can now adjust the analysis wall-clock budget independently of publication. Previously both provider and command layers imposed a hidden fixed 120-second analysis cap.

Problem and expected behavior

Both firmware tools accept optional analysis_timeout_ms / CLI --analysis-timeout-ms (default 120000; integer 1..2147483647). A timeout identifies the actual phase/budget and exact adjustment, preserves the question/input, and explains client headroom, cleanup and unchanged fixed limits. publication_timeout_ms cannot repair an analysis timeout.

Change and scope

One provider-owned deadline spans tool resolution, snapshot and commands. Inspection includes final workspace cleanup; extraction ends analysis at inventory, then uses its independent publication/final-cleanup budget. Queue/retained-cleanup admission is excluded. Remove the command's competing clock. Full/completed-partial results retain actual settings; historical omissions stay unknown and explicit selection stays explicit. Shared validation checks only small execution metadata, not the entire inventory again. Normalize observed launcher cancellation at its boundary and preserve interruptions during command cleanup without replacing earlier failures. Shared error history now reuses one projection owner (including SQLite), retaining each command capture once through failed CLI close.

No new provider/capability, target execution, sandbox relaxation, installation behavior or larger CPU/memory/byte allowance. Maintainer scope decision: not applicable to this ordinary fix within existing firmware authority. Staging refusal classification (#5846), arbitrary kill attribution and other providers are outside this change.

Contract and boundary impact

  • Semantic owner: firmware domain contracts and provider-owned phase deadline.
  • CLI/MCP: same named optional timer contract and shared application workflow; advertised input/output schemas checked after SDK conversion.
  • Compatibility: Linux; caller-supplied Binwalk 3.1.x / Unblob 26.6.x and existing prlimit. Fixed per-process CPU remains 120 seconds.
  • Evidence: input path/digest/range, coverage, gaps and raw producer observations retained. Old absent budget is not assigned a fictional default; fresh results must retain selected/default budget.
  • Cleanup: exact existing owned process/workspace leases, no server restart after confirmed release; absent extraction destinations remain required.
  • Generated metadata: ignored catalog/skill outputs only; no package/dependency changes or committed binaries.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process. Existing supplied analyzers only.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration. Existing private staging and explicitly selected extraction output only; no source/configuration mutation.
  • 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

Executed fail-before: 12 failures / 10 passes initially; admission cancellation 4 failures / 5 passes; repeated-close capture 1 failure / 15 passes; interruption during command cleanup 3 failures / 18 passes. Final head 272f9fb15: 535 passed / 4 platform skips across 39 exact firmware/SQLite/shared-error/CLI/native/managed/pwntools/PCAP/WABT files (151.06s). Independent queued settings, monotonic expiry, opaque reasons, completed partial facts and cleanup resolution covered. The full capture-consumer audit is 189 passed / 1 skip across 13 files. Four old history assertions exposed by Source/built CI migrated to canonical primary capture; pwntools' existing cleanup-owner snapshot remains intact, without a third generic-history copy or text-based deduplication. Subsequent commits are test-only; runtime is identical to 320a4a436.

Actual isolated Binwalk 3.1.0 / Unblob 26.6.4: baseline and initial public verifier passed independent gzip/USTAR/compiled-ELF offsets/digests, range, unknown-chunk and depth checks. Nine extra paired CLI/MCP cases cover default/selected/max settings, both 1ms analysis timeouts, publication timeout and fixed oversized refusal. A full run passed on c93e6f6b; final-head repeat had 17/18 expected endpoint outcomes, with one selected-budget MCP scan blocked by baseline report-missing #5876 (also reproduced 2/12 on pre-PR f801b2fb). Successful observations passed SDK-converted AJV 2020 schemas, bounds, immutable-source/oracle and retained-Evidence readback checks. No all-green real-provider claim.

Actual Codex CLI gpt-6.1-sol: 18 qualification attempts, 16 REA-dispatched: 10 corrected successes + 6 accurate blockers (missing providers, executable, prlimit, wrong version, fixed input cap); two zero-call tool-unavailable reports are not product passes. Latest head again corrected 1ms to 120000ms. No unchanged failed retries, shell/unexpected tools or surviving sampled PIDs. Controlled 121-second actual-tool startup experiment exceeded the old cap successfully with 135000ms on reviewed implementations; a later attempt hit baseline #5876, not a timeout. Whole completed-session costs, harness mistakes, exact oracle and limitations are in the executed evidence.

  • 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

  • npm run test:focused -- <39 exact test files> — 535 passed / 4 platform skips, 151.06s; required artifacts built.
  • npm run check:fast — typecheck and lint passed, 62.76s.
  • npm run docs:check — generated checks and 5 consistency tests passed.
  • Architecture guards / test discovery — passed across 1699 source / 1902 test files.
  • node scripts/verify/firmware/analysis.mjs — real public verifier passed on baseline and current runtime with the same independently generated fixture.
  • Ignored public.mjs — nine CLI/MCP cases; final 17/18 expected outcomes, one independently reproduced baseline #5876; schemas/Evidence/oracle checked for actual successful results.
  • git diff --check — passed.

Compatibility, safety, and release

Additive caller control; historical Evidence readable; default sandbox/fixed resource limits unchanged. No target/extracted-code execution, mounts or aggregate containment claim. Real-engine scope: Linux x64, small generated fixture, not vendor/large firmware or non-Linux. All 22 completed Codex sessions including four setup mistakes: 2,164,724 input / 1,780,096 cached / 11,988 output tokens, 655.47s wall / 201.73s local CPU, 1261.93 MiB max sampled family RSS (500ms). One interrupted harness session and build/setup/CI costs are unmeasured; caches uncontrolled, no cold-cache or speedup claim. Known baseline CI requiredness-test issue #5845 is outside this PR; no unrelated gate/test weakening.

Author readiness

Human owner: @gensokyo-dev (account selected by the user).

  • 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.

The user explicitly directed ready-for-review creation and authorized technical/admin merge. This is not an attestation that a human inspected the final diff or evidence; those declarations remain unchecked.

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/5863 **Author:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Base:** `main` ← **Head:** `feat/20261021-firmware-timeout-recovery` --- ### 📝 Commits (6) - [`3b2aea4`](https://github.com/morluto/rea/commit/3b2aea45dd8909b9e783dfd2211eabc86a01ab58) feat(firmware): make analysis deadlines recoverable per call - [`59d3a9e`](https://github.com/morluto/rea/commit/59d3a9ed9d8b2b26069730bf6f82559910f72445) fix(firmware): classify cancellation during launcher admission - [`c93e6f6`](https://github.com/morluto/rea/commit/c93e6f6b7b35026284f013428c6d695e8cdcf9f6) fix(errors): retain one command capture through repeated cleanup - [`320a4a4`](https://github.com/morluto/rea/commit/320a4a436296b1832b771f301a1aeb8e0118baf8) fix(firmware): retain interruptions observed during command cleanup - [`ef70dba`](https://github.com/morluto/rea/commit/ef70dbafcb6de1c8fea5c54e6c99e64b7b6226b9) test(errors): assert canonical output ownership in cleanup consumers - [`272f9fb`](https://github.com/morluto/rea/commit/272f9fb15910deb656f4c8786f61f2ba3d0c08c9) test(errors): verify capture ownership across decoder cleanup consumers ### 📊 Changes **23 files changed** (+843 additions, -118 deletions) <details> <summary>View changed files</summary> 📝 `docs/firmware-analysis.md` (+12 -1) 📝 `src/application/binary/AnalysisClientCleanup.test.ts` (+14 -3) 📝 `src/application/firmware/FirmwareAnalysisService.test.ts` (+129 -47) 📝 `src/application/firmware/FirmwareAnalysisService.ts` (+17 -0) 📝 `src/cli/firmwareCommands.ts` (+12 -2) 📝 `src/contracts/firmware/firmwareToolContracts.ts` (+1 -1) 📝 `src/domain/analysisErrorCleanup.test.ts` (+62 -2) 📝 `src/domain/analysisErrorCleanup.ts` (+8 -2) 📝 `src/domain/analysisErrorProjection.ts` (+11 -1) 📝 `src/domain/firmware/firmwareAnalysis.ts` (+21 -6) 📝 `src/firmware/FirmwareCommand.test.ts` (+97 -2) 📝 `src/firmware/FirmwareCommand.ts` (+67 -26) 📝 `src/firmware/FirmwareDeadline.test.ts` (+56 -0) 📝 `src/firmware/FirmwareFailures.ts` (+5 -1) 📝 `src/firmware/FirmwareProvider.ts` (+7 -2) 📝 `src/firmware/FirmwarePublication.ts` (+2 -0) 📝 `src/firmware/FirmwareRelease.ts` (+1 -1) 📝 `src/sqlite/SqliteDatabaseFailures.ts` (+8 -8) 📝 `tests/boundary/binaryDiagnostics/pwntoolsLayoutProvider.test.ts` (+17 -1) 📝 `tests/composition/directAnalysisCleanup.test.ts` (+15 -3) _...and 3 more files_ </details> ### 📄 Description ## Summary Fixes #5851. Firmware agents can now adjust the analysis wall-clock budget independently of publication. Previously both provider and command layers imposed a hidden fixed 120-second analysis cap. ## Problem and expected behavior Both firmware tools accept optional `analysis_timeout_ms` / CLI `--analysis-timeout-ms` (default 120000; integer 1..2147483647). A timeout identifies the actual phase/budget and exact adjustment, preserves the question/input, and explains client headroom, cleanup and unchanged fixed limits. `publication_timeout_ms` cannot repair an analysis timeout. ## Change and scope One provider-owned deadline spans tool resolution, snapshot and commands. Inspection includes final workspace cleanup; extraction ends analysis at inventory, then uses its independent publication/final-cleanup budget. Queue/retained-cleanup admission is excluded. Remove the command's competing clock. Full/completed-partial results retain actual settings; historical omissions stay unknown and explicit selection stays explicit. Shared validation checks only small execution metadata, not the entire inventory again. Normalize observed launcher cancellation at its boundary and preserve interruptions during command cleanup without replacing earlier failures. Shared error history now reuses one projection owner (including SQLite), retaining each command capture once through failed CLI close. No new provider/capability, target execution, sandbox relaxation, installation behavior or larger CPU/memory/byte allowance. Maintainer scope decision: not applicable to this ordinary fix within existing firmware authority. Staging refusal classification (#5846), arbitrary kill attribution and other providers are outside this change. ## Contract and boundary impact - Semantic owner: firmware domain contracts and provider-owned phase deadline. - CLI/MCP: same named optional timer contract and shared application workflow; advertised input/output schemas checked after SDK conversion. - Compatibility: Linux; caller-supplied Binwalk 3.1.x / Unblob 26.6.x and existing prlimit. Fixed per-process CPU remains 120 seconds. - Evidence: input path/digest/range, coverage, gaps and raw producer observations retained. Old absent budget is not assigned a fictional default; fresh results must retain selected/default budget. - Cleanup: exact existing owned process/workspace leases, no server restart after confirmed release; absent extraction destinations remain required. - Generated metadata: ignored catalog/skill outputs only; no package/dependency changes or committed binaries. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. Existing supplied analyzers only. - [ ] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. Existing private staging and explicitly selected extraction output only; no source/configuration mutation. - [ ] 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 Executed fail-before: 12 failures / 10 passes initially; admission cancellation 4 failures / 5 passes; repeated-close capture 1 failure / 15 passes; interruption during command cleanup 3 failures / 18 passes. Final head `272f9fb15`: **535 passed / 4 platform skips across 39 exact firmware/SQLite/shared-error/CLI/native/managed/pwntools/PCAP/WABT files (151.06s)**. Independent queued settings, monotonic expiry, opaque reasons, completed partial facts and cleanup resolution covered. The full capture-consumer audit is 189 passed / 1 skip across 13 files. Four old history assertions exposed by Source/built CI migrated to canonical primary capture; pwntools' existing cleanup-owner snapshot remains intact, without a third generic-history copy or text-based deduplication. Subsequent commits are test-only; runtime is identical to `320a4a436`. Actual isolated Binwalk 3.1.0 / Unblob 26.6.4: baseline and initial public verifier passed independent gzip/USTAR/compiled-ELF offsets/digests, range, unknown-chunk and depth checks. Nine extra paired CLI/MCP cases cover default/selected/max settings, both 1ms analysis timeouts, publication timeout and fixed oversized refusal. A full run passed on `c93e6f6b`; final-head repeat had **17/18 expected endpoint outcomes**, with one selected-budget MCP scan blocked by baseline report-missing #5876 (also reproduced 2/12 on pre-PR f801b2fb). Successful observations passed SDK-converted AJV 2020 schemas, bounds, immutable-source/oracle and retained-Evidence readback checks. No all-green real-provider claim. Actual Codex CLI gpt-6.1-sol: **18 qualification attempts, 16 REA-dispatched: 10 corrected successes + 6 accurate blockers** (missing providers, executable, prlimit, wrong version, fixed input cap); two zero-call tool-unavailable reports are not product passes. Latest head again corrected 1ms to 120000ms. No unchanged failed retries, shell/unexpected tools or surviving sampled PIDs. Controlled 121-second actual-tool startup experiment exceeded the old cap successfully with 135000ms on reviewed implementations; a later attempt hit baseline #5876, not a timeout. Whole completed-session costs, harness mistakes, exact oracle and limitations are in the [executed evidence](https://github.com/morluto/rea/issues/5851#issuecomment-6313469058). - [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 - `npm run test:focused -- <39 exact test files>` — 535 passed / 4 platform skips, 151.06s; required artifacts built. - `npm run check:fast` — typecheck and lint passed, 62.76s. - `npm run docs:check` — generated checks and 5 consistency tests passed. - Architecture guards / test discovery — passed across 1699 source / 1902 test files. - `node scripts/verify/firmware/analysis.mjs` — real public verifier passed on baseline and current runtime with the same independently generated fixture. - Ignored `public.mjs` — nine CLI/MCP cases; final 17/18 expected outcomes, one independently reproduced baseline #5876; schemas/Evidence/oracle checked for actual successful results. - `git diff --check` — passed. ## Compatibility, safety, and release Additive caller control; historical Evidence readable; default sandbox/fixed resource limits unchanged. No target/extracted-code execution, mounts or aggregate containment claim. Real-engine scope: Linux x64, small generated fixture, not vendor/large firmware or non-Linux. All 22 completed Codex sessions including four setup mistakes: 2,164,724 input / 1,780,096 cached / 11,988 output tokens, 655.47s wall / 201.73s local CPU, 1261.93 MiB max sampled family RSS (500ms). One interrupted harness session and build/setup/CI costs are unmeasured; caches uncontrolled, no cold-cache or speedup claim. Known baseline CI requiredness-test issue #5845 is outside this PR; no unrelated gate/test weakening. ## Author readiness Human owner: @gensokyo-dev (account selected by the user). - [ ] 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. - [x] I declare this PR ready for initial maintainer review. The user explicitly directed ready-for-review creation and authorized technical/admin merge. This is not an attestation that a human inspected the final diff or evidence; those declarations remain unchecked. ## 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>
bsakaguchi 2026-11-01 21:45:19 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

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

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7092
No description provided.