morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #4440] [CLOSED] build(nix): add a pinned development shell #6244

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4440
Author: @Dementor430
Created: 10/16/2026
Status: ❌ Closed

Base: main ← Head: build/nix-dev-shell

📝 Commits (3)

  • 6625bca build(nix): add a pinned development shell
  • f272aba build(nix): limit procps and util-linux to Linux
  • f2a1c08 Update shell.nix

📊 Changes

2 files changed (+93 additions, -0 deletions)

View changed files

📝 CONTRIBUTING.md (+8 -0)
➕ shell.nix (+85 -0)

📄 Description

Summary

Adds an optional, pinned Nix development shell (shell.nix) so contributors using Nix get the toolchain from .nvmrc and package.json#packageManager without nvm, and can opt into the bring-your-own providers for local verification. No linked issue; this is a small development-tooling addition.

Problem and expected behavior

Contributors on Nix (including setups without channels, where <nixpkgs> does not resolve) have no reproducible way to get Node.js 24 with npm 11.16.0, nor the provider tools that real-provider checks need. With this change:

  • nix-shell provides Node.js 24, npm 11.16.0 (packaged from the npm registry tarball, since nixpkgs ships a newer npm), Python 3, Git, procps (ps for the Linux owned-process prerequisite) and util-linux (prlimit), and runs npm ci when node_modules is missing. If node_modules exists but scripts/check-dependency-install.mjs reports it stale, it prints a hint instead of reinstalling.
  • nix-shell --arg withProviders true additionally provides JDK 21, Ghidra 12.1.4, the pinned jadx-headless-mcp-0.7.1-all.jar (fetched with the SHA-256 from docs/android-analysis.md), Binwalk 3.1.0 and Unblob 26.6.4, and exports GHIDRA_INSTALL_DIR, JAVA_HOME, REA_JADX_MCP_JAR, REA_BINWALK_COMMAND, REA_UNBLOB_COMMAND and REA_FIRMWARE_PRLIMIT_COMMAND.

Change and scope

  • shell.nix: nixpkgs is pinned to a fixed nixos-unstable revision via fetchTarball with a content hash (nixos-26.05 only has Ghidra 12.0.x; the docs require 12.1.x).
  • CONTRIBUTING.md: one paragraph in the development setup section.

Intentionally not included: a flake, CI wiring, and any change to rea setup or packaging. The shell is development tooling only; REA's installers and its bring-your-own provider policy are unchanged.

Open design question for maintainers: the shell hook runs npm ci automatically when node_modules is missing. Happy to change that to a hint only if preferred.

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.

Contract and boundary impact

  • Semantic owner and earliest changed stage: development environment only (repository root shell.nix); no source changes.
  • Contribution scope fit and linked maintainer decision: development tooling; no new provider or capability, so not applicable.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: none at runtime. The provider shell supplies provider binaries for local development only.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. shell.nix is not in package.json#files.

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.

(Entering the shell downloads nixpkgs, npm, the JADX JAR and npm dependencies from their registries; it does not interact with analysis targets.)

Evidence and regression coverage

  • Tests added or updated: none (development tooling).
  • Base reproduction or other evidence: executed on Ubuntu 24.04 under WSL2, Nix 2.33.3, x86_64-linux, based on 781d575; see Validation performed.
  • User-visible CLI/MCP output (if applicable): not applicable.
  • Remaining proof gaps:
    • Not run on NixOS itself. npm installs prebuilt native binaries (for example oxlint, oxfmt, turbo, esbuild, node-pty) that expect a standard dynamic loader; on NixOS these likely need nix-ld or similar. Not verified.
    • Not run on macOS or aarch64-linux; whether every provider package in the pinned revision supports those platforms is not verified.
    • Hopper and IDA are not provided (proprietary).

Validation performed

  • nix-instantiate --parse shell.nix — parses.
  • nixfmt shell.nix (nixfmt 1.5.0) — no changes.
  • rm -rf node_modules && nix-shell — hook ran npm ci (548 packages); node --version v24.21.0, npm --version 11.16.0.
  • npm run build:cached — succeeded.
  • npm run check:fast — 2/2 tasks successful; the pre-push hook also passed.
  • npx oxfmt --check CONTRIBUTING.md — correctly formatted.
  • npm run docs:check — passed, including tests/conformance/readmeConsistency.test.ts (5 tests).
  • npm run test:python — 35 and 71 tests OK.
  • nix-shell --arg withProviders true --run 'node scripts/rea.mjs doctor --json' — node, ghidra, ghidra-version (12.1.4), ghidra-headless, ghidra-native_decompiler, ghidra-java (JDK 21.0.12.1) and jadx checks all pass.
  • In the provider shell, binwalk --version reports binwalk 3.1.0 and unblob --version reports 26.6.4; both were also used successfully on a firmware image during local work.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: real Ghidra 12.1.4 and JADX bridge checked via rea doctor on x86_64 Linux (WSL2); no Ghidra analysis lane was run.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the shell only adds tools to PATH and exports provider variables within the shell session; nothing is installed system-wide. All downloads are pinned by hash (nixpkgs tarball, npm tarball, JADX JAR).

Author readiness

Human owner:

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

🤖 Generated with Claude Code

