[PR #465] [MERGED] fix(npm): preserve explicit setup versions #2010

New issue

Closed

opened 2026-10-16 21:13:21 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:13:21 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/465
Author: @morluto
Created: 8/6/2026
Status: ✅ Merged
Merged: 8/9/2026
Merged by: @morluto

Base: main ← Head: agent/refresh-stale-npx-bootstrap

📝 Commits (4)

78f3948 fix(npm): refresh stale setup bootstraps
b84008a Merge remote-tracking branch 'origin/main' into agent/refresh-stale-npx-bootstrap
ed000e1 fix(npm): preserve explicit setup versions
6599e50 docs: distinguish first-run and refresh setup

📊 Changes

13 files changed (+34 additions, -296 deletions)

View changed files

📝 README.md (+8 -10)
📝 README_ar.md (+2 -2)
📝 README_ja.md (+2 -2)
📝 README_ko.md (+2 -2)
📝 README_zh.md (+2 -2)
📝 docs/installation.md (+8 -10)
📝 package.json (+0 -1)
➖ scripts/package-runner-bootstrap.d.mts (+0 -19)
➖ scripts/package-runner-bootstrap.mjs (+0 -72)
📝 scripts/rea.mjs (+1 -11)
📝 tests/boundary/cli/dispatcher.test.ts (+0 -8)
➖ tests/boundary/cli/packageRunnerBootstrap.test.ts (+0 -153)
📝 tests/conformance/readmeConsistency.test.ts (+9 -4)

📄 Description

Description

npm consumes a positional package spec before launching the selected binary. Once REA starts, npx rea-agents setup and npx rea-agents@2.4.0 setup can therefore expose the same arguments and environment. The dispatcher cannot safely refresh one without risking replacement of an intentional exact-version request.

This change removes that ambiguous hidden self-relaunch. Each README keeps one low-friction npx rea-agents setup first-run entrypoint. Repeated quick-start, agent setup, terminal/no-install, and post-install paths explicitly request current online metadata with npx --yes --prefer-online rea-agents@latest setup. REA always runs the version npm selected.

The obsolete bootstrap helper, declaration, package entry, and implementation-shaped tests are removed. Documentation conformance now guards both the simple first-run entrypoint and the explicit freshness/rollback contract.

Intentional rollbacks remain available through:

npm exec --yes --package=rea-agents@2.4.0 -- rea setup

Type of Change

Bug fix
Documentation update
Refactoring
Tool contract change (MCP schema modification)

Testing Performed

npm exec -- vitest run tests/boundary/cli/dispatcher.test.ts tests/conformance/readmeConsistency.test.ts (10 tests passed)
npm run check:fast
npm run docs:check
npm pack --dry-run --json (dispatcher present; removed bootstrap absent)
npm run verify:package built and packed successfully, then stopped in the unrelated Linux Hopper platform check because Xvfb is unavailable on the local host

Tool Contract Impact

None. MCP tools and schemas are unchanged.

_{🔄 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/465 **Author:** [@morluto](https://github.com/morluto) **Created:** 8/6/2026 **Status:** ✅ Merged **Merged:** 8/9/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `agent/refresh-stale-npx-bootstrap` --- ### 📝 Commits (4) - [`78f3948`](https://github.com/morluto/rea/commit/78f39483b6992a0b98ee95666358e4b42af18343) fix(npm): refresh stale setup bootstraps - [`b84008a`](https://github.com/morluto/rea/commit/b84008ae4827dc60f7ab6e30aae39c54cf9b1194) Merge remote-tracking branch 'origin/main' into agent/refresh-stale-npx-bootstrap - [`ed000e1`](https://github.com/morluto/rea/commit/ed000e145990ba89f31197de615370ae0ec14259) fix(npm): preserve explicit setup versions - [`6599e50`](https://github.com/morluto/rea/commit/6599e50bd2e2ad9f3f96e956a42d4234a660e08c) docs: distinguish first-run and refresh setup ### 📊 Changes **13 files changed** (+34 additions, -296 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+8 -10) 📝 `README_ar.md` (+2 -2) 📝 `README_ja.md` (+2 -2) 📝 `README_ko.md` (+2 -2) 📝 `README_zh.md` (+2 -2) 📝 `docs/installation.md` (+8 -10) 📝 `package.json` (+0 -1) ➖ `scripts/package-runner-bootstrap.d.mts` (+0 -19) ➖ `scripts/package-runner-bootstrap.mjs` (+0 -72) 📝 `scripts/rea.mjs` (+1 -11) 📝 `tests/boundary/cli/dispatcher.test.ts` (+0 -8) ➖ `tests/boundary/cli/packageRunnerBootstrap.test.ts` (+0 -153) 📝 `tests/conformance/readmeConsistency.test.ts` (+9 -4) </details> ### 📄 Description ## Description npm consumes a positional package spec before launching the selected binary. Once REA starts, `npx rea-agents setup` and `npx rea-agents@2.4.0 setup` can therefore expose the same arguments and environment. The dispatcher cannot safely refresh one without risking replacement of an intentional exact-version request. This change removes that ambiguous hidden self-relaunch. Each README keeps one low-friction `npx rea-agents setup` first-run entrypoint. Repeated quick-start, agent setup, terminal/no-install, and post-install paths explicitly request current online metadata with `npx --yes --prefer-online rea-agents@latest setup`. REA always runs the version npm selected. The obsolete bootstrap helper, declaration, package entry, and implementation-shaped tests are removed. Documentation conformance now guards both the simple first-run entrypoint and the explicit freshness/rollback contract. Intentional rollbacks remain available through: ```bash npm exec --yes --package=rea-agents@2.4.0 -- rea setup ``` ## Type of Change - [x] Bug fix - [x] Documentation update - [x] Refactoring - [ ] Tool contract change (MCP schema modification) ## Testing Performed - `npm exec -- vitest run tests/boundary/cli/dispatcher.test.ts tests/conformance/readmeConsistency.test.ts` (10 tests passed) - `npm run check:fast` - `npm run docs:check` - `npm pack --dry-run --json` (dispatcher present; removed bootstrap absent) - `npm run verify:package` built and packed successfully, then stopped in the unrelated Linux Hopper platform check because Xvfb is unavailable on the local host ## Tool Contract Impact None. MCP tools and schemas are unchanged. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-16 21:13:21 +00:00