[PR #3] [MERGED] [codex] Publish REA as reaa #1800

New issue

Closed

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

bsakaguchi commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3
Author: @morluto
Created: 7/12/2026
Status: ✅ Merged
Merged: 7/12/2026
Merged by: @morluto

Base: main ← Head: codex/publish-reaa

📝 Commits (1)

853a547 Rename npm package to reaa

📊 Changes

6 files changed (+17 additions, -17 deletions)

View changed files

📝 README.md (+6 -6)
📝 package-lock.json (+2 -2)
📝 package.json (+1 -1)
📝 scripts/verify-package.mjs (+3 -3)
📝 src/identity.ts (+2 -2)
📝 tests/setupConfig.test.ts (+3 -3)

📄 Description

Why

The scoped npm locator @morluto/rea weakens the otherwise concise REA onboarding flow. The unscoped rea package is already occupied, while reaa is available.

What changed

Rename only the npm package locator to reaa.
Keep the product, installed executable, MCP key, repository, and skill named REA / rea.
Update floating setup registrations to npx -y reaa mcp.
Update the lockfile, identity assertions, package verifier, setup tests, and README examples.

User impact

Users can run npx -y reaa setup --yes, while globally installed and package-provided commands remain rea. Existing unpublished scoped-package references are removed before the first public release.

Verification

npm run check (102 tests)
npm run verify:package (42 MCP tools and target-free behavior)
npm pack --dry-run (33 files, no Python bytecode)
npx -y ./reaa-0.1.0.tgz --help
npm exec --yes --package ./reaa-0.1.0.tgz -- rea --help
Autoreview with gpt-5.6-terra: clean

_{🔄 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/3 **Author:** [@morluto](https://github.com/morluto) **Created:** 7/12/2026 **Status:** ✅ Merged **Merged:** 7/12/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/publish-reaa` --- ### 📝 Commits (1) - [`853a547`](https://github.com/morluto/rea/commit/853a54799bea2b66e18d2e51e067c5b07c69c488) Rename npm package to reaa ### 📊 Changes **6 files changed** (+17 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+6 -6) 📝 `package-lock.json` (+2 -2) 📝 `package.json` (+1 -1) 📝 `scripts/verify-package.mjs` (+3 -3) 📝 `src/identity.ts` (+2 -2) 📝 `tests/setupConfig.test.ts` (+3 -3) </details> ### 📄 Description ## Why The scoped npm locator `@morluto/rea` weakens the otherwise concise REA onboarding flow. The unscoped `rea` package is already occupied, while `reaa` is available. ## What changed - Rename only the npm package locator to `reaa`. - Keep the product, installed executable, MCP key, repository, and skill named `REA` / `rea`. - Update floating setup registrations to `npx -y reaa mcp`. - Update the lockfile, identity assertions, package verifier, setup tests, and README examples. ## User impact Users can run `npx -y reaa setup --yes`, while globally installed and package-provided commands remain `rea`. Existing unpublished scoped-package references are removed before the first public release. ## Verification - `npm run check` (102 tests) - `npm run verify:package` (42 MCP tools and target-free behavior) - `npm pack --dry-run` (33 files, no Python bytecode) - `npx -y ./reaa-0.1.0.tgz --help` - `npm exec --yes --package ./reaa-0.1.0.tgz -- rea --help` - Autoreview with `gpt-5.6-terra`: clean --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

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