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 #2349] [MERGED] test(analysis): verify real preset snapshot and cleanup boundaries #5181

New issue
Closed
opened 2026-10-31 01:04:37 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:04:37 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: test/analysis-preset-lifecycle-20261012

📝 Commits (3)

  • a27b45c test(analysis): verify real preset snapshot and cleanup boundaries
  • a415341 docs(analysis): record wider preset and failure verification
  • 67f817e test(analysis): verify recovered socket cleanup after retry

📊 Changes

4 files changed (+994 additions, -0 deletions)

View changed files

📝 experiments/analysis-efficiency/README.md (+4 -0)
➕ experiments/analysis-efficiency/preset-lifecycle.md (+208 -0)
➕ experiments/analysis-efficiency/verify-preset-lifecycle.mjs (+395 -0)
➕ experiments/analysis-efficiency/verify-preset-snapshot.mjs (+387 -0)

📄 Description

Summary

Part of #2016. Add reproducible real Ghidra CLI/MCP verification for the remaining task-scoped preset lifecycle boundaries: actual stored snapshot entries, profile mismatch in both directions, startup cancellation, recovery and cleanup retry.

The existing production default remains unchanged. The prior disabled-switch jq experiment changed a callee body, so this PR introduces no general fast-preset recommendation or runtime/API change.

Problem and expected behavior

Equal content-addressed replies do not prove snapshot reuse, a logical run ID does not identify a process generation, and a failed cleanup must retain its resource for another close. The new verifiers check those boundaries against real Ghidra and kernel/process observations instead of relying on those assumptions.

Change and scope

  • verify-preset-snapshot.mjs runs real default/disabled analysis, validates an actual exported query entry, checks fresh MCP and CLI reuse, rejects both wrong-profile snapshots before headless startup, and verifies original records/source bytes. It records the known headless launch command through caller-supplied strace.
  • verify-preset-lifecycle.mjs observes a token/start-identity verified JVM before endpoint readiness, cancels via the public SDK, confirms cleanup with production read-only token sweeps, and proves successful fresh work. A permission fault affects only its verified user-owned temporary project; restored permissions allow the retained-resource close retry.
  • Curated notes retain source/runtime pins, failed observer assumptions, exact scope and resource qualification. Raw JSON, traces, inputs and provider projects remain outside Git.

Contract and boundary impact

  • Semantic owner: experiment observer and cleanup lifetime; production process inspection/identity primitives are reused.
  • Contribution scope: verification of existing caller-selected, read-only Ghidra behavior in #2016. New provider/target execution/injection/protection recovery is not applicable.
  • CLI/MCP catalog: unchanged product commands, arguments, schemas, defaults and provider selection.
  • Provider/platform: real Ghidra 12.1.4/JDK 21, Linux x64; caller supplies installation/settings/strace. The permission fault requires a non-root user. Other platforms are unverified by these scripts.
  • Evidence/provenance: exact task facts, subject, parameters and profile survive valid reuse. CLI preserves the original cached ID; MCP marks cache reuse in its distinct response. Both mismatch directions preserve the original snapshot. Failed probes remain archived separately.
  • Authority/cleanup: no target execution or annotation requested. Controlled temporary directory permissions are restored; primary and cleanup failures are preserved together; success is published after cleanup callbacks finish.
  • Generated/package/installation: no package/version/dependency/install/configuration change; generated artifacts stay ignored.

Expected effects:

  • Read explicit native inputs and selected snapshots.
  • Launch existing local analysis/inspection processes.
  • Execute existing local analysis scripts; no target code or instrumentation.
  • Write new caller-selected verification files and temporarily change permissions only in the verifier-owned Ghidra project.
  • Contact network services or recover protected code.

