refactor: rename OpenHarbor.MCP to Svrnty.MCP across all libraries

- Renamed all directories: OpenHarbor.MCP.* → Svrnty.MCP.*
- Updated all namespaces in 179 C# files
- Renamed 20 .csproj files and 3 .sln files
- Updated 193 documentation references
- Updated 33 references in main CODEX codebase
- Updated Codex.sln with new paths
- Build verified: 0 errors

Preparing for extraction to standalone repositories.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

docs/deployment/https-setup.md

@@ -1,4 +1,4 @@
-# HTTPS/TLS Setup Guide - OpenHarbor.MCP.Server
+# HTTPS/TLS Setup Guide - Svrnty.MCP.Server
 
 **Purpose**: Production-grade HTTPS/TLS configuration for secure MCP server deployment
 **Audience**: DevOps engineers, system administrators
@@ -22,7 +22,7 @@
 
 ## Overview
 
-OpenHarbor.MCP.Server supports HTTPS/TLS through ASP.NET Core's Kestrel web server. This guide covers configuration for both development and production environments.
+Svrnty.MCP.Server supports HTTPS/TLS through ASP.NET Core's Kestrel web server. This guide covers configuration for both development and production environments.
 
 **Security Benefits:**
 - Encrypted communication (prevents eavesdropping)
@@ -101,7 +101,7 @@ Create or update `appsettings.Development.json` in the Server project:
 **Step 3: Run Server with HTTPS**
 
 ```bash
-cd OpenHarbor.MCP.Server/samples/CodexMcpServer
+cd Svrnty.MCP.Server/samples/CodexMcpServer
 dotnet run --environment Development
 
 # Server will listen on:
@@ -134,7 +134,7 @@ curl -k -X POST https://localhost:5051/mcp/invoke \
 
 ```bash
 # Create directory for certs
-mkdir -p /home/svrnty/codex/OpenHarbor.MCP.Server/certs
+mkdir -p /home/svrnty/codex/Svrnty.MCP.Server/certs
 
 # Generate private key
 openssl genrsa -out certs/localhost.key 2048