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 #7201] [CLOSED] docs(setup): call FreeBuff setup support shipped, not proposed #7711

New issue
Closed
opened 2026-11-03 13:39:49 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:49 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7201
Author: @XiaoBinGan
Created: 10/26/2026
Status: ❌ Closed

Base: main ← Head: docs/freebuff-published-support

📝 Commits (1)

  • e0591cc docs(setup): call FreeBuff setup support shipped, not proposed

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 docs/client-configuration.md (+3 -3)

📄 Description

Summary

The FreeBuff section still calls its setup support "proposed" in three places: "the proposed integration writes mcpServers.rea", "The proposed personal skill location is", and "are proposed integration boundaries". FreeBuff setup support shipped in rea-agents@6.8.0 and main now says so, so a reader is told a shipped client is still under proposal.

Scope note

This PR originally also corrected the release-availability paragraph. That half landed on main independently in 975900f56 (docs(setup): state the FreeBuff minimum release (#7066)), which now reads "FreeBuff setup support requires rea-agents@6.8.0 or later." I dropped my version of it and kept only what main still gets wrong, so this no longer duplicates that commit. Only the three "proposed" wordings change; the release statement, the limitation paragraph, and the installation-guide link are untouched.

Problem and expected behavior

Smallest trigger: read docs/client-configuration.md#freebuff on main (85075fa97).

  • Three statements describe shipped behavior as a proposal: lines 560, 562, and 570.
  • Violated invariant: authored client documentation must not present already-shipped support as proposed, because "proposed" reads as "not available yet" and contradicts the same section's own release statement.
  • Observed: main states "FreeBuff setup support requires rea-agents@6.8.0 or later" and the 6.8.0 registry package accepts rea setup --client freebuff, while the surrounding prose says the integration is proposed.

Expected: the section describes FreeBuff setup support as current and keeps the separate, still-true limitation that native FreeBuff MCP loading and skill discovery are unverified.

Change and scope

Authored documentation only, one section of one file, 3 insertions and 3 deletions — three words removed:

  1. "the proposed integration writes" → "setup writes"
  2. "The proposed personal skill location is" → "The personal skill location is"
  3. "are proposed integration boundaries" → "are integration boundaries"

Intentionally not included: the release-availability sentence (already fixed on main by 975900f56), the native-client limitation paragraph, and the installation-guide link. No runtime, catalogue, skill, or generated file changes.

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:
    Not applicable: authored prose in docs/client-configuration.md only. The behavior it describes is owned by the supported-client definitions in src/application/SupportedClients.ts, which this PR does not touch.
  • Contribution scope fit and linked maintainer decision: Documentation wording correction within an existing client boundary; no new provider, capability, or authority. Maintainer scope decision: not applicable.
  • CLI and MCP/tool-catalog contract: None. --client freebuff, its registration target, and its detection marker are unchanged.
  • Provider, bridge, target-format, or platform compatibility: None.
  • Evidence, artifact, provenance, or reconstruction contract: Not applicable.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable; no target interaction of any kind.
  • 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. No generator reads docs/client-configuration.md (git grep 'client-configuration' -- scripts/ is empty) and npm run docs:check passes without regenerating tracked 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.

Evidence and regression coverage

Ran on Node 24.22.1, Windows x64. No target was opened and no configuration was written; registry packages were inspected in disposable prefixes.

  • Tests added or updated: None. This is an authored-documentation wording correction with no executable behavior; the CI documentation job covers it (docs:check and docs:build).
  • Base reproduction or other evidence:
    • main at 85075fa97 states in the same section: "FreeBuff setup support requires rea-agents@6.8.0 or later. Older versions reject rea setup --client freebuff as an unsupported client." (added by 975900f56), while lines 560, 562 and 570 still say "proposed".
    • npm view rea-agents dist-tags.latest → 6.8.0.
    • npm install rea-agents@6.8.0 in an isolated prefix, then rea setup --client freebuff --skill=false --dry-run --json → exit 0, "status":"planned", plannedActions includes configure_client:freebuff targeting ~/.agents/mcp.json.
    • dist/application/SupportedClients.js in the published 6.8.0 tarball contains name: "freebuff", so the client definition itself is published, not only the CLI argument.
    • installation.md's Supported agents table already lists FreeBuff with --client value freebuff and states the 6.8.0 minimum, so it does not use "proposed" either.
  • User-visible CLI/MCP output (if applicable): The 6.8.0 dry-run JSON quoted above is the shipped behavior the section now describes as current.
  • Remaining proof gaps: Native FreeBuff MCP loading and skill discovery remain unverified with an installed FreeBuff client, exactly as the section still states. Verified against the npm registry package only; no live FreeBuff desktop client was exercised.

For boundary fixes, identify the applicable boundary regressions and lifecycle regressions covered by the evidence above, and explain relevant gaps.

Boundary regressions: not applicable. No parser, provider, filesystem, or lifecycle boundary changes; the diff is authored prose and the only runtime contact is reading registry packages during evidence collection. Lifecycle regressions: not applicable for the same reason.

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.

These three are left unchecked because this change produces no evidence records.

Validation performed

  • npm run docs:check — exit 0; 6/6 turbo tasks successful, then tests/conformance/readmeConsistency.test.ts 9 passed (9).
  • node scripts/check-doc-facts.mjs — exit 0.
  • git status --short — M docs/client-configuration.md only.
  • npm view rea-agents dist-tags.latest — 6.8.0.
  • rea setup --client freebuff --skill=false --dry-run --json on the installed 6.8.0 package — exit 0, status: planned, configure_client:freebuff.

Compatibility, safety, and release

  • Breaking changes or migration steps: None. No behavior or configuration changes; only the description of shipped support.
  • Real Hopper/Ghidra, browser, or OS coverage: Not applicable; no analysis provider or target interaction is involved.
  • Package or release metadata impact: None.
  • Security, privacy, process, or containment review: None. The change adds no capability.

Author readiness

Human owner: @XiaoBinGan

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

🔄 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/7201 **Author:** [@XiaoBinGan](https://github.com/XiaoBinGan) **Created:** 10/26/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/freebuff-published-support` --- ### 📝 Commits (1) - [`e0591cc`](https://github.com/morluto/rea/commit/e0591cc5a95531fea15d0c71ba8d2c982455d671) docs(setup): call FreeBuff setup support shipped, not proposed ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+3 -3) </details> ### 📄 Description ## Summary The FreeBuff section still calls its setup support "proposed" in three places: "the proposed integration writes `mcpServers.rea`", "The proposed personal skill location is", and "are proposed integration boundaries". FreeBuff setup support shipped in `rea-agents@6.8.0` and `main` now says so, so a reader is told a shipped client is still under proposal. ## Scope note This PR originally also corrected the release-availability paragraph. That half landed on `main` independently in `975900f56` (`docs(setup): state the FreeBuff minimum release (#7066)`), which now reads "FreeBuff setup support requires `rea-agents@6.8.0` or later." I dropped my version of it and kept only what `main` still gets wrong, so this no longer duplicates that commit. Only the three "proposed" wordings change; the release statement, the limitation paragraph, and the installation-guide link are untouched. ## Problem and expected behavior Smallest trigger: read `docs/client-configuration.md#freebuff` on `main` (85075fa97). - Three statements describe shipped behavior as a proposal: lines 560, 562, and 570. - Violated invariant: authored client documentation must not present already-shipped support as proposed, because "proposed" reads as "not available yet" and contradicts the same section's own release statement. - Observed: `main` states "FreeBuff setup support requires `rea-agents@6.8.0` or later" and the 6.8.0 registry package accepts `rea setup --client freebuff`, while the surrounding prose says the integration is proposed. Expected: the section describes FreeBuff setup support as current and keeps the separate, still-true limitation that native FreeBuff MCP loading and skill discovery are unverified. ## Change and scope Authored documentation only, one section of one file, 3 insertions and 3 deletions — three words removed: 1. "the proposed integration writes" → "setup writes" 2. "The proposed personal skill location is" → "The personal skill location is" 3. "are proposed integration boundaries" → "are integration boundaries" Intentionally not included: the release-availability sentence (already fixed on `main` by `975900f56`), the native-client limitation paragraph, and the installation-guide link. No runtime, catalogue, skill, or generated file changes. 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: Not applicable: authored prose in `docs/client-configuration.md` only. The behavior it describes is owned by the supported-client definitions in `src/application/SupportedClients.ts`, which this PR does not touch. - Contribution scope fit and linked maintainer decision: Documentation wording correction within an existing client boundary; no new provider, capability, or authority. Maintainer scope decision: not applicable. - CLI and MCP/tool-catalog contract: None. `--client freebuff`, its registration target, and its detection marker are unchanged. - Provider, bridge, target-format, or platform compatibility: None. - Evidence, artifact, provenance, or reconstruction contract: Not applicable. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable; no target interaction of any kind. - 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. No generator reads `docs/client-configuration.md` (`git grep 'client-configuration' -- scripts/` is empty) and `npm run docs:check` passes without regenerating tracked 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. ## Evidence and regression coverage Ran on Node 24.22.1, Windows x64. No target was opened and no configuration was written; registry packages were inspected in disposable prefixes. - Tests added or updated: None. This is an authored-documentation wording correction with no executable behavior; the CI documentation job covers it (`docs:check` and `docs:build`). - Base reproduction or other evidence: - `main` at `85075fa97` states in the same section: "FreeBuff setup support requires `rea-agents@6.8.0` or later. Older versions reject `rea setup --client freebuff` as an unsupported client." (added by `975900f56`), while lines 560, 562 and 570 still say "proposed". - `npm view rea-agents dist-tags.latest` → `6.8.0`. - `npm install rea-agents@6.8.0` in an isolated prefix, then `rea setup --client freebuff --skill=false --dry-run --json` → exit 0, `"status":"planned"`, `plannedActions` includes `configure_client:freebuff` targeting `~/.agents/mcp.json`. - `dist/application/SupportedClients.js` in the published 6.8.0 tarball contains `name: "freebuff"`, so the client definition itself is published, not only the CLI argument. - `installation.md`'s Supported agents table already lists FreeBuff with `--client` value `freebuff` and states the 6.8.0 minimum, so it does not use "proposed" either. - User-visible CLI/MCP output (if applicable): The 6.8.0 dry-run JSON quoted above is the shipped behavior the section now describes as current. - Remaining proof gaps: Native FreeBuff MCP loading and skill discovery remain unverified with an installed FreeBuff client, exactly as the section still states. Verified against the npm registry package only; no live FreeBuff desktop client was exercised. For boundary fixes, identify the applicable [boundary regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#boundary-regressions) and [lifecycle regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#lifecycle-regressions) covered by the evidence above, and explain relevant gaps. Boundary regressions: not applicable. No parser, provider, filesystem, or lifecycle boundary changes; the diff is authored prose and the only runtime contact is reading registry packages during evidence collection. Lifecycle regressions: not applicable for the same reason. 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. These three are left unchecked because this change produces no evidence records. ## Validation performed - `npm run docs:check` — exit 0; 6/6 turbo tasks successful, then `tests/conformance/readmeConsistency.test.ts` 9 passed (9). - `node scripts/check-doc-facts.mjs` — exit 0. - `git status --short` — ` M docs/client-configuration.md` only. - `npm view rea-agents dist-tags.latest` — `6.8.0`. - `rea setup --client freebuff --skill=false --dry-run --json` on the installed 6.8.0 package — exit 0, `status: planned`, `configure_client:freebuff`. ## Compatibility, safety, and release - Breaking changes or migration steps: None. No behavior or configuration changes; only the description of shipped support. - Real Hopper/Ghidra, browser, or OS coverage: Not applicable; no analysis provider or target interaction is involved. - Package or release metadata impact: None. - Security, privacy, process, or containment review: None. The change adds no capability. ## Author readiness Human owner: @XiaoBinGan - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-03 13:39:49 +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#7711
No description provided.