@amrhas82/agentic-kit 1.2.0 → 1.2.1

package/tests/installer/demo-cli-args.js

@@ -1,241 +0,0 @@
-/**
- * Demo: CLI Command-Line Arguments
- *
- * Demonstrates the new command-line argument parsing features
- */
-
-const colors = {
-  green: '\x1b[32m',
-  cyan: '\x1b[36m',
-  yellow: '\x1b[33m',
-  bright: '\x1b[1m',
-  reset: '\x1b[0m'
-};
-
-console.log(`
-${colors.bright}${colors.cyan}CLI Command-Line Arguments Demo${colors.reset}
-${colors.cyan}${'='.repeat(60)}${colors.reset}
-
-${colors.bright}New Features in Subtask 5.3:${colors.reset}
-
-${colors.cyan}1. Command-Line Argument Parsing${colors.reset}
-   The CLI now supports various flags for non-interactive operation:
-
-   ${colors.green}--help, -h${colors.reset}
-   Display usage information and exit
-   Example: node installer/cli.js --help
-
-   ${colors.green}--uninstall <tool>${colors.reset}
-   Uninstall a specific tool
-   Example: node installer/cli.js --uninstall claude
-
-   ${colors.green}--variant <lite|standard|pro>${colors.reset}
-   Select package variant for non-interactive installation
-   Example: node installer/cli.js --variant standard --tools claude
-
-   ${colors.green}--tools <tool1,tool2,...>${colors.reset}
-   Select tools (comma-separated) for non-interactive installation
-   Example: node installer/cli.js --tools claude,opencode
-
-   ${colors.green}--path <tool>=<path>${colors.reset}
-   Specify custom installation path
-   Example: node installer/cli.js --path claude=/custom/path
-
-   ${colors.green}--silent, --non-interactive${colors.reset}
-   Run in silent mode (no prompts, use defaults)
-   Example: node installer/cli.js --variant lite --tools claude --silent
-
-   ${colors.green}--config <file>${colors.reset}
-   Load configuration from JSON file
-   Example: node installer/cli.js --config install-config.json
-
-${colors.cyan}2. Uninstall Command Flow${colors.reset}
-   ${colors.bright}Features:${colors.reset}
-   • Detects installation at default path
-   • Prompts for custom path if not found at default location
-   • Displays file count and confirmation prompt
-   • Creates backup before uninstalling (with timestamp)
-   • Shows real-time progress during uninstall
-   • Displays detailed results (files/directories removed, backup path)
-   • Preserves user-created files not in manifest
-   • Lists any warnings or errors encountered
-
-   ${colors.bright}Example workflow:${colors.reset}
-   $ node installer/cli.js --uninstall claude
-
-   ${colors.cyan}Agentic Kit Uninstaller${colors.reset}
-
-   ${colors.bright}Tool:${colors.reset} Claude Code
-   ${colors.bright}Path:${colors.reset} /home/user/.claude
-
-   ${colors.yellow}This will remove 255 file(s) and create a backup.${colors.reset}
-
-   ${colors.bright}Proceed with uninstallation? (y/N):${colors.reset} y
-
-   ${colors.bright}Uninstalling Claude Code...${colors.reset}
-
-   ${colors.cyan}Progress:${colors.reset} 100% (255/255 files removed)
-
-   ${colors.green}✓ Claude Code uninstalled successfully${colors.reset}
-   ${colors.cyan}Files removed:${colors.reset} 255
-   ${colors.cyan}Directories removed:${colors.reset} 4
-   ${colors.cyan}Backup created:${colors.reset} /home/user/.claude.uninstall-backup.1730649123456
-
-${colors.cyan}3. Non-Interactive Mode${colors.reset}
-   ${colors.bright}Features:${colors.reset}
-   • Accepts variant and tools from command-line
-   • Validates inputs before installation
-   • Displays installation summary
-   • Runs installation without prompts
-   • Supports custom paths via --path flag
-   • Perfect for CI/CD and automated deployments
-
-   ${colors.bright}Example workflow:${colors.reset}
-   $ node installer/cli.js --variant standard --tools claude,opencode
-
-   ${colors.cyan}Agentic Kit Installer (Non-Interactive Mode)${colors.reset}
-
-   ${colors.bright}Installation Summary:${colors.reset}
-   ${colors.cyan}Variant:${colors.reset} Standard (13 agents, 8 skills)
-   ${colors.cyan}Tools:${colors.reset} claude, opencode
-
-   ${colors.bright}Claude Code${colors.reset}
-     Path: ~/.claude
-
-   ${colors.bright}Opencode${colors.reset}
-     Path: ~/.config/opencode
-
-   ${colors.bright}Installing standard package...${colors.reset}
-
-   ${colors.cyan}Performing pre-installation checks...${colors.reset}
-   ${colors.green}✓ Pre-installation checks passed${colors.reset}
-
-   [Installation proceeds automatically...]
-
-${colors.cyan}4. Configuration File Support${colors.reset}
-   ${colors.bright}Format:${colors.reset} JSON file with installation settings
-
-   ${colors.bright}Example config.json:${colors.reset}
-   {
-     "variant": "standard",
-     "tools": ["claude", "opencode"],
-     "paths": {
-       "claude": "~/.claude-custom",
-       "opencode": "~/.config/opencode-custom"
-     },
-     "silent": false
-   }
-
-   ${colors.bright}Usage:${colors.reset}
-   $ node installer/cli.js --config config.json
-
-   ${colors.green}✓ Configuration loaded from config.json${colors.reset}
-
-   [Installation proceeds with config settings...]
-
-${colors.cyan}5. Silent Mode for CI/CD${colors.reset}
-   ${colors.bright}Features:${colors.reset}
-   • No prompts or confirmations
-   • Uses default or specified values
-   • Minimal output (progress and results only)
-   • Perfect for automation scripts
-
-   ${colors.bright}Example:${colors.reset}
-   $ node installer/cli.js --variant lite --tools claude --silent
-
-   [Installation runs without any prompts]
-
-${colors.cyan}${'='.repeat(60)}${colors.reset}
-
-${colors.bright}Implementation Details:${colors.reset}
-
-${colors.cyan}parseCommandLineArgs()${colors.reset}
-• Parses process.argv to extract flags and values
-• Returns structured object with all parsed arguments
-• Handles both long (--flag) and short (-f) forms
-• Supports multiple values (e.g., comma-separated tools)
-• Parses key=value pairs for custom paths
-
-${colors.cyan}showHelp()${colors.reset}
-• Displays comprehensive usage information
-• Shows all available options with examples
-• Lists all tools and variants
-• Provides common usage scenarios
-
-${colors.cyan}runUninstall()${colors.reset}
-• Validates tool ID against available tools
-• Detects installation at default path
-• Prompts for custom path if needed
-• Reads manifest to get file count
-• Confirms with user (unless --silent)
-• Calls InstallationEngine.uninstall()
-• Displays progress and results
-
-${colors.cyan}loadConfig()${colors.reset}
-• Reads JSON configuration file
-• Validates and merges with command-line args
-• Applies settings to installer state
-• Handles errors gracefully
-
-${colors.cyan}runNonInteractive()${colors.reset}
-• Validates variant and tool selections
-• Sets up installation without prompts
-• Displays summary before installation
-• Calls install() method directly
-
-${colors.cyan}${'='.repeat(60)}${colors.reset}
-
-${colors.bright}Testing:${colors.reset}
-
-All 20 tests passing:
-• Parse --help, -h flags
-• Parse --uninstall, --variant, --tools, --path flags
-• Parse --silent, --non-interactive flags
-• Parse --config flag
-• Parse multiple flags together
-• Parse default state (no arguments)
-• Verify method existence (runUninstall, loadConfig, runNonInteractive)
-• Configuration file format validation
-
-${colors.cyan}${'='.repeat(60)}${colors.reset}
-
-${colors.bright}Usage Examples:${colors.reset}
-
-${colors.yellow}# Display help${colors.reset}
-node installer/cli.js --help
-
-${colors.yellow}# Interactive installation (default)${colors.reset}
-node installer/cli.js
-
-${colors.yellow}# Non-interactive installation${colors.reset}
-node installer/cli.js --variant standard --tools claude
-
-${colors.yellow}# Install with custom path${colors.reset}
-node installer/cli.js --variant pro --tools claude --path claude=~/.claude-custom
-
-${colors.yellow}# Silent installation for CI/CD${colors.reset}
-node installer/cli.js --variant lite --tools claude --silent
-
-${colors.yellow}# Uninstall a tool${colors.reset}
-node installer/cli.js --uninstall claude
-
-${colors.yellow}# Install from config file${colors.reset}
-node installer/cli.js --config install-config.json
-
-${colors.yellow}# Install multiple tools with custom paths${colors.reset}
-node installer/cli.js --variant pro --tools claude,opencode,ampcode \\
-  --path claude=/custom/claude \\
-  --path opencode=/custom/opencode \\
-  --path ampcode=/custom/ampcode
-
-${colors.cyan}${'='.repeat(60)}${colors.reset}
-
-${colors.green}Subtask 5.3 Complete!${colors.reset}
-
-Next steps (remaining subtasks):
-• 5.4: Add --config file support and --yes flag (partially complete)
-• 5.5: Add upgradeVariant() method to InstallationEngine
-• 5.6: Create comprehensive integration tests
-
-${colors.cyan}${'='.repeat(60)}${colors.reset}
-`);

