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 #6267] [MERGED] feat(config): make the regex matching deadline configurable #7242

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

📋 Pull Request Information

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

Base: main ← Head: cursor/regex-matching-deadline-b35c

📝 Commits (3)

  • ae96ddb feat(config): make the regex matching deadline configurable
  • 87456fc fix(setup): preserve the regex matching deadline in registrations
  • 609f0be test(config): restore a stubbed regex matching deadline on failure

📊 Changes

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

View changed files

📝 docs/kuna-provider.md (+1 -1)
📝 docs/native-investigation.md (+11 -3)
📝 scripts/lib/test-projects.mjs (+1 -1)
📝 src/application/Doctor.test.ts (+1 -0)
📝 src/application/SetupRegistrationEnvironment.ts (+1 -0)
📝 src/composition/binary.ts (+3 -1)
📝 src/config/environment.ts (+2 -0)
📝 src/config/parseConfig.ts (+8 -0)
➕ src/config/regexMatchingDeadline.test.ts (+136 -0)
➕ src/config/regexMatchingDeadline.ts (+92 -0)
📝 src/config/types.ts (+3 -0)
📝 src/contracts/officialToolContracts.ts (+5 -2)
📝 src/hopper/HopperProvider.ts (+9 -4)
📝 src/hopper/HopperProviderCapabilities.ts (+53 -45)
📝 src/hopper/HopperRegexSearch.ts (+9 -1)
📝 src/kuna/KunaProvider.ts (+15 -0)
📝 src/kuna/KunaProviderCapabilities.ts (+10 -4)
📝 src/kuna/KunaQueryWork.ts (+6 -0)
📝 src/kuna/KunaSessionClient.ts (+15 -7)
📝 src/process/RegexMatcher.test.ts (+6 -4)

...and 6 more files

📄 Description

Summary

Part of #6176. The supervised ECMAScript regex matching deadline is now REA_REGEX_MATCHING_DEADLINE_MS. Unset still uses 5000 ms. This does not cover the issue's later decoder-heap or MCP startup budgets.

Problem and expected behavior

MATCHING_DEADLINE_MS was a fixed 5000 ms, and capability, limitation, and recovery text said this release has no runtime override. Callers need a named setting whose default is that constant, with invalid values refused and recovery that names the setting, effective milliseconds, source (default or setting), default, floor, and maximum.

A caller override such as REA_REGEX_MATCHING_DEADLINE_MS=10000 rea setup was validated and then omitted from setup-created MCP registrations, so the launched server returned to 5000 ms.

Change and scope

src/config/regexMatchingDeadline.ts owns the setting. Startup (parseConfig) and doctor (parseEnvironment) resolve it with the same schema. The effective deadline is stored on AppConfig and passed into Hopper and Kuna, which pass it to RegexMatcher. A direct KunaProvider resolves the selected environment instead of ambient process.env.

Setup now keeps REA_REGEX_MATCHING_DEADLINE_MS in SELECTED_REGISTRATION_SETTINGS, with the other caller-selected registration settings. A present value is copied into the generated registration. An unset value is omitted.

The floor is 1 ms. The maximum is 2147483647 ms, the largest delay Node schedules exactly; a larger setTimeout delay is clamped to 1 ms, so it is refused rather than left unbounded. Zero, negative, non-decimal, and out-of-range values are configuration_invalid and do not fall back to 5000. The schema does not trim whitespace.

