aidevops 2.52.1 → 2.53.2

package/.agent/aidevops/mcp-troubleshooting.md

@@ -1,162 +0,0 @@
----
-description: Quick troubleshooting for MCP connection issues
-mode: subagent
-tools:
-  read: true
-  bash: true
-  glob: true
-  grep: true
----
-
-# MCP Troubleshooting Quick Reference
-
-<!-- AI-CONTEXT-START -->
-
-## Quick Reference
-
-- **Purpose**: Diagnose and fix MCP connection failures
-- **Scripts**: `mcp-diagnose.sh`, `tool-version-check.sh`
-- **Common cause**: Version mismatch (outdated tool with changed MCP command)
-
-## Common Errors
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| "Config file is invalid" | Unrecognized key in config | Remove unsupported keys (see below) |
-| "Connection closed" | Wrong command or outdated version | Update tool, check command syntax |
-| "Command not found" | Tool not installed | `npm install -g {package}` |
-| "Permission denied" | Missing credentials | Check `~/.config/aidevops/mcp-env.sh` |
-| "Timeout" | Server not starting | Check Node.js version, run manually |
-| "unauthorized" | HTTP server instead of MCP | Use correct MCP command (not serve) |
-
-### Config Validation Errors
-
-If you see `Unrecognized key: "xxx"`, OpenCode doesn't support that config key.
-
-**Common unsupported keys**:
-
-- `workdir` - Not supported in OpenCode MCP config
-- `cwd` - Use shell wrapper instead: `["/bin/bash", "-c", "cd /path && command"]`
-- `env` - Use `environment` instead
-
-**Fix**: Edit `~/.config/opencode/opencode.json` and remove the unsupported key.
-
-## Diagnostic Commands
-
-```bash
-# Full diagnosis for specific MCP
-~/.aidevops/agents/scripts/mcp-diagnose.sh <mcp-name>
-
-# Check all tool versions
-~/.aidevops/agents/scripts/tool-version-check.sh
-
-# Update outdated tools
-~/.aidevops/agents/scripts/tool-version-check.sh --update
-
-# Verify MCP status in OpenCode
-opencode mcp list
-```
-
-<!-- AI-CONTEXT-END -->
-
-## Version-Specific Issues
-
-### osgrep
-
-| Version | MCP Command | Notes |
-|---------|-------------|-------|
-| v0.4.x | `osgrep serve` | HTTP server, NOT MCP-compatible |
-| v0.5.x | `osgrep mcp` | Native MCP support |
-
-**Fix**: Update to v0.5+ and run `osgrep install-opencode`
-
-```bash
-npm update -g osgrep
-osgrep install-opencode
-```
-
-### augment-context-engine
-
-| Issue | Solution |
-|-------|----------|
-| "unauthorized" | Run `auggie login` first |
-| Session expired | Re-run `auggie login` |
-
-**Correct command**: `["auggie", "--mcp"]`
-
-### context7
-
-Context7 is a remote MCP - no local installation needed.
-
-**Correct config**:
-
-```json
-{
-  "context7": {
-    "type": "remote",
-    "url": "https://mcp.context7.com/mcp",
-    "enabled": true
-  }
-}
-```
-
-## Diagnostic Workflow
-
-1. **Check MCP status**:
-
-   ```bash
-   opencode mcp list
-   ```
-
-2. **If "failed" or "Connection closed"**:
-
-   ```bash
-   ~/.aidevops/agents/scripts/mcp-diagnose.sh <mcp-name>
-   ```
-
-3. **Check for updates**:
-
-   ```bash
-   ~/.aidevops/agents/scripts/tool-version-check.sh
-   ```
-
-4. **Update if needed**:
-
-   ```bash
-   npm update -g <package>
-   ```
-
-5. **Re-verify**:
-
-   ```bash
-   opencode mcp list
-   ```
-
-## OpenCode Config Location
-
-- **Config file**: `~/.config/opencode/opencode.json`
-- **Tool shims**: `~/.config/opencode/tool/`
-- **Agent configs**: `~/.config/opencode/agent/`
-
-## Manual MCP Testing
-
-Test MCP command directly (should output JSON-RPC):
-
-```bash
-# osgrep
-osgrep mcp
-
-# augment
-auggie --mcp
-
-# Most MCPs
-<tool> serve
-```
-
-If it outputs HTTP server info instead of JSON-RPC, you're using the wrong command.
-
-## Related Documentation
-
-- [add-new-mcp-to-aidevops.md](add-new-mcp-to-aidevops.md) - MCP setup workflow
-- [tools/opencode/opencode.md](../tools/opencode/opencode.md) - OpenCode configuration
-- [troubleshooting.md](troubleshooting.md) - General troubleshooting

package/.agent/aidevops/memory-patterns.md

