fix: Revert breaking changes from vteam to acp naming

- Revert API group to vteam.ambient-code (maintain backward compatibility)
- Revert namespace to vteam-dev (avoid breaking deployments)
- Revert service/route names to vteam-* (maintain service discovery)
- Revert container image names to vteam-* in examples
- Keep product name changes (vTeam → ACP in narrative text)
- Keep new Mermaid architecture diagrams

Per ACP Constitution naming guidelines, technical artifacts must
remain as 'vteam' for backward compatibility. Only user-facing
narrative text uses 'Ambient Code Platform' or 'ACP'.

Fixes 24 files with breaking changes while preserving improvements.

Author: bobbravo2

.security-scan.zip

@@ -0,0 +1,114 @@
+# Repository Security Analysis Report
+
+## Summary Statistics
+| Metric | Value |
+|--------|-------|
+| Total Files | 582 |
+| Source Files | 349 |
+| High Priority Files | 163 |
+| Total Dependencies | 88 |
+| Languages | Python, TypeScript, Go, JavaScript, Shell |
+
+## Repository Overview
+Kubernetes-native AI automation platform with multi-component architecture:
+- Frontend: NextJS + Shadcn UI
+- Backend: Go + Gin
+- Operator: Kubernetes Controller
+- Runner: Python-based Claude Code executor
+
+## Language Distribution
+| Language | Files | Lines of Code |
+|----------|-------|---------------|
+| Python | 14 | 5,748 |
+| TypeScript | 229 | 23,687 |
+| Go | 88 | 33,447 |
+| JavaScript | 2 | 89 |
+| Shell | 16 | 4,328 |
+
+## Dependency Files
+1. `components/frontend/package.json` (43 npm dependencies)
+2. `components/operator/go.mod` (45 Go dependencies)
+
+## Container Configuration
+Dockerfiles found for multiple components:
+1. Frontend (dev and prod)
+2. Backend (dev and prod)
+3. Operator
+4. Claude Code Runner
+
+## Source Files by Category
+
+### 🔒 Authentication Mechanisms (High Priority)
+**Key Files**:
+- `components/backend/handlers/github_auth.go`: GitHub OAuth handling
+- `components/backend/handlers/oauth.go`: Generic OAuth implementation
+- `components/frontend/src/lib/auth.ts`: Frontend authentication utilities
+
+**Pattern Analysis**:
+- Secure state validation in OAuth callbacks
+- HMAC-based state signature verification
+- User session matching
+- 10-minute state expiration
+- Comprehensive error handling
+
+### 🛡️ Input Validation (Security Critical)
+**Key Files**:
+- `components/runners/claude-code-runner/security_utils.py`: Exception sanitization
+- `components/backend/handlers/sessions.go`: Spec parsing with strict type checking
+
+**Pattern Analysis**:
+- Lenient logging validation (removes control characters)
+- Strict sanitization of user inputs
+- Prevents log injection
+- Redacts sensitive information in error messages
+- Maximum length enforcement for inputs
+
+### 🔐 Cryptographic Patterns
+**Key Files**:
+- `components/backend/github/token.go`: Token management
+- `components/backend/handlers/github_auth.go`: HMAC-based state signing
+
+**Observations**:
+- Uses HMAC-SHA256 for state signature generation
+- Secure token management
+- Explicit input sanitization in cryptographic contexts
+
+### 🌐 API Endpoint Security
+**Key Patterns**:
+- Project-scoped API endpoints
+- User token authentication
+- RBAC enforcement via Kubernetes self-subject access reviews
+- Namespace-level isolation
+
+### 📊 Data Handling
+**Security Observations**:
+- Explicit type conversion in data parsing
+- Defensive programming techniques
+- Strict input validation
+- Secrets management via Kubernetes secrets
+
+### 🤖 LLM Integration Security
+**Key Files**:
+- `components/runners/claude-code-runner/security_utils.py`
+- `components/runners/claude-code-runner/observability.py`
+
+**Pattern Analysis**:
+- Privacy-first approach to LLM tracing
+- Metadata masking
+- Operation timeouts
+- Exception sanitization
+
+## Key Observations
+1. Multi-layered security design
+2. Comprehensive input validation
+3. Secrets management via Kubernetes
+4. Privacy-preserving observability
+5. Defensive programming patterns
+6. Strict authentication mechanisms
+
+## Recommendations
+1. Continue current security design
+2. Regular dependency updates
+3. Expand test coverage for edge cases
+4. Periodic security audits
+