fix(release): remove version script that caused recursive lerna invocation (#142)

The version script in package.json was triggered as a lifecycle hook
during `lerna version`, causing a recursive call that failed with
EUNCOMMIT error. Removed conflicting npm scripts (version, publish,
release) and updated documentation to reference workflow source files.

Introduced in #135.

Author: groupsky

docs/PUBLISHING-SETUP.md

@@ -55,7 +55,7 @@ Check that workflow can authenticate:
 To publish packages manually from local machine:
 
 1. **Environment Variables**:
-   - `NPM_TOKEN` - For npm authentication
+   - `NPM_TOKEN` - For npm authentication (or `NODE_AUTH_TOKEN`)
    - `GH_TOKEN` - For creating GitHub releases
 
 2. **Clean Working Tree**: No uncommitted changes
@@ -64,7 +64,30 @@ To publish packages manually from local machine:
 
 4. **Tests Passing**: Run `npm test`
 
-See: docs/agents/release.md for manual release workflow
+### Manual Release Commands
+
+Execute these commands in order:
+
+```bash
+# Set npm authentication (use NPM_TOKEN from environment)
+npm config set //registry.npmjs.org/:_authToken $NPM_TOKEN
+
+# Build packages
+npm run build
+
+# Run tests
+npm run test
+
+# Version packages (creates git tags and GitHub releases)
+npx lerna version --yes --no-private
+
+# Publish to npm
+npx lerna publish from-git --yes --no-private
+```
+
+**Important**: Do NOT create npm scripts named `version` or `publish` - these names conflict with npm lifecycle hooks and cause recursive execution issues.
+
+See: docs/agents/release.md for more details on the release workflow
 
 ## Troubleshooting
 

docs/agents/release.md

@@ -10,38 +10,15 @@ Publishing packages to npm using Lerna-Lite with conventional commits.
 
 ### Production Releases
 
-Automatically triggered on:
+Auto-triggered on push to main. Skipped when commit starts with `chore(release):` or no package changes.
 
-- Push to main branch (after PR merge)
+### Pre-release (Feature Branch)
 
-Releases are SKIPPED when:
-
-- Commit message starts with `chore(release):`
-- No packages have changed since last release
-- Only test/doc/config files changed (see lerna.json ignoreChanges)
-
-### Feature Branch Releases (Pre-release)
-
-Manually triggered via GitHub Actions workflow_dispatch.
-
-Results:
-
-- Pre-release version (e.g., `0.1.0-beta.0`)
-- Custom dist-tag (auto-generated from branch name or specified)
-- NO git tags or GitHub releases
-- Does NOT affect `latest` npm dist-tag
-
-**Note**: Pre-release version changes are NOT committed back to the branch. Each manual trigger increments the pre-release counter (`.0`, `.1`, `.2`, etc.).
+Manual workflow_dispatch trigger. Creates pre-release version with custom dist-tag. NO git tags. Version changes NOT committed to branch.
 
 ### Pre-release Cleanup
 
-When a PR is closed or merged, the cleanup workflow automatically:
-
-- Removes the dist-tag from npm (e.g., `beta`, `feat-xyz`)
-- Leaves published versions in npm (doesn't break existing users)
-- Users can still install by exact version: `npm install @pkg@0.1.0-beta.0`
-
-The dist-tag removal prevents new installations via `npm install @pkg@beta` while keeping the version available for existing users.
+Auto-removes dist-tag when PR closed/merged. Published versions remain available.
 
 ## Version Bumping
 
@@ -59,25 +36,20 @@ Conventional commit types determine version bump:
 
 ### Production Release
 
-Automatic on push to main (after PR merge). No manual action needed.
-
-### Pre-release (Feature Branch Testing)
+Automatic on push to main. No action needed.
 
-Trigger manually via workflow_dispatch. Pre-release publishes to custom dist-tag.
+### Pre-release (Feature Branch)
 
-Requires maintain or admin repository access.
-
-Options:
-
-- Empty dist-tag input: auto-generates from branch name
-- Specified dist-tag: uses provided value (must be valid npm dist-tag format)
-- Dry-run: validates without publishing
+Manual workflow_dispatch. Requires maintain/admin access. Dist-tag auto-generated from branch or specified.
 
 ### Manual/Emergency Release
 
-For local releases when automation unavailable: build → test → version → publish
+NEVER use npm scripts named `version` or `publish` - they conflict with npm lifecycle hooks.
+
+Use npx lerna commands directly with `--yes` and `--no-private` flags.
 
-See: `.github/workflows/release.yml` for workflow implementation
-See: `docs/PUBLISHING-SETUP.md` for first-time configuration and manual release setup
+See: `.github/workflows/release.yml` lines 172-173, 249 for production commands
+See: `.github/workflows/release.yml` lines 192-197, 271-276 for pre-release commands
+See: `docs/PUBLISHING-SETUP.md` for complete manual release procedure
 See: `lerna.json` for Lerna configuration
 See: `docs/agents/git.md` for commit message format

package.json

@@ -40,10 +40,7 @@
     "test": "jest --coverage",
     "test:watch": "jest --watch",
     "test:ci": "jest --ci --coverage --maxWorkers=2",
-    "prepare": "husky",
-    "version": "lerna version --no-private",
-    "publish": "lerna publish from-git --no-private",
-    "release": "npm run build && npm run test && npm run version && npm run publish"
+    "prepare": "husky"
   },
   "devDependencies": {
     "@lerna-lite/cli": "^4.10.3",