Follow the contribution scope. This is an ordinary configuration of an existing matching deadline. It does not add target execution, injection, mutation, or protection recovery. Maintainer scope decision: not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/config/regexMatchingDeadline.ts parses the setting; parseConfig resolves it before providers match. explicitSetupRegistrationEnvironment preserves a caller-selected value when setup writes a registration.
  • Contribution scope fit and linked maintainer decision: existing regex matching only; not applicable.
  • CLI and MCP/tool-catalog contract: search_procedures and search_strings descriptions name REA_REGEX_MATCHING_DEADLINE_MS, the 5000 ms default, and the 2147483647 ms maximum. Capability and deadline failures name the effective value and source.
  • Provider, bridge, target-format, or platform compatibility: Hopper and Kuna share the deadline. The worker heap flags are unchanged and do not raise it.
  • Evidence, artifact, provenance, or reconstruction contract: deadline failures add matching_deadline_source beside matching_deadline_ms.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): none.
  • 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): tool descriptions changed in source contracts. No authored skill text claimed the deadline had no override.

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: parser and startup rejection; doctor and client-registration rejection; Hopper/Kuna capability text; worker timer armed at 10000 ms; a 100 ms deadline stops a slow match; the Kuna boundary probe still waits the unset 5000 ms deadline and a selected REA_REGEX_MATCHING_DEADLINE_MS=200 stops early. Ambient process.env does not override the selected environment. The Kuna capability assertion restores stubbed environment in finally. Setup-host state includes 10000 when set and omits the key when unset. Public Codex and Kimi setup writes REA_REGEX_MATCHING_DEADLINE_MS=10000 and still omits REA_UNRELATED_MARKER.
  • Base reproduction or other evidence: on main the deadline constant is 5000 and recovery says there is no runtime override. The unset Kuna probe still reports matching_deadline_ms: 5000 and takes about 5.4 s. Before this fix, SELECTED_REGISTRATION_SETTINGS did not include the deadline, so setup-created registrations dropped the override.
  • User-visible CLI/MCP output (if applicable): a deadline failure for the default says The effective REA_REGEX_MATCHING_DEADLINE_MS value is 5000 ms (source default; default 5000 ms, floor 1 ms, maximum 2147483647 ms). Set REA_REGEX_MATCHING_DEADLINE_MS in the environment that starts REA to a positive decimal integer from 1 to 2147483647, then restart REA. A 10000 ms setting uses source setting and 10000 ms.
  • Remaining proof gaps: no real Hopper or Kuna binary was used. The Kuna probe uses the fake Kuna executable and the production regex worker.

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 test:local -- src/config/regexMatchingDeadline.test.ts src/application/Doctor.test.ts — 74 passed.
  • npm run test:local -- src/config/regexMatchingDeadline.test.ts src/process/RegexMatcher.test.ts src/hopper/HopperProvider.test.ts — parser, matcher, and Hopper provider tests passed (the first parser run found and fixed schema/assertion failures; the rerun passed).
  • npm run check:fast — typecheck and lint passed (rerun on this fix; passed).
  • npm run format:check — passed on the previous head. This fix was covered by check:fast lint.
  • npm run test:focused -- tests/boundary/process/regexMatcher.test.ts tests/boundary/providers/kuna/kunaRegexSearch.test.ts tests/boundary/filesystem/clientConfigurationEnvironment.test.ts src/config/regexMatchingDeadline.test.ts src/process/RegexMatcher.test.ts — 107 passed, 10 skipped. Unset Kuna deadline probes took 5409 ms and 5356 ms. REA_REGEX_MATCHING_DEADLINE_MS=200 on the selected environment finished in 568 ms and reported source setting.
  • npm run test:local -- src/config/regexMatchingDeadline.test.ts src/setupEnvironment.test.ts — 23 passed.
  • npm run test:focused -- tests/acceptance/setup/registrationRuntimeEnvironmentCli.test.ts — 15 passed, 1 skipped. Codex and Kimi setup preserved 10000.

