morluto/rea

Fork 0

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

[GH-ISSUE #7199] [Bug] FreeBuff setup guide describes published support as unreleased #4301

New issue

Closed

opened 2026-10-31 00:48:41 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-31 00:48:41 +00:00

Owner

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

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

The FreeBuff guide still says support is main-only, npm 6.7.0 is latest, and setup against @latest rejects the client. The published package instead accepts --client freebuff and writes its registration. This concerns release-availability wording only.

Reproduction

Read the FreeBuff section of docs/client-configuration.md in the default branch and release source listed below.
Query npm view rea-agents dist-tags.latest, then install the published package in a disposable prefix with disposable HOME, XDG config/data/cache directories, and npm cache.
Run the installed rea setup --client freebuff --skill=false --yes --json and inspect the disposable home's .agents/mcp.json.
Create .config/freebuff-desktop under that disposable home as a detection marker, then run rea doctor --client freebuff --json.

Expected behavior

The guide should describe the published package's accepted setup client accurately while keeping its separate native-client verification limitations.

Impact and scope

Stale availability guidance can confuse readers; no runtime failure or consequential behavior change was observed. The explicit setup command works despite the warning. Native FreeBuff MCP loading and skill discovery were not tested, and creating a detection marker does not verify them.

REA version

Published package: rea-agents@6.8.0 (rea --version: 6.8.0), returned by npm's latest tag. Latest GitHub release: rea-agents-6.8.0, revision 160d821ac9a0310afcb8d1fc427862dd6508add5. Current main: 1173c0a9dc1b352a60943a491462294db8f353ae.

Runtime and platform

Node.js 26.12.1, npm 12.2.1, Linux x64; isolated configuration and install directories.

Target and artifact context

Documentation and a disposable client-registration file; no analysis target or native FreeBuff client.

Interface

CLI

Earliest failure stage

Unknown

The incorrect wording is visible before setup; no CLI failure stage applies.

Relevant output or evidence

Observed once each: setup exited 0 with clients.freebuff.status: "configured" and appliedActions: ["configured_freebuff"], creating mcpServers.rea; scoped doctor exited 0 with registration:freebuff healthy and registration identity aligned. These are selected fields with disposable paths omitted. Doctor's unrelated environment checks do not establish native-client behavior.

The current guide, lines 568–570 says: “FreeBuff is main-only and is not in a published release yet; npm 6.7.0 is the latest.” The same paragraph appears at lines 525–527 in the release source. Supporting static evidence: the published-release client definition, lines 721–735 registers freebuff.

Typed outcome or recovery expected

Not applicable to this wording defect. Restoration means the release-availability paragraph agrees with the accepted client in the published package, while preserving the native loading and skill-discovery caveat.

Analysis or suspected cause

Observed documentation/package mismatch; no runtime cause is alleged.

Additional context

Open PR #7066 already proposes this correction and remains unmerged. This report records the current published-package observation rather than requesting a second implementation.

References

Closed feature #3243 concerns adding FreeBuff setup support; the remaining requirement here is accurate release-availability documentation after publication.

Triage assessment

Impact level: P3
Assessment status: supported
Impact basis: This is stale release-availability wording; explicit setup succeeds and no runtime failure or consequential behavior change was observed.
Workaround status: available
Workaround basis: The tested published package accepts the explicit client ID and creates the registration without a source change. Native-client usability remains unverified.

Originally created by @coygeek on GitHub (Oct 26, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7199 ### 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 The FreeBuff guide still says support is main-only, npm 6.7.0 is latest, and setup against `@latest` rejects the client. The published package instead accepts `--client freebuff` and writes its registration. This concerns release-availability wording only. ### Reproduction 1. Read the FreeBuff section of `docs/client-configuration.md` in the default branch and release source listed below. 2. Query `npm view rea-agents dist-tags.latest`, then install the published package in a disposable prefix with disposable HOME, XDG config/data/cache directories, and npm cache. 3. Run the installed `rea setup --client freebuff --skill=false --yes --json` and inspect the disposable home's `.agents/mcp.json`. 4. Create `.config/freebuff-desktop` under that disposable home as a detection marker, then run `rea doctor --client freebuff --json`. ### Expected behavior The guide should describe the published package's accepted setup client accurately while keeping its separate native-client verification limitations. ### Impact and scope Stale availability guidance can confuse readers; no runtime failure or consequential behavior change was observed. The explicit setup command works despite the warning. Native FreeBuff MCP loading and skill discovery were not tested, and creating a detection marker does not verify them. ### REA version Published package: `rea-agents@6.8.0` (`rea --version`: `6.8.0`), returned by npm's `latest` tag. Latest GitHub release: `rea-agents-6.8.0`, revision `160d821ac9a0310afcb8d1fc427862dd6508add5`. Current `main`: `1173c0a9dc1b352a60943a491462294db8f353ae`. ### Runtime and platform Node.js `26.12.1`, npm `12.2.1`, Linux x64; isolated configuration and install directories. ### Target and artifact context Documentation and a disposable client-registration file; no analysis target or native FreeBuff client. ### Interface CLI ### Earliest failure stage Unknown The incorrect wording is visible before setup; no CLI failure stage applies. ### Relevant output or evidence Observed once each: setup exited 0 with `clients.freebuff.status: "configured"` and `appliedActions: ["configured_freebuff"]`, creating `mcpServers.rea`; scoped doctor exited 0 with `registration:freebuff` healthy and registration identity aligned. These are selected fields with disposable paths omitted. Doctor's unrelated environment checks do not establish native-client behavior. The [current guide, lines 568–570](https://github.com/morluto/rea/blob/1173c0a9dc1b352a60943a491462294db8f353ae/docs/client-configuration.md#L568-L570) says: “FreeBuff is main-only and is not in a published release yet; npm 6.7.0 is the latest.” The same paragraph appears at lines 525–527 in the release source. Supporting static evidence: the [published-release client definition, lines 721–735](https://github.com/morluto/rea/blob/160d821ac9a0310afcb8d1fc427862dd6508add5/src/application/SupportedClients.ts#L721-L735) registers `freebuff`. ### Typed outcome or recovery expected Not applicable to this wording defect. Restoration means the release-availability paragraph agrees with the accepted client in the published package, while preserving the native loading and skill-discovery caveat. ### Analysis or suspected cause Observed documentation/package mismatch; no runtime cause is alleged. ### Additional context [Open PR #7066](https://github.com/morluto/rea/pull/7066) already proposes this correction and remains unmerged. This report records the current published-package observation rather than requesting a second implementation. ## References [Closed feature #3243](https://github.com/morluto/rea/issues/3243) concerns adding FreeBuff setup support; the remaining requirement here is accurate release-availability documentation after publication. ## Triage assessment - Impact level: P3 - Assessment status: supported - Impact basis: This is stale release-availability wording; explicit setup succeeds and no runtime failure or consequential behavior change was observed. - Workaround status: available - Workaround basis: The tested published package accepts the explicit client ID and creates the registration without a source change. Native-client usability remains unverified.

bsakaguchi commented

2026-10-31 00:48:42 +00:00

Author

Owner

@morluto commented on GitHub (Oct 26, 2026):

Thank you for documenting the mismatch and checking the published package. The guide was corrected in #7066: it now states the minimum published version and retains the native-client verification limitations. Closing this as resolved; the PR did not claim native FreeBuff runtime verification.

@morluto commented on GitHub (Oct 26, 2026): Thank you for documenting the mismatch and checking the published package. The guide was corrected in #7066: it now states the minimum published version and retains the native-client verification limitations. Closing this as resolved; the PR did not claim native FreeBuff runtime verification.

bsakaguchi commented

2026-10-31 00:48:42 +00:00

Author

Owner

@morluto commented on GitHub (Oct 26, 2026):

Reopening after a closer review: #7066 added the minimum published version, but the FreeBuff section still calls the integration and skill location proposed. #7246 addresses that remaining documentation mismatch while retaining the native-client verification caveat. My earlier closure overlooked that wording; thanks for the correction.

@morluto commented on GitHub (Oct 26, 2026): Reopening after a closer review: #7066 added the minimum published version, but the FreeBuff section still calls the integration and skill location proposed. #7246 addresses that remaining documentation mismatch while retaining the native-client verification caveat. My earlier closure overlooked that wording; thanks for the correction.

bsakaguchi referenced this issue

2026-11-01 21:10:57 +00:00

[GH-ISSUE #3796] [Tracker] Open feature requests by area (October 2026) #1471

bsakaguchi closed this issue

2026-11-04 12:09:20 +00:00