morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00

[GH-ISSUE #7641] [Bug] Get started's all-supported-clients section still reflects npm 6.4.0 #4564

New issue

Closed

opened 2026-10-31 00:50:50 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:50:50 +00:00

Owner

Originally created by @coygeek on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7641

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Documentation

Observed behavior

Source-only documentation finding. A reader opening Get started and expanding “All supported clients and setup IDs” receives a 17-client npm 6.4.0 table alongside commands that run setup from rea-agents@latest. The page contains no kimi, workbuddy, or freebuff ID. It mentions five further released clients only in a note describing their availability on repository main and suggesting a source build or a release containing them.

The baseline reports REA 6.8.0. Its installation guide lists 25 managed clients, including seven released in 6.5.0 and FreeBuff in 6.8.0. I ran the static comparison below and node scripts/rea.mjs --version; I did not visit the live website, execute client setup, or test native clients.

Reproduction

From source revision 65f1c447344a423fa2785847dbcea1e9a9e2454a, run this read-only comparison with Python 3:

from pathlib import Path
import re, json
page = Path('website/public/get-started/index.html').read_text()
section = page.split('id="supported-clients"', 1)[1].split('</details>', 1)[0]
table = section.split('<tbody>', 1)[1].split('</tbody>', 1)[0]
page_ids = re.findall(r'<td><code>([^<]+)</code></td>', table)
doc = Path('docs/installation.md').read_text().split('## Supported agents', 1)[1]
doc_ids = re.findall(r'^\|[^\n|]+\| `([^`]+)`\s*\|', doc, re.M)
print('package:', json.loads(Path('package.json').read_text())['version'])
print('website table count:', len(page_ids))
print('installation table count:', len(doc_ids))
print('missing table IDs:', ', '.join(sorted(set(doc_ids) - set(page_ids))))
print('IDs absent everywhere on page:', ', '.join(x for x in doc_ids if x not in page))
print('6.4.0 release note present:', 'The npm 6.4.0 release supports' in section)
print('repository-main/source-build note present:',
      'are available on repository\n                main; use a source build' in section)
print('latest setup commands:', len(re.findall(r'rea-agents@latest setup', page)))

Read the expanded supported-clients section and compare its release note with the installation guide's minimum-version notes. The exact source locations are below.

The static comparison was executed once and returned the output below. It requires no fixture, provider, package installation, or configuration change.

Expected behavior

The public setup guide should identify currently released setup clients and state their actual minimum releases. Its maintenance instructions explicitly require setup/support statements to agree with the current installation guide and released package, while preserving historical versions for case studies. Get started is the site's current setup entry point, rather than a historical case study.

An accurate historical statement about 6.4.0 can remain labeled as such, but it should not serve as the complete list under “All supported clients and setup IDs” for the page's current-release setup commands.

Impact and scope

P3: the verified effect is incomplete client-ID documentation and stale release-availability wording. No failed installation, incorrect registration, or consequential user decision was demonstrated. Readers can obtain all 25 IDs and minimum releases from the installation guide.

The missing whole-page IDs affect documentation for Kimi Code, WorkBuddy, and FreeBuff. The table also omits Qoder, Factory Droid, Trae, ZCode, and DeepSeek Harness; those five appear in the following release note. Whether either live host currently serves this source revision, and how readers act on the wording, was not checked.

REA version

Exact stdout from node scripts/rea.mjs --version:

6.8.0

Source revision: 65f1c447344a423fa2785847dbcea1e9a9e2454a.

Runtime and platform

Node.js v24.22.1, macOS (darwin), arm64. The version command used isolated HOME and XDG directories. Static source inspection used Python 3; no analysis provider or native client was launched.

Target and artifact context

The English Get started source page and the baseline's installation documentation; no binary or runtime-analysis target.

Interface

Other

Earliest failure stage

Unknown

Relevant output or evidence

The comparison above returned:

package: 6.8.0
website table count: 17
installation table count: 25
missing table IDs: droid, dsh, freebuff, kimi, qoder, trae, workbuddy, zcode
IDs absent everywhere on page: kimi, workbuddy, freebuff
6.4.0 release note present: True
repository-main/source-build note present: True
latest setup commands: 11

Source anchors at the stated revision:

website/public/get-started/index.html:633-724: the all-supported-clients heading, npm 6.4.0 table, and following main/source-build note.
docs/installation.md:610-646: the 25-client table and minimum releases. Seven IDs require 6.5.0 or later; freebuff requires 6.8.0 or later.
src/application/SupportedClients.ts:623-751: definitions for the later clients; CHANGELOG.md:54 and CHANGELOG.md:228 corroborate their release availability.
website/AGENTS.md, final setup/support maintenance bullet, and website/README.md:163-166: the current-release comparison rule and separate historical-case-study exception.
website/public/index.html:212 and scripts/website.py:22: public homepage and shared navigation entry points to Get started.
website/README.md:562-585 and .github/workflows/website-pages.yml: manual publication from main, with one checked artifact deployed to Cloudflare and GitHub Pages and a published-commit check.
scripts/website_i18n.py:615-637: English public sources are copied into the generated publish artifact. No release-specific Get started snapshot is selected by this build path.

These anchors establish the baseline documentation and its publication path; they do not establish the currently activated website revision.

Typed outcome or recovery expected

The expanded supported-clients section should agree with the installation guide's currently released IDs and minimum versions. This is a documentation correction, not a request to change setup acceptance or to claim native-client verification.

Analysis or suspected cause

Source-derived: this section is authored directly in the English HTML, and the website build copies that content rather than regenerating its client table from the supported-client definitions. Its 6.4.0 checkpoint has persisted into the 6.8.0 source tree. No runtime cause is alleged.

Additional context

The duplicate search covered open and closed issues, issue comments, and open/closed/merged PRs. Related records have different correction targets: #3423 concerns pinning install commands; #3465 corrected release notes in the installation guide; #7199 and PRs #7066/#7246 concern FreeBuff wording in the client-configuration guide; #1522 and #4451 concern bundled-skill lists. The old FAQ omission mentioned in #1522 and a review comment on #1564 concerns another page and another client set. None reports or fixes this Get started table and its release note.

Originally created by @coygeek on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7641 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Documentation ### Observed behavior Source-only documentation finding. A reader opening Get started and expanding “All supported clients and setup IDs” receives a 17-client npm 6.4.0 table alongside commands that run setup from `rea-agents@latest`. The page contains no `kimi`, `workbuddy`, or `freebuff` ID. It mentions five further released clients only in a note describing their availability on repository main and suggesting a source build or a release containing them. The baseline reports REA 6.8.0. Its installation guide lists 25 managed clients, including seven released in 6.5.0 and FreeBuff in 6.8.0. I ran the static comparison below and `node scripts/rea.mjs --version`; I did not visit the live website, execute client setup, or test native clients. ### Reproduction 1. From source revision `65f1c447344a423fa2785847dbcea1e9a9e2454a`, run this read-only comparison with Python 3: ```python from pathlib import Path import re, json page = Path('website/public/get-started/index.html').read_text() section = page.split('id="supported-clients"', 1)[1].split('</details>', 1)[0] table = section.split('<tbody>', 1)[1].split('</tbody>', 1)[0] page_ids = re.findall(r'<td><code>([^<]+)</code></td>', table) doc = Path('docs/installation.md').read_text().split('## Supported agents', 1)[1] doc_ids = re.findall(r'^\|[^\n|]+\| `([^`]+)`\s*\|', doc, re.M) print('package:', json.loads(Path('package.json').read_text())['version']) print('website table count:', len(page_ids)) print('installation table count:', len(doc_ids)) print('missing table IDs:', ', '.join(sorted(set(doc_ids) - set(page_ids)))) print('IDs absent everywhere on page:', ', '.join(x for x in doc_ids if x not in page)) print('6.4.0 release note present:', 'The npm 6.4.0 release supports' in section) print('repository-main/source-build note present:', 'are available on repository\n main; use a source build' in section) print('latest setup commands:', len(re.findall(r'rea-agents@latest setup', page))) ``` 2. Read the expanded supported-clients section and compare its release note with the installation guide's minimum-version notes. The exact source locations are below. The static comparison was executed once and returned the output below. It requires no fixture, provider, package installation, or configuration change. ### Expected behavior The public setup guide should identify currently released setup clients and state their actual minimum releases. Its maintenance instructions explicitly require setup/support statements to agree with the current installation guide and released package, while preserving historical versions for case studies. Get started is the site's current setup entry point, rather than a historical case study. An accurate historical statement about 6.4.0 can remain labeled as such, but it should not serve as the complete list under “All supported clients and setup IDs” for the page's current-release setup commands. ### Impact and scope P3: the verified effect is incomplete client-ID documentation and stale release-availability wording. No failed installation, incorrect registration, or consequential user decision was demonstrated. Readers can obtain all 25 IDs and minimum releases from the installation guide. The missing whole-page IDs affect documentation for Kimi Code, WorkBuddy, and FreeBuff. The table also omits Qoder, Factory Droid, Trae, ZCode, and DeepSeek Harness; those five appear in the following release note. Whether either live host currently serves this source revision, and how readers act on the wording, was not checked. ### REA version Exact stdout from `node scripts/rea.mjs --version`: ```text 6.8.0 ``` Source revision: `65f1c447344a423fa2785847dbcea1e9a9e2454a`. ### Runtime and platform Node.js v24.22.1, macOS (darwin), arm64. The version command used isolated HOME and XDG directories. Static source inspection used Python 3; no analysis provider or native client was launched. ### Target and artifact context The English Get started source page and the baseline's installation documentation; no binary or runtime-analysis target. ### Interface Other ### Earliest failure stage Unknown ### Relevant output or evidence The comparison above returned: ```text package: 6.8.0 website table count: 17 installation table count: 25 missing table IDs: droid, dsh, freebuff, kimi, qoder, trae, workbuddy, zcode IDs absent everywhere on page: kimi, workbuddy, freebuff 6.4.0 release note present: True repository-main/source-build note present: True latest setup commands: 11 ``` Source anchors at the stated revision: - `website/public/get-started/index.html:633-724`: the all-supported-clients heading, npm 6.4.0 table, and following main/source-build note. - `docs/installation.md:610-646`: the 25-client table and minimum releases. Seven IDs require 6.5.0 or later; `freebuff` requires 6.8.0 or later. - `src/application/SupportedClients.ts:623-751`: definitions for the later clients; `CHANGELOG.md:54` and `CHANGELOG.md:228` corroborate their release availability. - `website/AGENTS.md`, final setup/support maintenance bullet, and `website/README.md:163-166`: the current-release comparison rule and separate historical-case-study exception. - `website/public/index.html:212` and `scripts/website.py:22`: public homepage and shared navigation entry points to Get started. - `website/README.md:562-585` and `.github/workflows/website-pages.yml`: manual publication from `main`, with one checked artifact deployed to Cloudflare and GitHub Pages and a published-commit check. - `scripts/website_i18n.py:615-637`: English public sources are copied into the generated publish artifact. No release-specific Get started snapshot is selected by this build path. These anchors establish the baseline documentation and its publication path; they do not establish the currently activated website revision. ### Typed outcome or recovery expected The expanded supported-clients section should agree with the installation guide's currently released IDs and minimum versions. This is a documentation correction, not a request to change setup acceptance or to claim native-client verification. ### Analysis or suspected cause Source-derived: this section is authored directly in the English HTML, and the website build copies that content rather than regenerating its client table from the supported-client definitions. Its 6.4.0 checkpoint has persisted into the 6.8.0 source tree. No runtime cause is alleged. ### Additional context The duplicate search covered open and closed issues, issue comments, and open/closed/merged PRs. Related records have different correction targets: #3423 concerns pinning install commands; #3465 corrected release notes in the installation guide; #7199 and PRs #7066/#7246 concern FreeBuff wording in the client-configuration guide; #1522 and #4451 concern bundled-skill lists. The old FAQ omission mentioned in #1522 and a review comment on #1564 concerns another page and another client set. None reports or fixes this Get started table and its release note.

bsakaguchi closed this issue

2026-10-31 00:50:50 +00:00

bsakaguchi referenced this issue

2026-10-31 00:50:56 +00:00

[GH-ISSUE #7654] [Bug] Translated setup guides omit the MCP output-profile option #4576

bsakaguchi referenced this issue

2026-10-31 00:50:58 +00:00

[GH-ISSUE #7656] [Bug] Indonesian and Italian analysis tables omit the Linux x64 host prerequisite #4579

bsakaguchi referenced this issue

2026-10-31 01:13:29 +00:00

[PR #4570] [CLOSED] docs(i18n): sync Go, SQLite and Bun update facts in translated READMEs #6311

bsakaguchi referenced this issue