Compatibility, safety, and release

  • Breaking changes or migration steps: none for an unset environment. The deadline remains 5000 ms. User-facing text no longer says the deadline has no runtime override; it names REA_REGEX_MATCHING_DEADLINE_MS. Invalid values that were previously ignored, because the variable was unread, now fail configuration. An existing registration created before this fix does not gain the override until setup runs again with the setting present.
  • Real Hopper/Ghidra, browser, or OS coverage: not run. Deadline behavior was measured with the production regex worker and the fake Kuna probe.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the worker is still terminated when the deadline fires. The heap request is unchanged. A longer deadline only extends that existing supervision.

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/6267 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/22/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/regex-matching-deadline-b35c` --- ### 📝 Commits (3) - [`ae96ddb`](https://github.com/morluto/rea/commit/ae96ddbe3e6ae1cafb5261e9e5a636d1d4c82e44) feat(config): make the regex matching deadline configurable - [`87456fc`](https://github.com/morluto/rea/commit/87456fc08bb8c357ca36c7b96615837c26360fa4) fix(setup): preserve the regex matching deadline in registrations - [`609f0be`](https://github.com/morluto/rea/commit/609f0be2b6042eee25aa30fad9b23d7df332c877) test(config): restore a stubbed regex matching deadline on failure ### 📊 Changes **26 files changed** (+588 additions, -95 deletions) <details> <summary>View changed files</summary> 📝 `docs/kuna-provider.md` (+1 -1) 📝 `docs/native-investigation.md` (+11 -3) 📝 `scripts/lib/test-projects.mjs` (+1 -1) 📝 `src/application/Doctor.test.ts` (+1 -0) 📝 `src/application/SetupRegistrationEnvironment.ts` (+1 -0) 📝 `src/composition/binary.ts` (+3 -1) 📝 `src/config/environment.ts` (+2 -0) 📝 `src/config/parseConfig.ts` (+8 -0) ➕ `src/config/regexMatchingDeadline.test.ts` (+136 -0) ➕ `src/config/regexMatchingDeadline.ts` (+92 -0) 📝 `src/config/types.ts` (+3 -0) 📝 `src/contracts/officialToolContracts.ts` (+5 -2) 📝 `src/hopper/HopperProvider.ts` (+9 -4) 📝 `src/hopper/HopperProviderCapabilities.ts` (+53 -45) 📝 `src/hopper/HopperRegexSearch.ts` (+9 -1) 📝 `src/kuna/KunaProvider.ts` (+15 -0) 📝 `src/kuna/KunaProviderCapabilities.ts` (+10 -4) 📝 `src/kuna/KunaQueryWork.ts` (+6 -0) 📝 `src/kuna/KunaSessionClient.ts` (+15 -7) 📝 `src/process/RegexMatcher.test.ts` (+6 -4) _...and 6 more files_ </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Part of #6176. The supervised ECMAScript regex matching deadline is now `REA_REGEX_MATCHING_DEADLINE_MS`. Unset still uses 5000 ms. This does not cover the issue's later decoder-heap or MCP startup budgets. ## Problem and expected behavior `MATCHING_DEADLINE_MS` was a fixed 5000 ms, and capability, limitation, and recovery text said this release has no runtime override. Callers need a named setting whose default is that constant, with invalid values refused and recovery that names the setting, effective milliseconds, source (`default` or `setting`), default, floor, and maximum. A caller override such as `REA_REGEX_MATCHING_DEADLINE_MS=10000 rea setup` was validated and then omitted from setup-created MCP registrations, so the launched server returned to 5000 ms. ## Change and scope `src/config/regexMatchingDeadline.ts` owns the setting. Startup (`parseConfig`) and doctor (`parseEnvironment`) resolve it with the same schema. The effective deadline is stored on `AppConfig` and passed into Hopper and Kuna, which pass it to `RegexMatcher`. A direct `KunaProvider` resolves the selected environment instead of ambient `process.env`. Setup now keeps `REA_REGEX_MATCHING_DEADLINE_MS` in `SELECTED_REGISTRATION_SETTINGS`, with the other caller-selected registration settings. A present value is copied into the generated registration. An unset value is omitted. The floor is 1 ms. The maximum is 2147483647 ms, the largest delay Node schedules exactly; a larger `setTimeout` delay is clamped to 1 ms, so it is refused rather than left unbounded. Zero, negative, non-decimal, and out-of-range values are `configuration_invalid` and do not fall back to 5000. The schema does not trim whitespace. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). This is an ordinary configuration of an existing matching deadline. It does not add target execution, injection, mutation, or protection recovery. Maintainer scope decision: not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/config/regexMatchingDeadline.ts` parses the setting; `parseConfig` resolves it before providers match. `explicitSetupRegistrationEnvironment` preserves a caller-selected value when setup writes a registration. - Contribution scope fit and linked maintainer decision: existing regex matching only; not applicable. - CLI and MCP/tool-catalog contract: `search_procedures` and `search_strings` descriptions name `REA_REGEX_MATCHING_DEADLINE_MS`, the 5000 ms default, and the 2147483647 ms maximum. Capability and deadline failures name the effective value and source. - Provider, bridge, target-format, or platform compatibility: Hopper and Kuna share the deadline. The worker heap flags are unchanged and do not raise it. - Evidence, artifact, provenance, or reconstruction contract: deadline failures add `matching_deadline_source` beside `matching_deadline_ms`. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none. - 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): tool descriptions changed in source contracts. No authored skill text claimed the deadline had no override. 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: parser and startup rejection; doctor and client-registration rejection; Hopper/Kuna capability text; worker timer armed at 10000 ms; a 100 ms deadline stops a slow match; the Kuna boundary probe still waits the unset 5000 ms deadline and a selected `REA_REGEX_MATCHING_DEADLINE_MS=200` stops early. Ambient `process.env` does not override the selected environment. The Kuna capability assertion restores stubbed environment in `finally`. Setup-host state includes `10000` when set and omits the key when unset. Public Codex and Kimi setup writes `REA_REGEX_MATCHING_DEADLINE_MS=10000` and still omits `REA_UNRELATED_MARKER`. - Base reproduction or other evidence: on main the deadline constant is 5000 and recovery says there is no runtime override. The unset Kuna probe still reports `matching_deadline_ms: 5000` and takes about 5.4 s. Before this fix, `SELECTED_REGISTRATION_SETTINGS` did not include the deadline, so setup-created registrations dropped the override. - User-visible CLI/MCP output (if applicable): a deadline failure for the default says `The effective REA_REGEX_MATCHING_DEADLINE_MS value is 5000 ms (source default; default 5000 ms, floor 1 ms, maximum 2147483647 ms). Set REA_REGEX_MATCHING_DEADLINE_MS in the environment that starts REA to a positive decimal integer from 1 to 2147483647, then restart REA.` A 10000 ms setting uses `source setting` and `10000 ms`. - Remaining proof gaps: no real Hopper or Kuna binary was used. The Kuna probe uses the fake Kuna executable and the production regex worker. 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 test:local -- src/config/regexMatchingDeadline.test.ts src/application/Doctor.test.ts` — 74 passed. - `npm run test:local -- src/config/regexMatchingDeadline.test.ts src/process/RegexMatcher.test.ts src/hopper/HopperProvider.test.ts` — parser, matcher, and Hopper provider tests passed (the first parser run found and fixed schema/assertion failures; the rerun passed). - `npm run check:fast` — typecheck and lint passed (rerun on this fix; passed). - `npm run format:check` — passed on the previous head. This fix was covered by `check:fast` lint. - `npm run test:focused -- tests/boundary/process/regexMatcher.test.ts tests/boundary/providers/kuna/kunaRegexSearch.test.ts tests/boundary/filesystem/clientConfigurationEnvironment.test.ts src/config/regexMatchingDeadline.test.ts src/process/RegexMatcher.test.ts` — 107 passed, 10 skipped. Unset Kuna deadline probes took 5409 ms and 5356 ms. `REA_REGEX_MATCHING_DEADLINE_MS=200` on the selected environment finished in 568 ms and reported source `setting`. - `npm run test:local -- src/config/regexMatchingDeadline.test.ts src/setupEnvironment.test.ts` — 23 passed. - `npm run test:focused -- tests/acceptance/setup/registrationRuntimeEnvironmentCli.test.ts` — 15 passed, 1 skipped. Codex and Kimi setup preserved `10000`. ## Compatibility, safety, and release - Breaking changes or migration steps: none for an unset environment. The deadline remains 5000 ms. User-facing text no longer says the deadline has no runtime override; it names `REA_REGEX_MATCHING_DEADLINE_MS`. Invalid values that were previously ignored, because the variable was unread, now fail configuration. An existing registration created before this fix does not gain the override until setup runs again with the setting present. - Real Hopper/Ghidra, browser, or OS coverage: not run. Deadline behavior was measured with the production regex worker and the fake Kuna probe. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the worker is still terminated when the deadline fires. The heap request is unchanged. A longer deadline only extends that existing supervision. ## 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 - [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. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-2e60afce-9d76-5143-b7d9-f1a858fdb35c?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-2e60afce-9d76-5143-b7d9-f1a858fdb35c&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:46:26 +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#7242
No description provided.