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 #6071] [MERGED] fix(process): name the Swift compile deadline #7139

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

📋 Pull Request Information

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

Base: main ← Head: cursor/swiftc-compile-deadline-19d7

📝 Commits (1)

  • 8dac533 fix(process): name the Swift compile deadline

📊 Changes

26 files changed (+321 additions, -95 deletions)

View changed files

📝 docs/installation.md (+4 -2)
📝 docs/kuna-provider.md (+1 -1)
📝 docs/mcp-contracts.md (+7 -7)
📝 docs/native-investigation.md (+4 -2)
📝 docs/process-capture.md (+9 -0)
📝 src/captures/TsharkCaptureProvider.ts (+7 -4)
📝 src/config/providerStartupTimeout.ts (+6 -3)
📝 src/contracts/officialToolContracts.ts (+2 -2)
📝 src/contracts/sessionToolContracts.ts (+1 -1)
📝 src/domain/fixedAllowanceRemediation.ts (+13 -0)
📝 src/domain/process/processScenario.test.ts (+16 -1)
📝 src/domain/process/processScenario.ts (+3 -3)
📝 src/process/ArtifactAnalysisResources.test.ts (+75 -1)
📝 src/process/ArtifactAnalysisResources.ts (+19 -10)
📝 src/process/DarwinProcessRunTokenReader.timeout.test.ts (+15 -1)
📝 src/process/DarwinProcessRunTokenReader.ts (+19 -4)
📝 src/process/ProcessOwnership.ts (+10 -11)
📝 src/process/ProcessOwnership.validation.test.ts (+3 -2)
📝 src/process/RegexMatcher.ts (+33 -23)
📝 src/process/ownedDebuggerSession.ts (+1 -1)

...and 6 more files

📄 Description

Summary

Names the existing REA_SWIFTC_COMPILE_TIMEOUT_MS control on a Darwin ownership-helper compile timeout, and says when REA retains a tighter inherited producer limit. Agent-visible fixed caps in the process/swiftc theme say this release has no runtime override. Part of #5910 (parent #5808). Numbers are unchanged.

Problem and expected behavior

A timed-out swiftc helper reported milliseconds without the setting name, the allowed range, the omitted default, or when a change applies. SIGXCPU and SIGXFSZ recovery did not say that REA keeps the tighter inherited ceiling. Other agent-visible process caps in this theme omitted the no-override sentence.

A timeout now names the effective REA_SWIFTC_COMPILE_TIMEOUT_MS value in milliseconds, the integer range 1..2147483647, and the omitted default of 120000 ms. The reader captures that value when it is created. Production creates systemProcessOwnershipHost from the launch environment at process start, so a change applies after REA restarts, on the next ownership-helper compile. Invalid ambient values still fall back to 120000 in the reader; parseConfig still rejects them at CLI/MCP admission.

Change and scope

Wording and error projection only. The timeout sentence is built from resolveSwiftcCompileTimeoutMs and MAX_PROVIDER_STARTUP_TIMEOUT_MS (the same schema bound as providerStartupTimeoutSchema). SIGXCPU and SIGXFSZ name the reported inherited address-space, file, and CPU ceilings and say REA retains the tighter inherited limit. Fixed producer command, input, and output allowances, the 512-byte compiler diagnostic excerpt, regex deadline and heap, terminal cell budget, debugger detach, and process-group revalidation say there is no runtime override.

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.

Not applicable. This stays inside existing process, capture, and signal error text. No new provider, target execution, injection, mutation, or protection recovery.

Out of scope: MCP (#6005), providers (#6014), JavaScript (#6022), Android (#6024), browser (#6036), native (#6059), engines, and ASAR. No settings tool. Internal poll intervals and stored bounds that are not an agent sentence are unchanged.

Contract and boundary impact

  • Semantic owner and earliest changed stage: process ownership and producer command projection; the swiftc deadline is read when the Darwin token reader is constructed.
  • Contribution scope fit and linked maintainer decision: not applicable. Wording within existing boundaries.
  • CLI and MCP/tool-catalog contract: recovery text and tool descriptions change. No new arguments or settings.
  • Provider, bridge, target-format, or platform compatibility: Darwin helper timeout text; Linux producer SIGXCPU/SIGXFSZ and sigrok/tshark limitation text. No behavior change on either platform.
  • Evidence, artifact, provenance, or reconstruction contract: none. Compiler outcome facts stay the same; the timeout message names the deadline that was already applied.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): cleanup still uses the same intervals. Failure reasons now include the fixed count and a no-override sentence.
  • 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): docs updated in docs/installation.md, docs/mcp-contracts.md, docs/process-capture.md, docs/kuna-provider.md, and docs/native-investigation.md. No package or catalog source change.

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: Darwin timeout unit and boundary tests, producer command projection, process-group revalidation, debugger detach, regex matcher, terminal cell budget, and sigrok/tshark SIGXFSZ recovery.
  • Base reproduction or other evidence: source inspection of resolveSwiftcCompileTimeoutMs, createDarwinProcessRunTokenReader, and systemProcessOwnershipHost. The control is REA_SWIFTC_COMPILE_TIMEOUT_MS in src/config/environment.ts, parsed by providerStartupTimeoutSchema (1..2147483647, default 120000).
  • User-visible CLI/MCP output (if applicable): a timeout includes The effective REA_SWIFTC_COMPILE_TIMEOUT_MS value is <ms> ms (integer range 1..2147483647; omitted default 120000 ms). Set it in the environment that starts REA and restart REA; the next ownership-helper compile uses the new value.
  • Remaining proof gaps: no real swiftc, Xcode, or prlimit run. Linux fixture compilers and projected errors only. A successful compile remains cached for the process, so the captured deadline also covers retries in that process.

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

  • npm run check:fast — typecheck and lint succeeded (turbo 2.11.7, 2 tasks, 5.723s).
  • npm run format:check — oxfmt reported all matched files correctly formatted.
  • npm run test:focused -- the ten process, swiftc, capture, and signal tests listed below — 10 files passed, 250 tests passed, 7 skipped.

