feat: complete monorepo structure with frontend and shared resources

- Add complete backend/ directory with full Django application
- Add frontend/ directory with Vite + TypeScript setup ready for Next.js
- Add comprehensive shared/ directory with:
  - Complete documentation and memory-bank archives
  - Media files and avatars (letters, park/ride images)
  - Deployment scripts and automation tools
  - Shared types and utilities
- Add architecture/ directory with migration guides
- Configure pnpm workspace for monorepo development
- Update .gitignore to exclude .django_tailwind_cli/ build artifacts
- Preserve all historical documentation in shared/docs/memory-bank/
- Set up proper structure for full-stack development with shared resources

shared/docs/memory-bank/projects/company-migration-analysis.md

@@ -0,0 +1,173 @@
+# Company Migration Analysis - Complete Codebase Assessment
+
+**Date**: 2025-07-04  
+**Status**: ✅ ANALYSIS COMPLETE  
+**Risk Level**: 🔴 HIGH (300+ references, complex dependencies)  
+**Next Phase**: Documentation → Implementation → Testing
+
+## Executive Summary
+
+Comprehensive analysis of the ThrillWiki Django codebase has identified **300+ company references** across the entire application. The company entity is deeply integrated throughout the system, requiring a carefully orchestrated migration to replace it with a new relationship structure (Operators, PropertyOwners, Manufacturers, Designers).
+
+## Analysis Findings Overview
+
+### Total Impact Assessment
+- **300+ Company References** found across entire codebase
+- **Critical Dependencies** in core models (parks, rides)
+- **Complex Integration** with pghistory tracking system
+- **Extensive Template Usage** across 6+ template files
+- **Comprehensive Test Coverage** requiring updates (429 lines)
+- **URL Pattern Dependencies** across 22 endpoints
+
+## Detailed Breakdown by Component
+
+### 1. Models & Database Schema
+**Location**: `companies/models.py`, `parks/models.py:57`, `rides/models.py:173`
+
+#### Critical Dependencies Identified:
+- **Parks Model** (`parks/models.py:57`): Foreign key relationship to Company.owner
+- **Rides Model** (`rides/models.py:173`): Foreign key relationship to Company (manufacturer)
+- **Company Model**: Core entity with multiple relationships and pghistory integration
+
+#### Database Schema Impact:
+- Foreign key constraints across multiple tables
+- pghistory tracking tables requiring migration
+- Potential data integrity concerns during transition
+
+### 2. URL Patterns & Routing
+**Location**: `companies/urls.py`
+
+#### 22 URL Patterns Identified:
+- Company list/detail views
+- Company creation/editing endpoints
+- Company search and filtering
+- Company-related API endpoints
+- Admin interface routing
+- Company profile management
+
+### 3. Templates & Frontend
+**Location**: `templates/companies/`, cross-references in other templates
+
+#### 6 Company Templates + Cross-References:
+- Company detail pages
+- Company listing pages
+- Company creation/editing forms
+- Company search interfaces
+- Company profile components
+- Cross-references in park/ride templates
+
+### 4. Test Coverage
+**Location**: `companies/tests.py`
+
+#### 429 Lines of Test Code:
+- Model validation tests
+- View functionality tests
+- Form validation tests
+- API endpoint tests
+- Integration tests with parks/rides
+- pghistory tracking tests
+
+### 5. Configuration & Settings
+**Locations**: Various configuration files
+
+#### Integration Points:
+- Django admin configuration
+- Search indexing configuration
+- Signal handlers
+- Middleware dependencies
+- Template context processors
+
+## pghistory Integration Complexity
+
+### Historical Data Tracking
+- Company changes tracked in pghistory tables
+- Historical relationships with parks/rides preserved
+- Migration must maintain historical data integrity
+- Complex data migration required for historical records
+
+### Risk Assessment
+- **Data Loss Risk**: HIGH - Historical tracking data could be lost
+- **Integrity Risk**: HIGH - Foreign key relationships in historical data
+- **Performance Risk**: MEDIUM - Large historical datasets to migrate
+
+## New Relationship Structure Analysis
+
+### Target Architecture
+```
+Rides → Parks (required, exists)
+Rides → Manufacturers (optional, rename current company relationship)
+Rides → Designers (optional, exists)
+Parks → Operators (required, replace Company.owner)
+Parks → PropertyOwners (optional, new concept)
+```
+
+### Key Relationship Changes
+1. **Company.owner → Operators**: Direct replacement for park ownership
+2. **Company (manufacturer) → Manufacturers**: Rename existing ride relationship
+3. **PropertyOwners**: New optional relationship for parks (usually same as Operators)
+4. **Designers**: Existing relationship, no changes required
+
+## Critical Migration Challenges
+
+### 1. Data Preservation
+- **300+ company records** need proper categorization
+- **Historical data** must be preserved and migrated
+- **Relationship integrity** must be maintained throughout
+
+### 2. Dependency Order
+- Models must be updated before views/templates
+- Foreign key relationships require careful sequencing
+- pghistory integration adds complexity to migration order
+
+### 3. Testing Requirements
+- **429 lines of tests** need updates
+- Integration tests across multiple apps
+- Historical data integrity verification
+
+### 4. URL Pattern Migration
+- **22 URL patterns** need updates or removal
+- Backward compatibility considerations
+- Search engine optimization impact
+
+## Risk Mitigation Requirements
+
+### Database Safety
+- **MANDATORY**: Full database backup before any migration steps
+- **MANDATORY**: Dry-run testing of all migration scripts
+- **MANDATORY**: Rollback procedures documented and tested
+
+### Testing Strategy
+- **Phase-by-phase testing** after each migration step
+- **Full test suite execution** before proceeding to next phase
+- **pghistory data integrity verification** at each checkpoint
+
+### Deployment Considerations
+- **Zero-downtime migration** strategy required
+- **Backward compatibility** during transition period
+- **Monitoring and alerting** for migration issues
+
+## Implementation Readiness Assessment
+
+### Prerequisites Complete ✅
+- [x] Comprehensive codebase analysis
+- [x] Dependency mapping
+- [x] Risk assessment
+- [x] Impact quantification
+
+### Next Phase Requirements
+- [ ] Detailed migration plan creation
+- [ ] Migration script development
+- [ ] Test environment setup
+- [ ] Backup and rollback procedures
+- [ ] Implementation timeline
+
+## Conclusion
+
+The company migration represents a **HIGH-RISK, HIGH-IMPACT** change affecting **300+ references** across the entire ThrillWiki codebase. The analysis confirms the migration is feasible but requires:
+
+1. **Meticulous Planning**: Detailed phase-by-phase implementation plan
+2. **Comprehensive Testing**: Full test coverage at each migration phase
+3. **Data Safety**: Robust backup and rollback procedures
+4. **Careful Sequencing**: Critical order of operations for safe migration
+
+**Recommendation**: Proceed to detailed migration planning phase with emphasis on data safety and comprehensive testing protocols.