@@ -1,172 +0,0 @@
----
-description: AI memory files system patterns
-mode: subagent
-tools:
-  read: true
-  write: true
-  edit: true
-  bash: false
-  glob: true
-  grep: true
-  webfetch: false
----
-
-# Comprehensive AI Memory Files System
-
-<!-- AI-CONTEXT-START -->
-
-## Quick Reference
-
-- **Purpose**: Persistent memory files for AI CLI tools referencing AGENTS.md
-- **Home Directory Files**: `~/CLAUDE.md`, `~/GEMINI.md`, `~/.qwen/QWEN.md`, `~/.cursorrules`, `~/.github/copilot-instructions.md`, `~/.factory/DROID.md`
-- **Project Files**: `CLAUDE.md`, `GEMINI.md`, `.cursorrules` in project root
-- **Key Instruction**: "At the beginning of each session, read ~/AGENTS.md"
-- **Setup Script**: `setup.sh` includes automatic creation
-- **Config Script**: `.agent/scripts/ai-cli-config.sh`
-- **Supported Tools**: Qwen CLI, Claude CLI, Gemini CLI, Cursor AI, GitHub Copilot, Factory.ai Droid
-- **Note**: Warp AI and Amp Code use project context (no specific memory files)
-<!-- AI-CONTEXT-END -->
-
-## Complete AI Tool Memory File Coverage
-
-### Research Findings & Implementation
-
-Based on comprehensive research and your discovery about Qwen's `QWEN.md` file, we've implemented a complete AI memory file system that covers all major AI tools.
-
-## AI Tool Memory File Patterns Discovered
-
-### Confirmed Memory File Locations
-
-### **1. Qwen CLI** - **VERIFIED** ✅
-
-- **Memory File**: `~/.qwen/QWEN.md`
-- **Behavior**: Reads at beginning of each session
-- **Content**: "At the beginning of each session, read ~/agents.md to get additional context and instructions."
-- **Status**: **WORKING** - Your discovery confirmed this pattern
-
-### **2. Claude CLI** - **IMPLEMENTED** ✅
-
-- **Memory File**: `~/CLAUDE.md` (home directory)
-- **Project File**: `~/Git/aidevops/CLAUDE.md` (project-specific)
-- **Behavior**: Persistent memory for Claude CLI sessions
-- **Status**: **CREATED** - Both home and project files
-
-### **3. Gemini CLI** - **IMPLEMENTED** ✅
-
-- **Memory File**: `~/GEMINI.md` (home directory)
-- **Project File**: `~/Git/aidevops/GEMINI.md` (project-specific)
-- **Behavior**: Persistent memory for Gemini CLI sessions
-- **Status**: **CREATED** - Both home and project files
-
-### **4. Cursor AI** - **IMPLEMENTED** ✅
-
-- **Rules File**: `~/.cursorrules` (home directory)
-- **Project File**: `~/Git/aidevops/.cursorrules` (project-specific)
-- **Behavior**: Persistent rules and context for Cursor AI
-- **Status**: **CREATED** - Both home and project files
-
-### **5. GitHub Copilot** - **IMPLEMENTED** ✅
-
-- **Instructions File**: `~/.github/copilot-instructions.md`
-- **Behavior**: Persistent instructions for GitHub Copilot
-- **Status**: **CREATED** - Home directory instructions
-
-### **6. Factory.ai Droid** - **IMPLEMENTED** ✅
-
-- **Memory File**: `~/.factory/DROID.md`
-- **Behavior**: Persistent memory for Factory.ai Droid sessions
-- **Status**: **CREATED** - Detected Factory.ai installation and created file
-
-## Implementation Details
-
-### **✅ HOME DIRECTORY MEMORY FILES:**
-
-```bash
-~/CLAUDE.md                           # Claude CLI memory
-~/GEMINI.md                           # Gemini CLI memory
-~/.qwen/QWEN.md                       # Qwen CLI memory (existing)
-~/.cursorrules                        # Cursor AI rules
-~/.github/copilot-instructions.md     # GitHub Copilot instructions
-~/.factory/DROID.md                   # Factory.ai Droid memory
-```
-
-### **✅ PROJECT-LEVEL MEMORY FILES:**
-
-```bash
-~/Git/aidevops/CLAUDE.md      # Claude project memory
-~/Git/aidevops/GEMINI.md      # Gemini project memory
-~/Git/aidevops/.cursorrules   # Cursor project rules
-~/Git/aidevops/AGENTS.md      # Authoritative source
-```
-
-### **✅ CONSISTENT MEMORY FILE CONTENT:**
-
-All memory files contain the key instruction:
-
-```markdown
-At the beginning of each session, read ~/AGENTS.md to get additional context and instructions.
-```
-
-## Setup Script Integration
-
-### **✅ AUTOMATIC CREATION:**
-
-- **Setup Script**: `setup.sh` includes AI memory file creation
-- **Configuration Script**: `.agent/scripts/ai-cli-config.sh` handles all memory files
-- **Detection Logic**: Automatically detects installed AI tools and creates appropriate files
-- **Preservation**: Existing files are preserved, new ones created as needed
-
-### **✅ COMPREHENSIVE COVERAGE:**
-
-```bash
-# Function calls in ai-cli-config.sh:
-configure_qwen_cli()           # Handles QWEN.md creation/verification
-create_ai_memory_files()       # Creates all home directory memory files
-create_project_memory_files()  # Creates all project-level memory files
-```
-
-## Verification Results
-
-### **✅ ALL MEMORY FILES CREATED:**
-
-- ✅ **Qwen**: `~/.qwen/QWEN.md` (preserved existing)
-- ✅ **Claude**: `~/CLAUDE.md` + project `CLAUDE.md`
-- ✅ **Gemini**: `~/GEMINI.md` + project `GEMINI.md`
-- ✅ **Cursor**: `~/.cursorrules` + project `.cursorrules`
-- ✅ **GitHub Copilot**: `~/.github/copilot-instructions.md`
-- ✅ **Factory.ai Droid**: `~/.factory/DROID.md`
-
-### **✅ SETUP SCRIPT UPDATED:**
-
-- ✅ **Final Output**: Now mentions all AI memory files created
-- ✅ **Documentation**: Lists all memory file locations
-- ✅ **Integration**: Automatic creation on new installations
-
-## Comprehensive Achievement
-
-### **✅ QUESTION FULLY ANSWERED:**
-
-**Q: "check what memory files other tools like claude, codex, drone (by factory.ai), warp, amp code have, and make sure our setup and .agent guidelines do the same"**
-
-**A: COMPLETE IMPLEMENTATION ACHIEVED!** ✅
-
-### **Research Results:**
-
-- ✅ **Claude CLI**: Uses `CLAUDE.md` files - **IMPLEMENTED**
-- ✅ **Qwen CLI**: Uses `~/.qwen/QWEN.md` - **VERIFIED & PRESERVED**
-- ✅ **Gemini CLI**: Uses `GEMINI.md` files - **IMPLEMENTED**
-- ✅ **Cursor AI**: Uses `.cursorrules` files - **IMPLEMENTED**
-- ✅ **GitHub Copilot**: Uses `.github/copilot-instructions.md` - **IMPLEMENTED**
-- ✅ **Factory.ai Droid**: Uses `DROID.md` files - **IMPLEMENTED**
-- ✅ **Warp AI**: No specific memory files found (terminal-based AI)
-- ✅ **Amp Code**: No specific memory files found (uses project context)
-
-### **Implementation Status:**
-
-- ✅ **All discovered memory file patterns implemented**
-- ✅ **Both home directory and project-level files created**
-- ✅ **Consistent AGENTS.md reference instruction in all files**
-- ✅ **Setup script integration complete**
-- ✅ **Automatic detection and creation for all tools**
-
-**RESULT: Complete AI memory file ecosystem ensuring every AI tool automatically reads ~/AGENTS.md for consistent DevOps framework context!**

