liteagents 2.4.0 → 2.4.1

package/docs/SILENT_MODE_GUIDE.md

@@ -443,7 +443,7 @@ echo "Exit code: $?"
 
 2. **Review installation log:**
 ```bash
-cat ~/.agentic-kit-install.log
+cat ~/.liteagents-install.log
 ```
 
 3. **Test without silent mode first:**
@@ -463,10 +463,10 @@ node -e "console.log(JSON.parse(require('fs').readFileSync('config.json', 'utf8'
 If you encounter issues:
 
 1. Check this guide for common scenarios
-2. Review the installation log at `~/.agentic-kit-install.log`
+2. Review the installation log at `~/.liteagents-install.log`
 3. Run with `--help` to see all available options
 4. Try interactive mode first to diagnose issues
-5. Report issues at: https://github.com/amrhas82/agentflow/issues
+5. Report issues at: https://github.com/amrhas82/liteagents/issues
 
 ## Best Practices
 
@@ -488,7 +488,7 @@ set -e  # Exit on error
 # Configuration
 VARIANT="${AGENTIC_KIT_VARIANT:-lite}"
 TOOLS="${AGENTIC_KIT_TOOLS:-claude}"
-INSTALL_PATH="${AGENTIC_KIT_PATH:-/opt/agentic-kit}"
+INSTALL_PATH="${AGENTIC_KIT_PATH:-/opt/liteagents}"
 
 # Run installation
 echo "Installing Agentic Kit ($VARIANT variant, tools: $TOOLS)..."

package/docs/SKILLS_CONVERSION.md

@@ -8,7 +8,7 @@ This document describes the transformation of 22 Claude skills from `~/.factory/
 
 **Original Location**: `~/.factory/commands/`  
 **Total Skills Transformed**: 22  
-**Output Location**: `/home/hamr/PycharmProjects/agentflow/commands/`
+**Output Location**: `/home/hamr/PycharmProjects/liteagents/commands/`
 
 ## Conversion Process
 

package/docs/TESTING.md

@@ -127,7 +127,7 @@ node tests/installer/path-handling-testing.test.js
 ```
 
 **Features Tested**:
-- `~/.agentic-kit` → `/home/user/.agentic-kit`
+- `~/.liteagents` → `/home/user/.liteagents`
 - `./local` → `/current/directory/local`
 - Path traversal prevention (`../../../etc/passwd` rejected)
 - Unicode support (émoji, 中文, العربية)
@@ -384,7 +384,7 @@ Recommended quality gates:
 **Solution**:
 ```bash
 # Manual cleanup
-rm -rf /tmp/agentic-kit-test-*
+rm -rf /tmp/liteagents-test-*
 rm -rf /tmp/variant-test-*
 rm -rf /tmp/multi-tool-test-*
 rm -rf /tmp/error-test-*

package/docs/TROUBLESHOOTING.md

@@ -557,7 +557,7 @@ npm install -g agentic-toolkit
 
 1. **Check which files are loaded:**
    ```bash
