@dollhousemcp/mcp-server 1.6.10 → 1.7.0

package/README.md

@@ -1,1801 +1,298 @@
 # DollhouseMCP
 
-## Project Status
-[![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-green)](https://modelcontextprotocol.io)
 [![npm version](https://img.shields.io/npm/v/@dollhousemcp/mcp-server.svg)](https://www.npmjs.com/package/@dollhousemcp/mcp-server)
+[![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-green)](https://modelcontextprotocol.io)
 [![License: AGPL-3.0](https://img.shields.io/badge/License-AGPL--3.0-blue.svg)](https://www.gnu.org/licenses/agpl-3.0)
-[![GitHub Views](https://komarev.com/ghpvc/?username=DollhouseMCP&repo=mcp-server&label=Repository+Views&style=flat)](https://github.com/DollhouseMCP/mcp-server)
-
-## Build & Quality
 [![Core Build & Test](https://github.com/DollhouseMCP/mcp-server/actions/workflows/core-build-test.yml/badge.svg)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/core-build-test.yml)
-[![Build Artifacts](https://github.com/DollhouseMCP/mcp-server/actions/workflows/build-artifacts.yml/badge.svg)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/build-artifacts.yml)
-[![Test Coverage](https://img.shields.io/badge/Coverage-1858%2B%20Tests-green)](https://github.com/DollhouseMCP/mcp-server/tree/main/__tests__)
-[![Enterprise-Grade Security](https://img.shields.io/badge/Security-Enterprise%20Grade-purple)](docs/SECURITY.md)
-
-## Platform Support
-[![Windows Build Status](https://img.shields.io/badge/Windows-✓_Tested-0078D4?logo=windows&logoColor=white)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/core-build-test.yml?query=branch:main "Windows CI Build Status")
-[![macOS Build Status](https://img.shields.io/badge/macOS-✓_Tested-000000?logo=apple&logoColor=white)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/core-build-test.yml?query=branch:main "macOS CI Build Status")
-[![Linux Build Status](https://img.shields.io/badge/Linux-✓_Tested-FCC624?logo=linux&logoColor=black)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/core-build-test.yml?query=branch:main "Linux CI Build Status")
-[![Docker](https://img.shields.io/badge/Docker-Ready-2496ED?logo=docker&logoColor=white)](https://github.com/DollhouseMCP/mcp-server/blob/main/Dockerfile)
-
-## Technology
-[![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?logo=typescript&logoColor=white)](https://www.typescriptlang.org/)
-[![Node.js](https://img.shields.io/badge/Node.js-339933?logo=nodedotjs&logoColor=white)](https://nodejs.org/)
-[![Extended Node Compatibility](https://github.com/DollhouseMCP/mcp-server/actions/workflows/extended-node-compatibility.yml/badge.svg)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/extended-node-compatibility.yml)
-[![Docker Testing](https://github.com/DollhouseMCP/mcp-server/actions/workflows/docker-testing.yml/badge.svg)](https://github.com/DollhouseMCP/mcp-server/actions/workflows/docker-testing.yml)
 
 A comprehensive Model Context Protocol (MCP) server that enables dynamic AI persona management with an integrated GitHub-powered collection. DollhouseMCP allows Claude and other compatible AI assistants to activate different behavioral personas while supporting community sharing and monetization.
 
 **🌐 Repository**: https://github.com/DollhouseMCP/mcp-server  
 **🏪 Collection**: https://github.com/DollhouseMCP/collection  
 **📦 NPM Package**: https://www.npmjs.com/package/@dollhousemcp/mcp-server  
-**🌍 Website**: https://dollhousemcp.com (planned)  
-**📦 Version**: v1.6.10
-
-> **🎉 New in v1.6.9**: Fixed version update script to prevent wrong file creation and package-lock.json corruption. The release workflow now works reliably with proper version management.
-
-> **⚠️ Breaking Change**: PersonaTools have been streamlined in v1.6.0. 9 redundant tools were removed in favor of ElementTools. See [PersonaTools Migration Guide](docs/PERSONATOOLS_MIGRATION_GUIDE.md) for migration instructions.
+**🌍 Website**: https://dollhousemcp.com (planned)
 
 ## 🚀 Quick Start
 
-```bash
-# Install globally
-npm install -g @dollhousemcp/mcp-server
-
-# ✅ v1.6.9 fixes version management and release workflow!
-# Browse and submit to collection with or without authentication:
-# npm install -g @dollhousemcp/mcp-server@latest
-
-# Add to Claude Desktop config (see path below for your OS)
-# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
-# Windows: %APPDATA%\Claude\claude_desktop_config.json  
-# Linux: ~/.config/Claude/claude_desktop_config.json
-```
-
-```json
-{
-  "mcpServers": {
-    "dollhousemcp": {
-      "command": "npx",
-      "args": ["@dollhousemcp/mcp-server"]
-    }
-  }
-}
-```
-
-Restart Claude Desktop and you're ready to use DollhouseMCP! Try `list_elements type="personas"` to get started.
-
-> **🎯 New User?** Follow our [Roundtrip Workflow Guide](docs/guides/ROUNDTRIP_WORKFLOW_USER_GUIDE.md) for a complete walkthrough of discovering, customizing, and sharing AI elements with the community.
-
-## ✨ Key Features
-
-| Feature | Description |
-|---------|-------------|
-| 🎭 **42 MCP Tools** | Complete portfolio element management through chat interface |
-| 🏪 **GitHub Collection** | Browse, search, install, and submit personas to community collection |
-| 🔄 **Roundtrip Workflow** | Complete cycle: discover → customize → share → collaborate |
-| 📁 **GitHub Portfolio** | Personal repository for storing and versioning your AI elements |
-| 👤 **User Identity System** | Environment-based attribution for persona creators |
-| 🆔 **Unique ID System** | Advanced ID generation: `{type}_{name}_{author}_{YYYYMMDD}-{HHMMSS}` |
-| 💬 **Chat-Based Management** | Create, edit, and validate personas through conversational interface |
-| 🔄 **Real-time Operations** | Live editing with automatic version bumping and validation |
-| 📦 **NPM Installation** | Install MCP servers from npm with cross-platform support and atomic operations |
-| 🛡️ **Data Protection** | Copy-on-write for default personas, comprehensive backup system |
-| 🏠 **Local-First Architecture** | Full functionality without cloud dependency |
-
-## 🎨 Portfolio Customization Elements
-
-DollhouseMCP introduces a comprehensive portfolio system for customizing AI behavior through **customization element types**. Your portfolio is your personal collection of these element types that enhance and tailor your AI experience. Each element type serves a specific purpose in shaping how AI assistants interact with you.
-
-### Current Portfolio Element Types
-
-| Element | Purpose | Status |
-|---------|---------|--------|
-| 🎭 **Personas** | Define AI personality, tone, and behavioral characteristics | ✅ Available |
-| 🛠️ **Skills** | Add specific capabilities like code review, data analysis, or creative writing | ✅ Available |
-| 📝 **Templates** | Create reusable response formats for emails, reports, documentation | ✅ Available |
-| 🤖 **Agents** | Build autonomous assistants that can pursue goals and make decisions | ✅ Available |
-
-### Coming Soon
-
-| Element | Purpose | Status |
-|---------|---------|--------|
-| 💬 **Prompts** | Pre-configured conversation starters and structured interactions | 🔄 Coming Soon |
-| 🧠 **Memory** | Persistent context storage with retention policies and search capabilities | 🔄 Coming Soon |
-| 🎯 **Ensemble** | Orchestrate multiple elements together as one unified entity | 🔄 Coming Soon |
-
-> **📢 Note**: Prompt, memory, and ensemble element types are actively being developed and will be available in upcoming releases.
-
-### Managing Your Portfolio
-
-Use these new generic tools to manage any element type in your portfolio:
-
-- **`list_elements`** - Browse your portfolio elements by type
-- **`activate_element`** - Activate elements to customize AI behavior
-- **`get_active_elements`** - View currently active customizations
-- **`deactivate_element`** - Deactivate specific customizations
-- **`get_element_details`** - Examine element configuration and metadata
-- **`reload_elements`** - Refresh portfolio from filesystem
-
-### GitHub Portfolio Integration (NEW!)
-
-Manage your portfolio on GitHub for sharing and collaboration:
-
-- **`portfolio_status`** - Check your GitHub portfolio repository status
-- **`init_portfolio`** - Create a new GitHub portfolio repository
-- **`portfolio_config`** - Configure sync and submission settings
-- **`sync_portfolio`** - Synchronize local and GitHub repositories
-- **`search_portfolio`** - Search your local portfolio with advanced indexing
-- **`search_all`** - Unified search across local, GitHub, and collection sources
-- **`submit_content`** - Upload elements to your GitHub portfolio
+### Choose Your Installation Method
+
+<table>
+<tr>
+<th>Method</th>
+<th>Best For</th>
+<th>Pros</th>
+<th>Cons</th>
+</tr>
+<tr>
+<td><strong>Local Install</strong><br>(Recommended)</td>
+<td>Most users, multiple configs, customization</td>
+<td>✅ Multiple setups<br>✅ Easy backup<br>✅ No permissions</td>
+<td>❌ Longer path in config</td>
+</tr>
+<tr>
+<td><strong>npx</strong></td>
+<td>Quick testing, always latest</td>
+<td>✅ No install<br>✅ Always updated</td>
+<td>❌ Slower startup<br>❌ Needs internet</td>
+</tr>
+<tr>
+<td><strong>Global Install</strong></td>
+<td>Single shared instance</td>
+<td>✅ Short command</td>
+<td>❌ Only one version<br>❌ Needs sudo/admin</td>
+</tr>
+</table>
 
-> **📘 Getting Started**: New to portfolios? Follow our [Portfolio Setup Guide](docs/guides/PORTFOLIO_SETUP_GUIDE.md) for step-by-step instructions.
+---
 
-### Smart Element Detection
+### Method 1: Local Installation (Recommended)
 
-DollhouseMCP automatically detects element types when submitting content, eliminating the need to manually specify types:
+Create a dedicated folder for your MCP servers and install there:
 
 ```bash
-# System automatically detects whether this is a persona, skill, template, etc.
-submit_content name="code-review"
-```
-
-**Key Features:**
-- **Automatic Type Detection**: Searches all element directories simultaneously
-- **Fuzzy Matching**: Finds content with partial names or different extensions  
-- **Clear Error Messages**: Provides actionable guidance when content isn't found
-- **No More Mistakes**: Prevents accidentally submitting content as wrong element type
-
-**Example Output:**
-```
-✅ Smart detection: Found "code-review" as SKILL
-✅ Successfully uploaded code-review to your GitHub portfolio!
-```
-
-> **📖 Learn More**: See our [Element Detection Guide](docs/guides/ELEMENT_DETECTION_GUIDE.md) for detailed usage examples and troubleshooting tips.
-
-### Complete Naming Freedom
-
-DollhouseMCP gives you **complete freedom** to name your elements whatever you want. There are no naming restrictions or forbidden words.
-
-**✅ You can create elements named**:
-- "Test Assistant" - Previously blocked, now fully supported
-- "Sample Code Reviewer" - No restrictions
-- "テスト" (Japanese for "test") - Unicode supported
-- "My Debugging Helper" - Any descriptive name
-
-**How it works**: DollhouseMCP uses metadata-based test detection instead of filename patterns, so only internal DollhouseMCP test files are filtered (those with `_dollhouseMCPTest: true` metadata). Your personal elements are never affected.
-
-> **📘 Technical Details**: See our [Test Metadata Convention](docs/TEST_METADATA_CONVENTION.md) for information about how DollhouseMCP identifies its own test files without affecting user content.
-
-### Specialized Element Tools
-
-Some portfolio elements have specialized operations:
-
-- **`render_template`** - Generate content using template elements with variables
-- **`execute_agent`** - Deploy agent elements to accomplish specific goals
-
-### Portfolio Examples
-
-```
-# Browse your skill portfolio
-list_elements type="skills"
-
-# Activate a code review skill
-activate_element name="code-review" type="skills"
-
-# Activate a professional email template
-activate_element name="email-professional" type="templates"
+# Create MCP servers directory
+mkdir ~/mcp-servers
+cd ~/mcp-servers
 
-# Use a template to generate content
-render_template name="project-update" variables='{"project": "DollhouseMCP", "status": "Released"}'
-
-# Deploy an agent for a specific task
-execute_agent name="project-manager" goal="Create a sprint plan for next week"
+# Install DollhouseMCP
+npm install @dollhousemcp/mcp-server
 ```
 
-### Portfolio Structure
-
-Your portfolio lives in `~/.dollhouse/portfolio/` with elements organized by type:
-
-```
-~/.dollhouse/portfolio/
-├── personas/       # Personality and behavior profiles
-├── skills/         # Specialized capabilities
-├── templates/      # Reusable content structures
-└── agents/         # Autonomous assistants
-```
-
-### Persona Management via ElementTools
-
-Personas are now managed through the generic ElementTools system:
-- **`list_elements type="personas"`** - Display all local personas with enhanced metadata
-- **`activate_element name="name" type="personas"`** - Activate by name, filename, or unique ID
-- **`get_active_elements type="personas"`** - Get current active persona information
-- **`deactivate_element type="personas"`** - Return to default mode
-- **`get_element_details name="name" type="personas"`** - View complete persona details
-- **`reload_elements type="personas"`** - Refresh personas from filesystem
-
-> **📖 Migration**: Legacy PersonaTools were removed in v1.6.0. See [PersonaTools Migration Guide](docs/PERSONATOOLS_MIGRATION_GUIDE.md) for complete migration instructions.
-
-## 🔒 Enterprise-Grade Security
-
-DollhouseMCP implements comprehensive security measures to protect your personas and system:
-
-### Security Features
-- **🛡️ Content Sanitization**: DOMPurify integration prevents XSS attacks in persona content
-- **📝 YAML Injection Prevention**: Secure parsing with schema validation and size limits
-- **🔐 Token Security**: GitHub OAuth device flow authentication with AES-256-GCM encrypted storage
-- **🐳 Container Hardening**: Non-root execution, read-only filesystem, resource limits
-- **🚦 Rate Limiting**: Token bucket algorithm prevents API abuse (10 checks/hour default)
-- **✅ Signature Verification**: GPG verification ensures release authenticity
-- **🔍 Input Validation**: Comprehensive validation for all user inputs
-- **📊 Security Monitoring**: Audit logging for security-relevant operations
-
-### Security Testing
-- **487 comprehensive tests** including security-specific test suites
-- **Continuous security scanning** with GitHub Advanced Security
-- **Vulnerability-free**: All security alerts resolved (0 active)
-
-## 📋 Prerequisites
-
-- **Node.js**: v20.0.0 or higher (LTS recommended)
-- **npm**: v10.0.0 or higher
-- **git**: For cloning the repository
-- **Operating System**: Windows, macOS, or Linux
+**Configure Claude Desktop:**
 
-> **Note**: DollhouseMCP is developed on Node.js 24 but supports Node.js 20+ for broad compatibility.
-
-## 🚀 Quick Start
-
-### Installation
-
-#### NPM Installation (NEW! - Recommended)
-
-```bash
-npm install -g @dollhousemcp/mcp-server
-```
-
-After installation, add DollhouseMCP to your Claude Desktop configuration:
-
-**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`  
-**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`  
-**Linux**: `~/.config/Claude/claude_desktop_config.json`
+Add to your config file:
+- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
+- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`  
+- **Linux**: `~/.config/Claude/claude_desktop_config.json`
 
 ```json
 {
   "mcpServers": {
     "dollhousemcp": {
-      "command": "npx",
-      "args": ["@dollhousemcp/mcp-server"]
+      "command": "node",
+      "args": ["/Users/YOUR_USERNAME/mcp-servers/node_modules/@dollhousemcp/mcp-server/dist/index.js"]
     }
   }
 }
 ```
 
-> **Note**: If you have other MCP servers configured, add dollhousemcp to your existing mcpServers object.
-
-#### Automated Setup (Alternative) - Claude Desktop Only
+💡 **Pro tip**: Replace `/Users/YOUR_USERNAME` with your actual home directory path.
 
-> [!WARNING]
-> **Claude Desktop Only**: The automated setup script is specifically designed for **Claude Desktop** integration. If you're using **Claude Code**, other AI platforms (ChatGPT, BoltAI, Gemini, etc.), or custom MCP implementations, please use the [Manual Installation](#manual-installation) process below.
-
-```bash
-# Clone the repository
-git clone https://github.com/DollhouseMCP/mcp-server.git
-cd mcp-server
-
-# Run automated setup script (Claude Desktop only)
-./setup.sh
-```
-
-The setup script will:
-- 📦 Install all dependencies
-- 🔨 Build the TypeScript code
-- 📍 Detect your installation path
-- 🔧 Generate the exact Claude Desktop configuration
-- 📋 Provide step-by-step setup instructions
-
-#### Manual Installation
-
-> **Note**: Manual installation works with all MCP-compatible platforms including Claude Desktop, Claude Code, ChatGPT, BoltAI, Gemini, and custom implementations.
-
-```bash
-# Clone the repository
-git clone https://github.com/DollhouseMCP/mcp-server.git
-cd mcp-server
-
-# Install dependencies and build
-npm install
-npm run build
-
-# Optional: Set user identity for persona attribution
-export DOLLHOUSE_USER="your-username"
-export DOLLHOUSE_EMAIL="your-email@example.com"
-```
-
-### Claude Desktop Configuration
+---
 
-Add DollhouseMCP to your Claude Desktop configuration:
+### Method 2: Always Latest with npx
 
-**Location**: `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
+No installation needed! Configure Claude Desktop to always use the latest version:
 
-#### For NPM Installation:
 ```json
 {
   "mcpServers": {
     "dollhousemcp": {
       "command": "npx",
-      "args": ["@dollhousemcp/mcp-server"]
+      "args": ["@dollhousemcp/mcp-server@latest"]
     }
   }
 }
 ```
 
-#### For Source Installation:
-```json
-{
-  "mcpServers": {
-    "dollhousemcp": {
-      "command": "node",
-      "args": ["/absolute/path/to/DollhouseMCP/dist/index.js"]
-    }
-  }
-}
-```
-
-**🔄 After configuration:**
-1. Save the file
-2. Restart Claude Desktop completely
-3. All 42 DollhouseMCP tools will be available
-
-## 🛠️ Available Tools (42 Total)
-
-### Portfolio Element Management (NEW!)
-- **`list_elements`** - List all elements of a specific type
-- **`activate_element`** - Activate an element by name and type
-- **`get_active_elements`** - Get currently active elements of a type
-- **`deactivate_element`** - Deactivate a specific element
-- **`get_element_details`** - View detailed information about an element
-- **`reload_elements`** - Refresh elements from filesystem
-
-### Element-Specific Operations (NEW!)
-- **`render_template`** - Render a template element with provided variables
-- **`execute_agent`** - Execute an agent element with a specific goal
-
-### Persona Export/Import (Specialized Tools)
-- **`export_persona`** - Export single persona to JSON format
-- **`export_all_personas`** - Export all personas to JSON bundle  
-- **`import_persona`** - Import persona from file path or JSON string
-- **`share_persona`** - Generate shareable URL for persona
-- **`import_from_url`** - Import persona from shared URL
-
-### GitHub Collection Integration
-- **`browse_collection`** - Browse content by section and type (flat structure, no categories)
-- **`search_collection`** - Search across all collection content
-- **`search_collection_enhanced`** - Enhanced search with pagination, filtering, and sorting
-- **`get_collection_content`** - View detailed content info
-- **`get_collection_cache_health`** - Monitor collection cache status and performance
-- **`install_element`** - One-click download and installation of any element type
-- **`submit_persona`** - Submit to collection via GitHub issue
-
-### GitHub Portfolio Management (NEW!)
-- **`portfolio_status`** - Check your GitHub portfolio repository status
-- **`init_portfolio`** - Create a new GitHub portfolio repository
-- **`sync_portfolio`** - Synchronize local and GitHub repositories
-- **`search_portfolio`** - Search your local portfolio with advanced indexing
-- **`search_all`** - Unified search across local, GitHub, and collection sources
-- **`submit_content`** - Upload elements to your GitHub portfolio
-
-### Collection Configuration (NEW!)
-- **`configure_collection_submission`** - Configure auto-submit and default settings
-- **`get_collection_submission_config`** - View current submission configuration
-
-### User Identity Management
-- **`set_user_identity`** - Set username for persona attribution
-- **`get_user_identity`** - View current identity status
-- **`clear_user_identity`** - Return to anonymous mode
-
-
-### System Tools
-- **`get_build_info`** - Comprehensive build and runtime information
-
-### Persona Indicators
-- **`configure_indicator`** - Configure how persona indicators appear in AI responses
-- **`get_indicator_config`** - View current indicator configuration settings
-
-### GitHub Authentication (NEW!)
-- **`setup_github_auth`** - Start GitHub OAuth device flow authentication
-- **`check_github_auth`** - Check current authentication status
-- **`clear_github_auth`** - Remove stored authentication credentials
-
-## 📖 Usage Examples
-
-### Collection Operations
-```
-# Browse collection content by type
-browse_collection section="library" type="personas"    # Browse all personas
-browse_collection section="library" type="skills"      # Browse skills
-browse_collection section="library" type="templates"   # Browse templates
-
-# Search collection content
-search_collection query="writing"                      # Search for writing personas
-search_collection query="code review"                  # Find code review skills
-
-# Enhanced collection search with pagination
-search_collection_enhanced query="data analysis" maxResults=10 elementType="skills"
-search_collection_enhanced query="creative" page=2 resultsPerPage=5
-
-# Install elements from collection
-install_element path="library/personas/storyteller.md"        # Install persona
-install_element path="library/skills/code-reviewer.md"       # Install skill
-install_element path="library/templates/email-template.md"   # Install template
-
-# Check collection cache health
-get_collection_cache_health
-```
-
-### Portfolio Workflow (NEW!)
-```
-# Check GitHub portfolio status
-portfolio_status                                       # Check repository status
-
-# Initialize a new GitHub portfolio (first time setup)
-init_portfolio                                         # Create GitHub repository
-init_portfolio repoName="my-ai-portfolio"             # Custom repository name
-
-# Synchronize local and GitHub portfolios
-sync_portfolio                                         # Sync both directions
-sync_portfolio direction="push"                        # Push local to GitHub
-sync_portfolio direction="pull"                        # Pull GitHub to local
-
-# Search your local portfolio with advanced indexing
-search_portfolio query="writing"                       # Search all element types
-search_portfolio query="code" elementType="skills"     # Search specific type
-search_portfolio query="email" fuzzyMatch=true         # Enable fuzzy matching
-
-# Unified search across all sources (local, GitHub, collection)
-search_all query="data analysis"                       # Search everywhere
-search_all query="creative writing" maxResults=20      # Limit results
-search_all query="templates" source="local"            # Search specific source
-
-# Submit content with smart auto-detection
-submit_content name="code-review"                      # Auto-detects element type
-submit_content name="my-persona" elementType="personas" # Explicit type
-submit_content name="email-template" description="Professional email template"
-
-# Configure collection submission settings
-configure_collection_submission autoSubmit=true        # Enable auto-submit
-configure_collection_submission defaultLicense="MIT"   # Set default license
-get_collection_submission_config                       # View current config
-```
-
-### Portfolio Element Management
-```
-# List elements by type (works with all element types)
-list_elements type="personas"                          # List personas
-list_elements type="skills"                            # List skills  
-list_elements type="templates"                         # List templates
-list_elements type="agents"                            # List agents
-
-# Activate elements to customize AI behavior
-activate_element name="code-reviewer" type="skills"    # Activate skill
-activate_element name="professional" type="personas"   # Activate persona
-activate_element name="email-format" type="templates"  # Activate template
-
-# View active elements
-get_active_elements                                     # All active elements
-get_active_elements type="skills"                      # Active skills only
-
-# Get detailed element information
-get_element_details name="code-reviewer" type="skills" # View skill details
-get_element_details name="my-persona" type="personas"  # View persona details
-
-# Deactivate elements
-deactivate_element name="code-reviewer" type="skills"  # Deactivate specific
-deactivate_element type="personas"                     # Deactivate all personas
-
-# Refresh elements from filesystem
-reload_elements                                         # Reload all elements
-reload_elements type="skills"                          # Reload specific type
-```
-
-### Specialized Element Operations
-```
-# Render templates with variables
-render_template name="project-update" variables='{"project": "DollhouseMCP", "status": "Released"}'
-render_template name="email-professional" variables='{"recipient": "John", "subject": "Meeting"}'
-
-# Execute agents with specific goals
-execute_agent name="project-manager" goal="Create a sprint plan for next week"
-execute_agent name="data-analyst" goal="Analyze sales trends for Q3"
-```
-
-### System Information
-```
-# Get comprehensive build and runtime information
-get_build_info                                         # Full system info
-get_build_info section="version"                       # Version info only
-get_build_info section="environment"                   # Environment details
-get_build_info section="dependencies"                  # Dependency versions
-```
-
-### Persona Management with ElementTools
-```
-# List all personas
-list_elements type="personas"
-
-# Activate a persona
-activate_element name="Study Buddy" type="personas"
-
-# Get persona details
-get_element_details name="Study Buddy" type="personas"
-
-# Submit to community collection
-submit_persona "Study Buddy"               # Share with community
-```
-
-### User Identity
-```
-set_user_identity "your-username"          # Set attribution
-get_user_identity                          # Check current status
-clear_user_identity                        # Return to anonymous
-```
-
-
-
-
-### Persona Indicators
-DollhouseMCP adds visual indicators to AI responses when a persona is active:
-```
-[🎭 Creative Writer v2.1 by @mickdarling] Your creative response here...
-```
-
-Configure indicators:
-```
-get_indicator_config                       # View current settings
-configure_indicator enabled:false          # Disable indicators
-configure_indicator style:"minimal"        # Use minimal format: 🎭 Creative Writer
-configure_indicator style:"compact"        # Use compact: [Creative Writer v2.1]
-configure_indicator style:"full"           # Full format (default)
-configure_indicator emoji:"🤖"             # Change emoji
-configure_indicator showAuthor:false       # Hide author attribution
-configure_indicator bracketStyle:"round"   # Use (parentheses) instead of [brackets]
-```
-
-Environment variables for persistent configuration:
-```bash
-export DOLLHOUSE_INDICATOR_ENABLED=true
-export DOLLHOUSE_INDICATOR_STYLE=minimal
-export DOLLHOUSE_INDICATOR_EMOJI=🎨
-```
-
-## 🔄 Complete Workflows
-
-### Setting Up Portfolio from Scratch
-
-**Step 1: Initial Setup**
-```
-# Set your user identity for attribution
-set_user_identity "your-username"
-
-# Check current portfolio status
-portfolio_status
-
-# Initialize a new GitHub portfolio repository
-init_portfolio repoName="my-ai-portfolio"
-```
-
-**Step 2: Browse and Install Elements**
-```
-# Browse the community collection
-browse_collection section="library" type="personas"
-browse_collection section="library" type="skills"
-
-# Search for specific elements
-search_collection query="code review"
-search_collection_enhanced query="data analysis" elementType="skills" maxResults=5
-
-# Install elements you like
-install_element path="library/skills/code-reviewer.md"
-install_element path="library/personas/technical-writer.md"
-install_element path="library/templates/project-update.md"
-```
-
-**Step 3: Customize and Activate**
-```
-# Activate installed elements
-activate_element name="code-reviewer" type="skills"
-activate_element name="technical-writer" type="personas"
-
-# View your active elements
-get_active_elements
-
-# Get details about any element
-get_element_details name="technical-writer" type="personas"
-```
-
-**Step 4: Sync and Share**
-```
-# Submit your custom content to GitHub portfolio
-submit_content name="My Assistant"
-
-# Sync everything to GitHub
-sync_portfolio direction="push"
-
-# Optionally submit personas to community collection
-submit_persona name="My Assistant"
-```
-
-### Searching Across All Sources
-
-**Unified Search Example**
-```
-# Search everything (local portfolio, GitHub portfolio, community collection)
-search_all query="writing assistant"
-
-# Search with filters
-search_all query="code" elementType="skills" maxResults=10
-
-# Search specific sources
-search_all query="templates" source="collection"    # Collection only
-search_all query="my content" source="local"        # Local portfolio only
-search_all query="my content" source="github"       # GitHub portfolio only
-```
-
-**Advanced Portfolio Search**
-```
-# Search your local portfolio with fuzzy matching
-search_portfolio query="analysi" fuzzyMatch=true    # Finds "analysis" elements
-
-# Search by element type
-search_portfolio query="email" elementType="templates"
-search_portfolio query="review" elementType="skills"
-
-# Get all elements of a type
-list_elements type="personas"
-list_elements type="agents"
-```
-
-### Content Submission with Auto-Detection
-
-**Smart Element Detection**
-```
-# System automatically detects element type
-submit_content name="code-review"                   # Finds in skills/
-submit_content name="email-template"                # Finds in templates/
-submit_content name="my-persona"                    # Finds in personas/
-
-# Add description for better documentation
-submit_content name="data-analyzer" description="Advanced data analysis skill"
-
-# Override auto-detection if needed
-submit_content name="ambiguous-name" elementType="skills"
-```
-
-**Batch Content Management**
-```
-# Configure submission settings
-configure_collection_submission autoSubmit=true
-configure_collection_submission defaultLicense="CC-BY-SA-4.0"
-
-# Check configuration
-get_collection_submission_config
-
-# Submit multiple elements
-submit_content name="skill-1"
-submit_content name="skill-2"
-submit_content name="template-1"
+📝 **Note**: The `@latest` tag ensures you always get the newest version. Remove it to use npm's cached version.
 
-# Sync all changes to GitHub
-sync_portfolio
-```
-
-### Daily Workflow Example
-
-**Morning Setup**
-```
-# Check for updates
-get_build_info section="version"
-portfolio_status
-
-# Activate your daily toolkit
-activate_element name="code-reviewer" type="skills"
-activate_element name="professional" type="personas"
-activate_element name="email-template" type="templates"
-
-# Check what's active
-get_active_elements
-```
-
-**During Work**
-```
-# Use templates for communication
-render_template name="email-template" variables='{"recipient": "team", "subject": "Sprint Update"}'
-
-# Deploy agents for tasks
-execute_agent name="project-manager" goal="Review pending tasks and prioritize"
-
-# Search for tools as needed
-search_all query="debugging" elementType="skills"
-```
-
-**End of Day**
-```
-# Save any new content
-submit_content name="new-skill"
-submit_content name="daily-template"
-
-# Sync to GitHub
-sync_portfolio
-
-# Check system health
-get_collection_cache_health
-```
-
-### GitHub Authentication (v1.5.0+)
-
-DollhouseMCP supports GitHub OAuth device flow authentication for enhanced features. **FIXED in v1.6.2**: Default OAuth client ID now works correctly - no configuration needed!
-
-#### OAuth Setup (For Self-Hosting)
-
-If you're self-hosting or developing, you need to configure a GitHub OAuth app:
-
-1. **Create GitHub OAuth App**:
-   - Go to GitHub → Settings → Developer settings → OAuth Apps → New OAuth App
-   - **Application name**: `DollhouseMCP Server`
-   - **Homepage URL**: `https://github.com/DollhouseMCP/mcp-server`
-   - **Authorization callback URL**: `http://localhost:12345/callback` (required but not used)
-   - Click "Register application"
-
-2. **Enable Device Flow**:
-   - In your OAuth app settings, check ✅ **Enable Device Flow**
-   - Copy your Client ID (format: `Ov23liXXXXXXXXXXXXXX`)
-
-3. **Configure Environment**:
-   ```bash
-   # Add to your shell profile (.bashrc, .zshrc, etc)
-   export DOLLHOUSE_GITHUB_CLIENT_ID="your_client_id_here"
-   
-   # Or in Claude Desktop config:
-   "env": {
-     "DOLLHOUSE_GITHUB_CLIENT_ID": "your_client_id_here"
-   }
-   ```
-
-See [OAuth Setup Guide](docs/setup/OAUTH_SETUP.md) for detailed instructions.
-
-#### Using Authentication
-
-```
-setup_github_auth                         # Start OAuth device flow
-check_github_auth                         # Check authentication status
-clear_github_auth                         # Remove stored credentials
-```
-
-**Features:**
-- 🔐 **Secure Token Storage**: Tokens encrypted with AES-256-GCM
-- 📱 **Device Flow**: No need to manually create or paste tokens
-- 🔄 **Automatic Token Management**: Secure storage and retrieval
-- 🛡️ **Rate Limiting**: Built-in protection against API abuse
-- ✅ **Unicode Security**: Prevents homograph attacks
-
-**How It Works:**
-1. Run `setup_github_auth` to start the OAuth flow
-2. Visit the provided URL and enter the user code
-3. Authorize DollhouseMCP in your browser
-4. Authentication completes automatically
-5. Token is securely stored for future use
-
-**Example Usage:**
-```
-# First-time setup
-setup_github_auth
-# Copy the user code: XXXX-XXXX
-# Visit: https://github.com/login/device
-# Enter the code and authorize
-
-# Check status
-check_github_auth
-# ✅ Authenticated as: your-username
-
-# Later sessions automatically use stored token
-browse_collection  # Works with authenticated access
-```
-
-## 🖥️ Cross-Platform Installation
-
-### 🐧 Linux Installation
-
-#### Prerequisites
-- **Node.js**: v20.0.0 or higher
-- **npm**: v10.0.0 or higher
-- **git**: For version control
-
-```bash
-# Ubuntu/Debian
-sudo apt update
-sudo apt install -y nodejs npm git
-# Verify Node.js version
-node --version  # Should be v20.0.0 or higher
-
-# CentOS/RHEL/Fedora  
-sudo dnf install -y nodejs npm git
-# Verify Node.js version
-node --version  # Should be v20.0.0 or higher
-
-# Arch Linux
-sudo pacman -S nodejs npm git
-# Verify Node.js version
-node --version  # Should be v20.0.0 or higher
-```
+---
 
-> **Note**: If your system's Node.js is older than v20, install from [NodeSource](https://github.com/nodesource/distributions) or use [nvm](https://github.com/nvm-sh/nvm).
+### Method 3: Global Installation
 
-#### Installation Steps
 ```bash
-# Clone and build
-git clone https://github.com/DollhouseMCP/mcp-server.git
-cd mcp-server
-npm install
-npm run build
-
-# Optional: Set user identity
-export DOLLHOUSE_USER="your-username"
-export DOLLHOUSE_EMAIL="your-email@example.com"
+# Install globally (may require sudo/admin)
+npm install -g @dollhousemcp/mcp-server
 ```
 
-#### Claude Desktop Configuration (Linux)
-```bash
-# Configuration location
-~/.config/Claude/claude_desktop_config.json
+**Configure Claude Desktop:**
 
-# Or use XDG_CONFIG_HOME if set
-$XDG_CONFIG_HOME/Claude/claude_desktop_config.json
-```
-
-Configuration content:
 ```json
 {
   "mcpServers": {
     "dollhousemcp": {
-      "command": "node",
-      "args": ["/absolute/path/to/DollhouseMCP/dist/index.js"]
+      "command": "dollhousemcp"
     }
   }
 }
 ```
 
-### 🪟 Windows Installation
-
-#### Prerequisites
-- **Node.js**: v20.0.0 or higher
-- **npm**: v10.0.0 or higher (included with Node.js)
-- **git**: For version control
+⚠️ **Warning**: Only one version system-wide. Consider local installation for more flexibility.
 
-```powershell
-# Install Node.js from https://nodejs.org/ (download LTS version)
-# Or using Chocolatey
-choco install nodejs --version=20.18.0
-choco install git
-
-# Or using winget
-winget install OpenJS.NodeJS Git.Git
-
-# Verify Node.js version
-node --version  # Should be v20.0.0 or higher
-```
-
-#### Installation Steps (PowerShell)
-```powershell
-# Clone and build
-git clone https://github.com/DollhouseMCP/mcp-server.git
-cd mcp-server
-npm install
-npm run build
-
-# Optional: Set user identity
-$env:DOLLHOUSE_USER = "your-username"
-$env:DOLLHOUSE_EMAIL = "your-email@example.com"
-```
-
-#### Claude Desktop Configuration (Windows)
-```powershell
-# Configuration location
-$env:APPDATA\Claude\claude_desktop_config.json
-```
-
-Configuration content (use forward slashes or double backslashes):
-```json
-{
-  "mcpServers": {
-    "dollhousemcp": {
-      "command": "node",
-      "args": ["C:/path/to/DollhouseMCP/dist/index.js"]
-    }
-  }
-}
-```
+---
 
-### 🍎 macOS Installation
+### 🎯 Advanced: Multiple Configurations
 
-#### Prerequisites
-- **Node.js**: v20.0.0 or higher
-- **npm**: v10.0.0 or higher (included with Node.js)
-- **git**: For version control
+Want separate portfolios for different contexts? Create multiple local installations:
 
 ```bash
-# Using Homebrew (recommended)
-brew install node git
+# Personal assistant
+mkdir ~/mcp-servers/personal
+cd ~/mcp-servers/personal
+npm install @dollhousemcp/mcp-server
 
-# Or download from https://nodejs.org/ (LTS version)
+# Work assistant
+mkdir ~/mcp-servers/work
+cd ~/mcp-servers/work
+npm install @dollhousemcp/mcp-server
 
-# Verify Node.js version
-node --version  # Should be v20.0.0 or higher
+# Creative writing
+mkdir ~/mcp-servers/creative
+cd ~/mcp-servers/creative
+npm install @dollhousemcp/mcp-server
 ```
 
-#### Installation Steps
-```bash
-# Clone and build
-git clone https://github.com/DollhouseMCP/mcp-server.git
-cd mcp-server
-npm install
-npm run build
-
-# Optional: Set user identity
-export DOLLHOUSE_USER="your-username"
-export DOLLHOUSE_EMAIL="your-email@example.com"
-```
-
-#### Claude Desktop Configuration (macOS)
-```bash
-# Configuration location
-~/Library/Application Support/Claude/claude_desktop_config.json
-```
+**Configure each with its own portfolio:**
 
-Configuration content:
 ```json
 {
   "mcpServers": {
-    "dollhousemcp": {
+    "dollhouse-personal": {
+      "command": "node",
+      "args": ["/Users/YOU/mcp-servers/personal/node_modules/@dollhousemcp/mcp-server/dist/index.js"],
+      "env": {
+        "DOLLHOUSE_PORTFOLIO_DIR": "/Users/YOU/portfolios/personal"
+      }
+    },
+    "dollhouse-work": {
       "command": "node",
-      "args": ["/absolute/path/to/DollhouseMCP/dist/index.js"]
+      "args": ["/Users/YOU/mcp-servers/work/node_modules/@dollhousemcp/mcp-server/dist/index.js"],
+      "env": {
+        "DOLLHOUSE_PORTFOLIO_DIR": "/Users/YOU/portfolios/work"
+      }
     }
   }
 }
 ```
 
-## 🐳 Docker Installation
-
-### Quick Start with Docker
-```bash
-# Clone repository
-git clone https://github.com/DollhouseMCP/mcp-server.git
-cd mcp-server
-
-# Build and run with Docker Compose
-docker-compose up -d
-
-# Or build manually
-docker build -t dollhousemcp .
-docker run -d --name dollhousemcp dollhousemcp
-```
+Now you can enable/disable different configurations in Claude Desktop as needed!
 
-### Docker Compose (Recommended)
-
-#### Production deployment:
-```bash
-docker-compose up -d
-```
-
-#### Development with hot reload:
-```bash
-docker-compose --profile dev up dollhousemcp-dev
-```
+---
 
-### Custom Personas with Docker
-```bash
-# Mount your custom personas directory
-docker run -d \
-  --name dollhousemcp \
-  -v /path/to/your/personas:/app/personas \
-  -e DOLLHOUSE_USER="your-username" \
-  dollhousemcp
-```
+### ✅ Verify Installation
 
-### Docker Environment Variables
-```bash
-# Set user identity
-DOLLHOUSE_USER=your-username
-DOLLHOUSE_EMAIL=your-email@example.com
+After configuring and restarting Claude Desktop, test with:
 
-# Custom personas directory (inside container)
-PERSONAS_DIR=/app/personas
-
-# Node.js environment
-NODE_ENV=production
 ```
-
-## 🧪 Testing
-
-### Running Tests
-
-The project includes comprehensive tests for cross-platform compatibility:
-
-```bash
-# Run all tests
-npm test
-
-# Run tests with coverage
-npm run test:coverage
-
-# Run tests in watch mode (for development)
-npm run test:watch
-
-# Run specific test suites
-npm run test:personas
-npm run test:collection
+list_elements type="personas"
 ```
 
-### Test Coverage
-
-Current test coverage includes:
-- ✅ **102 comprehensive tests** covering all functionality
-- ✅ **Auto-update system** - GitHub API, backup/rollback, dependency validation
-- ✅ **Security testing** - Command injection prevention, input validation
-- ✅ **Cross-platform compatibility** - Windows, macOS, Linux path handling
-- ✅ **Version validation** - Parsing tests for git/npm output formats
-- ✅ **Edge case coverage** - Network failures, missing dependencies, malformed input
-
-### Manual Verification
-
-Verify your setup works correctly:
-
-```bash
-# Build the project
-npm run build
-
-# Test the server (should output server info)
-node dist/index.js --help 2>/dev/null || echo "Server compiled successfully"
+You should see your available personas. If not, check the [Troubleshooting](#troubleshooting) section.
 
-# Verify personas directory
-ls -la personas/
-```
-
-## ☁️ Cloud Deployment
+---
 
-### Container Registries
+### 📁 Default Portfolio Location
 
-The project supports deployment to:
-- **GitHub Container Registry** (ghcr.io)
-- **Docker Hub**
-- **AWS ECR**
-- **Google Container Registry**
+By default, your elements are stored in:
+- **macOS/Linux**: `~/.dollhouse/portfolio/`
+- **Windows**: `%USERPROFILE%\.dollhouse\portfolio\`
 
-### Example Cloud Deployments
+Use the `DOLLHOUSE_PORTFOLIO_DIR` environment variable to customize this location.
 
-#### AWS ECS
-```json
-{
-  "family": "dollhousemcp",
-  "containerDefinitions": [{
-    "name": "dollhousemcp",
-    "image": "ghcr.io/mickdarling/dollhousemcp:latest",
-    "memory": 512,
-    "cpu": 256,
-    "environment": [
-      {"name": "NODE_ENV", "value": "production"},
-      {"name": "PERSONAS_DIR", "value": "/app/personas"},
-      {"name": "DOLLHOUSE_USER", "value": "production"}
-    ]
-  }]
-}
-```
+## 🎯 Getting Started
 
-#### Google Cloud Run
-```bash
-gcloud run deploy dollhousemcp \
-  --image ghcr.io/mickdarling/dollhousemcp:latest \
-  --platform managed \
-  --region us-central1 \
-  --set-env-vars NODE_ENV=production,DOLLHOUSE_USER=production
-```
+Once installed, try these commands in Claude:
 
-#### Azure Container Instances
 ```bash
-az container create \
-  --name dollhousemcp \
-  --resource-group myResourceGroup \
-  --image ghcr.io/mickdarling/dollhousemcp:latest \
-  --environment-variables NODE_ENV=production DOLLHOUSE_USER=production
-```
-
-## 🏗️ Project Structure
-
-```
-DollhouseMCP/
-├── .github/
-│   ├── actions/
-│   │   └── validate-yaml/         # Reusable YAML validation action
-│   ├── workflows/                 # CI/CD workflows
-│   └── ISSUE_TEMPLATE/           # Issue templates for bug/feature/task
-├── __tests__/
-│   ├── unit/                     # Unit tests for components
-│   ├── integration/              # Integration tests
-│   └── *.test.ts                 # Test files (600+ tests total)
-├── src/
-│   ├── index.ts                  # Main MCP server (DollhouseMCPServer)
-│   ├── cache/                    # API caching layer
-│   ├── config/                   # Configuration management
-│   ├── collection/               # GitHub collection integration
-│   ├── persona/                  # Persona management core
-│   ├── security/                 # Input validation and security
-│   ├── server/                   # MCP server setup and tools
-│   ├── types/                    # TypeScript type definitions
-│   ├── update/                   # Auto-update system components
-│   └── utils/                    # Utility functions
-├── dist/                         # Compiled JavaScript (auto-generated)
-├── personas/                     # Default persona collection
-│   ├── creative-writer.md
-│   ├── technical-analyst.md
-│   ├── eli5-explainer.md
-│   ├── business-consultant.md
-│   └── debug-detective.md
-├── custom-personas/              # User-created personas (git-ignored)
-├── docs/                         # Documentation
-│   └── development/             # Development notes and guides
-├── scripts/                      # Management and utility scripts
-├── Dockerfile                    # Multi-stage Docker build
-├── docker-compose.yml           # Production and development configs
-├── package.json                 # Project config (dollhousemcp v1.6.10)
-├── tsconfig.json                # TypeScript configuration
-├── jest.config.cjs              # Jest test configuration
-├── setup.sh                     # Automated installation script
-├── LICENSE                      # AGPL-3.0 with platform stability
-├── CHANGELOG.md                 # Version history
-├── claude.md                    # Project context for Claude
-└── README.md                    # This file
-```
-
-## 📝 Creating Custom Personas
-
-### Enhanced Persona Format
-
-Create `.md` files in the `personas/` directory with this structure:
-
-```markdown
----
-name: "Your Persona Name"
-description: "Brief description of what this persona does"
-unique_id: "auto-generated-if-missing"
-author: "your-username"
-triggers: ["keyword1", "keyword2"]
-version: "1.0"
-category: "creative"
-age_rating: "all"
-ai_generated: false
-generation_method: "human"
-price: "free"
-license: "CC-BY-SA-4.0"
----
-
-# Your Persona Name
+# Browse available personas
+list_elements type="personas"
 
-Your persona instructions go here. This content defines how the AI should behave when this persona is activated.
+# Activate a persona
+activate_element name="creative-writer" type="personas"
 
-## Response Style
-- Communication guidelines
-- Tone and approach
-- Specific behaviors
+# Browse the community collection
+browse_collection type="personas"
 
-## Key Techniques
-- Problem-solving methods
-- Interaction patterns
+# Search for specific content
+search_collection query="python" type="skills"
 ```
 
-### Metadata Fields
-
-#### Required Fields
-| Field | Description |
-|-------|-------------|
-| `name` | Display name for the persona |
-| `description` | Brief description of purpose and capabilities |
-
-#### Optional Fields
-| Field | Description |
-|-------|-------------|
-| `unique_id` | Auto-generated in format: `what-it-is_YYYYMMDD-HHMMSS_who-made-it` |
-| `author` | Creator username (uses DOLLHOUSE_USER environment variable or generates anonymous ID) |
-| `category` | One of: creative, professional, educational, gaming, personal |
-| `triggers` | Array of keywords that suggest when to use this persona |
-| `version` | Semantic version number (auto-incremented on edits) |
-| `age_rating` | Content rating: all, 13+, or 18+ |
-| `ai_generated` | Boolean flag indicating if content was AI-created |
-| `price` | Monetization field - **TODO: Future Release** (will support "free" or pricing tiers) |
-
-## 📚 Built-in Personas
-
-| Persona | Purpose | Best For |
-|---------|---------|----------|
-| **Creative Writer** | Imaginative storytelling and creative content | Brainstorming, creative writing, engaging narratives |
-| **Technical Analyst** | Deep technical analysis and systematic problem-solving | Architecture decisions, debugging, technical docs |
-| **ELI5 Explainer** | Simplifying complex topics for beginners | Teaching, onboarding, concept explanation |
-| **Business Consultant** | Strategic business analysis and recommendations | Strategy planning, business decisions, market analysis |
-| **Debug Detective** | Systematic debugging and troubleshooting | Bug hunting, system troubleshooting, root cause analysis |
-
-## 🏪 Collection Integration (Beta)
-
-> **🧪 Beta Feature**: The GitHub-powered collection is currently in beta. Features may change based on community feedback.
-
-DollhouseMCP includes an experimental GitHub-powered collection:
-
-- **Browse by Category**: creative, professional, educational, gaming, personal
-- **Search Content**: Find personas by keywords and descriptions
-- **One-Click Install**: Download and integrate collection personas
-- **Community Submissions**: Submit your personas via `submit_persona` tool
-- **Version Control**: Full Git history for all collection content
-
-> **Note**: Collection features require internet connection and GitHub API access. Rate limits may apply.
+> **📘 New User?** Follow our [Roundtrip Workflow Guide](docs/guides/ROUNDTRIP_WORKFLOW_USER_GUIDE.md) for a complete walkthrough of discovering, customizing, and sharing AI elements with the community.
 
-### ⚠️ Migration Guide - Breaking Changes
-
-**Important**: Tool names have changed in recent versions:
-- `browse_marketplace` → `browse_collection`
-- `search_marketplace` → `search_collection`
-- `get_marketplace_persona` → `get_collection_content`
-
-If you have scripts or workflows using the old tool names, please update them to use the new names.
-
-## 💼 Business Model & Legal
-
-### Licensing
-- **Core Server**: AGPL-3.0 (prevents proprietary competing platforms)
-- **Persona Content**: CC-BY-SA-4.0 for free personas, custom licenses for premium
-- **Platform Terms**: Creator-friendly 80/20 revenue split (applies only to paid personas when monetization is implemented)
-
-### Platform Stability Commitments
-- 90-day advance notice for monetization changes
-- 12-month revenue sharing locks for existing paid personas
-- Transparent governance for platform policy updates
-- Full data portability rights
-- Community advisory input on policy changes
-
-## 🛠️ Development
-
-### Available Scripts
-
-| Script | Description |
-|--------|-------------|
-| `npm run build` | Compile TypeScript to JavaScript |
-| `npm run start` | Run the compiled server |
-| `npm run dev` | Run in development mode with auto-reload |
-| `npm run clean` | Remove compiled files |
-| `npm run rebuild` | Clean and rebuild the project |
-| `npm run setup` | Install dependencies and build |
-| `npm test` | Run the comprehensive test suite |
-| `npm run test:coverage` | Run tests with coverage reporting |
-
-### Environment Variables
-
-Customize server behavior with these environment variables:
+## ✨ Key Features
 
-```bash
-# User Attribution
-export DOLLHOUSE_USER="your-username"          # User attribution for persona creation
-export DOLLHOUSE_EMAIL="your-email"            # Contact email (optional)
+| Feature | Description |
+|---------|-------------|
+| 🎭 **41 MCP Tools** | Complete portfolio element management through chat interface |
+| 🏪 **GitHub Collection** | Browse, search, install, and submit personas to community collection |
+| 🔄 **Roundtrip Workflow** | Complete cycle: discover → customize → share → collaborate |
+| 📁 **GitHub Portfolio** | Personal repository for storing and versioning your AI elements |
+| 👤 **User Identity System** | Environment-based attribution for persona creators |
+| 🆔 **Unique ID System** | Advanced ID generation: `{type}_{name}_{author}_{YYYYMMDD}-{HHMMSS}` |
+| 💬 **Chat-Based Management** | Create, edit, and validate personas through conversational interface |
+| 🔄 **Real-time Operations** | Live editing with automatic version bumping and validation |
+| 📦 **NPM Installation** | Install MCP servers from npm with cross-platform support and atomic operations |
+| 🛡️ **Data Protection** | Copy-on-write for default personas, comprehensive backup system |
+| 🏠 **Local-First Architecture** | Full functionality without cloud dependency |
 
-# GitHub OAuth Configuration
-export DOLLHOUSE_GITHUB_CLIENT_ID="Ov23li..."  # OAuth app client ID (for self-hosting)
+## 🎨 Portfolio Elements
 
-# Directory Configuration
-export PERSONAS_DIR="/custom/path/to/personas"  # Custom personas directory
+DollhouseMCP supports multiple element types for customizing AI behavior:
 
-# Auto-Update Configuration
-export GITHUB_TOKEN="your-token"               # For private repository access (optional)
+| Element | Purpose | Status |
+|---------|---------|--------|
+| 🎭 **Personas** | Define AI personality, tone, and behavioral characteristics | ✅ Available |
+| 🛠️ **Skills** | Add specific capabilities like code review, data analysis, or creative writing | ✅ Available |
+| 📝 **Templates** | Create reusable response formats for emails, reports, documentation | ✅ Available |
+| 🤖 **Agents** | Build autonomous assistants that can pursue goals and make decisions | ✅ Available |
+| 💬 **Prompts** | Pre-configured conversation starters and structured interactions | 🔄 Coming Soon |
+| 🧠 **Memory** | Persistent context storage with retention policies and search capabilities | 🔄 Coming Soon |
+| 🎯 **Ensemble** | Orchestrate multiple elements together as one unified entity | 🔄 Coming Soon |
 
-# Development Configuration
-export NODE_ENV="development"                  # Development mode
-export DEBUG="dollhousemcp:*"                  # Debug logging (optional)
-```
+Your portfolio lives in `~/.dollhouse/portfolio/` with elements organized by type.
 
 ## 🔧 Troubleshooting
 
-### ⚠️ NPM Installation Issues (v1.4.2)
-
-If the MCP server crashes on startup after NPM installation:
-1. Check your version: `npm list -g @dollhousemcp/mcp-server`
-2. If you have v1.4.2, upgrade immediately: `npm install -g @dollhousemcp/mcp-server@latest`
-3. Clear your portfolio and let it regenerate: `rm -rf ~/.dollhouse/portfolio`
-
-**Note**: v1.4.2 had a critical bug that prevented proper initialization. v1.4.3 attempted to fix this but introduced new crashes. Both issues are fixed in v1.4.4.
-
-### Directory Structure (v1.4.3+)
-
-As of v1.4.3, all element directories use plural names:
-- `~/.dollhouse/portfolio/personas/` (was `persona/` in v1.4.2)
-- `~/.dollhouse/portfolio/skills/` (was `skill/` in v1.4.2)
-- `~/.dollhouse/portfolio/templates/` (was `template/` in v1.4.2)
-- `~/.dollhouse/portfolio/agents/` (was `agent/` in v1.4.2)
-- `~/.dollhouse/portfolio/memories/` (was `memory/` in v1.4.2)
-- `~/.dollhouse/portfolio/ensembles/` (was `ensemble/` in v1.4.2)
-
-If you upgraded from v1.4.2, the server will automatically migrate your directories.
-
 ### Common Issues
 
 | Issue | Solution |
 |-------|----------|
-| **v1.4.2 or v1.4.3 installation broken** | Upgrade to v1.4.4+ immediately |
 | **Personas not loading** | Check `~/.dollhouse/portfolio/personas/` directory exists |
-| **Server won't start** | Run `npm run rebuild` to clean and rebuild |
+| **Server won't start** | Ensure Node.js v20+ is installed: `node --version` |
 | **Collection not working** | Check internet connection and GitHub API access |
-| **User identity not saving** | Set `DOLLHOUSE_USER` environment variable before starting Claude |
-| **"Cannot find module" errors** | Ensure `npm install` completed successfully |
-| **TypeScript compilation errors** | Verify Node.js version is 20+ with `node --version` |
 | **Tools not appearing in Claude** | Restart Claude Desktop completely after config changes |
-| **Default personas modified** | v1.2.1+ uses copy-on-write; git restore if needed |
-| **Update/rollback issues** | Check write permissions; disable with `DOLLHOUSE_DISABLE_UPDATES=true` |
+| **"Cannot find module" errors** | Reinstall: `npm install -g @dollhousemcp/mcp-server@latest` |
 | **Rate limit errors** | Wait 60 seconds; GitHub API has hourly limits |
 
-### Debug Steps
-
-1. **Check build status:**
-   ```bash
-   npm run build
-   ```
-
-2. **Verify persona files:**
-   ```bash
-   ls -la personas/*.md
-   ```
-
-3. **Test server startup:**
-   ```bash
-   node dist/index.js
-   ```
-
-4. **Validate configuration:**
-   ```bash
-   # Check Claude Desktop config
-   cat ~/Library/Application\ Support/Claude/claude_desktop_config.json
-   
-   # Verify Node.js version (requires 20+)
-   node --version
-   
-   # Check npm version
-   npm --version
-   ```
-
-5. **Check system status:**
-   ```bash
-   # Use within Claude Desktop
-   get_build_info    # Get build and runtime information
-   ```
-
-6. **Validate personas:**
-   Use the `reload_personas` tool to check for loading errors
-
-## 📚 Documentation
-
-### User Guides (START HERE!)
-- **[🎯 Roundtrip Workflow Guide](docs/guides/ROUNDTRIP_WORKFLOW_USER_GUIDE.md)** - Complete workflow: discover → customize → share
-- **[📁 Portfolio Setup Guide](docs/guides/PORTFOLIO_SETUP_GUIDE.md)** - Set up your GitHub portfolio step-by-step  
-- **[🔧 Troubleshooting Guide](docs/guides/TROUBLESHOOTING_ROUNDTRIP.md)** - Solutions for common workflow issues
-
-### Element System Documentation
-- **[Element Architecture](docs/ELEMENT_ARCHITECTURE.md)** - System design and core concepts
-- **[Element Types Reference](docs/ELEMENT_TYPES.md)** - Detailed guide for all element types
-- **[Developer Guide](docs/ELEMENT_DEVELOPER_GUIDE.md)** - How to create new element types
-- **[API Reference](docs/API_REFERENCE.md)** - Complete MCP tool documentation
-- **[Migration Guide](docs/MIGRATION_TO_PORTFOLIO.md)** - Upgrading from personas-only
-
-### Setup & Configuration
-- **[OAuth Setup Guide](docs/setup/OAUTH_SETUP.md)** - GitHub authentication configuration
-- **[Anonymous Submission Guide](docs/ANONYMOUS_SUBMISSION_GUIDE.md)** - Use without GitHub authentication
-
-### Additional Resources
-- **[Security Guidelines](docs/SECURITY.md)** - Security best practices
-- **[Contributing Guide](CONTRIBUTING.md)** - How to contribute
-
-## 🤝 Contributing
-
-We welcome contributions! DollhouseMCP includes integrated tools for submitting personas directly from Claude.
-
-### Integrated Contribution Process (Recommended)
-
-1. **Create or modify a persona** using the chat-based tools:
-   ```
-   create_persona "My Awesome Persona" "A helpful assistant for..." "professional"
-   ```
-
-2. **Validate your persona** to ensure quality:
-   ```
-   validate_persona "My Awesome Persona"
-   ```
-
-3. **Submit to the collection** directly from Claude:
-   ```
-   submit_persona "My Awesome Persona"
-   ```
-   This automatically creates a GitHub issue for community review.
-
-### Manual Contribution Process
-
-1. Fork the repository
-2. Create persona files in `personas/` or `custom-personas/`
-3. Follow the metadata format and naming conventions
-4. Test thoroughly with `validate_persona` tool
-5. Submit a pull request with clear description
-
-### Reporting Issues
-
-Please include:
-- Node.js version (`node --version`)
-- Operating system and version
-- Complete error messages
-- Steps to reproduce the issue
-- Relevant persona files (if applicable)
-- Claude Desktop configuration (without sensitive paths)
-
-### Development Guidelines
-
-1. **Follow TypeScript best practices**
-2. **Maintain existing code style and patterns**
-3. **Add comprehensive error handling**
-4. **Update documentation for new features**
-5. **Test thoroughly across platforms before submitting PRs**
-6. **Include tests for new functionality**
-7. **Follow semantic versioning for releases**
-
-### Development Workflow
+### Need Help?
 
-```bash
-# Fork and clone
-git clone https://github.com/your-username/DollhouseMCP.git
-cd mcp-server
+- 📖 [Full Troubleshooting Guide](docs/TROUBLESHOOTING.md)
+- 💬 [GitHub Issues](https://github.com/DollhouseMCP/mcp-server/issues)
+- 💭 [GitHub Discussions](https://github.com/DollhouseMCP/mcp-server/discussions)
 
-# Install dependencies
-npm install
+## 📚 Resources
 
-# Create feature branch
-git checkout -b feature/your-feature-name
+### Documentation
+- [Roundtrip Workflow Guide](docs/guides/ROUNDTRIP_WORKFLOW_USER_GUIDE.md)
+- [Portfolio Setup Guide](docs/guides/PORTFOLIO_SETUP_GUIDE.md)
+- [Element Detection Guide](docs/guides/ELEMENT_DETECTION_GUIDE.md)
+- [PersonaTools Migration Guide](docs/PERSONATOOLS_MIGRATION_GUIDE.md)
+- [API Documentation](docs/API.md)
 
-# Make changes and test
-npm run build
-npm test
+### Community
+- [GitHub Repository](https://github.com/DollhouseMCP/mcp-server)
+- [NPM Package](https://www.npmjs.com/package/@dollhousemcp/mcp-server)
+- [Community Collection](https://github.com/DollhouseMCP/collection)
+- [Discord Community](https://discord.gg/dollhousemcp) (coming soon)
 
-# Commit and push
-git commit -m "feat: your feature description"
-git push origin feature/your-feature-name
-
-# Submit pull request
-```
-
-## 📄 API Reference
-
-### MCP Tool Specifications
-
-Each tool follows the MCP specification:
-
-```typescript
-interface DollhouseTool {
-  name: string;
-  description: string;
-  inputSchema: {
-    type: "object";
-    properties: Record<string, any>;
-    required?: string[];
-  };
-}
-```
-
-### Tool Categories
-
-#### Persona Export/Import
-```typescript
-// export_persona - { persona: string }
-// export_all_personas - { includeDefaults?: boolean }
-// import_persona - { source: string, overwrite?: boolean }
-// share_persona - { persona: string, expiryDays?: number }
-// import_from_url - { url: string, overwrite?: boolean }
-```
-
-#### Collection Integration
-```typescript
-// browse_collection - { section?: string, type?: string }
-// search_collection - { query: string }
-// get_collection_content - { path: string }
-// install_element - { path: string, type?: string }
-// submit_persona - { persona: string }
-```
-
-#### User Identity Management
-```typescript
-// set_user_identity - { username: string }
-// get_user_identity - No parameters
-// clear_user_identity - No parameters
-```
-
-
-
-### Error Handling
-
-The server provides detailed error messages for:
-- **Invalid persona identifiers** - Clear suggestions for valid names
-- **File system issues** - Permission and path resolution errors
-- **Malformed persona files** - YAML parsing and validation errors
-- **Network errors** - GitHub API and collection connectivity issues
-- **Runtime errors** - Server startup and operation failures
-
-### Response Formats
-
-All responses follow consistent patterns:
-- **Success responses**: Include requested data and operation status
-- **Error responses**: Include error type, message, and suggested resolution
-- **Progress indicators**: Step-by-step feedback for long operations
-- **Validation results**: Detailed reports with recommendations
+### Development
+- [Contributing Guide](CONTRIBUTING.md)
+- [Security Policy](SECURITY.md)
+- [Full Changelog](CHANGELOG.md)
 
 ## 📄 License
 
-This project is licensed under the **AGPL-3.0** License with Platform Stability Commitments - see the [LICENSE](LICENSE) file for details.
-
-**Platform Stability Guarantees:**
-- 90-day advance notice for policy changes
-- 12-month revenue sharing locks
-- Full data portability rights
-- Community advisory input
-
-## 🏷️ Version History
-
-### v1.6.9 - August 26, 2025
-
-**Critical Fixes**: Fixed OAuth helper NPM packaging and performance testing workflow
-
-#### 🔧 Bug Fixes
-- **OAuth NPM Packaging**: Fixed missing `oauth-helper.mjs` file in NPM distribution
-  - File was present in repository but not included in published package
-  - OAuth authentication now works correctly for NPM users
-- **Performance Tests**: Fixed CI workflow running all tests instead of performance tests
-  - Performance monitoring now works correctly in GitHub Actions
+DollhouseMCP is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
 
----
-
-### v1.6.3 - August 25, 2025
+### What this means:
+- ✅ **Free to use** for personal and commercial purposes
+- ✅ **Modify and distribute** with the same license
+- ✅ **Network use** requires source code disclosure
+- ✅ **Platform stability** commitments protect users
 
-**OAuth Authentication Fix**: Fixed invalid OAuth client ID and improved error handling
-
-#### 🔧 Bug Fixes
-- **OAuth Client ID**: Updated from incorrect ID to correct `Ov23li9gyNZP6m9aJ2EP`
-- **Error Handling**: Added comprehensive error codes throughout OAuth flow
-- **Debug Logging**: Added detailed logging at each authentication step
+See [LICENSE](LICENSE) for full terms.
 
 ---
 
-### v1.6.2 - August 25, 2025
-
-**Critical Hotfix**: Fixed OAuth default client ID not being used in `setup_github_auth` tool
-
-#### 🔧 Bug Fixes
-- **OAuth Authentication**: Fixed critical bug where default OAuth client ID wasn't used in `setupGitHubAuth()` method
-- **Configuration Fallback**: Now correctly uses `GitHubAuthManager.getClientId()` with proper fallback hierarchy
-
-#### 📚 Technical Details
-- Made `GitHubAuthManager.getClientId()` public (was private)
-- Updated `setupGitHubAuth()` to use proper fallback chain
-- Restored "just works" authentication experience promised in v1.6.1
-
----
-
-### v1.6.1 - August 25, 2025
-
-**⚠️ Breaking Changes**:
-- 🔄 **Serialization Format Change** - `BaseElement.serialize()` now returns markdown with YAML frontmatter instead of JSON
-  - Migration: Use new `serializeToJSON()` method for backward compatibility
-- 🏗️ **Server Initialization** - Portfolio initialization moved from constructor to `run()` method
-  - New `ensureInitialized()` method provides lazy initialization for tests
-
-**Major New Features**:
-- 🔍 **Enhanced Portfolio System** (6 new tools):
-  - `portfolio_status` - Check GitHub portfolio status
-  - `init_portfolio` - Create GitHub portfolio repository
-  - `sync_portfolio` - Synchronize local/GitHub repositories  
-  - `search_portfolio` - Search with advanced indexing
-  - `search_all` - Unified search across all sources
-  - Complete GitHub integration with indexing
-- 📊 **Enhanced Collection Search**:
-  - `search_collection_enhanced` - Pagination, filtering, sorting
-  - `get_collection_cache_health` - Cache monitoring
-  - Smart caching with ETags and conditional requests
-- 🛠️ **System Tools**:
-  - `get_build_info` - Comprehensive build and runtime information
-- ⚙️ **Collection Configuration**:
-  - `configure_collection_submission` - Auto-submit settings
-  - `get_collection_submission_config` - Check submission config
-
-**Infrastructure Improvements**:
-- 🚀 **High-Performance Caching** - Memory-aware LRU cache system
-- 🔒 **Enhanced Security** - YAML bomb protection, content validation
-- 📦 **Build Information Service** - Runtime and build info API
-- 🎯 **Error Handler** - Centralized error management system
-- 🔄 **Roundtrip Workflow** - Complete content submission cycle
-
-**Statistics**:
-- 42 total MCP tools (down from 51 - 9 PersonaTools removed, 5 preserved)
-- 89 commits ahead of main
-- 257 files changed
-- 50,857 lines added
-- 76 test files modified/added
-
-### v1.5.1 - August 5, 2025
-**Critical Bug Fixes**:
-- 🔧 **Fixed OAuth Token Retrieval** - `setup_github_auth` tokens now properly used for API calls
-- 🔧 **Fixed Collection Browsing** - Removed legacy category validation blocking browsing
-- 🔧 **Persona Creation Simplified** - Categories no longer required or validated
-- ✅ **Element System Alignment** - Full consistency with new architecture
-
-### v1.5.0 - August 5, 2025
-**GitHub OAuth Authentication**:
-- 🔐 **OAuth Device Flow** - Secure authentication without manual token management
-- 🔒 **AES-256-GCM Encryption** - Tokens encrypted at rest with machine-specific keys
-- 🛡️ **Rate Limiting** - Built-in protection against brute force attacks
-- ✅ **Natural Language Flow** - User-friendly authentication instructions
-- 🧪 **Comprehensive Tests** - 420+ lines of OAuth implementation tests
-
-### v1.4.5 - August 5, 2025
-**Claude Desktop Integration Fix**:
-- ✅ **Fixed "Server disconnected" errors** when using `npx` or `dollhousemcp` CLI
-- 🔄 **Progressive retry mechanism** for better compatibility across different machine speeds
-- 🔒 **Security improvements** - removed detailed error logging to prevent information disclosure
-- 🧪 **Added comprehensive tests** for execution detection logic
-
-### v1.4.4 - August 4, 2025
-**Emergency Hotfix**:
-- 🚨 **Fixed v1.4.3 total failure** - initialization crashes fixed
-- 🔧 **Fixed jsdom crash** - heavy dependencies now load lazily
-- 🐳 **Fixed Docker compatibility** - handles read-only environments
-
-### v1.4.3 - August 4, 2025
-**Directory Structure Fix**:
-- 🚨 **Fixed NPM installation failure** but introduced new crashes
-
-### v1.4.2 - August 4, 2025
-**Critical NPM Installation Fix**:
-- 🚨 **Fixed NPM installation failure** where empty portfolios caused server crashes
-- 📦 **DefaultElementProvider** automatically populates default content on first run
-- 🔍 **Smart path detection** searches multiple NPM/Git installation locations
-- 💬 **Helpful error messages** guide new users when portfolios are empty
-- 🔒 **Security hardened** with audit logging and file integrity verification
-
-### v1.4.1 - August 2, 2025
-**NPM Installation Support**:
-- 📦 **Install MCP servers from npm packages** with full cross-platform support
-- 🔄 **Atomic operations** with transaction-based rollback on failure
-- 📊 **Progress indicators** for better user experience during long operations
-- 🏗️ **Centralized configuration** respecting platform conventions (XDG on Linux)
-- 🛠️ **FileOperations utility** for consistent cross-platform behavior
-
-### v1.4.0 - August 2, 2025
-**Complete Element System**:
-- 🎭 **Ensemble elements** for orchestrating multiple elements together
-- 🧠 **Memory elements** with retention policies and search capabilities
-- 🤖 **Agent elements** with goal-oriented decision making
-- 📝 **Template elements** with secure variable substitution
-- 🛠️ **Skill elements** with parameter system and proficiency tracking
-- 🔒 **Comprehensive security** throughout all element types
-
-### v1.3.3 - August 2, 2025
-**Portfolio System & Element Types**:
-- 🎨 **Portfolio-based architecture** for managing all AI customization elements
-- 🛠️ **Generic element tools** that work with any element type
-- 📁 **Structured directory layout** under `~/.dollhouse/portfolio/`
-- 🔄 **Backward compatibility** maintained for existing personas
-
-### v1.3.2 - August 1, 2025
-**GitFlow Implementation**:
-- 🔀 **GitFlow branching model** for better release management
-- 🏷️ **Automated version tagging** on releases
-- 📦 **NPM release automation** (pending token configuration)
-
-### v1.3.1 - July 31, 2025
-**Collection System Updates**:
-- 🏪 **Improved collection browsing** with better error handling
-- 🔍 **Enhanced search functionality** for finding content
-- 📥 **Better installation process** with validation
-
-### v1.3.0 - July 30, 2025
-**Major Architecture Refactor**:
-- 🏗️ **Element interface system** providing foundation for all element types
-- 🔐 **Security-first implementation** with comprehensive protections
-- 📊 **Improved test coverage** reaching 96%+
-
-### v1.2.5 - July 2025
-
-**Collection Rename & Breaking Changes**:
-- 🔄 **Renamed all "marketplace" tools to "collection"**:
-  - `browse_marketplace` → `browse_collection`
-  - `search_marketplace` → `search_collection`
-  - `get_marketplace_persona` → `get_collection_content`
-  - `install_persona` → `install_persona` (unchanged)
-  - `submit_persona` → `submit_persona` (unchanged)
-- ✅ **Added backward compatibility aliases** (deprecated, will be removed in v2.0.0)
-- ✅ **Updated repository** from `/personas` to `/collection`
-- ✅ **Created migration guide** for users to update their scripts
-- ✅ **Fixed all date references** from January to July 2025
-
-### v1.2.4 - July 10, 2025
-
-**Critical Fix**:
-- ✅ **Fixed MCP protocol compatibility** - console output no longer breaks JSON-RPC communication
-- ✅ **Added MCP-safe logger utility** for proper logging during protocol sessions
-- ✅ **Resolves connection failures** in Claude Desktop
-- ✅ **Updated Docker tests** to work with new logging approach
-- ✅ **Added comprehensive logger unit tests**
-
-### v1.2.3 - July 10, 2025
-
-**Bug Fix**:
-- ✅ **Fixed personas directory path resolution** for production environments
-- ✅ **Changed from process.cwd() to __dirname-based paths**
-- ✅ **Fixed setup script** with correct tool count and repository URLs
-
-### v1.2.2 - July 10, 2025
-- ✅ **Comprehensive security enhancements**:
-  - Content sanitization with DOMPurify (SEC-001)
-  - YAML injection prevention (SEC-003)
-  - GitHub token security (SEC-004)
-  - Docker container hardening (SEC-005)
-- ✅ **487 comprehensive tests** including extensive security coverage
-- ✅ **CI timing test fixes** for reliable cross-platform testing
-- ✅ **TypeScript compilation fixes** for all test files
-- ✅ **All security vulnerabilities resolved** (0 active alerts)
-
-### v1.2.1 - July 8, 2025
-- ✅ **Critical bug fixes** for data protection:
-  - Copy-on-write for default personas (Issue #145)
-  - User personas included in backups (Issue #144)
-- ✅ **Node.js 20+ requirement** for npm publishing compatibility
-- ✅ **372 comprehensive tests** covering all functionality
-- ✅ **Enhanced security** with all vulnerabilities resolved
-- ✅ **Improved documentation** with clear prerequisites
-
-### v1.2.0 - July 7, 2025
-- ✅ **Rate limiting implementation** to prevent API abuse
-- ✅ **GPG signature verification** for release authenticity
-- ✅ **GitHub Advanced Security** integration
-- ✅ **309 tests** with improved CI environment coverage
-- ✅ **Package optimization** at 279.3 kB
-
-### v1.1.0 - July 4, 2025
-- ✅ **Platform-specific badges** for Windows, macOS, Linux visibility
-- ✅ **GitHub Project management** with issue templates and milestones
-- ✅ **ARM64 Docker fix** switching from Alpine to Debian base images
-- ✅ **100% workflow reliability** (except Docker ARM64)
-- ✅ **First GitHub release** with CHANGELOG.md
-- ✅ **21 total MCP tools** at time of release
-
-### Phase 2B+ - July 3, 2025
-- ✅ **Enterprise-grade auto-update system** with 4 new MCP tools
-- ✅ **50 comprehensive tests** covering all functionality  
-- ✅ **Security hardening** - eliminated all command injection vulnerabilities
-- ✅ **Cross-platform support** - Windows, macOS, Linux with CI/CD testing
-- ✅ **Docker containerization** with production and development configurations
-- ✅ **21 total MCP tools** with backup/rollback and dependency validation
-
-### Phase 2B - July 1-2, 2025
-- ✅ Complete chat-based persona management
-- ✅ GitHub marketplace integration
-- ✅ User identity and attribution system
-- ✅ Real-time validation and editing
-- ✅ Enterprise-grade GitHub Actions security
-
-### Phase 1 - July 1, 2025
-- ✅ Fresh AGPL-3.0 licensed repository
-- ✅ Enhanced unique ID system
-- ✅ Anonymous user support
-- ✅ Marketplace-ready metadata schema
-
----
-
-**🎭 Transform your AI interactions with the power of personas**
-
-For support, please [open an issue](https://github.com/DollhouseMCP/mcp-server/issues) or visit our [collection](https://github.com/DollhouseMCP/collection).
+*Built with ❤️ by the DollhouseMCP team*