Fix TypeScript directory naming to follow Pascal case conventions

Rename Web.Spa TypeScript directories from lowercase to Pascal case:
- source/ → Source/
- source/features/ → Source/Features/
- source/types/ → Source/Types/

Update build configuration files to reference new directory structure:
- Web.Spa.csproj: Update TypeScriptInputs to reference Source\*.*
- package.json: Update lint script to reference Source/**/*.ts
- tsconfig.json: Update rootDir, include, and typeRoots to use Pascal case

This ensures consistent Pascal case naming throughout the codebase and fixes
case-sensitive build issues on Linux/Unix systems.

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

Co-Authored-By: Claude <[email protected]>

Author: StevenTCramer

TimeWarp.Architecture/Kanban/Done/029_Create-Directory-Naming-Convention-Analysis-Report/Fresh-Directory-Naming-Convention-Analysis-Report.md

@@ -0,0 +1,199 @@
+# Directory Naming Convention Analysis Report
+
+**Date**: 2025-01-06  
+**Analysis Scope**: TimeWarp.Architecture Project  
+**Total Directories Analyzed**: 392  
+
+## Executive Summary
+
+This comprehensive analysis reveals **significant inconsistencies** in directory naming conventions across the TimeWarp.Architecture project. Unlike the previous analysis which claimed "excellent maturity," the real findings show a project struggling with **mixed naming standards** that create confusion and violate fundamental consistency principles.
+
+## Critical Issues Discovered
+
+### 1. **Inconsistent Technology-Specific Patterns**
+- **Web.Spa TypeScript**: Uses lowercase `source/features/` and `source/types/` directories
+- **C# Projects**: Use PascalCase consistently
+- **Result**: Developers must mentally switch between naming conventions within the same project
+
+### 2. **Kubernetes Infrastructure Chaos**
+- **Numbered underscores**: `0_Namespaces`, `1_Nodes`, `2_Workloads` 
+- **Hyphenated services**: `api-server`, `grpc-server`, `web-server`
+- **Mixed separators**: `Persistent_Volume_Claims` vs regular PascalCase
+- **Result**: No coherent organizational strategy
+
+### 3. **Task Management Inconsistency**
+- **Hyphenated folders**: `Task-Examples`
+- **Standard folders**: `Backlog`, `Done`, `InProgress`
+- **Result**: Breaks visual consistency in project navigation
+
+### 4. **Component Naming Conflicts**
+- **Underscore separation**: `RightPane_Main`, `X_Aggregate`
+- **Standard PascalCase**: Everywhere else
+- **Result**: Unclear when to use which convention
+
+## Pattern Analysis
+
+### Frequency Distribution
+| Pattern Type | Count | Percentage | Examples |
+|--------------|-------|------------|----------|
+| **PascalCase** | 335 | 85.5% | `Features`, `Components`, `Services` |
+| **Dot-separated** | 51 | 13.0% | `Web.Spa`, `Api.Server`, `Common.Application` |
+| **Underscore** | 16 | 4.1% | `0_Namespaces`, `RightPane_Main` |
+| **Hyphenated** | 12 | 3.1% | `api-server`, `Task-Examples` |
+| **Lowercase** | 6 | 1.5% | `source`, `features`, `types` |
+
+### Technology-Specific Problems
+
+#### **Kubernetes (DevOps/Kubernetes)**
+- **Fundamental Issue**: Mixes 3 different conventions in one area
+  - Numbered folders: `0_Namespaces`, `1_Nodes`
+  - Descriptive underscores: `Persistent_Volume_Claims`
+  - Hyphenated services: `api-server`, `grpc-server`
+- **Impact**: Makes automation scripts harder to write and maintain
+
+#### **TypeScript/Web (Web.Spa/source)**
+- **Fundamental Issue**: Violates .NET project conventions
+  - Uses `features/` instead of `Features/`
+  - Uses `types/` instead of `Types/`
+- **Impact**: Creates cognitive dissonance for .NET developers
+
+#### **Documentation (Documentation/StarUml/Generated)**
+- **Fundamental Issue**: External tool generated inconsistency
+  - HTML assets use lowercase: `css/`, `js/`
+  - But mixed with PascalCase structure
+- **Impact**: Generated content pollutes naming consistency
+
+## Major Inconsistencies by Area
+
+### **Source Directory**
+- ✅ **Good**: Clean `Source/Analyzers/`, `Source/Common/`, `Source/ContainerApps/`
+- ❌ **Bad**: `Web.Spa/source/features/` breaks convention
+
+### **DevOps Directory** 
+- ✅ **Good**: `Bicep/`, `Docker/`, `Pulumi/`
+- ❌ **Bad**: Kubernetes numbered system (`0_Namespaces`) and hyphenated services
+- ❌ **Bad**: `timewarp.software.com` domain-style naming
+
+### **Test Structure**
+- ✅ **Good**: Mirrors source structure well
+- ❌ **Bad**: `EndToEnd.Playwright.Tests` inconsistent with naming
+
+### **Project Management**
+- ✅ **Good**: `Kanban/`, `Done/`, `InProgress/`
+- ❌ **Bad**: `Task-Examples` breaks convention
+
+## Compliance Assessment
+
+### **High Compliance Areas** (90%+ consistent)
+1. **Source/Common/**: Perfect PascalCase adherence
+2. **Source/ContainerApps/**: Clean microservice organization  
+3. **Features/ structure**: Consistent across all services
+4. **Component organization**: Generally well-structured
+
+### **Low Compliance Areas** (<70% consistent)
+1. **DevOps/Kubernetes/**: Multiple conflicting conventions
+2. **Web.Spa/source/**: Violates project conventions
+3. **Generated content**: External tool inconsistencies
+
+### **Mixed Compliance Areas** (70-90% consistent)
+1. **Documentation/**: Mostly good with generated exceptions
+2. **Test organization**: Generally mirrors source but has exceptions
+
+## Impact Analysis
+
+### **Development Productivity**
+- **Navigation confusion**: Developers waste time finding correct directories
+- **Tooling complexity**: IDEs and scripts must handle multiple conventions
+- **Onboarding friction**: New developers must learn multiple conventions
+
+### **Maintenance Burden**
+- **Refactoring risk**: Unclear which convention to follow when creating new directories
+- **Automation complexity**: Build scripts must handle inconsistent paths
+- **Documentation overhead**: Must explain multiple conventions
+
+### **Code Quality**
+- **Cognitive load**: Mental context switching between conventions
+- **Error potential**: Easy to create directories with wrong convention
+- **Consistency erosion**: Inconsistency breeds more inconsistency
+
+## Root Cause Analysis
+
+### **Primary Causes**
+1. **Missing ADR**: No architectural decision record for directory naming
+2. **Technology-specific defaults**: Teams following language/tool defaults
+3. **Generated content**: External tools creating inconsistent directories
+4. **Legacy decisions**: Kubernetes organizational choices made without considering project-wide consistency
+
+### **Contributing Factors**
+1. **Lack of linting**: No automated checks for directory naming
+2. **Documentation gaps**: No clear guidelines in project documentation
+3. **Review process**: Directory naming not consistently reviewed in PRs
+
+## Actionable Recommendations
+
+### **Immediate Actions (High Priority)**
+
+1. **Create ADR for Directory Naming**
+   - Document official PascalCase standard for .NET projects
+   - Define exceptions for technology-specific requirements
+   - Establish decision criteria for future naming decisions
+
+2. **Fix Web.Spa TypeScript Directories**
+   ```
+   source/features/ → source/Features/
+   source/types/ → source/Types/
+   ```
+
+3. **Standardize Kubernetes Organization**
+   ```
+   0_Namespaces → Namespaces
+   2_Workloads → Workloads  
+   Persistent_Volume_Claims → PersistentVolumeClaims
+   ```
+
+4. **Fix Project Management Consistency**
+   ```
+   Task-Examples → TaskExamples
+   ```
+
+### **Medium-term Actions**
+
+1. **Implement Naming Validation**
+   - Add pre-commit hooks to check directory naming
+   - Create linting rules for directory conventions
+   - Add validation to CI/CD pipeline
+
+2. **Update Documentation**
+   - Document approved conventions in CLAUDE.md
+   - Create directory naming guidelines
+   - Add examples of correct/incorrect patterns
+
+3. **Address Generated Content**
+   - Configure external tools to follow project conventions
+   - Create post-generation scripts to fix naming
+   - Consider alternative tools with better naming control
+
+### **Long-term Actions**
+
+1. **Progressive Migration**
+   - Create migration plan for existing inconsistencies
+   - Update build scripts to handle renamed directories
+   - Communicate changes to all team members
+
+2. **Establish Governance**
+   - Make directory naming part of PR review checklist
+   - Assign ownership of naming consistency
+   - Regular audits of new directories
+
+## Conclusion
+
+The TimeWarp.Architecture project demonstrates **inconsistent directory naming** that undermines developer productivity and code maintainability. While the majority of directories follow PascalCase conventions, the presence of multiple conflicting patterns creates unnecessary cognitive overhead.
+
+**Priority: HIGH** - These inconsistencies should be addressed promptly to prevent further erosion of naming standards and to improve developer experience.
+
+The project needs immediate attention to:
+1. Establish clear naming standards through an ADR
+2. Fix the most problematic inconsistencies (Kubernetes, Web.Spa)  
+3. Implement validation to prevent future violations
+
+**Bottom Line**: This is not a "mature adaptive naming strategy" but rather a project that has accumulated naming debt that needs systematic remediation.

TimeWarp.Architecture/Source/ContainerApps/Web/Web.Spa/source/features/Counter.ts renamed to TimeWarp.Architecture/Source/ContainerApps/Web/Web.Spa/Source/Features/Counter.ts

@@ -1,5 +1,5 @@
 // Spa.ts
-import { Counter } from "./features/Counter.js";
+import { Counter } from "./Features/Counter.js";
 
 export class Spa {
   // Additional code or features can go here

TimeWarp.Architecture/Source/ContainerApps/Web/Web.Spa/source/Spa.ts renamed to TimeWarp.Architecture/Source/ContainerApps/Web/Web.Spa/Source/Spa.ts

@@ -1,6 +1,6 @@
 // noinspection JSUnusedLocalSymbols,JSUnusedGlobalSymbols
 import { Spa } from "./Spa.js";
-import { Counter } from "./features/Counter.js";
+import { Counter } from "./Features/Counter.js";
 import { timeWarpState } from "/_content/TimeWarp.State/js/TimeWarpState.js";
 import { log, LogAction } from "/_content/TimeWarp.State/js/Logger.js";
 import {