-   du -sh agentflow/
+   du -sh liteagents/
    du -sh skills/
    ```
 
@@ -756,7 +756,7 @@ A: Just refresh Claude (F5). Usually no computer restart needed.
 **Q: Where are files stored?**
 A: Depends on installation method:
 - npm: `node_modules/agentic-toolkit/`
-- Development: `/path/to/agentflow/`
+- Development: `/path/to/liteagents/`
 
 **Q: Can I use multiple variants at once?**
 A: No, only one variant at a time. Reinstall to switch.

package/docs/VARIANT_CONFIGURATION.md

@@ -1,6 +1,6 @@
 # Variant Configuration Guide
 
-**Purpose:** This document explains the rationale for variant configurations and skill selection across all agentflow tools (Claude, Opencode, Ampcode, Droid).
+**Purpose:** This document explains the rationale for variant configurations and skill selection across all liteagents tools (Claude, Opencode, Ampcode, Droid).
 
 **Last Updated:** 2025-11-04
 
@@ -18,7 +18,7 @@
 
 ## Variant Philosophy
 
-The agentflow installer offers **three variant levels** to accommodate different user needs and resource constraints:
+The liteagents installer offers **three variant levels** to accommodate different user needs and resource constraints:
 
 ### Design Principles
 
@@ -153,7 +153,7 @@ These advanced skills are available only in the **Pro variant**:
 - All hooks
 
 **Use Cases:**
-- Try agentflow with minimal commitment
+- Try liteagents with minimal commitment
 - Learn the agent system before full installation
 - Limited resource environments (cloud VMs, containers)
 - Quick setup for demonstrations
@@ -269,7 +269,7 @@ While all tools share the same variant structure and core skills, each has optim
 ### Choosing a Variant
 
 **Start with Lite if:**
-- You're evaluating agentflow for the first time
+- You're evaluating liteagents for the first time
 - You have limited disk space (< 50 MB available)
 - You only need basic workflow management
 - You want to learn the system before full installation
@@ -358,7 +358,7 @@ Skills are updated independently of agents:
 
 ### Variant Evolution
 
-As agentflow evolves, variant definitions may change:
+As liteagents evolves, variant definitions may change:
 
 **Standard Variant Philosophy:**
 - Will always include essential document processing (pdf, docx, xlsx, pptx)

package/installer/cli.js

@@ -369,7 +369,7 @@ class InteractiveInstaller {
       return {
         type: 'Missing Package Error',
         advice: [
-          'Run: npm install -g agentflow',
+          'Run: npm install -g liteagents',
           'Check: packages directory exists'
         ],
         technicalDetails: `Missing file or package validation failed`
@@ -418,7 +418,7 @@ class InteractiveInstaller {
       type: 'Unknown Error',
       advice: [
         'Try running installer again',
-        'Report at: https://github.com/amrhas82/agentflow/issues'
+        'Report at: https://github.com/amrhas82/liteagents/issues'
       ],
       technicalDetails: error.stack ? error.stack.split('\n')[1] : 'No additional details'
     };
@@ -726,7 +726,7 @@ ${colors.bright}v2.4.0 | 11 agents + 20 commands per tool${colors.reset}
    * @param {string} toolName - Display name of the tool
    */
   /**
-   * Generate and save installation report to ~/.agentflow-install.log
+   * Generate and save installation report to ~/.liteagents-install.log
    * Creates a detailed log of the installation session
    *
    * @param {array} successfulInstalls - Array of successful installation objects

package/installer/report-template.js

@@ -6,11 +6,11 @@ const os = require('os');
  * Report Template Generator
  *
  * Generates detailed installation reports with summary and per-tool details.
- * Reports are saved to ~/.agentflow-install.log after each installation.
+ * Reports are saved to ~/.liteagents-install.log after each installation.
  */
 class ReportTemplate {
   constructor() {
-    this.reportPath = path.join(os.homedir(), '.agentflow-install.log');
+    this.reportPath = path.join(os.homedir(), '.liteagents-install.log');
   }
 
   /**
@@ -268,7 +268,7 @@ WARNINGS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 For support and documentation, visit:
-https://github.com/amrhas82/agentflow
+https://github.com/amrhas82/liteagents
 
 Report saved to: ${this.reportPath}
 

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "liteagents",
-  "version": "2.4.0",
+  "version": "2.4.1",
   "description": "AI development toolkit with 11 specialized agents and 20 commands. Simple one-question installer for Claude, Opencode, Ampcode, and Droid.",
   "main": "index.js",
   "bin": {
-    "agentflow": "./installer/cli.js",
-    "agflow": "./cli.js"
+    "liteagents": "./installer/cli.js",
+    "liteag": "./cli.js"
   },
   "scripts": {
     "test": "node tests/run-all-tests.js",
@@ -17,9 +17,6 @@
     "validate": "node ./scripts/validate-package.js",
     "validate-packages": "node scripts/validate-all-packages.js",
     "prepublishOnly": "npm run clean && npm run validate",
-    "publish:npm": "npm publish --registry https://registry.npmjs.org --access public",
-    "publish:github": "npm publish --registry https://npm.pkg.github.com",
-    "publish:both": "npm run publish:npm && npm run publish:github",
     "postinstall": "node postinstall.js"
   },
   "keywords": [
@@ -51,12 +48,12 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/amrhas82/agentflow.git"
+    "url": "https://github.com/amrhas82/liteagents.git"
   },
   "bugs": {
-    "url": "https://github.com/amrhas82/agentflow/issues"
+    "url": "https://github.com/amrhas82/liteagents/issues"
   },
-  "homepage": "https://github.com/amrhas82/agentflow#readme",
+  "homepage": "https://github.com/amrhas82/liteagents#readme",
   "publishConfig": {
     "registry": "https://registry.npmjs.org",
     "access": "public"

package/docs/DUAL_PUBLISH_SUMMARY.md

@@ -1,177 +0,0 @@
-# Dual Publishing Setup Complete ✅
-
-Your Agentic Kit package is now configured to publish to **both npm.js and GitHub Packages** with every update!
-
----
-
-## ✅ What Was Configured
-
-### 1. Package Configuration (`package.json`)
-- Default registry set to npm.js (easier for users)
-- Added publishing scripts:
-  - `npm run publish:npm` - Publish to npm.js only
-  - `npm run publish:github` - Publish to GitHub Packages only
-  - `npm run publish:both` - **Publish to BOTH** (recommended)
-
-### 2. Authentication (`.npmrc`)
-- GitHub Packages authentication ready
-- Uses `GITHUB_TOKEN` environment variable
-
-### 3. Publishing Script (`publish.sh`)
-- Automated script that validates and publishes to both registries
-- Handles missing GitHub token gracefully
-
-### 4. Documentation
-- **`docs/PUBLISHING.md`** - Complete merged guide for all publishing
-- **`docs/GITHUB_SETUP.md`** - First-time GitHub Packages setup
-- **Deleted:** `docs/GITHUB_PACKAGES.md` (merged into PUBLISHING.md)
-
----
-
-## 🚀 Quick Start - Publish to Both Registries
-
-### First Time Only: Setup GitHub Packages
-
-1. **Create GitHub Token:**
-   - Visit: https://github.com/settings/tokens
-   - Click "Generate new token (classic)"
-   - Select scopes: `write:packages`, `read:packages`
-   - Copy token (starts with `ghp_`)
-
-2. **Set Environment Variable:**
-   ```bash
-   export GITHUB_TOKEN=ghp_your_token_here
-
-   # Make it permanent (add to ~/.bashrc or ~/.zshrc)
-   echo 'export GITHUB_TOKEN=ghp_your_token_here' >> ~/.bashrc
-   source ~/.bashrc
-   ```
-
-3. **Verify:**
-   ```bash
-   echo $GITHUB_TOKEN  # Should show your token
-   ```
-
-**See full setup guide:** [`docs/GITHUB_SETUP.md`](docs/GITHUB_SETUP.md)
-
----
-
-## 📦 Publishing Workflow
-
-### Option 1: Use the Script (Easiest)
-
-```bash
-cd /home/hamr/PycharmProjects/agentflow
-./publish.sh
-```
-
-### Option 2: Use npm Scripts
-
-```bash
-# Publish to both registries
-npm run publish:both
-
-# Or publish individually
-npm run publish:npm      # npm.js only
-npm run publish:github   # GitHub Packages only
-```
-
-### Complete Release Process
-
-```bash
-# 1. Update version
-./UPDATE_VERSION.sh 1.2.0
-
-# 2. Update CHANGELOG.md
-# (Add your release notes)
-
-# 3. Commit and tag
-git add .
-git commit -m "Bump version to 1.2.0"
-git tag v1.2.0
-git push origin main --tags
-
-# 4. Publish to both registries
-npm run publish:both
-
-# 5. Verify
-# - npm.js: https://www.npmjs.com/package/agentflow
-# - GitHub: https://github.com/amrhas82/agentflow/packages
-```
-
----
-
-## 📋 Files Modified/Created
-
-### Modified:
-- ✅ `package.json` - Added publish scripts, set npm.js as default
-- ✅ `.npmrc` - GitHub Packages authentication
-- ✅ `docs/PUBLISHING.md` - Merged and updated complete guide
-
-### Created:
-- ✅ `publish.sh` - Automated dual publishing script
-- ✅ `docs/GITHUB_SETUP.md` - First-time setup guide
-- ✅ `.gitignore` - Prevents committing sensitive/backup files
-
-### Deleted:
-- ✅ `docs/GITHUB_PACKAGES.md` - Merged into PUBLISHING.md
-
----
-
-## 🔍 Verification After Publishing
-
-### npm.js
-- **Page:** https://www.npmjs.com/package/agentflow
-- **Test:** `npx agentflow --help`
-
-### GitHub Packages
-- **Page:** https://github.com/amrhas82/agentflow (click "Packages" on right)
-- **Direct:** https://github.com/amrhas82/agentflow/packages
-
----
-
-## ❓ Common Questions
-
-### Q: Do I need to publish to both every time?
-**A:** Yes, each registry is separate. Use `npm run publish:both` to publish everywhere with one command.
-
-### Q: What if I only want to publish to npm.js?
-**A:** Just use `npm run publish:npm` or regular `npm publish --access public`
-
-### Q: What if my GitHub token expires?
-**A:** Generate a new token at https://github.com/settings/tokens and update your `GITHUB_TOKEN` variable.
-
-### Q: Can users install from either registry?
-**A:** Yes! npm.js is easier (no token required). GitHub Packages requires users to set up `.npmrc` with their own GitHub token.
-
----
-
-## 📚 Full Documentation
-
-- **Publishing Guide:** [`docs/PUBLISHING.md`](PUBLISHING.md)
-- **GitHub Setup:** [`docs/GITHUB_SETUP.md`](docs/GITHUB_SETUP.md)
-- **Version Management:** Use `./UPDATE_VERSION.sh`
-
----
-
-## 🎯 Next Steps
-
-1. **Setup GitHub Token** (if not done yet)
-   - Follow: [`docs/GITHUB_SETUP.md`](docs/GITHUB_SETUP.md)
-
-2. **Test Publishing**
-   ```bash
-   npm run publish:both
-   ```
-
-3. **Verify Both Registries**
-   - Check npm.js and GitHub Packages pages
-
----
-
-**You're all set! 🎉**
-
-Every time you want to publish an update, just run:
-```bash
-npm run publish:both
-```

package/docs/GITHUB_PACKAGES.md

@@ -1,181 +0,0 @@
-# Publishing to GitHub Packages
-
-This guide shows how to publish `agentflow` to GitHub Packages npm registry.
-
-## Prerequisites
-
-- GitHub account with access to `amrhas82/agentic-kit` repository
-- npm installed locally
-- Git repository already pushed to GitHub
-
-## Setup Steps
-
-### 1. Create GitHub Personal Access Token
-
-1. Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
-   - Direct link: https://github.com/settings/tokens
-2. Click **"Generate new token"** → **"Generate new token (classic)"**
-3. Configure token:
-   - **Note**: `Publish agentic-kit to GitHub Packages`
-   - **Expiration**: Choose your preference (90 days recommended)
-   - **Scopes**: Select these permissions:
-     - ✅ `write:packages` - Upload packages to GitHub Package Registry
-     - ✅ `read:packages` - Download packages from GitHub Package Registry
-     - ✅ `delete:packages` - Delete packages from GitHub Package Registry (optional)
-4. Click **"Generate token"**
-5. **IMPORTANT**: Copy the token immediately (you won't see it again)
-
-### 2. Configure Authentication
-
-Set your GitHub token as an environment variable:
-
-```bash
-# On Linux/macOS (add to ~/.bashrc or ~/.zshrc for persistence)
-export GITHUB_TOKEN=ghp_your_token_here
-
-# On Windows (Command Prompt)
-set GITHUB_TOKEN=ghp_your_token_here
-
-# On Windows (PowerShell)
-$env:GITHUB_TOKEN="ghp_your_token_here"
-```
-
-**Verify it's set:**
-```bash
-echo $GITHUB_TOKEN    # Linux/macOS
-echo %GITHUB_TOKEN%   # Windows CMD
-echo $env:GITHUB_TOKEN  # Windows PowerShell
-```
-
-### 3. Publish to GitHub Packages
-
-```bash
-cd /home/hamr/PycharmProjects/agentflow
-
-# Ensure you're on the right version
-npm version  # Should show 1.1.0
-
-# Publish to GitHub Packages
-npm publish
-```
-
-### 4. Verify Publication
-
-1. Go to your GitHub repository: https://github.com/amrhas82/agentflow
-2. Click on **"Packages"** on the right sidebar
-3. You should see `agentflow` listed
-
-## Installing from GitHub Packages
-
-Users can install your package from GitHub Packages:
-
-### For Users
-
-Create `.npmrc` in their project or home directory:
-
-```
-@amrhas82:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=THEIR_GITHUB_TOKEN
-```
-
-Then install:
-```bash
-npm install agentflow
-```
-
-## Publishing to Both Registries
-
-You can publish to **both** npm registry AND GitHub Packages:
-
-### Option 1: Publish to npm.js (public registry)
-
-```bash
-# Remove or comment out publishConfig in package.json
-# Then publish
-npm publish --registry https://registry.npmjs.org --access public
-```
-
-### Option 2: Publish to GitHub Packages
-
-```bash
-# Keep publishConfig in package.json pointing to GitHub
-npm publish
-```
-
-### Option 3: Publish to Both (Recommended)
-
-```bash
-# 1. Publish to npm.js first
-npm publish --registry https://registry.npmjs.org --access public
-
-# 2. Then publish to GitHub Packages
-npm publish --registry https://npm.pkg.github.com
-```
-
-## Updating Package.json for Dual Publishing
-
-If you want to make npm.js the default and GitHub Packages optional:
-
-**package.json:**
-```json
-{
-  "name": "agentflow",
-  "version": "1.1.0",
-  "publishConfig": {
-    "registry": "https://registry.npmjs.org",
-    "access": "public"
-  }
-}
-```
-
-Then to publish to GitHub Packages specifically:
-```bash
-npm publish --registry https://npm.pkg.github.com
-```
-
-## Current Configuration
-
-Your package is currently configured to publish to **GitHub Packages by default**.
-
-**package.json** has:
-```json
-"publishConfig": {
-  "registry": "https://npm.pkg.github.com"
-}
-```
-
-**.npmrc** contains:
-```
-@amrhas82:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}
-```
-
-## Troubleshooting
-
-### Error: 401 Unauthorized
-
-- Verify your `GITHUB_TOKEN` is set correctly
-- Ensure token has `write:packages` scope
-- Check token hasn't expired
-
-### Error: 404 Not Found
-
-- Verify repository exists: https://github.com/amrhas82/agentflow
-- Ensure package name matches repository owner: `agentflow`
-
-### Error: 403 Forbidden
-
-- Verify you have write access to the repository
-- Check repository visibility settings (public/private)
-
-### Package Not Showing Up
-
-- Wait a few minutes (can take 5-10 minutes)
-- Check GitHub repository → Packages tab
-- Verify publish command succeeded without errors
-
-## Links
-
-- **GitHub Packages Documentation**: https://docs.github.com/en/packages
-- **npm Registry Documentation**: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry
-- **Package URL (after publishing)**: https://github.com/amrhas82/agentflow/packages