Evidence and regression coverage

  • Installed GNU true: real default/disabled profile digests, stored analyze_function entry, exact SDK/CLI task facts, two-sided snapshot rejection, valid default restoration and headless launch counts pass.
  • Public pinned jq at the previously observed entry 0x403a50: the same complete snapshot/profile/CLI workflow passes. The selected entry agrees across profiles; this does not establish call-graph or whole-app equivalence.
  • GNU true, both profiles: actual pending startup cancellation, native start-identity proof of recovery, read-only token cleanup, real cleanup_incomplete/EACCES with retained resource, restored-permission retry and unchanged source bytes pass.
  • Actual invalid analyzer requests preserve the exact name in CLI and MCP execution_failure diagnostics. MCP retains a healthy bundled EVM peer. CLI uses an error string with sibling fields; saved replies were regraded against that actual envelope without rerunning the provider.

For evidence-bearing changes:

  • Observations, derivations, inferences and unknowns remain explicit.
  • Source identity, provenance and failed attempts are preserved.
  • Unsupported/unavailable/partial proof scopes remain visible.

Validation performed

  • Both source verifiers run against the built production baseline f76163c2467db623f9de0bda757c9d8610ca9565; their exact source hashes and private receipts are documented.
  • node --check / focused oxlint — both scripts pass with no warnings.
  • Single-task Turbo typecheck, then npm run check — pass under the unchanged one-CPU/4 GiB hard/3 GiB early-stop controls. The valid typecheck cache is reused by the full gate; its near-limit memory and soft-limit events are excluded from efficiency claims.
  • npm run docs:check — pass.
  • No production code/test contracts changed, so prior model/provider matrices are not rerun for this verifier-only increment.

Compatibility, safety and release

Existing users keep their API/default/provider choices. The scripts require explicit local inputs and new private output directories; no install or configuration migration is introduced. Revision is caller-supplied and should accompany the built/frozen runtime receipt.

Timings include discovery, tracing, profile inspection, rejection and cleanup. They verify the existing explicit JSON snapshot mechanism and are not new architecture speedups, repeated whole-question performance claims or model token measurements. Final completed-scope cgroup counters remain unknown; sampled values do not establish absent late OOM/limit events. Wider native/OS/domain cases remain scoped to their earlier checkpoints.

No release, deployment or version change. Existing REA defects remain in the requested private /tmp record.

Detailed pins, actual observations, corrections and reproduction.

Before merge

  • Concrete agreed #2016 verification outcome; scope/authority resolved.
  • Conventional title and focused diff.
  • Changed observer behavior and meaningful failures verified.
  • Source reproduction and curated documentation updated.
  • Diff reviewed for secrets, unrelated changes and unsupported claims.
  • Current-head CI and manual final review complete at 67f817e3653efad35f7044e68fbd6f163b86864b: all 36 checks succeed. CI receipt. Bot review quota is exhausted; automated approval is not claimed.

Latest-main review checkpoint

Rebased onto main 3ee6ff43c1696a5a5269bd4aa5de72f7e5f40627, which independently fixes the exact shard-6 fixture mismatch also observed on the prior main base. The related MCP file passes all five focused cases; missing coverage remains unknown. Final review additionally checks that the recovered socket directory is absent after permission-restoration cleanup retry and records its ownership manifest. Both actual profiles pass that related workflow again; broader artifact/model matrices were not repeated.

The native single-task typecheck and required fast checks pass with the unchanged 3 GiB early-stop/4 GiB hard bounds. A guarded typecheck stop and an overly restrictive 128 MiB docs heap attempt remain archived; the docs-only retry uses the existing 512 MiB Node heap and passes (434 MB sampled family peak). Final counters remain unverified. Current head is 67f817e3653efad35f7044e68fbd6f163b86864b; new current-head CI is still running.