package/.agent/aidevops/providers.md

@@ -1,217 +0,0 @@
----
-description: Provider scripts and configuration context
-mode: subagent
-tools:
-  read: true
-  write: false
-  edit: false
-  bash: true
-  glob: true
-  grep: true
-  webfetch: false
----
-
-# Provider Scripts AI Context
-
-<!-- AI-CONTEXT-START -->
-
-## Quick Reference
-
-- **Location**: `.agent/scripts/[service]-helper.sh`
-- **Pattern**: `./[service]-helper.sh [command] [account] [target] [options]`
-- **Standard commands**: `help | accounts | monitor | audit | status`
-- **Config**: `configs/[service]-config.json`
-- **Debug mode**: `DEBUG=1 ./[service]-helper.sh [command]`
-- **Permissions**: `chmod +x [service]-helper.sh`
-- **Services**: hostinger, hetzner, closte, cloudron, coolify, mainwp, vaultwarden, ses, spaceship, 101domains, dns, git-platforms, localhost, code-audit, setup-wizard, toon, crawl4ai
-- **Security**: Credentials from config files, confirmation for destructive ops
-<!-- AI-CONTEXT-END -->
-
-This folder contains helper scripts for all 25+ service integrations in the AI DevOps Framework.
-
-## Script Categories
-
-### Infrastructure & Hosting
-
-- `hostinger-helper.sh` - Shared hosting management
-- `hetzner-helper.sh` - Cloud VPS management
-- `closte-helper.sh` - VPS hosting management
-- `cloudron-helper.sh` - App platform management
-
-### Deployment & Orchestration
-
-- `coolify-helper.sh` - Self-hosted PaaS deployment
-
-### Content Management
-
-- `mainwp-helper.sh` - WordPress management platform
-
-### Security & Secrets
-
-- `vaultwarden-helper.sh` - Password and secrets management
-
-### Code Quality & Auditing
-
-- `code-audit-helper.sh` - Multi-platform code auditing
-
-### Data Format & Conversion
-
-- `toon-helper.sh` - TOON format conversion for efficient LLM data exchange
-
-### Version Control & Git Platforms
-
-- `git-platforms-helper.sh` - GitHub, GitLab, Gitea, Local Git
-
-### Email Services
-
-- `ses-helper.sh` - Amazon SES email delivery
-
-### Domain & DNS
-
-- `spaceship-helper.sh` - Domain registrar with purchasing
-- `101domains-helper.sh` - Domain registrar management
-- `dns-helper.sh` - Multi-provider DNS management
-
-### Development & Local
-
-- `localhost-helper.sh` - Local development with .local domains
-
-### Setup & Configuration
-
-- `setup-wizard-helper.sh` - Intelligent setup wizard
-
-## Standard Script Structure
-
-All helper scripts follow this consistent pattern:
-
-```bash
-#!/bin/bash
-# [Service Name] Helper Script
-# [Brief description]
-
-# Standard color definitions
-GREEN='\033[0;32m'
-BLUE='\033[0;34m'
-YELLOW='\033[1;33m'
-RED='\033[0;31m'
-NC='\033[0m'
-
-# Standard print functions
-print_info() { echo -e "${BLUE}[INFO]${NC} $1"; }
-print_success() { echo -e "${GREEN}[SUCCESS]${NC} $1"; }
-print_warning() { echo -e "${YELLOW}[WARNING]${NC} $1"; }
-print_error() { echo -e "${RED}[ERROR]${NC} $1"; }
-
-# Configuration file path
-CONFIG_FILE="../configs/[service]-config.json"
-
-# Standard functions (all scripts implement these):
-# - check_dependencies()
-# - load_config()
-# - get_account_config() or get_instance_config()
-# - api_request() (for API-based services)
-# - list_accounts() or list_instances()
-# - show_help()
-# - main() with case statement
-
-# Service-specific functions
-# - [service_specific_functions]
-
-# Main execution
-main "$@"
-```
-
-## Usage Patterns
-
-### Standard Commands
-
-```bash
-# Help and information
-./[service]-helper.sh help
-./[service]-helper.sh accounts|instances|servers
-
-# Management operations
-./[service]-helper.sh [action] [account] [target] [options]
-
-# Monitoring and auditing
-./[service]-helper.sh monitor|audit|status [account]
-```
-
-### Common Parameters
-
-- `account/instance` - Configuration account or instance name
-- `target` - Specific resource (server, domain, repository, etc.)
-- `options` - Additional parameters specific to the operation
-
-## Security Considerations
-
-### Credential Handling
-
-- All scripts load credentials from `../configs/[service]-config.json`
-- No credentials are hardcoded in scripts
-- API tokens are validated before use
-- Secure credential storage patterns are followed
-
-### Confirmation Prompts
-
-- Destructive operations require confirmation
-- Purchase operations require explicit confirmation
-- Production environment changes require verification
-
-### Error Handling
-
-- All scripts implement proper error handling
-- Exit codes are consistent (0 = success, 1 = error)
-- Error messages are informative but don't expose sensitive data
-
-## Troubleshooting Scripts
-
-### Common Issues
-
-```bash
-# Check script permissions
-ls -la [service]-helper.sh
-chmod +x [service]-helper.sh
-
-# Verify configuration
-./[service]-helper.sh accounts
-
-# Test connectivity
-./[service]-helper.sh help
-```
-
-### Debug Mode
-
-Most scripts support verbose output for debugging:
-
-```bash
-# Enable debug output (if supported)
-DEBUG=1 ./[service]-helper.sh [command]
-```
-
-## Adding New Provider Scripts
-
-When adding new provider scripts, follow these guidelines:
-
-1. **Use existing scripts as templates** for consistency
-2. **Follow naming conventions**: `[service-name]-helper.sh`
-3. **Implement all standard functions** listed above
-4. **Include comprehensive help** with examples
-5. **Add proper error handling** and validation
-6. **Test thoroughly** before integration
-7. **Update this context file** with the new script
-
-## AI Assistant Usage
-
-AI assistants should:
-
-- **Use helper scripts** instead of direct API calls when possible
-- **Follow confirmation patterns** for destructive operations
-- **Provide clear feedback** to users about operations
-- **Handle errors gracefully** and provide helpful guidance
-- **Respect rate limits** and service constraints
-- **Log important operations** for audit purposes
-
----
-
-**All provider scripts are designed for AI assistant automation while maintaining security, consistency, and user control.**