[PR #4] [MERGED] [codex] Publish REA under the morluto scope #1803

New issue

Closed

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

bsakaguchi commented

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

Owner

📋 Pull Request Information

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

Base: main ← Head: codex/publish-morluto-rea

📝 Commits (1)

4c8b334 Publish REA under the morluto scope

📊 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

Summary

Publish REA through the dependable @morluto/rea npm scope while preserving REA as the product, rea as the executable, and rea as the MCP server key.

The previously selected unscoped locator, reaa, was rejected by npm's package-name similarity policy. The scoped locator avoids that global namespace restriction and keeps the user-facing command unchanged.

This updates the manifest and lockfile identity, central product identity, setup-generated MCP launch command, package verifier, setup transaction tests, and README examples. Fresh registrations now launch npx -y @morluto/rea mcp.

Verification

npm run check — 102 tests across 17 files
npm run verify:package — CLI, setup backup/readback/recovery, and target-free beta.3 MCP server with 42 tools
npm pack --dry-run — 33 intended files, no Python cache artifacts
Local tarball npx help smoke test
npm publish --access public — accepted as @morluto/rea@0.1.0

Real-Hopper verification was not repeated for this identity-only change; the package verifier exercises the shared runtime seams without opening Hopper.

Registry CDN smoke tests remain pending initial npm propagation. npm's access API reports the package as public.

_{🔄 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/4 **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-morluto-rea` --- ### 📝 Commits (1) - [`4c8b334`](https://github.com/morluto/rea/commit/4c8b3341c2919dcaadb928097b1aee5e9adb0585) Publish REA under the morluto scope ### 📊 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 ## Summary Publish REA through the dependable `@morluto/rea` npm scope while preserving `REA` as the product, `rea` as the executable, and `rea` as the MCP server key. The previously selected unscoped locator, `reaa`, was rejected by npm's package-name similarity policy. The scoped locator avoids that global namespace restriction and keeps the user-facing command unchanged. This updates the manifest and lockfile identity, central product identity, setup-generated MCP launch command, package verifier, setup transaction tests, and README examples. Fresh registrations now launch `npx -y @morluto/rea mcp`. ## Verification - `npm run check` — 102 tests across 17 files - `npm run verify:package` — CLI, setup backup/readback/recovery, and target-free beta.3 MCP server with 42 tools - `npm pack --dry-run` — 33 intended files, no Python cache artifacts - Local tarball `npx` help smoke test - `npm publish --access public` — accepted as `@morluto/rea@0.1.0` Real-Hopper verification was not repeated for this identity-only change; the package verifier exercises the shared runtime seams without opening Hopper. Registry CDN smoke tests remain pending initial npm propagation. npm's access API reports the package as public. --- <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:12 +00:00