🔄 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/2349 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/12/2026 **Status:** ✅ Merged **Merged:** 10/12/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `test/analysis-preset-lifecycle-20261012` --- ### 📝 Commits (3) - [`a27b45c`](https://github.com/morluto/rea/commit/a27b45c2a2bfa599680054a3f3c2ee878406dbf6) test(analysis): verify real preset snapshot and cleanup boundaries - [`a415341`](https://github.com/morluto/rea/commit/a415341218124e45e5a40fa22b139e263c0b928b) docs(analysis): record wider preset and failure verification - [`67f817e`](https://github.com/morluto/rea/commit/67f817e3653efad35f7044e68fbd6f163b86864b) test(analysis): verify recovered socket cleanup after retry ### 📊 Changes **4 files changed** (+994 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `experiments/analysis-efficiency/README.md` (+4 -0) ➕ `experiments/analysis-efficiency/preset-lifecycle.md` (+208 -0) ➕ `experiments/analysis-efficiency/verify-preset-lifecycle.mjs` (+395 -0) ➕ `experiments/analysis-efficiency/verify-preset-snapshot.mjs` (+387 -0) </details> ### 📄 Description ## Summary Part of #2016. Add reproducible real Ghidra CLI/MCP verification for the remaining task-scoped preset lifecycle boundaries: actual stored snapshot entries, profile mismatch in both directions, startup cancellation, recovery and cleanup retry. The existing production default remains unchanged. The prior disabled-switch jq experiment changed a callee body, so this PR introduces no general fast-preset recommendation or runtime/API change. ## Problem and expected behavior Equal content-addressed replies do not prove snapshot reuse, a logical run ID does not identify a process generation, and a failed cleanup must retain its resource for another close. The new verifiers check those boundaries against real Ghidra and kernel/process observations instead of relying on those assumptions. ## Change and scope - `verify-preset-snapshot.mjs` runs real default/disabled analysis, validates an actual exported query entry, checks fresh MCP and CLI reuse, rejects both wrong-profile snapshots before headless startup, and verifies original records/source bytes. It records the known headless launch command through caller-supplied strace. - `verify-preset-lifecycle.mjs` observes a token/start-identity verified JVM before endpoint readiness, cancels via the public SDK, confirms cleanup with production read-only token sweeps, and proves successful fresh work. A permission fault affects only its verified user-owned temporary project; restored permissions allow the retained-resource close retry. - Curated notes retain source/runtime pins, failed observer assumptions, exact scope and resource qualification. Raw JSON, traces, inputs and provider projects remain outside Git. ## Contract and boundary impact - Semantic owner: experiment observer and cleanup lifetime; production process inspection/identity primitives are reused. - Contribution scope: verification of existing caller-selected, read-only Ghidra behavior in #2016. New provider/target execution/injection/protection recovery is not applicable. - CLI/MCP catalog: unchanged product commands, arguments, schemas, defaults and provider selection. - Provider/platform: real Ghidra 12.1.4/JDK 21, Linux x64; caller supplies installation/settings/strace. The permission fault requires a non-root user. Other platforms are unverified by these scripts. - Evidence/provenance: exact task facts, subject, parameters and profile survive valid reuse. CLI preserves the original cached ID; MCP marks cache reuse in its distinct response. Both mismatch directions preserve the original snapshot. Failed probes remain archived separately. - Authority/cleanup: no target execution or annotation requested. Controlled temporary directory permissions are restored; primary and cleanup failures are preserved together; success is published after cleanup callbacks finish. - Generated/package/installation: no package/version/dependency/install/configuration change; generated artifacts stay ignored. Expected effects: - [x] Read explicit native inputs and selected snapshots. - [x] Launch existing local analysis/inspection processes. - [x] Execute existing local analysis scripts; no target code or instrumentation. - [x] Write new caller-selected verification files and temporarily change permissions only in the verifier-owned Ghidra project. - [ ] Contact network services or recover protected code. ## Evidence and regression coverage - Installed GNU `true`: real default/disabled profile digests, stored `analyze_function` entry, exact SDK/CLI task facts, two-sided snapshot rejection, valid default restoration and headless launch counts pass. - Public pinned jq at the previously observed entry `0x403a50`: the same complete snapshot/profile/CLI workflow passes. The selected entry agrees across profiles; this does not establish call-graph or whole-app equivalence. - GNU `true`, both profiles: actual pending startup cancellation, native start-identity proof of recovery, read-only token cleanup, real `cleanup_incomplete`/EACCES with retained resource, restored-permission retry and unchanged source bytes pass. - Actual invalid analyzer requests preserve the exact name in CLI and MCP `execution_failure` diagnostics. MCP retains a healthy bundled EVM peer. CLI uses an error string with sibling fields; saved replies were regraded against that actual envelope without rerunning the provider. For evidence-bearing changes: - [x] Observations, derivations, inferences and unknowns remain explicit. - [x] Source identity, provenance and failed attempts are preserved. - [x] Unsupported/unavailable/partial proof scopes remain visible. ## Validation performed - Both source verifiers run against the built production baseline `f76163c2467db623f9de0bda757c9d8610ca9565`; their exact source hashes and private receipts are documented. - `node --check` / focused `oxlint` — both scripts pass with no warnings. - Single-task Turbo typecheck, then `npm run check` — pass under the unchanged one-CPU/4 GiB hard/3 GiB early-stop controls. The valid typecheck cache is reused by the full gate; its near-limit memory and soft-limit events are excluded from efficiency claims. - `npm run docs:check` — pass. - No production code/test contracts changed, so prior model/provider matrices are not rerun for this verifier-only increment. ## Compatibility, safety and release Existing users keep their API/default/provider choices. The scripts require explicit local inputs and new private output directories; no install or configuration migration is introduced. Revision is caller-supplied and should accompany the built/frozen runtime receipt. Timings include discovery, tracing, profile inspection, rejection and cleanup. They verify the existing explicit JSON snapshot mechanism and are not new architecture speedups, repeated whole-question performance claims or model token measurements. Final completed-scope cgroup counters remain unknown; sampled values do not establish absent late OOM/limit events. Wider native/OS/domain cases remain scoped to their earlier checkpoints. No release, deployment or version change. Existing REA defects remain in the requested private `/tmp` record. [Detailed pins, actual observations, corrections and reproduction](https://github.com/morluto/rea/blob/test/analysis-preset-lifecycle-20261012/experiments/analysis-efficiency/preset-lifecycle.md). ## Before merge - [x] Concrete agreed #2016 verification outcome; scope/authority resolved. - [x] Conventional title and focused diff. - [x] Changed observer behavior and meaningful failures verified. - [x] Source reproduction and curated documentation updated. - [x] Diff reviewed for secrets, unrelated changes and unsupported claims. - [x] Current-head CI and manual final review complete at `67f817e3653efad35f7044e68fbd6f163b86864b`: all 36 checks succeed. [CI receipt](https://github.com/morluto/rea/actions/runs/38307614983). Bot review quota is exhausted; automated approval is not claimed. ## Latest-main review checkpoint Rebased onto main `3ee6ff43c1696a5a5269bd4aa5de72f7e5f40627`, which independently fixes the exact shard-6 fixture mismatch also observed on the prior main base. The related MCP file passes all five focused cases; missing coverage remains unknown. Final review additionally checks that the recovered socket directory is absent after permission-restoration cleanup retry and records its ownership manifest. Both actual profiles pass that related workflow again; broader artifact/model matrices were not repeated. The native single-task typecheck and required fast checks pass with the unchanged 3 GiB early-stop/4 GiB hard bounds. A guarded typecheck stop and an overly restrictive 128 MiB docs heap attempt remain archived; the docs-only retry uses the existing 512 MiB Node heap and passes (434 MB sampled family peak). Final counters remain unverified. Current head is `67f817e3653efad35f7044e68fbd6f163b86864b`; [new current-head CI](https://github.com/morluto/rea/actions/runs/38307614983) is still running. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:04:37 +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#5181
No description provided.