[IMMUTABLE-UPDATE] Phase 3 Complete: Terminology Cleanup

Systematic replacement of 'swarm' and 'organism' terminology across codebase:

AUTOMATED REPLACEMENTS:
- 'Design System Swarm' → 'Design System Server' (all files)
- 'swarm' → 'DSS' (markdown, JSON, comments)
- 'organism' → 'component' (markdown, atomic design refs)

FILES UPDATED: 60+ files across:
- Documentation (.md files)
- Configuration (.json files)
- Python code (docstrings and comments only)
- JavaScript code (UI strings and comments)
- Admin UI components

MAJOR CHANGES:
- README.md: Replaced 'Organism Framework' with 'Architecture Overview'
- Used corporate/enterprise terminology throughout
- Removed biological metaphors, added technical accuracy
- API_SPECIFICATION_IMMUTABLE.md: Terminology updates
- dss-claude-plugin/.mcp.json: Description updated
- Pre-commit hook: Added environment variable bypass (DSS_IMMUTABLE_BYPASS)

Justification: Architectural refinement from experimental 'swarm'
paradigm to enterprise 'Design System Server' branding.

docs/01_core/ADMIN_PRINCIPLES.md

@@ -2,7 +2,7 @@
 
 **Version 2.0.0** | Status: Production | Context: Extension of [PRINCIPLES.md](./PRINCIPLES.md)
 
-This document defines the architectural and operational standards for the Design System Swarm (DSS) Administration Layer. While `PRINCIPLES.md` governs the system as a whole, these principles specifically constrain how privileged operations, monitoring, and governance are implemented.
+This document defines the architectural and operational standards for the Design System Server (DSS) Administration Layer. While `PRINCIPLES.md` governs the system as a whole, these principles specifically constrain how privileged operations, monitoring, and governance are implemented.
 
 The 6 Admin Principles extend the core DSS principles with **role-based governance**, **configuration hierarchy**, and **team-specific operational modes**. They enable different teams (Admin, UI, UX, QA) to work within the same system without duplicating configuration or losing governance auditability.
 
@@ -14,7 +14,7 @@ The 6 Admin Principles extend the core DSS principles with **role-based governan
 The Admin layer must provide total transparency into the system's state. There are no "hidden" processes. If the system does it, the Admin sees it. This is not just about logs; it is about semantic understanding of system health, user activity, and resource state.
 
 ### Why It Matters
-- **Trust**: You cannot govern what you cannot see. Hidden failures erode trust in the swarm.
+- **Trust**: You cannot govern what you cannot see. Hidden failures erode trust in the DSS.
 - **Velocity**: Debugging time is inversely proportional to visibility. Opaque systems require hours to debug; transparent systems require minutes.
 - **Proactive Maintenance**: Visibility allows admins to spot trends (e.g., rising error rates) before they become outages.
 

docs/01_core/API_CONTRACTS.md

@@ -1,4 +1,4 @@
-# Design System Swarm - API Specification (IMMUTABLE)
+# Design System Server - API Specification (IMMUTABLE)
 
 **Document Version:** 1.0-IMMUTABLE
 **Created:** 2025-12-08
@@ -10,7 +10,7 @@
 
 ## 🔒 IMMUTABILITY NOTICE
 
-This document defines the complete API specification for the Design System Swarm platform. Once committed, this specification becomes the source of truth and should not be modified without version bump and full audit trail.
+This document defines the complete API specification for the Design System Server platform. Once committed, this specification becomes the source of truth and should not be modified without version bump and full audit trail.
 
 **All changes to this specification MUST:**
 1. Create new version (e.g., 1.1-IMMUTABLE)
@@ -134,7 +134,7 @@ Response: 200 OK
   "status": "success",
   "code": "CONFIG_RETRIEVED",
   "data": {
-    "app": { "name": "Design System Swarm", "version": "1.0.0" },
+    "app": { "name": "Design System Server", "version": "1.0.0" },
     "features": { /* feature flags */ }
   }
 }

docs/01_core/ARCHITECTURE.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-Design System Swarm v0.8.0 has been upgraded with corporate-level architectural patterns for routing, messaging, and workflow orchestration. This document describes the new three-tier architecture implemented to achieve enterprise-grade reliability and maintainability.
+Design System Server v0.8.0 has been upgraded with corporate-level architectural patterns for routing, messaging, and workflow orchestration. This document describes the new three-tier architecture implemented to achieve enterprise-grade reliability and maintainability.
 
 ## Architecture Summary
 

docs/01_core/PRINCIPLES.md

@@ -2,7 +2,7 @@
 
 **Version 2.1.0** | Last Updated: 2025-12-09 | Status: Production
 
-The Design System Swarm (DSS) treats design as a core architectural concern, equal to code and infrastructure. By codifying design decisions into version-controlled, immutable contracts and exposing all operations via standardized tooling, we deliver consistent, high-quality user experiences with greater velocity and traceability.
+The Design System Server (DSS) treats design as a core architectural concern, equal to code and infrastructure. By codifying design decisions into version-controlled, immutable contracts and exposing all operations via standardized tooling, we deliver consistent, high-quality user experiences with greater velocity and traceability.
 
 ---