morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[PR #3465] [MERGED] docs(installation): list every client that first shipped in 6.5.0 #5756

New issue

Closed

opened 2026-10-31 01:09:12 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:09:12 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3465
Author: @555aaditya
Created: 10/14/2026
Status: ✅ Merged
Merged: 10/15/2026
Merged by: @baron

Base: main ← Head: docs/release-gated-clients

📝 Commits (2)

da1f4fd docs(installation): list every client missing from npm 6.4.0
f233c20 Merge origin/main into docs/release-gated-clients

📊 Changes

1 file changed (+5 additions, -4 deletions)

View changed files

📝 docs/installation.md (+5 -4)

📄 Description

Summary

docs/installation.md has two notes about which setup clients need a newer npm release. After the 6.5.0 release (#1693), both are incomplete:

The 6.4.0 registry-check note says only DeepSeek Harness (dsh) "is included from 6.5.0 and was absent from the checked npm 6.4.0 package".
The supported-agents table note still says "dsh, kimi, and workbuddy require a release containing them". That's stale now that 6.5.0 is published, and it omits four more clients.

In fact, seven client IDs were absent from 6.4.0 and first shipped in 6.5.0: droid, dsh, kimi, qoder, trae, workbuddy and zcode. Both notes now name all seven, and the table note says they require rea-agents@6.5.0 or later.

This is a documentation-only change, and there's no related issue. It was originally opened against 6.4.0, then updated after #1693 merged and 6.5.0 was published to npm.

Problem and expected behavior

Before (main after #1693):

"DeepSeek Harness (dsh) is included from 6.5.0 and was absent from the checked npm 6.4.0 package."
"dsh, kimi, and workbuddy require a release containing them."

After:

"Seven client IDs are included from 6.5.0 and were absent from the checked npm 6.4.0 package: droid, dsh, kimi, qoder, trae, workbuddy and zcode."
"… require rea-agents@6.5.0 or later. The 6.4.0 registry check above does not cover them."

How I confirmed it:

Source. I compared the client name entries in src/application/SupportedClients.ts. The rea-agents-6.4.0 tag has 18 entries (including the manual Grok Bot connector, which matches the guide's "17 client IDs"). Both rea-agents-6.5.0 and current main have 25. The seven IDs above are exactly the ones 6.4.0 lacks, and 6.5.0 lacks none.

Observed against the published packages. In isolated temporary HOMEs, npx -y rea-agents@<version> setup --client <id> --dry-run gave:

Client	6.4.0	6.5.0
`trae`	`VALIDATION_ERROR`: "Unsupported agent integration"	`status: planned`
`qoder`	`VALIDATION_ERROR`: "Unsupported agent integration"	`status: planned`
`droid`	(not run)	`status: planned`
`zcode`	(not run)	`status: planned`
`qwen_code` (control)	`status: planned`	(not run)

Both isolated HOMEs stayed empty, so nothing was written.

Change and scope

docs/installation.md only: two sentences. The release-owned version strings and the 2026-10-11 6.4.0 registry-check record are left as they are.

Contribution scope: documentation within existing boundaries, so not applicable.

Contract and boundary impact

Semantic owner and earliest changed stage: docs/installation.md (documentation).
Contribution scope fit and linked maintainer decision: documentation-only; not applicable.
CLI and MCP/tool-catalog contract: none.
Provider, bridge, target-format, or platform compatibility: none.
Evidence, artifact, provenance, or reconstruction contract: none.
Target selection, authority, upstream behavior, and cleanup details: not applicable.
Generated metadata, package, or installation impact: none (prose only).

Expected effects:

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

Evidence and regression coverage

Tests added or updated: none; this is documentation only.
Base reproduction or other evidence: the source comparison and the published-package dry runs above.
User-visible CLI/MCP output: against 6.4.0, rea setup --client trae --dry-run returns VALIDATION_ERROR "Unsupported agent integration". Against 6.5.0, it returns status: planned.
Remaining proof gaps:
- 6.5.0 dry runs covered trae, qoder, droid and zcode. dsh, kimi and workbuddy are covered by the source comparison, and the release already documents dsh.
- I didn't verify live client integration. Dry runs check planning and argument admission only.

Validation performed

git show rea-agents-6.4.0:src/application/SupportedClients.ts vs rea-agents-6.5.0 vs origin/main: 18 / 25 / 25 client names. The seven listed IDs are exactly the ones 6.4.0 lacks, and 6.5.0 lacks none.
HOME=<temp> npx -y rea-agents@6.4.0 setup --client {trae,qoder} --dry-run: both VALIDATION_ERROR, "Unsupported agent integration".
HOME=<temp> npx -y rea-agents@6.4.0 setup --client qwen_code --dry-run: status: planned.
HOME=<temp> npx -y rea-agents@6.5.0 setup --client {trae,qoder,droid,zcode} --dry-run: all status: planned.
npx oxfmt --check docs/installation.md: clean.
npm run docs:check: passed, after merging current origin/main.

Compatibility, safety, and release

Breaking changes or migration steps: none.
Real Hopper/Ghidra, browser, or OS coverage: not applicable.
Package or release metadata impact: none. The conflict with release #1693 was resolved by merging main and updating the notes for 6.5.0.
Security, privacy, process, or containment review: not applicable.

Author readiness

Human owner: @555aaditya

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/3465 **Author:** [@555aaditya](https://github.com/555aaditya) **Created:** 10/14/2026 **Status:** ✅ Merged **Merged:** 10/15/2026 **Merged by:** [@baron](https://github.com/baron) **Base:** `main` ← **Head:** `docs/release-gated-clients` --- ### 📝 Commits (2) - [`da1f4fd`](https://github.com/morluto/rea/commit/da1f4fdc5fe60701c1c879e0b311218c8fe8e551) docs(installation): list every client missing from npm 6.4.0 - [`f233c20`](https://github.com/morluto/rea/commit/f233c2076cd501cd83cd966c9e12a94d1435598c) Merge origin/main into docs/release-gated-clients ### 📊 Changes **1 file changed** (+5 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+5 -4) </details> ### 📄 Description ## Summary `docs/installation.md` has two notes about which setup clients need a newer npm release. After the 6.5.0 release (#1693), both are incomplete: - The 6.4.0 registry-check note says only DeepSeek Harness (`dsh`) "is included from 6.5.0 and was absent from the checked npm 6.4.0 package". - The supported-agents table note still says "`dsh`, `kimi`, and `workbuddy` require a release containing them". That's stale now that 6.5.0 is published, and it omits four more clients. In fact, **seven** client IDs were absent from 6.4.0 and first shipped in 6.5.0: `droid`, `dsh`, `kimi`, `qoder`, `trae`, `workbuddy` and `zcode`. Both notes now name all seven, and the table note says they require `rea-agents@6.5.0` or later. This is a documentation-only change, and there's no related issue. It was originally opened against 6.4.0, then updated after #1693 merged and 6.5.0 was published to npm. ## Problem and expected behavior **Before (main after #1693):** - "DeepSeek Harness (`dsh`) is included from 6.5.0 and was absent from the checked npm 6.4.0 package." - "`dsh`, `kimi`, and `workbuddy` require a release containing them." **After:** - "Seven client IDs are included from 6.5.0 and were absent from the checked npm 6.4.0 package: `droid`, `dsh`, `kimi`, `qoder`, `trae`, `workbuddy` and `zcode`." - "… require `rea-agents@6.5.0` or later. The 6.4.0 registry check above does not cover them." How I confirmed it: - **Source.** I compared the client `name` entries in `src/application/SupportedClients.ts`. The `rea-agents-6.4.0` tag has 18 entries (including the manual Grok Bot connector, which matches the guide's "17 client IDs"). Both `rea-agents-6.5.0` and current `main` have 25. The seven IDs above are exactly the ones 6.4.0 lacks, and 6.5.0 lacks none. - **Observed against the published packages.** In isolated temporary `HOME`s, `npx -y rea-agents@<version> setup --client <id> --dry-run` gave: | Client | 6.4.0 | 6.5.0 | |---|---|---| | `trae` | `VALIDATION_ERROR`: "Unsupported agent integration" | `status: planned` | | `qoder` | `VALIDATION_ERROR`: "Unsupported agent integration" | `status: planned` | | `droid` | (not run) | `status: planned` | | `zcode` | (not run) | `status: planned` | | `qwen_code` (control) | `status: planned` | (not run) | Both isolated `HOME`s stayed empty, so nothing was written. ## Change and scope `docs/installation.md` only: two sentences. The release-owned version strings and the 2026-10-11 6.4.0 registry-check record are left as they are. Contribution scope: documentation within existing boundaries, so not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `docs/installation.md` (documentation). - Contribution scope fit and linked maintainer decision: documentation-only; not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none (prose only). Expected effects: - [ ] 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 - **Tests added or updated:** none; this is documentation only. - **Base reproduction or other evidence:** the source comparison and the published-package dry runs above. - **User-visible CLI/MCP output:** against 6.4.0, `rea setup --client trae --dry-run` returns `VALIDATION_ERROR` "Unsupported agent integration". Against 6.5.0, it returns `status: planned`. - **Remaining proof gaps:** - 6.5.0 dry runs covered `trae`, `qoder`, `droid` and `zcode`. `dsh`, `kimi` and `workbuddy` are covered by the source comparison, and the release already documents `dsh`. - I didn't verify live client integration. Dry runs check planning and argument admission only. ## Validation performed - `git show rea-agents-6.4.0:src/application/SupportedClients.ts` vs `rea-agents-6.5.0` vs `origin/main`: 18 / 25 / 25 client names. The seven listed IDs are exactly the ones 6.4.0 lacks, and 6.5.0 lacks none. - `HOME=<temp> npx -y rea-agents@6.4.0 setup --client {trae,qoder} --dry-run`: both `VALIDATION_ERROR`, "Unsupported agent integration". - `HOME=<temp> npx -y rea-agents@6.4.0 setup --client qwen_code --dry-run`: `status: planned`. - `HOME=<temp> npx -y rea-agents@6.5.0 setup --client {trae,qoder,droid,zcode} --dry-run`: all `status: planned`. - `npx oxfmt --check docs/installation.md`: clean. - `npm run docs:check`: passed, after merging current `origin/main`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. The conflict with release #1693 was resolved by merging main and updating the notes for 6.5.0. - Security, privacy, process, or containment review: not applicable. ## Author readiness  Human owner: @555aaditya - [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  - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:09:12 +00:00

closed this issue
added the
pull-request
label

No milestone

No project

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#5756

No description provided.

Rows
Columns