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 #5301] [CLOSED] fix(sqlite): bind returned cleanup errors to their exact root and worker owners #6867

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5301
Author: @charan-rathore
Created: 10/19/2026
Status: ❌ Closed

Base: main ← Head: fix/5294-sqlite-cleanup-owner-binding

📝 Commits (10+)

  • 509b8f1 fix(sqlite): bind returned cleanup errors to their exact root and worker owners
  • 2e85d6c test(sqlite): cover cleanup-error owner binding through release
  • 7f20e30 fix(sqlite): bind close-time and root-wrapper failures to every cleanup owner
  • c1f921a test(sqlite): pin descriptor-close failure resolution through its leases
  • e5e8736 fix(sqlite): keep prior cleanup failures as dependencies of root-retry wrappers
  • cefe0e2 style(sqlite): drop the trailing blank line oxfmt rejects
  • aa96e45 test(sqlite): type the caught aggregate in the close-descriptor cleanup test
  • 5f4329a test(sqlite): compare the aggregate owner list order-insensitively
  • b708c5a test(sqlite): prove a root-retry wrapper waits on its embedded read failure
  • 0606858 fix(sqlite): keep a root-retry wrapper pending until its retained owner releases

📊 Changes

5 files changed (+593 additions, -74 deletions)

View changed files

📝 src/artifacts/AnalysisCleanupLease.test.ts (+22 -0)
📝 src/artifacts/AnalysisCleanupLease.ts (+5 -0)
📝 src/domain/analysisErrorBase.ts (+18 -3)
📝 src/sqlite/SqliteDatabaseProvider.ts (+167 -70)
📝 tests/boundary/sqlite/sqliteDatabaseCleanup.test.ts (+381 -1)

📄 Description

Summary

Fixes #5294. A cleanup error returned from the SQLite provider kept reporting cleanupIncomplete: true and the removed runtime root after provider.close() had already confirmed that root's release, so a caller retaining the original error saw a cleanup blocker for a resource the owner no longer held.

Problem and expected behavior

Smallest trigger: the worker launch fails (or the first snapshot removal is denied), so inspect returns a ProviderCleanupError; a later provider.close() removes the actual root successfully. The returned error still reports cleanupIncomplete: true and keeps the deleted path in cleanupResources. A returned cleanup error must stay bound to the exact worker and root owners it reports, resolve only when every one of them has confirmed release, and never keep listing a released owner's resources.

Change and scope

src/sqlite/SqliteDatabaseProvider.ts now gives every retained root one AnalysisCleanupLease whose release is staged (confirm the retained worker has stopped, then remove the snapshot) and whose live resource attribution comes from the pending map — worker resources while the worker is retained, then the root path, then nothing. Returned inspection errors, retry failures, and close aggregates are bound to their exact leases through AnalysisCleanupLeaseGroup, and multi-failure aggregates use bindCleanupDependencies, the same ownership pattern ArtifactAnalysisResources already uses. The artifact-descriptor scope keeps owning its own leases; no API, admission, or evidence behavior changes.

Contribution scope: not applicable — ordinary fix within the existing SQLite provider boundary.

Contract and boundary impact

  • Semantic owner and earliest changed stage: SqliteDatabaseProvider; cleanup, cancellation, and lifecycle stage only.
  • Contribution scope fit and linked maintainer decision: not applicable (ordinary fix within existing boundaries).
  • CLI and MCP/tool-catalog contract: unchanged.
  • Provider, bridge, target-format, or platform compatibility: unchanged; boundary tests run on Linux.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; partial-Evidence retention across continued cleanup refusal is preserved.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): returned cleanup errors now resolve (cleanupIncomplete: false, empty cleanupResources) only after every owner they report has confirmed release; a still-owned worker or root continues to block replacement admission exactly as before.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