package/tests/installer/demo-error-handling.js

@@ -1,127 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Demo script for CLI error handling and rollback functionality
- *
- * Demonstrates:
- * - Error categorization with actionable advice
- * - Pre-installation checks
- * - Fatal error handling
- * - Recovery options display
- */
-
-const InteractiveInstaller = require('../../installer/cli');
-
-// ANSI color codes
-const colors = {
-  reset: '\x1b[0m',
-  green: '\x1b[32m',
-  red: '\x1b[31m',
-  yellow: '\x1b[33m',
-  cyan: '\x1b[36m',
-  bright: '\x1b[1m'
-};
-
-console.log(`${colors.cyan}${colors.bright}Demo: CLI Error Handling and Rollback${colors.reset}\n`);
-
-// Create installer instance
-const installer = new InteractiveInstaller();
-
-console.log(`${colors.bright}Scenario 1: Permission Error${colors.reset}`);
-console.log('─'.repeat(60));
-const permError = new Error('Permission denied');
-permError.code = 'EACCES';
-const result1 = installer.categorizeError(permError);
-console.log(`Type: ${colors.yellow}${result1.type}${colors.reset}`);
-console.log(`Message: ${permError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result1.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result1.technicalDetails}\n`);
-
-console.log(`${colors.bright}Scenario 2: Disk Space Error${colors.reset}`);
-console.log('─'.repeat(60));
-const diskError = new Error('No space left on device');
-diskError.code = 'ENOSPC';
-const result2 = installer.categorizeError(diskError);
-console.log(`Type: ${colors.yellow}${result2.type}${colors.reset}`);
-console.log(`Message: ${diskError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result2.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result2.technicalDetails}\n`);
-
-console.log(`${colors.bright}Scenario 3: Network Error${colors.reset}`);
-console.log('─'.repeat(60));
-const netError = new Error('Connection timeout');
-netError.code = 'ETIMEDOUT';
-const result3 = installer.categorizeError(netError);
-console.log(`Type: ${colors.yellow}${result3.type}${colors.reset}`);
-console.log(`Message: ${netError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result3.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result3.technicalDetails}\n`);
-
-console.log(`${colors.bright}Scenario 4: Missing Package Error${colors.reset}`);
-console.log('─'.repeat(60));
-const fileError = new Error('No such file or directory');
-fileError.code = 'ENOENT';
-const result4 = installer.categorizeError(fileError);
-console.log(`Type: ${colors.yellow}${result4.type}${colors.reset}`);
-console.log(`Message: ${fileError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result4.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result4.technicalDetails}\n`);
-
-console.log(`${colors.bright}Scenario 5: Path Validation Error${colors.reset}`);
-console.log('─'.repeat(60));
-const pathError = new Error('Path must be absolute');
-const result5 = installer.categorizeError(pathError);
-console.log(`Type: ${colors.yellow}${result5.type}${colors.reset}`);
-console.log(`Message: ${pathError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result5.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result5.technicalDetails}\n`);
-
-console.log(`${colors.bright}Scenario 6: Installation Error${colors.reset}`);
-console.log('─'.repeat(60));
-const instError = new Error('Failed to install package');
-const result6 = installer.categorizeError(instError);
-console.log(`Type: ${colors.yellow}${result6.type}${colors.reset}`);
-console.log(`Message: ${instError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result6.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result6.technicalDetails}\n`);
-
-console.log(`${colors.bright}Scenario 7: Unknown Error${colors.reset}`);
-console.log('─'.repeat(60));
-const unknownError = new Error('Something completely unexpected happened');
-const result7 = installer.categorizeError(unknownError);
-console.log(`Type: ${colors.yellow}${result7.type}${colors.reset}`);
-console.log(`Message: ${unknownError.message}`);
-console.log(`\n${colors.cyan}Suggested Actions:${colors.reset}`);
-result7.advice.forEach((advice, i) => {
-  console.log(`  ${i + 1}. ${advice}`);
-});
-console.log(`\n${colors.cyan}Technical Details:${colors.reset} ${result7.technicalDetails}\n`);
-
-console.log(`${colors.cyan}${'='.repeat(60)}${colors.reset}`);
-console.log(`${colors.green}${colors.bright}Demo Complete${colors.reset}`);
-console.log(`\n${colors.cyan}Key Features Demonstrated:${colors.reset}`);
-console.log(`  ${colors.green}✓${colors.reset} Error categorization for 7+ error types`);
-console.log(`  ${colors.green}✓${colors.reset} Actionable advice for each error type`);
-console.log(`  ${colors.green}✓${colors.reset} Technical details for debugging`);
-console.log(`  ${colors.green}✓${colors.reset} User-friendly error messages`);
-console.log(`  ${colors.green}✓${colors.reset} Automatic rollback on failures`);
-console.log(`  ${colors.green}✓${colors.reset} Pre-installation validation checks`);
-console.log(`  ${colors.green}✓${colors.reset} Recovery options during installation\n`);

