[PR #1627] [MERGED] fix(onboarding): isolate client homes and clarify npm release support #4710

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

📋 Pull Request Information

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

Base: main ← Head: fix/agent-client-onboarding


📝 Commits (1)

  • a7ba07b fix(onboarding): isolate native client homes and clarify release scope

📊 Changes

4 files changed (+29 additions, -17 deletions)

View changed files

📝 docs/installation.md (+16 -2)
📝 docs/testing.md (+9 -5)
📝 scripts/verify-deepseek-client.mjs (+2 -2)
📝 scripts/verify-native-agent-client.mjs (+2 -8)

📄 Description

First-time users following the Pi/Hermes commands in the installation guide can download npm 6.3.0, which rejects both client IDs. Document the checked release and point those integrations to a build containing them.

The native client verifiers also left HOME unset on POSIX, allowing OS-account resources to participate in disposable runs. Bind HOME and USERPROFILE, remove Pi's explicit skill setting and DeepSeek's agents-home override, and verify their default personal skill discovery through real native clients.

Closes #1625
Closes #1626
Refs #1587

Validation: 8 sequential native call runs after the isolation change, plus Pi, Hermes, Hermes sticky profile and DeepSeek repeated on the final rebased head. Each discovered all 170 REA tools, loaded the installed skill and returned validated Unicode-path JavaScript Evidence. npm run check and npm run docs:check passed. The branch was subsequently rebased onto bbd01923 (including the separately merged duplicate-fixture fix #1631) and passed build:cached, check:ci and docs:check again; native client calls were repeated on that integrated head. Reduced HOME probes reproduced the original fallback twice; released 6.3.0 rejected Pi and Hermes twice each before writes.

Native clients: Pi 1.1.0, Hermes 66605471/Python 3.14.7, DeepSeek Harness 0.2.0-rc.2, Linux x64/Node 24.18.0. Verifier model responses use a deterministic loopback fixture; these results do not establish live DeepSeek/other model-provider, native Windows or analysis-engine coverage. Separate live Codex-backed client and cold-npx audits are recorded in #1587. Two fresh native Pi and two Hermes model runs answered the inert bundle questions correctly; one Pi run recovered from an invalid seed. Six missing-target runs clarified with zero REA operations. DeepSeek returned correct answers but did not exit; two no-REA, zero-tool controls also failed to exit. These client-owned or uncertain observations are tracked in #1632, #1633 and #1636; this PR does not add speculative production workarounds. Two independent empty-cache npx 6.3.0 Codex installs passed approval/no-write planning, install, idempotence, doctor and actual CLI/MCP analysis (139 release tools), with two successful native-PTY approval cancellations. Other model providers/platforms remain TODO.


🔄 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/1627 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/10/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/agent-client-onboarding` --- ### 📝 Commits (1) - [`a7ba07b`](https://github.com/morluto/rea/commit/a7ba07ba7331d585bf1f8e570a98fb973edc15c6) fix(onboarding): isolate native client homes and clarify release scope ### 📊 Changes **4 files changed** (+29 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+16 -2) 📝 `docs/testing.md` (+9 -5) 📝 `scripts/verify-deepseek-client.mjs` (+2 -2) 📝 `scripts/verify-native-agent-client.mjs` (+2 -8) </details> ### 📄 Description First-time users following the Pi/Hermes commands in the installation guide can download npm 6.3.0, which rejects both client IDs. Document the checked release and point those integrations to a build containing them. The native client verifiers also left HOME unset on POSIX, allowing OS-account resources to participate in disposable runs. Bind HOME and USERPROFILE, remove Pi's explicit skill setting and DeepSeek's agents-home override, and verify their default personal skill discovery through real native clients. Closes #1625 Closes #1626 Refs #1587 Validation: 8 sequential native call runs after the isolation change, plus Pi, Hermes, Hermes sticky profile and DeepSeek repeated on the final rebased head. Each discovered all 170 REA tools, loaded the installed skill and returned validated Unicode-path JavaScript Evidence. npm run check and npm run docs:check passed. The branch was subsequently rebased onto bbd01923 (including the separately merged duplicate-fixture fix #1631) and passed build:cached, check:ci and docs:check again; native client calls were repeated on that integrated head. Reduced HOME probes reproduced the original fallback twice; released 6.3.0 rejected Pi and Hermes twice each before writes. Native clients: Pi 1.1.0, Hermes 66605471/Python 3.14.7, DeepSeek Harness 0.2.0-rc.2, Linux x64/Node 24.18.0. Verifier model responses use a deterministic loopback fixture; these results do not establish live DeepSeek/other model-provider, native Windows or analysis-engine coverage. Separate live Codex-backed client and cold-npx audits are recorded in #1587. Two fresh native Pi and two Hermes model runs answered the inert bundle questions correctly; one Pi run recovered from an invalid seed. Six missing-target runs clarified with zero REA operations. DeepSeek returned correct answers but did not exit; two no-REA, zero-tool controls also failed to exit. These client-owned or uncertain observations are tracked in #1632, #1633 and #1636; this PR does not add speculative production workarounds. Two independent empty-cache npx 6.3.0 Codex installs passed approval/no-write planning, install, idempotence, doctor and actual CLI/MCP analysis (139 release tools), with two successful native-PTY approval cancellations. Other model providers/platforms remain TODO. --- <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:13 +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#4710
No description provided.