Source: DarwinProcessRunTokenReader.timeout.test.ts, ArtifactAnalysisResources.test.ts, ProcessOwnership.validation.test.ts, processScenario.test.ts, fixedAllowanceRemediation.test.ts. Boundary: darwinProcessRunTokenReader.test.ts, ownedDebuggerSession.test.ts, regexMatcher.test.ts, captureProvider.test.ts, recordingProvider.test.ts.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Recovery text is more specific. Callers that match old timeout or cleanup sentences need to expect the added sentences.
  • Real Hopper/Ghidra, browser, or OS coverage: not run. No macOS swiftc or live prlimit producer.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no authority change. The SIGXCPU/SIGXFSZ sentence still says the signal's exact cause is not independently established. Inherited address space, file size, and CPU time stay clamped; command, input, and output budgets stay REA fixed caps.

Author readiness

Human owner: @morluto

  • 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.
Open in Web Open in Cursor 

🔄 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/6071 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/swiftc-compile-deadline-19d7` --- ### 📝 Commits (1) - [`8dac533`](https://github.com/morluto/rea/commit/8dac533fd594b2b1025c2a0a04612f3869c6df15) fix(process): name the Swift compile deadline ### 📊 Changes **26 files changed** (+321 additions, -95 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+4 -2) 📝 `docs/kuna-provider.md` (+1 -1) 📝 `docs/mcp-contracts.md` (+7 -7) 📝 `docs/native-investigation.md` (+4 -2) 📝 `docs/process-capture.md` (+9 -0) 📝 `src/captures/TsharkCaptureProvider.ts` (+7 -4) 📝 `src/config/providerStartupTimeout.ts` (+6 -3) 📝 `src/contracts/officialToolContracts.ts` (+2 -2) 📝 `src/contracts/sessionToolContracts.ts` (+1 -1) 📝 `src/domain/fixedAllowanceRemediation.ts` (+13 -0) 📝 `src/domain/process/processScenario.test.ts` (+16 -1) 📝 `src/domain/process/processScenario.ts` (+3 -3) 📝 `src/process/ArtifactAnalysisResources.test.ts` (+75 -1) 📝 `src/process/ArtifactAnalysisResources.ts` (+19 -10) 📝 `src/process/DarwinProcessRunTokenReader.timeout.test.ts` (+15 -1) 📝 `src/process/DarwinProcessRunTokenReader.ts` (+19 -4) 📝 `src/process/ProcessOwnership.ts` (+10 -11) 📝 `src/process/ProcessOwnership.validation.test.ts` (+3 -2) 📝 `src/process/RegexMatcher.ts` (+33 -23) 📝 `src/process/ownedDebuggerSession.ts` (+1 -1) _...and 6 more files_ </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Names the existing `REA_SWIFTC_COMPILE_TIMEOUT_MS` control on a Darwin ownership-helper compile timeout, and says when REA retains a tighter inherited producer limit. Agent-visible fixed caps in the process/swiftc theme say this release has no runtime override. Part of #5910 (parent #5808). Numbers are unchanged. ## Problem and expected behavior A timed-out `swiftc` helper reported milliseconds without the setting name, the allowed range, the omitted default, or when a change applies. SIGXCPU and SIGXFSZ recovery did not say that REA keeps the tighter inherited ceiling. Other agent-visible process caps in this theme omitted the no-override sentence. A timeout now names the effective `REA_SWIFTC_COMPILE_TIMEOUT_MS` value in milliseconds, the integer range 1..2147483647, and the omitted default of 120000 ms. The reader captures that value when it is created. Production creates `systemProcessOwnershipHost` from the launch environment at process start, so a change applies after REA restarts, on the next ownership-helper compile. Invalid ambient values still fall back to 120000 in the reader; `parseConfig` still rejects them at CLI/MCP admission. ## Change and scope Wording and error projection only. The timeout sentence is built from `resolveSwiftcCompileTimeoutMs` and `MAX_PROVIDER_STARTUP_TIMEOUT_MS` (the same schema bound as `providerStartupTimeoutSchema`). SIGXCPU and SIGXFSZ name the reported inherited address-space, file, and CPU ceilings and say REA retains the tighter inherited limit. Fixed producer command, input, and output allowances, the 512-byte compiler diagnostic excerpt, regex deadline and heap, terminal cell budget, debugger detach, and process-group revalidation say there is no runtime override. 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. Not applicable. This stays inside existing process, capture, and signal error text. No new provider, target execution, injection, mutation, or protection recovery. Out of scope: MCP (#6005), providers (#6014), JavaScript (#6022), Android (#6024), browser (#6036), native (#6059), engines, and ASAR. No settings tool. Internal poll intervals and stored bounds that are not an agent sentence are unchanged. ## Contract and boundary impact - Semantic owner and earliest changed stage: process ownership and producer command projection; the swiftc deadline is read when the Darwin token reader is constructed. - Contribution scope fit and linked maintainer decision: not applicable. Wording within existing boundaries. - CLI and MCP/tool-catalog contract: recovery text and tool descriptions change. No new arguments or settings. - Provider, bridge, target-format, or platform compatibility: Darwin helper timeout text; Linux producer SIGXCPU/SIGXFSZ and sigrok/tshark limitation text. No behavior change on either platform. - Evidence, artifact, provenance, or reconstruction contract: none. Compiler outcome facts stay the same; the timeout message names the deadline that was already applied. - Target selection, authority, upstream behavior, and cleanup details (if applicable): cleanup still uses the same intervals. Failure reasons now include the fixed count and a no-override sentence. - 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): docs updated in `docs/installation.md`, `docs/mcp-contracts.md`, `docs/process-capture.md`, `docs/kuna-provider.md`, and `docs/native-investigation.md`. No package or catalog source change. 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. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: Darwin timeout unit and boundary tests, producer command projection, process-group revalidation, debugger detach, regex matcher, terminal cell budget, and sigrok/tshark SIGXFSZ recovery. - Base reproduction or other evidence: source inspection of `resolveSwiftcCompileTimeoutMs`, `createDarwinProcessRunTokenReader`, and `systemProcessOwnershipHost`. The control is `REA_SWIFTC_COMPILE_TIMEOUT_MS` in `src/config/environment.ts`, parsed by `providerStartupTimeoutSchema` (`1..2147483647`, default `120000`). - User-visible CLI/MCP output (if applicable): a timeout includes `The effective REA_SWIFTC_COMPILE_TIMEOUT_MS value is <ms> ms (integer range 1..2147483647; omitted default 120000 ms). Set it in the environment that starts REA and restart REA; the next ownership-helper compile uses the new value.` - Remaining proof gaps: no real `swiftc`, Xcode, or `prlimit` run. Linux fixture compilers and projected errors only. A successful compile remains cached for the process, so the captured deadline also covers retries in that process. 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 - `npm run check:fast` — typecheck and lint succeeded (turbo 2.11.7, 2 tasks, 5.723s). - `npm run format:check` — oxfmt reported all matched files correctly formatted. - `npm run test:focused --` the ten process, swiftc, capture, and signal tests listed below — 10 files passed, 250 tests passed, 7 skipped. Source: `DarwinProcessRunTokenReader.timeout.test.ts`, `ArtifactAnalysisResources.test.ts`, `ProcessOwnership.validation.test.ts`, `processScenario.test.ts`, `fixedAllowanceRemediation.test.ts`. Boundary: `darwinProcessRunTokenReader.test.ts`, `ownedDebuggerSession.test.ts`, `regexMatcher.test.ts`, `captureProvider.test.ts`, `recordingProvider.test.ts`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Recovery text is more specific. Callers that match old timeout or cleanup sentences need to expect the added sentences. - Real Hopper/Ghidra, browser, or OS coverage: not run. No macOS `swiftc` or live `prlimit` producer. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no authority change. The SIGXCPU/SIGXFSZ sentence still says the signal's exact cause is not independently established. Inherited address space, file size, and CPU time stay clamped; command, input, and output budgets stay REA fixed caps. ## Author readiness Human owner: @morluto - [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. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-b0abc371-9120-5b11-b445-e9790d4619d7?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-b0abc371-9120-5b11-b445-e9790d4619d7&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <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:40 +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#7139
No description provided.