package/tests/installer/demo-silent-mode.js

@@ -1,329 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Silent Mode Demo
- *
- * Demonstrates silent mode functionality with various scenarios
- */
-
-const colors = {
-  green: '\x1b[32m',
-  cyan: '\x1b[36m',
-  yellow: '\x1b[33m',
-  bright: '\x1b[1m',
-  reset: '\x1b[0m',
-  blue: '\x1b[34m',
-  magenta: '\x1b[35m'
-};
-
-console.log(`
-${colors.bright}${colors.cyan}Silent Mode and Non-Interactive Installation Demo${colors.reset}
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Overview:${colors.reset}
-Silent mode (--silent or --non-interactive) enables fully automated installations
-suitable for CI/CD pipelines, Docker containers, and scripted deployments.
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Key Features Implemented in Subtask 5.4:${colors.reset}
-
-${colors.green}✓ Auto-proceed on warnings${colors.reset}
-  - Pre-installation warnings don't block installation
-  - Displays warning message and continues automatically
-  - Perfect for CI/CD where user intervention is impossible
-
-${colors.green}✓ Auto-continue on multi-tool installation failures${colors.reset}
-  - If one tool fails, automatically continues with remaining tools
-  - Failed installations are rolled back (no partial installs)
-  - All successful installations are preserved
-
-${colors.green}✓ Configuration file support${colors.reset}
-  - Load installation settings from JSON file
-  - Supports variant, tools, paths, and silent flag
-  - Enables versioned, repeatable installations
-
-${colors.green}✓ Proper exit codes${colors.reset}
-  - Exit 0: Successful installation or help display
-  - Exit 1: Validation errors, installation failures, missing files
-  - Essential for CI/CD error detection
-
-${colors.green}✓ Comprehensive testing${colors.reset}
-  - 16 dedicated silent mode tests (all passing)
-  - Tests cover: flag parsing, config files, exit codes, behavior
-  - Ensures reliability in automated environments
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Usage Examples:${colors.reset}
-
-${colors.yellow}1. Basic Silent Installation${colors.reset}
-   ${colors.cyan}Command:${colors.reset}
-   node installer/cli.js --variant lite --tools claude --silent
-
-   ${colors.cyan}What happens:${colors.reset}
-   • Validates variant and tools
-   • Performs pre-installation checks
-   • Auto-proceeds on warnings
-   • Installs without any prompts
-   • Displays progress and results
-   • Exits with code 0 on success, 1 on failure
-
-${colors.yellow}2. Multi-Tool Installation${colors.reset}
-   ${colors.cyan}Command:${colors.reset}
-   node installer/cli.js --variant standard --tools claude,opencode --silent
-
-   ${colors.cyan}What happens:${colors.reset}
-   • Installs multiple tools sequentially
-   • If one fails, automatically continues with remaining tools
-   • Failed installations are rolled back
-   • Successful installations are preserved
-   • Final summary shows success/failure for each tool
-
-${colors.yellow}3. Custom Paths${colors.reset}
-   ${colors.cyan}Command:${colors.reset}
-   node installer/cli.js \\
-     --variant pro \\
-     --tools claude \\
-     --path claude=/custom/path \\
-     --silent
-
-   ${colors.cyan}What happens:${colors.reset}
-   • Uses specified custom path instead of default (~/.claude)
-   • No confirmation prompts for custom paths in silent mode
-   • Path validation still occurs (must be absolute and writable)
-
-${colors.yellow}4. Configuration File${colors.reset}
-   ${colors.cyan}Create config.json:${colors.reset}
-   {
-     "variant": "standard",
-     "tools": ["claude", "opencode"],
-     "paths": {
-       "claude": "~/.claude-custom"
-     },
-     "silent": true
-   }
-
-   ${colors.cyan}Command:${colors.reset}
-   node installer/cli.js --config config.json
-
-   ${colors.cyan}What happens:${colors.reset}
-   • Loads all settings from JSON file
-   • Validates configuration
-   • Runs non-interactive installation
-   • Perfect for version-controlled, repeatable installs
-
-${colors.yellow}5. Silent Uninstall${colors.reset}
-   ${colors.cyan}Command:${colors.reset}
-   node installer/cli.js --uninstall claude --silent
-
-   ${colors.cyan}What happens:${colors.reset}
-   • Skips confirmation prompts
-   • Automatically proceeds with uninstallation
-   • Creates backup before removing files
-   • Displays progress and results
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}CI/CD Integration Examples:${colors.reset}
-
-${colors.yellow}GitHub Actions:${colors.reset}
-${colors.cyan}- name: Install Agentic Kit
-  run: |
-    node installer/cli.js \\
-      --variant lite \\
-      --tools claude \\
-      --silent${colors.reset}
-
-${colors.yellow}GitLab CI:${colors.reset}
-${colors.cyan}install_agentic_kit:
-  script:
-    - node installer/cli.js --variant standard --tools claude --silent
-  only:
-    - main${colors.reset}
-
-${colors.yellow}Docker:${colors.reset}
-${colors.cyan}RUN node installer/cli.js \\
-    --variant lite \\
-    --tools claude \\
-    --path claude=/app/.claude \\
-    --silent${colors.reset}
-
-${colors.yellow}Jenkins:${colors.reset}
-${colors.cyan}sh '''
-    node installer/cli.js \\
-        --variant lite \\
-        --tools claude \\
-        --silent
-'''${colors.reset}
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Silent Mode Behavior Details:${colors.reset}
-
-${colors.yellow}Automatic Decisions:${colors.reset}
-┌────────────────────────────┬──────────────────────┬─────────────────────┐
-│ Scenario                   │ Interactive Mode     │ Silent Mode         │
-├────────────────────────────┼──────────────────────┼─────────────────────┤
-│ Pre-install warnings       │ Prompt Y/n          │ Auto-proceed        │
-│ Multi-tool failure         │ Prompt Continue/Quit │ Auto-continue       │
-│ Custom path validation     │ Show confirmation    │ Use without prompt  │
-│ Uninstall confirmation     │ Prompt y/N          │ Auto-proceed        │
-└────────────────────────────┴──────────────────────┴─────────────────────┘
-
-${colors.yellow}Default Paths (when not specified):${colors.reset}
-• Claude:    ~/.claude
-• Opencode:  ~/.config/opencode
-• Ampcode:   ~/.config/amp
-• Droid:     ~/.factory
-
-${colors.yellow}Error Handling:${colors.reset}
-• Fail fast: Exits immediately on pre-installation check failures
-• Continue on partial failure: Continues with remaining tools if one fails
-• Rollback: Failed installations are automatically rolled back
-• Exit codes: 0 for success, 1 for errors
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Testing Results:${colors.reset}
-
-${colors.green}✓ All 16 silent mode tests passing${colors.reset}
-
-Test coverage includes:
-• Flag parsing (--silent, --non-interactive)
-• Configuration file loading and validation
-• Exit codes for various scenarios
-• Auto-proceed behavior on warnings
-• Auto-continue behavior on failures
-• Validation of variant and tools
-• Custom path handling
-• Uninstall silent mode support
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Implementation Details:${colors.reset}
-
-${colors.yellow}Modified Files:${colors.reset}
-• ${colors.cyan}installer/cli.js${colors.reset}
-  - Updated install() to check cliArgs.silent before warning prompts
-  - Updated offerRecoveryOptions() to auto-continue in silent mode
-  - Existing parseCommandLineArgs() already handles --silent flag
-  - Existing runNonInteractive() already validates and installs
-  - Existing loadConfig() already supports silent flag in JSON
-
-${colors.yellow}New Files:${colors.reset}
-• ${colors.cyan}tests/installer/test-silent-mode.js${colors.reset}
-  - 16 comprehensive tests for silent mode
-  - Tests flag parsing, config files, exit codes, behavior
-  - Validates CI/CD suitability
-
-• ${colors.cyan}docs/SILENT_MODE_GUIDE.md${colors.reset}
-  - Complete guide for silent mode usage
-  - CI/CD examples for GitHub Actions, GitLab, Jenkins, Docker
-  - Exit code documentation
-  - Troubleshooting guide
-  - Best practices
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Exit Codes Reference:${colors.reset}
-
-${colors.green}Exit Code 0 (Success):${colors.reset}
-• All tools installed successfully
-• Help information displayed (--help)
-• Uninstallation completed successfully
-
-${colors.yellow}Exit Code 1 (Error):${colors.reset}
-• Invalid variant specified (must be lite, standard, or pro)
-• Invalid tool ID specified
-• Missing required arguments (variant or tools)
-• Installation failed due to errors
-• Pre-installation checks failed
-• Missing configuration file
-• Invalid JSON in configuration file
-• Permission denied errors
-• Insufficient disk space
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Example CI/CD Script:${colors.reset}
-
-${colors.cyan}#!/bin/bash
-set -e  # Exit on error
-
-# Install Agentic Kit in silent mode
-echo "Installing Agentic Kit..."
-node installer/cli.js \\
-    --variant lite \\
-    --tools claude \\
-    --silent
-
-# Check exit code
-if [ $? -eq 0 ]; then
-    echo "✓ Installation successful"
-else
-    echo "✗ Installation failed"
-    exit 1
-fi
-
-# Verify installation
-if [ -f ~/.claude/manifest.json ]; then
-    echo "✓ Installation verified"
-    cat ~/.claude/manifest.json | grep -E '(tool|variant|version)'
-else
-    echo "✗ Verification failed"
-    exit 1
-fi
-
-echo "Agentic Kit ready for use!"${colors.reset}
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}What's New in Subtask 5.4:${colors.reset}
-
-${colors.green}1. Enhanced Silent Mode${colors.reset}
-   • Warning prompts now respect silent mode
-   • Recovery options respect silent mode
-   • Full automation support without any user intervention
-
-${colors.green}2. Comprehensive Testing${colors.reset}
-   • 16 dedicated silent mode tests
-   • Exit code validation
-   • Configuration file validation
-   • Behavior verification
-
-${colors.green}3. Complete Documentation${colors.reset}
-   • SILENT_MODE_GUIDE.md with CI/CD examples
-   • Exit code reference
-   • Troubleshooting guide
-   • Best practices for automation
-
-${colors.green}4. CI/CD Ready${colors.reset}
-   • Proper exit codes for automation
-   • No prompts or hanging
-   • Fail-fast on errors
-   • Continue on partial failures
-   • Automatic rollback on failures
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.bright}Next Steps:${colors.reset}
-
-${colors.yellow}For Developers:${colors.reset}
-• Review SILENT_MODE_GUIDE.md for complete usage instructions
-• Test silent mode in your CI/CD pipeline
-• Use configuration files for repeatable installations
-• Leverage exit codes for error detection
-
-${colors.yellow}Remaining Subtasks:${colors.reset}
-• 5.5: Implement upgradeVariant() for variant upgrades/downgrades
-• 5.6: Create comprehensive integration tests
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-
-${colors.green}${colors.bright}Subtask 5.4 Complete!${colors.reset}
-
-Silent mode is now fully functional and ready for CI/CD environments!
-
-${colors.cyan}${'='.repeat(70)}${colors.reset}
-`);