No new effects: the diff changes only how returned errors track the cleanup owners the provider already retains.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/sqlite/sqliteDatabaseCleanup.test.ts — three new regressions: a returned error resolves and empties once its retained root's close is confirmed; a worker-plus-root error drops only the worker's resources when the worker's stop is confirmed, then resolves when the root is removed; a close aggregate tracks every unresolved owner until each retained root releases.
  • Base reproduction or other evidence: each new test fails on base revision 71ae02c without the provider change (the kept error stays cleanupIncomplete with the removed path still listed) and passes with it.
  • User-visible CLI/MCP output (if applicable): none.
  • Remaining proof gaps: macOS worker paths are exercised through the same seams but were not run on Darwin; two SQLite boundary failures on Linux (cancels an acquired SQLite worker and removes its private snapshot, retains reply-read cancellation and retries the failed reply descriptor close) reproduce identically with and without this change.

For evidence-bearing changes:

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

Validation performed

  • npx vitest run tests/boundary/sqlite/sqliteDatabaseCleanup.test.ts — 8 passed (5 existing + 3 new).
  • Same file with the provider change reverted — the 3 new tests fail (RED), the 5 existing pass.
  • npx vitest run tests/boundary/sqlite/ — 48 passed, 42 skipped, 2 failed; both failures reproduce identically on clean 71ae02c.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; Linux boundary suite only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new process launches, target interaction, or external writes; the change binds returned errors to cleanup owners the provider already retains.

Author readiness

Human owner: @charan-rathore

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

AI-assisted; Charan Rathore is the human driver.