🔄 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/4440 **Author:** [@Dementor430](https://github.com/Dementor430) **Created:** 10/16/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `build/nix-dev-shell` --- ### 📝 Commits (3) - [`6625bca`](https://github.com/morluto/rea/commit/6625bca5985536286da956c3f7cfd66534bb794c) build(nix): add a pinned development shell - [`f272aba`](https://github.com/morluto/rea/commit/f272abad4f3c4f2d0fc457df8d3ee27b3fb6fa5a) build(nix): limit procps and util-linux to Linux - [`f2a1c08`](https://github.com/morluto/rea/commit/f2a1c08eb9f320b898ee55803726bebf8001a326) Update shell.nix ### 📊 Changes **2 files changed** (+93 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `CONTRIBUTING.md` (+8 -0) ➕ `shell.nix` (+85 -0) </details> ### 📄 Description ## Summary Adds an optional, pinned Nix development shell (`shell.nix`) so contributors using Nix get the toolchain from `.nvmrc` and `package.json#packageManager` without nvm, and can opt into the bring-your-own providers for local verification. No linked issue; this is a small development-tooling addition. ## Problem and expected behavior Contributors on Nix (including setups without channels, where `<nixpkgs>` does not resolve) have no reproducible way to get Node.js 24 with npm 11.16.0, nor the provider tools that real-provider checks need. With this change: - `nix-shell` provides Node.js 24, npm 11.16.0 (packaged from the npm registry tarball, since nixpkgs ships a newer npm), Python 3, Git, procps (`ps` for the Linux owned-process prerequisite) and util-linux (`prlimit`), and runs `npm ci` when `node_modules` is missing. If `node_modules` exists but `scripts/check-dependency-install.mjs` reports it stale, it prints a hint instead of reinstalling. - `nix-shell --arg withProviders true` additionally provides JDK 21, Ghidra 12.1.4, the pinned `jadx-headless-mcp-0.7.1-all.jar` (fetched with the SHA-256 from `docs/android-analysis.md`), Binwalk 3.1.0 and Unblob 26.6.4, and exports `GHIDRA_INSTALL_DIR`, `JAVA_HOME`, `REA_JADX_MCP_JAR`, `REA_BINWALK_COMMAND`, `REA_UNBLOB_COMMAND` and `REA_FIRMWARE_PRLIMIT_COMMAND`. ## Change and scope - `shell.nix`: nixpkgs is pinned to a fixed nixos-unstable revision via `fetchTarball` with a content hash (nixos-26.05 only has Ghidra 12.0.x; the docs require 12.1.x). - `CONTRIBUTING.md`: one paragraph in the development setup section. Intentionally not included: a flake, CI wiring, and any change to `rea setup` or packaging. The shell is development tooling only; REA's installers and its bring-your-own provider policy are unchanged. Open design question for maintainers: the shell hook runs `npm ci` automatically when `node_modules` is missing. Happy to change that to a hint only if preferred. 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. ## Contract and boundary impact - Semantic owner and earliest changed stage: development environment only (repository root `shell.nix`); no source changes. - Contribution scope fit and linked maintainer decision: development tooling; no new provider or capability, so not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none at runtime. The provider shell supplies provider binaries for local development only. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. `shell.nix` is not in `package.json#files`. 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. (Entering the shell downloads nixpkgs, npm, the JADX JAR and npm dependencies from their registries; it does not interact with analysis targets.) ## Evidence and regression coverage - Tests added or updated: none (development tooling). - Base reproduction or other evidence: executed on Ubuntu 24.04 under WSL2, Nix 2.33.3, x86_64-linux, based on `781d575`; see Validation performed. - User-visible CLI/MCP output (if applicable): not applicable. - Remaining proof gaps: - Not run on NixOS itself. npm installs prebuilt native binaries (for example oxlint, oxfmt, turbo, esbuild, node-pty) that expect a standard dynamic loader; on NixOS these likely need `nix-ld` or similar. Not verified. - Not run on macOS or aarch64-linux; whether every provider package in the pinned revision supports those platforms is not verified. - Hopper and IDA are not provided (proprietary). ## Validation performed - `nix-instantiate --parse shell.nix` — parses. - `nixfmt shell.nix` (nixfmt 1.5.0) — no changes. - `rm -rf node_modules && nix-shell` — hook ran `npm ci` (548 packages); `node --version` v24.21.0, `npm --version` 11.16.0. - `npm run build:cached` — succeeded. - `npm run check:fast` — 2/2 tasks successful; the pre-push hook also passed. - `npx oxfmt --check CONTRIBUTING.md` — correctly formatted. - `npm run docs:check` — passed, including `tests/conformance/readmeConsistency.test.ts` (5 tests). - `npm run test:python` — 35 and 71 tests OK. - `nix-shell --arg withProviders true --run 'node scripts/rea.mjs doctor --json'` — `node`, `ghidra`, `ghidra-version` (12.1.4), `ghidra-headless`, `ghidra-native_decompiler`, `ghidra-java` (JDK 21.0.12.1) and `jadx` checks all pass. - In the provider shell, `binwalk --version` reports `binwalk 3.1.0` and `unblob --version` reports `26.6.4`; both were also used successfully on a firmware image during local work. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: real Ghidra 12.1.4 and JADX bridge checked via `rea doctor` on x86_64 Linux (WSL2); no Ghidra analysis lane was run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the shell only adds tools to `PATH` and exports provider variables within the shell session; nothing is installed system-wide. All downloads are pinned by hash (nixpkgs tarball, npm tarball, JADX JAR). ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: <!-- @GitHub-handle --> - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:12:58 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/procedure-reference-stacked
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#6244
No description provided.