[PR #1637] [MERGED] docs(installation): clarify that npm 6.3.0 excludes automatic pi and hermes setup #4715

Closed
opened 2026-10-31 00:54:16 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1637
Author: @Totopo27
Created: 10/10/2026
Status: ✅ Merged
Merged: 10/10/2026
Merged by: @morluto

Base: main ← Head: docs/clarify-npm-pi-hermes-setup


📝 Commits (2)

  • 05e6a58 docs(installation): clarify that npm 6.3.0 excludes automatic pi and hermes setup
  • 33a82f5 docs(installation): reconcile release guidance with main

📄 Description

Summary

Closes #1626

Clarify in docs/installation.md that the current published npm release 6.3.0 does not include automatic setup for Pi or Hermes, which require a source build or a subsequent release.

Problem and expected behavior

Users running npx rea-agents@latest setup --client pi or --client hermes download npm package 6.3.0 and encounter VALIDATION_ERROR: Unsupported agent integration because these client integrations were added after the 6.3.0 checkpoint. The documentation previously referenced release checkpoint 5.0.0 and did not state this boundary clearly next to the Pi and Hermes setup instructions.

Change and scope

  • Update the released package checkpoint in docs/installation.md to 6.3.0 (74cf9e14, 166 MCP tools).
  • Explicitly state in the release section and in the Pi / Hermes setup sections that automatic setup for these clients is not included in npm 6.3.0 and requires a source build or a subsequent release.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Documentation (docs/installation.md)
  • CLI and MCP/tool-catalog contract: none
  • Provider, bridge, target-format, or platform compatibility: none
  • Evidence, artifact, provenance, or reconstruction contract: none
  • Process execution, authorization, cleanup, or containment impact: none
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none

Evidence and regression coverage

  • Tests added or updated: none (documentation-only change)
  • Base reproduction or other evidence: Verified against Issue #1626 report
  • User-visible CLI/MCP output: none
  • Remaining proof gaps: none

Validation performed

  • git diff — verified exact 15-line documentation diff.
  • gentle-ai review assess — evaluated diff risk: passive (non_executable_only).

Compatibility, safety, and release

  • Breaking changes or migration steps: none
  • Real Hopper/Ghidra, browser, or OS coverage: none
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: none

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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/1637 **Author:** [@Totopo27](https://github.com/Totopo27) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/10/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `docs/clarify-npm-pi-hermes-setup` --- ### 📝 Commits (2) - [`05e6a58`](https://github.com/morluto/rea/commit/05e6a585d47328445524155a25401020f9fa2f29) docs(installation): clarify that npm 6.3.0 excludes automatic pi and hermes setup - [`33a82f5`](https://github.com/morluto/rea/commit/33a82f5786652bcda4c02853081835f5001d6489) docs(installation): reconcile release guidance with main ### 📄 Description ## Summary Closes #1626 Clarify in `docs/installation.md` that the current published npm release 6.3.0 does not include automatic setup for Pi or Hermes, which require a source build or a subsequent release. ## Problem and expected behavior Users running `npx rea-agents@latest setup --client pi` or `--client hermes` download npm package 6.3.0 and encounter `VALIDATION_ERROR: Unsupported agent integration` because these client integrations were added after the 6.3.0 checkpoint. The documentation previously referenced release checkpoint 5.0.0 and did not state this boundary clearly next to the Pi and Hermes setup instructions. ## Change and scope - Update the released package checkpoint in `docs/installation.md` to 6.3.0 (`74cf9e14`, 166 MCP tools). - Explicitly state in the release section and in the Pi / Hermes setup sections that automatic setup for these clients is not included in npm 6.3.0 and requires a source build or a subsequent release. ## Contract and boundary impact - Semantic owner and earliest changed stage: Documentation (`docs/installation.md`) - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: none - Evidence, artifact, provenance, or reconstruction contract: none - Process execution, authorization, cleanup, or containment impact: none - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none ## Evidence and regression coverage - Tests added or updated: none (documentation-only change) - Base reproduction or other evidence: Verified against Issue #1626 report - User-visible CLI/MCP output: none - Remaining proof gaps: none ## Validation performed - `git diff` — verified exact 15-line documentation diff. - `gentle-ai review assess` — evaluated diff risk: passive (`non_executable_only`). ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: none - Package or release metadata impact: none - Security, privacy, process, or containment review: none ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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-10-31 00:54:16 +00:00
Sign in to join this conversation.
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#4715
No description provided.