🔄 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/5301 **Author:** [@charan-rathore](https://github.com/charan-rathore) **Created:** 10/19/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/5294-sqlite-cleanup-owner-binding` --- ### 📝 Commits (10+) - [`509b8f1`](https://github.com/morluto/rea/commit/509b8f1f6aad886b45f0c3991c826d46bec4a42f) fix(sqlite): bind returned cleanup errors to their exact root and worker owners - [`2e85d6c`](https://github.com/morluto/rea/commit/2e85d6ce08e66472e637e6a5a7bde01c37f1bbca) test(sqlite): cover cleanup-error owner binding through release - [`7f20e30`](https://github.com/morluto/rea/commit/7f20e30f1a8b7ff18af0f4ea285e2bf267d3ce84) fix(sqlite): bind close-time and root-wrapper failures to every cleanup owner - [`c1f921a`](https://github.com/morluto/rea/commit/c1f921a39d09f9e0ca446628941f4e63d5b04b41) test(sqlite): pin descriptor-close failure resolution through its leases - [`e5e8736`](https://github.com/morluto/rea/commit/e5e873649b20c3bf4bcdd1ba1e0d8e84dd97e664) fix(sqlite): keep prior cleanup failures as dependencies of root-retry wrappers - [`cefe0e2`](https://github.com/morluto/rea/commit/cefe0e27365b09111e8ecf2e3e8cfc2f4f6b8f2e) style(sqlite): drop the trailing blank line oxfmt rejects - [`aa96e45`](https://github.com/morluto/rea/commit/aa96e452329d51140dafb382bd40403bfe8642a0) test(sqlite): type the caught aggregate in the close-descriptor cleanup test - [`5f4329a`](https://github.com/morluto/rea/commit/5f4329ab75f361602b2ce391648c40cee5a0b4c0) test(sqlite): compare the aggregate owner list order-insensitively - [`b708c5a`](https://github.com/morluto/rea/commit/b708c5a2cee91d63e7bb74ca31743cdd7534d3c1) test(sqlite): prove a root-retry wrapper waits on its embedded read failure - [`0606858`](https://github.com/morluto/rea/commit/060685819361ecfb1416f547a0c60d6b03885d39) fix(sqlite): keep a root-retry wrapper pending until its retained owner releases ### 📊 Changes **5 files changed** (+593 additions, -74 deletions) <details> <summary>View changed files</summary> 📝 `src/artifacts/AnalysisCleanupLease.test.ts` (+22 -0) 📝 `src/artifacts/AnalysisCleanupLease.ts` (+5 -0) 📝 `src/domain/analysisErrorBase.ts` (+18 -3) 📝 `src/sqlite/SqliteDatabaseProvider.ts` (+167 -70) 📝 `tests/boundary/sqlite/sqliteDatabaseCleanup.test.ts` (+381 -1) </details> ### 📄 Description ## Summary Fixes #5294. A cleanup error returned from the SQLite provider kept reporting `cleanupIncomplete: true` and the removed runtime root after `provider.close()` had already confirmed that root's release, so a caller retaining the original error saw a cleanup blocker for a resource the owner no longer held. ## Problem and expected behavior Smallest trigger: the worker launch fails (or the first snapshot removal is denied), so `inspect` returns a `ProviderCleanupError`; a later `provider.close()` removes the actual root successfully. The returned error still reports `cleanupIncomplete: true` and keeps the deleted path in `cleanupResources`. A returned cleanup error must stay bound to the exact worker and root owners it reports, resolve only when every one of them has confirmed release, and never keep listing a released owner's resources. ## Change and scope `src/sqlite/SqliteDatabaseProvider.ts` now gives every retained root one `AnalysisCleanupLease` whose release is staged (confirm the retained worker has stopped, then remove the snapshot) and whose live resource attribution comes from the pending map — worker resources while the worker is retained, then the root path, then nothing. Returned inspection errors, retry failures, and close aggregates are bound to their exact leases through `AnalysisCleanupLeaseGroup`, and multi-failure aggregates use `bindCleanupDependencies`, the same ownership pattern `ArtifactAnalysisResources` already uses. The artifact-descriptor scope keeps owning its own leases; no API, admission, or evidence behavior changes. Contribution scope: not applicable — ordinary fix within the existing SQLite provider boundary. ## Contract and boundary impact - Semantic owner and earliest changed stage: `SqliteDatabaseProvider`; cleanup, cancellation, and lifecycle stage only. - Contribution scope fit and linked maintainer decision: not applicable (ordinary fix within existing boundaries). - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: unchanged; boundary tests run on Linux. - Evidence, artifact, provenance, or reconstruction contract: unchanged; partial-Evidence retention across continued cleanup refusal is preserved. - Target selection, authority, upstream behavior, and cleanup details (if applicable): returned cleanup errors now resolve (`cleanupIncomplete: false`, empty `cleanupResources`) only after every owner they report has confirmed release; a still-owned worker or root continues to block replacement admission exactly as before. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. No new effects: the diff changes only how returned errors track the cleanup owners the provider already retains. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/sqlite/sqliteDatabaseCleanup.test.ts` — three new regressions: a returned error resolves and empties once its retained root's close is confirmed; a worker-plus-root error drops only the worker's resources when the worker's stop is confirmed, then resolves when the root is removed; a close aggregate tracks every unresolved owner until each retained root releases. - Base reproduction or other evidence: each new test fails on base revision 71ae02c without the provider change (the kept error stays `cleanupIncomplete` with the removed path still listed) and passes with it. - User-visible CLI/MCP output (if applicable): none. - Remaining proof gaps: macOS worker paths are exercised through the same seams but were not run on Darwin; two SQLite boundary failures on Linux (`cancels an acquired SQLite worker and removes its private snapshot`, `retains reply-read cancellation and retries the failed reply descriptor close`) reproduce identically with and without this change. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npx vitest run tests/boundary/sqlite/sqliteDatabaseCleanup.test.ts` — 8 passed (5 existing + 3 new). - Same file with the provider change reverted — the 3 new tests fail (RED), the 5 existing pass. - `npx vitest run tests/boundary/sqlite/` — 48 passed, 42 skipped, 2 failed; both failures reproduce identically on clean 71ae02c. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; Linux boundary suite only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new process launches, target interaction, or external writes; the change binds returned errors to cleanup owners the provider already retains. ## Author readiness Human owner: @charan-rathore - [ ] 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 - [x] 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. AI-assisted; Charan Rathore is the human driver. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:43: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#6867
No description provided.