Fix circular import by registering TicketStatusHistory before Ticket in models init to resolve SQLAlchemy mapper errors.

docs/ORGANIZATION_CODES.md

@@ -1,468 +0,0 @@
-# SwiftOps Organization Codes Implementation
-
-## Overview
-
-SwiftOps codes are unique, memorable identifiers for organizations (clients and contractors) that enable easy search and discovery in the platform.
-
-### Format
-
-**Pattern:** `[Initials(1-3)][Year(2)][Sequence(3)]`
-
-**Examples:**
-- `FWL25001` - FiberWorks Ltd (2025, sequence 1)
-- `TIL25002` - TechInstall Ltd (2025, sequence 2)
-- `ABC25001` - ABC Corporation (2025, sequence 1)
-- `M25001` - M Company (single letter name)
-
-**Length:** 6-8 characters (depending on name length)
-
-## Key Features
-
-1. **Uniqueness:** Codes are unique across ALL organizations (both clients and contractors)
-2. **Memorability:** Based on organization name initials for easy recall
-3. **Searchability:** Can search organizations by typing initials (e.g., "FWL" finds FiberWorks)
-4. **Year-aware:** Includes year suffix to organize chronologically
-5. **Sequential:** Auto-increments within same prefix+year combination
-
-## Code Generation Logic
-
-### Initials Extraction
-
-```python
-# Multi-word names: First letter of each word (max 3)
-"FiberWorks Ltd" → "FWL"
-"ABC Corp" → "ABC"
-
-# Single-word names: First N characters (max 3)
-"TechInstall" → "TEC"
-"M" → "M"
-```
-
-### Year Suffix
-
-- Takes last 2 digits of current year
-- Examples: 2025 → "25", 2026 → "26"
-
-### Sequence Number
-
-- 3-digit zero-padded number (001-999)
-- Finds next available sequence for given prefix+year
-- Checks both clients and contractors tables
-- Supports up to 999 organizations with same prefix per year
-
-## Implementation
-
-### Database Schema
-
-```sql
--- Added to both clients and contractors tables
-ALTER TABLE public.clients
-ADD COLUMN swiftops_code VARCHAR(10) NULL;
-
-ALTER TABLE public.contractors
-ADD COLUMN swiftops_code VARCHAR(10) NULL;
-
--- Unique indexes
-CREATE UNIQUE INDEX idx_clients_swiftops_code 
-ON public.clients(swiftops_code) WHERE swiftops_code IS NOT NULL;
-
-CREATE UNIQUE INDEX idx_contractors_swiftops_code 
-ON public.contractors(swiftops_code) WHERE swiftops_code IS NOT NULL;
-```
-
-### SQLAlchemy Models
-
-Both `Client` and `Contractor` models have:
-
-```python
-swiftops_code = Column(String(10), unique=True, nullable=True, index=True)
-```
-
-### API Changes
-
-#### Response Schemas
-
-All organization responses now include `swiftops_code`:
-
-- `ClientResponse`
-- `ContractorResponse`
-- `OrganizationPartner`
-
-#### Search Enhancement
-
-The `/api/v1/organizations/partners` endpoint now searches by both name AND code:
-
-```python
-# Users can search by typing organization name or code
-GET /api/v1/organizations/partners?search=FWL
-# Returns: FiberWorks Ltd (FWL25001)
-
-GET /api/v1/organizations/partners?search=FiberWorks
-# Same result
-```
-
-#### Auto-Generation on Create
-
-When creating new clients or contractors, codes are automatically generated if not provided:
-
-```python
-POST /api/v1/clients
-{
-    "name": "FiberWorks Ltd",
-    "industry": "Telecommunications"
-}
-
-# Response includes auto-generated code:
-{
-    "id": "...",
-    "name": "FiberWorks Ltd",
-    "swiftops_code": "FWL25001",  // ← Auto-generated
-    ...
-}
-```
-
-## Migration Process
-
-### Step 1: Run Database Migration
-
-```bash
-# Apply the migration (adds nullable columns with indexes)
-# Run this in Supabase SQL Editor:
-supabase/migrations/20250128000000_add_swiftops_code.sql
-```
-
-### Step 2: Populate Existing Organizations
-
-```bash
-# Generate codes for all existing organizations
-python scripts/populate_org_codes.py
-```
-
-Output:
-```
-Starting organization code population...
-------------------------------------------------------------
-
-Found 15 clients without codes
-✓ Client: FiberWorks Ltd                         -> FWL25001
-✓ Client: TechInstall Corporation                -> TIC25002
-...
-
-Found 22 contractors without codes
-✓ Contractor: FieldOps Kenya                     -> FOK25001
-✓ Contractor: InstallPro Services                -> IPS25002
-...
-
-✅ Code population completed successfully!
-```
-
-### Step 3: Verify Population
-
-```sql
--- Check for any organizations without codes
-SELECT name, swiftops_code FROM clients WHERE swiftops_code IS NULL;
-SELECT name, swiftops_code FROM contractors WHERE swiftops_code IS NULL;
-
--- Should return 0 rows
-```
-
-### Step 4: Make Field Required (Optional)
-
-Once all organizations have codes, you can make the field NOT NULL:
-
-```sql
-ALTER TABLE public.clients ALTER COLUMN swiftops_code SET NOT NULL;
-ALTER TABLE public.contractors ALTER COLUMN swiftops_code SET NOT NULL;
-```
-
-## Utility Functions
-
-### `generate_org_code(org_name: str, db: Session) -> str`
-
-Generates a unique code for an organization.
-
-```python
-from app.utils.org_code_generator import generate_org_code
-
-code = generate_org_code("FiberWorks Ltd", db)
-# Returns: "FWL25001"
-```
-
-### `is_code_available(code: str, db: Session) -> bool`
-
-Checks if a code is available (not in use).
-
-```python
-from app.utils.org_code_generator import is_code_available
-
-available = is_code_available("FWL25001", db)
-# Returns: False (already in use)
-```
-
-### `validate_org_code_format(code: str) -> bool`
-
-Validates code format.
-
-```python
-from app.utils.org_code_generator import validate_org_code_format
-
-valid = validate_org_code_format("FWL25001")  # True
-valid = validate_org_code_format("fwl25001")  # False (must be uppercase)
-valid = validate_org_code_format("FWL-25001") # False (no special chars)
-```
-
-## Code Collision Handling
-
-### What Happens if Initials Match?
-
-Organizations with same initials get sequential codes:
-
-```
-FiberWorks Ltd     → FWL25001
-Fiber World LLC    → FWL25002
-FW Logistics Inc   → FWL25003
-```
-
-### What if All 999 Slots Are Taken?
-
-The system raises a `ValueError` indicating exhaustion. This is unlikely in practice (would require 999 organizations with same initials in same year).
-
-## Use Cases
-
-### 1. Partner Discovery
-
-Frontend can show codes in organization lists:
-
-```
-Available Contractors:
-- FiberWorks Ltd (FWL25001)
-- TechInstall Corp (TIC25001)
-- FieldOps Kenya (FOK25001)
-```
-
-### 2. Quick Search
-
-Users can type initials to quickly find organizations:
-
-```
-Search: "FWL" → FiberWorks Ltd
-Search: "TIC" → TechInstall Corp
-Search: "FOK" → FieldOps Kenya
-```
-
-### 3. Project Creation
-
-When creating projects, display partner codes:
-
-```
-Select Client:
-- FiberWorks Ltd (FWL25001) - 5 active projects
-
-Select Contractor:
-- TechInstall Corp (TIC25001) - 12 active projects
-```
-
-### 4. External Communication
-
-Include codes in:
-- Invoices: "Invoice for project with FWL25001"
-- Reports: "Contractor performance: TIC25001"
-- Support tickets: "Issue with organization FWL25001"
-
-## Frontend Integration
-
-### Display Format
-
-Recommended display: `Name (CODE)`
-
-```jsx
-<div>
-  <span>{org.name}</span>
-  <span className="text-gray-500">({org.swiftops_code})</span>
-</div>
-```
-
-### Search Implementation
-
-```jsx
-// Search by name or code
-<SearchBar
-  placeholder="Search by name or SwiftOps code (e.g., FWL)"
-  onChange={(value) => fetchOrganizations({ search: value })}
-/>
-```
-
-### Partner Selection
-
-```jsx
-// Show code in dropdown
-<Select>
-  {partners.map(p => (
-    <option value={p.id}>
-      {p.name} ({p.swiftops_code})
-    </option>
-  ))}
-</Select>
-```
-
-## Testing
-
-### Unit Tests
-
-Test code generation:
-
-```python
-def test_generate_org_code():
-    code = generate_org_code("FiberWorks Ltd", db)
-    assert code.startswith("FWL")
-    assert len(code) == 8
-    assert code[-3:].isdigit()
-
-def test_code_uniqueness():
-    code1 = generate_org_code("FiberWorks Ltd", db)
-    code2 = generate_org_code("FiberWorks Ltd", db)
-    assert code1 != code2  # Different sequences
-```
-
-### Integration Tests
-
-Test endpoint:
-
-```python
-def test_create_client_generates_code():
-    response = client.post("/api/v1/clients", json={
-        "name": "Test Company",
-        "industry": "Tech"
-    })
-    assert response.status_code == 201
-    assert "swiftops_code" in response.json()
-    assert len(response.json()["swiftops_code"]) >= 6
-```
-
-## Monitoring
-
-### Metrics to Track
-
-1. **Code Generation Success Rate**
-   - Track failures to generate codes
-   - Alert if collision rate increases
-
-2. **Search Usage**
-   - Track how often users search by code vs name
-   - Optimize search if code search is popular
-
-3. **Code Uniqueness**
-   - Monitor prefix collision rates
-   - Plan for alternative formats if needed
-
-## Future Enhancements
-
-### 1. Custom Codes (Optional)
-
-Allow admins to customize their organization code:
-
-```python
-# Validation would ensure uniqueness
-PUT /api/v1/clients/{id}
-{
-    "swiftops_code": "FIBER01"  // Custom code
-}
-```
-
-### 2. Code Reservation
-
-Pre-reserve codes for known organizations:
-
-```sql
-INSERT INTO reserved_codes (code, org_name) 
-VALUES ('FWL25001', 'FiberWorks Ltd');
-```
-
-### 3. QR Code Integration
-
-Generate QR codes containing SwiftOps code for:
-- Asset tagging
-- Job site check-ins
-- Invoice scanning
-
-### 4. Code Analytics
-
-Dashboard showing:
-- Most searched codes
-- Code collision patterns
-- Yearly code generation trends
-
-## Troubleshooting
-
-### Problem: Code not generated on create
-
-**Solution:** Ensure code generation is called before `db.add()`:
-
-```python
-new_client = Client(**data)
-new_client.swiftops_code = generate_org_code(new_client.name, db)
-db.add(new_client)
-```
-
-### Problem: Duplicate codes
-
-**Solution:** Check unique index exists:
-
-```sql
-SELECT * FROM pg_indexes 
-WHERE tablename IN ('clients', 'contractors') 
-AND indexname LIKE '%swiftops_code%';
-```
-
-### Problem: Population script fails
-
-**Solution:** Run with transaction rollback on error:
-
-```python
-try:
-    # Generate codes
-    db.commit()
-except Exception as e:
-    db.rollback()
-    print(f"Error: {e}")
-```
-
-## Files Modified
-
-### Models
-- `src/app/models/client.py` - Added swiftops_code field
-- `src/app/models/contractor.py` - Added swiftops_code field
-
-### Schemas
-- `src/app/schemas/client.py` - Added swiftops_code to ClientBase, ClientUpdate
-- `src/app/schemas/contractor.py` - Added swiftops_code to ContractorBase, ContractorUpdate
-
-### API Endpoints
-- `src/app/api/v1/clients.py` - Auto-generate code on create
-- `src/app/api/v1/contractors.py` - Auto-generate code on create
-- `src/app/api/v1/organizations.py` - Added code to responses, search by code
-
-### Utilities
-- `src/app/utils/org_code_generator.py` - Code generation logic
-
-### Database
-- `supabase/migrations/20250128000000_add_swiftops_code.sql` - Migration
-
-### Scripts
-- `scripts/populate_org_codes.py` - Population script
-
-### Documentation
-- `docs/ORGANIZATION_CODES.md` - This file
-
-## Summary
-
-SwiftOps codes provide a memorable, searchable way to identify organizations in the system. The implementation:
-
-✅ Automatically generates codes on organization creation  
-✅ Supports searching by both name and code  
-✅ Ensures uniqueness across all organizations  
-✅ Handles existing organizations via migration script  
-✅ Uses memorable format based on organization names  
-✅ Scales to 999 organizations per prefix per year  
-
-The system is production-ready and requires only running the migration and population script to activate for existing organizations.

docs/ORGANIZATION_CODES_QUICK_REFERENCE.md

@@ -1,162 +0,0 @@
-# SwiftOps Codes - Quick Reference
-
-## Code Format
-
-```
-[Initials(1-3)][Year(2)][Sequence(3)]
-
-Examples:
-FWL25001 - FiberWorks Ltd
-TIC25002 - TechInstall Corp
-ABC25001 - ABC Corporation
-```
-
-## Deployment Steps
-
-### 1. Apply Migration
-
-```sql
--- Run in Supabase SQL Editor
-\i supabase/migrations/20250128000000_add_swiftops_code.sql
-```
-
-### 2. Populate Existing Organizations
-
-```bash
-# Set DATABASE_URL environment variable
-export DATABASE_URL="your-database-url"
-
-# Run population script
-python scripts/populate_org_codes.py
-```
-
-### 3. Verify (Optional)
-
-```sql
--- Check all have codes
-SELECT COUNT(*) FROM clients WHERE swiftops_code IS NULL;  -- Should be 0
-SELECT COUNT(*) FROM contractors WHERE swiftops_code IS NULL;  -- Should be 0
-```
-
-### 4. Make Required (Optional)
-
-```sql
--- Only after verification
-ALTER TABLE clients ALTER COLUMN swiftops_code SET NOT NULL;
-ALTER TABLE contractors ALTER COLUMN swiftops_code SET NOT NULL;
-```
-
-## API Usage
-
-### Search by Code
-
-```bash
-# Search organizations by name or code
-GET /api/v1/organizations/partners?search=FWL
-
-# Response includes swiftops_code
-{
-  "partners": [
-    {
-      "id": "...",
-      "name": "FiberWorks Ltd",
-      "swiftops_code": "FWL25001",
-      ...
-    }
-  ]
-}
-```
-
-### Create with Auto-Generated Code
-
-```bash
-# POST to create client or contractor
-POST /api/v1/clients
-{
-  "name": "New Company Ltd",
-  "industry": "Telecommunications"
-}
-
-# Response includes auto-generated code
-{
-  "id": "...",
-  "name": "New Company Ltd",
-  "swiftops_code": "NCL25001",  # Auto-generated
-  ...
-}
-```
-
-## Python Utility Functions
-
-```python
-from app.utils.org_code_generator import generate_org_code, is_code_available
-
-# Generate code
-code = generate_org_code("FiberWorks Ltd", db)  # "FWL25001"
-
-# Check availability
-available = is_code_available("FWL25002", db)  # True/False
-```
-
-## Frontend Display
-
-```jsx
-// Recommended format: Name (CODE)
-<div>
-  <span>{org.name}</span>
-  <span className="text-gray-500">({org.swiftops_code})</span>
-</div>
-
-// Example: FiberWorks Ltd (FWL25001)
-```
-
-## Troubleshooting
-
-| Issue | Solution |
-|-------|----------|
-| Code not generated on create | Ensure `generate_org_code()` called before `db.add()` |
-| Population script fails | Check DATABASE_URL is set correctly |
-| Duplicate codes | Verify unique index exists on swiftops_code |
-| Search not finding codes | Ensure search filter includes `swiftops_code.ilike()` |
-
-## Files Modified
-
-**Models:**
-- `src/app/models/client.py`
-- `src/app/models/contractor.py`
-
-**Schemas:**
-- `src/app/schemas/client.py`
-- `src/app/schemas/contractor.py`
-
-**Endpoints:**
-- `src/app/api/v1/clients.py`
-- `src/app/api/v1/contractors.py`
-- `src/app/api/v1/organizations.py`
-
-**Utilities:**
-- `src/app/utils/org_code_generator.py`
-
-**Database:**
-- `supabase/migrations/20250128000000_add_swiftops_code.sql`
-- `scripts/populate_org_codes.py`
-
-## Key Features
-
-✅ **Unique** - Across all organizations (clients + contractors)  
-✅ **Memorable** - Based on organization name initials  
-✅ **Searchable** - Type initials to find organizations  
-✅ **Auto-generated** - On organization creation  
-✅ **Year-aware** - Includes year suffix  
-✅ **Sequential** - Auto-increments within prefix  
-
-## Next Steps After Deployment
-
-1. Update frontend to display codes in organization lists
-2. Add code-based search to partner selection UI
-3. Include codes in invoices and reports
-4. Train users on searching by code (e.g., "FWL" for FiberWorks)
-
----
-
-**Full Documentation:** See `docs/ORGANIZATION_CODES.md`

docs/PROJECT_CREATION_FLOW.md

@@ -1,366 +0,0 @@
-# 🚀 PROJECT CREATION FLOW - Complete Guide
-
-## Current Implementation Status: ✅ FULLY WORKING
-
-Your intuition was **100% CORRECT**. The system already implements an **open marketplace model** without invitations!
-
----
-
-## How Client Admin Creates a Project
-
-### Step 1: Login as Client Admin
-```
-User: client_admin@company.com
-Role: client_admin
-Organization: Acme Telecom (client_id: xxx-xxx-xxx)
-```
-
-### Step 2: Discover Available Partners
-**NEW ENDPOINT (Just implemented):**
-```http
-GET /api/v1/organizations/partners
-```
-
-**What it returns:**
-- **For Client Admins**: List of ALL contractors on SwiftOps
-- **For Contractor Admins**: List of ALL clients on SwiftOps
-- Each with stats: active_projects_count, total_projects_count, competencies
-
-**Response example:**
-```json
-{
-  "partners": [
-    {
-      "id": "550e8400-e29b-41d4-a716-446655440000",
-      "name": "FiberWorks Ltd",
-      "type": "contractor",
-      "industry": "Telecommunications",
-      "competencies": ["FTTH Installation", "Fiber Splicing", "Network Testing"],
-      "is_active": true,
-      "active_projects_count": 5,
-      "total_projects_count": 23,
-      "main_email": "contact@fiberworks.com",
-      "main_phone": "+254712345678",
-      "contact_person": "John Doe"
-    },
-    {
-      "id": "660e8400-e29b-41d4-a716-446655440001",
-      "name": "NetworkPro Solutions",
-      "type": "contractor",
-      "industry": "Telecommunications",
-      "competencies": ["Fixed Wireless", "DSL", "Customer Support"],
-      "is_active": true,
-      "active_projects_count": 2,
-      "total_projects_count": 15,
-      "main_email": "info@networkpro.com",
-      "main_phone": "+254723456789",
-      "contact_person": "Jane Smith"
-    }
-  ],
-  "total": 2,
-  "user_role": "client_admin",
-  "user_organization_type": "client"
-}
-```
-
-**Filters available:**
-- `?is_active=true` - Only active organizations
-- `?industry=Telecommunications` - Filter by industry
-- `?search=Fiber` - Search by name
-- `?skip=0&limit=100` - Pagination
-
-### Step 3: View Partner Details (Optional)
-```http
-GET /api/v1/organizations/partners/{contractor_id}
-```
-
-Returns full details about the contractor, including:
-- Contact information
-- Service capabilities
-- Project history
-- Performance stats
-
-### Step 4: Create Project
-```http
-POST /api/v1/projects
-
-{
-  "title": "Nairobi West FTTH Rollout",
-  "client_id": "xxx-xxx-xxx",  // Your own client_id (auto-filled)
-  "contractor_id": "550e8400-e29b-41d4-a716-446655440000",  // Selected partner
-  "description": "Install fiber optic infrastructure in Nairobi West area",
-  "project_type": "installation",
-  "service_type": "ftth",
-  "budget": {
-    "materials": { "amount": 500000, "currency": "KES" },
-    "labor": { "amount": 300000, "currency": "KES" }
-  },
-  "start_date": "2025-02-01",
-  "end_date": "2025-04-30"
-}
-```
-
-**Backend validation:**
-- ✅ Client must be YOUR organization (enforced)
-- ✅ Contractor must exist and be active
-- ✅ No duplicate projects (same client+contractor+title)
-- ✅ Dates are valid (end >= start)
-
----
-
-## How Contractor Admin Creates a Project
-
-Same flow, but reversed:
-
-### Step 1: Login as Contractor Admin
-```
-User: contractor@fiberworks.com
-Role: contractor_admin
-Organization: FiberWorks Ltd (contractor_id: xxx-xxx-xxx)
-```
-
-### Step 2: Discover Available Clients
-```http
-GET /api/v1/organizations/partners
-```
-
-**Returns ALL clients on the platform** with their project history and contact info.
-
-### Step 3: Create Project
-```http
-POST /api/v1/projects
-
-{
-  "title": "Safaricom FTTH Maintenance Contract",
-  "client_id": "770e8400-e29b-41d4-a716-446655440002",  // Selected client
-  "contractor_id": "xxx-xxx-xxx",  // Your own contractor_id (auto-filled)
-  "description": "Ongoing maintenance and support for Safaricom FTTH network",
-  "project_type": "maintenance",
-  "service_type": "ftth"
-}
-```
-
----
-
-## Authorization Model
-
-### Who Can Create Projects?
-
-| Role | Can Create? | Restrictions |
-|------|-------------|--------------|
-| **platform_admin** | ✅ Yes | Can create ANY project (any client + any contractor) |
-| **client_admin** | ✅ Yes | Can ONLY create projects for THEIR OWN client |
-| **contractor_admin** | ✅ Yes | Can ONLY create projects for THEIR OWN contractor |
-| field_agent | ❌ No | Cannot create projects |
-| project_manager | ❌ No | Cannot create projects (only assigned to existing ones) |
-
-### Who Can See Which Organizations?
-
-| Role | Sees Clients? | Sees Contractors? |
-|------|---------------|-------------------|
-| **platform_admin** | ALL clients | ALL contractors |
-| **client_admin** | Only OWN client | ALL contractors ✅ |
-| **contractor_admin** | ALL clients ✅ | Only OWN contractor |
-
----
-
-## Why This "Open Marketplace" Model Makes Sense
-
-### ✅ Advantages:
-
-1. **No Gatekeeping**
-   - Client admin sees ALL available contractors
-   - Can immediately create project with any contractor
-   - No approval workflows or invitation delays
-
-2. **Discovery**
-   - Organizations can browse partners
-   - See project history and capabilities
-   - Make informed decisions
-
-3. **Self-Service Onboarding**
-   - If partner not on platform, invite them to subscribe
-   - No platform admin bottleneck
-   - Organic network growth
-
-4. **B2B Transparency**
-   - Organizations are businesses, not individuals
-   - Transparency builds trust
-   - Similar to Upwork, Procore, Buildertrend
-
-### ⚠️ Potential Concerns (And Why They Don't Matter):
-
-**"What if competitors see each other?"**
-- In B2B, this is normal. Contractors know who their competition is.
-- Clients benefit from transparency when choosing partners.
-
-**"What about privacy?"**
-- Organization details are public-facing anyway (website, social media)
-- We only show business contact info, not sensitive data
-- Similar to Yellow Pages or LinkedIn Company Pages
-
-**"Should we require approval?"**
-- NO. Approval slows down business.
-- If organization is on SwiftOps, they're already vetted.
-- Projects can have their own approval workflows if needed.
-
----
-
-## Alternative Models (Why They're NOT Better)
-
-### ❌ Invitation-Only Model
-```
-Client → Send invitation → Contractor → Accept → Create project
-```
-**Problems:**
-- Adds friction (2-3 day delay)
-- Requires contractor to be online and check email
-- Platform admin becomes bottleneck
-- Hurts user experience
-
-### ❌ Request-Approval Model
-```
-Client → Request project → Platform admin reviews → Approve → Create
-```
-**Problems:**
-- Platform admin becomes bottleneck
-- Doesn't scale beyond 10-20 projects/day
-- Kills the "self-service" value proposition
-
-### ✅ Current Open Marketplace (BEST)
-```
-Client → Browse contractors → Select → Create project (instant)
-```
-**Benefits:**
-- Instant project creation
-- Self-service
-- Scalable
-- Industry standard
-
----
-
-## Implementation Complete ✅
-
-### What Was Already There:
-1. ✅ Project creation endpoint with proper validation
-2. ✅ Authorization checks (client_admin/contractor_admin)
-3. ✅ Open visibility (clients see all contractors, vice versa)
-4. ✅ Duplicate project prevention
-5. ✅ Active organization validation
-
-### What I Just Added:
-1. ✅ `/api/v1/organizations/partners` - Unified partner discovery endpoint
-2. ✅ `/api/v1/organizations/partners/{id}` - Partner detail view
-3. ✅ Project statistics (active_projects_count, total_projects_count)
-4. ✅ Search and filter capabilities
-5. ✅ Proper response schemas with all needed info
-
----
-
-## Frontend Implementation Guide
-
-### Project Creation Form:
-
-```typescript
-// Step 1: Load available partners when form opens
-const loadPartners = async () => {
-  const response = await fetch('/api/v1/organizations/partners', {
-    headers: { 'Authorization': `Bearer ${token}` }
-  });
-  const data = await response.json();
-  
-  // data.partners = array of organizations
-  // data.user_organization_type = "client" or "contractor"
-  
-  return data;
-};
-
-// Step 2: Display partner selection dropdown
-<Select
-  label={data.user_organization_type === 'client' ? 'Select Contractor' : 'Select Client'}
-  options={data.partners.map(p => ({
-    value: p.id,
-    label: `${p.name} (${p.active_projects_count} active projects)`,
-    subtitle: p.industry,
-    badge: p.competencies?.join(', ')
-  }))}
-/>
-
-// Step 3: Create project
-const createProject = async (formData) => {
-  const response = await fetch('/api/v1/projects', {
-    method: 'POST',
-    headers: {
-      'Authorization': `Bearer ${token}`,
-      'Content-Type': 'application/json'
-    },
-    body: JSON.stringify({
-      title: formData.title,
-      client_id: userRole === 'client_admin' ? userOrgId : formData.selectedPartnerId,
-      contractor_id: userRole === 'contractor_admin' ? userOrgId : formData.selectedPartnerId,
-      description: formData.description,
-      // ... other fields
-    })
-  });
-  
-  if (response.ok) {
-    // Project created! Redirect to project details
-  }
-};
-```
-
-### Partner Discovery Page (Optional):
-
-```typescript
-// Browse all available partners with search
-<PartnersList>
-  <SearchBar placeholder="Search contractors by name or competency" />
-  <FilterBar>
-    <Filter type="industry" />
-    <Filter type="active_only" />
-  </FilterBar>
-  
-  {partners.map(partner => (
-    <PartnerCard
-      name={partner.name}
-      industry={partner.industry}
-      competencies={partner.competencies}
-      stats={{
-        activeProjects: partner.active_projects_count,
-        totalProjects: partner.total_projects_count
-      }}
-      contact={{
-        email: partner.main_email,
-        phone: partner.main_phone,
-        person: partner.contact_person
-      }}
-      onSelect={() => openProjectForm(partner.id)}
-      onViewDetails={() => navigate(`/partners/${partner.id}`)}
-    />
-  ))}
-</PartnersList>
-```
-
----
-
-## Summary
-
-### Your Intuition: ✅ CORRECT
-
-The "open marketplace without invitations" model is:
-- ✅ Already mostly implemented
-- �� The right approach for B2B collaboration
-- ✅ Scalable and self-service
-- ✅ Industry standard
-
-### What Changed:
-- Added unified `/organizations/partners` endpoint
-- Added project statistics to partner listings
-- Made partner discovery easier
-
-### What Stayed the Same:
-- Authorization rules (can only create for own org)
-- Project validation
-- Open visibility model
-
-**You can now create robust projects with full partner discovery!** 🎉

docs/TODO/NOTIFICATION_SYSTEM_REFACTOR.md

@@ -0,0 +1,166 @@
+# Notification System Refactor - TODO
+
+## Current State (MVP)
+
+**Problem:** Mixed sync/async code causing event loop errors. Services are sync but notification helpers are async.
+
+**Temporary Solution:** Removed notification calls entirely, just logging "notification queued".
+
+**Limitations:**
+- No actual notifications sent
+- Lost on server restart
+- No retries on failure
+- Runs in web worker (blocks requests)
+- Tight coupling (endpoints know about notifications)
+
+## Proper Implementation Plan
+
+### Phase 1: Sync Notification Wrapper (Quick Fix)
+
+**Goal:** Get notifications working without full async refactor.
+
+**Implementation:**
+```python
+# app/background/notifications.py
+from fastapi import BackgroundTasks
+
+def notify_ticket_assigned(db, ticket_id, agent_id, background_tasks: BackgroundTasks):
+    """Sync wrapper - creates notification and queues sending"""
+    # 1. Create notification record (sync DB insert)
+    notification = NotificationService().create_notification_sync(...)
+    
+    # 2. Queue async sending
+    background_tasks.add_task(send_notification_async, notification.id)
+```
+
+**Changes needed:**
+- Create sync version of `create_notification()`
+- Add `BackgroundTasks` parameter to all endpoints
+- Update services to accept `background_tasks` parameter
+- Call notification wrapper from services
+
+**Pros:** Works now, minimal changes
+**Cons:** Still not production-ready, lost on crash
+
+### Phase 2: Full Async/Await (Proper Fix)
+
+**Goal:** Make everything async for proper async notification handling.
+
+**Changes:**
+```python
+# All services become async
+class TicketAssignmentService:
+    async def self_assign_ticket(self, ...):  # Add async
+        assignment = await create_assignment()  # Add await
+        await NotificationHelper.notify_ticket_assigned(...)  # Works now
+        return assignment
+
+# All endpoints become async
+@router.post("/tickets/{id}/self-assign")
+async def self_assign(...):  # Add async
+    assignment = await service.self_assign_ticket(...)  # Add await
+    return assignment
+```
+
+**Migration steps:**
+1. Convert database operations to async (use `asyncpg` or SQLAlchemy async)
+2. Convert all service methods to `async def`
+3. Convert all endpoints to `async def`
+4. Add `await` to all async calls
+5. Test thoroughly (async bugs are subtle)
+
+**Pros:** Proper async, notifications work correctly
+**Cons:** Large refactor, risky, time-consuming
+
+### Phase 3: Celery for Critical Tasks (Production)
+
+**Goal:** Reliable, persistent, retriable background tasks.
+
+**Setup:**
+```bash
+pip install celery redis
+```
+
+**Implementation:**
+```python
+# celery_app/celery.py
+from celery import Celery
+
+celery_app = Celery('swiftops', broker='redis://localhost:6379/0')
+
+# celery_app/tasks/notifications.py
+@celery_app.task(bind=True, max_retries=3)
+def send_notification(self, notification_id):
+    try:
+        # Send notification
+        pass
+    except Exception as e:
+        raise self.retry(exc=e, countdown=60)
+
+# In service
+from celery_app.tasks.notifications import send_notification
+
+def self_assign_ticket(self, ...):
+    assignment = create_assignment()
+    notification = create_notification_record(...)
+    send_notification.delay(notification.id)  # Queue in Celery
+    return assignment
+```
+
+**Run:**
+```bash
+# Terminal 1: Web server
+uvicorn app.main:app
+
+# Terminal 2: Celery worker
+celery -A celery_app worker --loglevel=info
+```
+
+**Pros:** Persistent, retriable, scalable, monitoring
+**Cons:** Extra process to manage, more complexity
+
+### Phase 4: Event-Driven Architecture (Scale)
+
+**Goal:** Decouple services from notifications completely.
+
+**Pattern:**
+```python
+# Services emit events
+event_bus.emit(TicketAssignedEvent(ticket_id, agent_id))
+
+# Handlers react
+@event_bus.on(TicketAssignedEvent)
+def on_ticket_assigned(event):
+    send_notification.delay(event.ticket_id, event.agent_id)
+    update_analytics(event)
+    log_audit_trail(event)
+```
+
+**Benefits:** Clean separation, easy to add new reactions, testable
+
+## Recommendation
+
+**Now:** Skip Phase 1, go straight to Phase 3 (Celery) when you implement notifications properly.
+
+**Why skip Phase 1?** It's a half-measure that you'll throw away anyway. Better to do it right once.
+
+**When to do it:** When you implement payroll (needs Celery anyway), add notifications at same time.
+
+## Files to Update (Phase 3)
+
+1. Create `celery_app/celery.py` - Celery config
+2. Create `celery_app/tasks/notifications.py` - Notification tasks
+3. Update `src/app/services/ticket_assignment_service.py` - Call Celery tasks
+4. Update `src/app/services/notification_service.py` - Add sync create method
+5. Update `requirements.txt` - Add celery, redis
+6. Update deployment - Run celery worker process
+
+## Testing Checklist
+
+- [ ] Notifications sent on ticket assignment
+- [ ] Notifications sent on inventory distribution
+- [ ] Notifications sent on bulk sales order promotion
+- [ ] Failed notifications retry automatically
+- [ ] Server restart doesn't lose queued notifications
+- [ ] Can monitor notification queue status
+- [ ] Can manually retry failed notifications

docs/devlogs/browser/browserconsole.txt

@@ -1,12 +1,95 @@
-index-CJi_XLkH.js:583 ℹ️ [05:58:31] [AUTH] Token expired, attempting refresh
-index-CJi_XLkH.js:583 ℹ️ [05:58:35] [AUTH] Token refreshed successfully
-index-CJi_XLkH.js:583 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/me
-index-CJi_XLkH.js:583 GET https://kamau1-swiftops-backend.hf.space/api/v1/auth/me → 200 (845ms)
-index-CJi_XLkH.js:583 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/tickets/1f807cf8-f139-421b-86e3-38c2f8bc7070/detail
-index-CJi_XLkH.js:583 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/me/preferences
-index-CJi_XLkH.js:583 GET https://kamau1-swiftops-backend.hf.space/api/v1/auth/me/preferences → 200 (931ms)
-kamau1-swiftops-backend.hf.space/api/v1/tickets/1f807cf8-f139-421b-86e3-38c2f8bc7070/detail:1  Failed to load resource: the server responded with a status of 500 ()
-index-CJi_XLkH.js:583 GET https://kamau1-swiftops-backend.hf.space/api/v1/tickets/1f807cf8-f139-421b-86e3-38c2f8bc7070/detail → 500 (972ms)
-index-CJi_XLkH.js:583 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/tickets/1f807cf8-f139-421b-86e3-38c2f8bc7070/detail
-kamau1-swiftops-backend.hf.space/api/v1/tickets/1f807cf8-f139-421b-86e3-38c2f8bc7070/detail:1  Failed to load resource: the server responded with a status of 500 ()
-index-CJi_XLkH.js:583 GET https://kamau1-swiftops-backend.hf.space/api/v1/tickets/1f807cf8-f139-421b-86e3-38c2f8bc7070/detail → 500 (1.11s)
+chunk-276SZO74.js?v=c40a0948:21551 Download the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
+react-router-dom.js?v=c40a0948:4393 ⚠️ React Router Future Flag Warning: React Router will begin wrapping state updates in `React.startTransition` in v7. You can use the `v7_startTransition` future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_starttransition.
+warnOnce @ react-router-dom.js?v=c40a0948:4393
+logDeprecation @ react-router-dom.js?v=c40a0948:4396
+logV6DeprecationWarnings @ react-router-dom.js?v=c40a0948:4399
+(anonymous) @ react-router-dom.js?v=c40a0948:5271
+commitHookEffectListMount @ chunk-276SZO74.js?v=c40a0948:16915
+commitPassiveMountOnFiber @ chunk-276SZO74.js?v=c40a0948:18156
+commitPassiveMountEffects_complete @ chunk-276SZO74.js?v=c40a0948:18129
+commitPassiveMountEffects_begin @ chunk-276SZO74.js?v=c40a0948:18119
+commitPassiveMountEffects @ chunk-276SZO74.js?v=c40a0948:18109
+flushPassiveEffectsImpl @ chunk-276SZO74.js?v=c40a0948:19490
+flushPassiveEffects @ chunk-276SZO74.js?v=c40a0948:19447
+(anonymous) @ chunk-276SZO74.js?v=c40a0948:19328
+workLoop @ chunk-276SZO74.js?v=c40a0948:197
+flushWork @ chunk-276SZO74.js?v=c40a0948:176
+performWorkUntilDeadline @ chunk-276SZO74.js?v=c40a0948:384
+react-router-dom.js?v=c40a0948:4393 ⚠️ React Router Future Flag Warning: Relative route resolution within Splat routes is changing in v7. You can use the `v7_relativeSplatPath` future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_relativesplatpath.
+warnOnce @ react-router-dom.js?v=c40a0948:4393
+logDeprecation @ react-router-dom.js?v=c40a0948:4396
+logV6DeprecationWarnings @ react-router-dom.js?v=c40a0948:4402
+(anonymous) @ react-router-dom.js?v=c40a0948:5271
+commitHookEffectListMount @ chunk-276SZO74.js?v=c40a0948:16915
+commitPassiveMountOnFiber @ chunk-276SZO74.js?v=c40a0948:18156
+commitPassiveMountEffects_complete @ chunk-276SZO74.js?v=c40a0948:18129
+commitPassiveMountEffects_begin @ chunk-276SZO74.js?v=c40a0948:18119
+commitPassiveMountEffects @ chunk-276SZO74.js?v=c40a0948:18109
+flushPassiveEffectsImpl @ chunk-276SZO74.js?v=c40a0948:19490
+flushPassiveEffects @ chunk-276SZO74.js?v=c40a0948:19447
+(anonymous) @ chunk-276SZO74.js?v=c40a0948:19328
+workLoop @ chunk-276SZO74.js?v=c40a0948:197
+flushWork @ chunk-276SZO74.js?v=c40a0948:176
+performWorkUntilDeadline @ chunk-276SZO74.js?v=c40a0948:384
+core.ts:117 ℹ️ [09:56:24] [AUTH] Login attempt {email: 'viyisa8151@feralrex.com'}
+core.ts:167 %cPOST%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/login
+auth.service.ts:152  POST https://kamau1-swiftops-backend.hf.space/api/v1/auth/login 401 (Unauthorized)
+login @ auth.service.ts:152
+handleSubmit @ LoginPage.tsx:47
+callCallback2 @ chunk-276SZO74.js?v=c40a0948:3674
+invokeGuardedCallbackDev @ chunk-276SZO74.js?v=c40a0948:3699
+invokeGuardedCallback @ chunk-276SZO74.js?v=c40a0948:3733
+invokeGuardedCallbackAndCatchFirstError @ chunk-276SZO74.js?v=c40a0948:3736
+executeDispatch @ chunk-276SZO74.js?v=c40a0948:7014
+processDispatchQueueItemsInOrder @ chunk-276SZO74.js?v=c40a0948:7034
+processDispatchQueue @ chunk-276SZO74.js?v=c40a0948:7043
+dispatchEventsForPlugins @ chunk-276SZO74.js?v=c40a0948:7051
+(anonymous) @ chunk-276SZO74.js?v=c40a0948:7174
+batchedUpdates$1 @ chunk-276SZO74.js?v=c40a0948:18913
+batchedUpdates @ chunk-276SZO74.js?v=c40a0948:3579
+dispatchEventForPluginEventSystem @ chunk-276SZO74.js?v=c40a0948:7173
+dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-276SZO74.js?v=c40a0948:5478
+dispatchEvent @ chunk-276SZO74.js?v=c40a0948:5472
+dispatchDiscreteEvent @ chunk-276SZO74.js?v=c40a0948:5449
+core.ts:167 POST https://kamau1-swiftops-backend.hf.space/api/v1/auth/login → 401 (1.74s)
+core.ts:117 ❌ [09:56:26] [AUTH] Login failed {email: 'viyisa8151@feralrex.com', error: {…}}
+log @ core.ts:117
+error @ core.ts:157
+login @ auth.service.ts:164
+await in login
+handleSubmit @ LoginPage.tsx:47
+callCallback2 @ chunk-276SZO74.js?v=c40a0948:3674
+invokeGuardedCallbackDev @ chunk-276SZO74.js?v=c40a0948:3699
+invokeGuardedCallback @ chunk-276SZO74.js?v=c40a0948:3733
+invokeGuardedCallbackAndCatchFirstError @ chunk-276SZO74.js?v=c40a0948:3736
+executeDispatch @ chunk-276SZO74.js?v=c40a0948:7014
+processDispatchQueueItemsInOrder @ chunk-276SZO74.js?v=c40a0948:7034
+processDispatchQueue @ chunk-276SZO74.js?v=c40a0948:7043
+dispatchEventsForPlugins @ chunk-276SZO74.js?v=c40a0948:7051
+(anonymous) @ chunk-276SZO74.js?v=c40a0948:7174
+batchedUpdates$1 @ chunk-276SZO74.js?v=c40a0948:18913
+batchedUpdates @ chunk-276SZO74.js?v=c40a0948:3579
+dispatchEventForPluginEventSystem @ chunk-276SZO74.js?v=c40a0948:7173
+dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-276SZO74.js?v=c40a0948:5478
+dispatchEvent @ chunk-276SZO74.js?v=c40a0948:5472
+dispatchDiscreteEvent @ chunk-276SZO74.js?v=c40a0948:5449
+LoginPage.tsx:55 Login error: Error: Incorrect email or password
+    at AuthService.login (auth.service.ts:163:21)
+    at async handleSubmit (LoginPage.tsx:47:7)
+handleSubmit @ LoginPage.tsx:55
+await in handleSubmit
+callCallback2 @ chunk-276SZO74.js?v=c40a0948:3674
+invokeGuardedCallbackDev @ chunk-276SZO74.js?v=c40a0948:3699
+invokeGuardedCallback @ chunk-276SZO74.js?v=c40a0948:3733
+invokeGuardedCallbackAndCatchFirstError @ chunk-276SZO74.js?v=c40a0948:3736
+executeDispatch @ chunk-276SZO74.js?v=c40a0948:7014
+processDispatchQueueItemsInOrder @ chunk-276SZO74.js?v=c40a0948:7034
+processDispatchQueue @ chunk-276SZO74.js?v=c40a0948:7043
+dispatchEventsForPlugins @ chunk-276SZO74.js?v=c40a0948:7051
+(anonymous) @ chunk-276SZO74.js?v=c40a0948:7174
+batchedUpdates$1 @ chunk-276SZO74.js?v=c40a0948:18913
+batchedUpdates @ chunk-276SZO74.js?v=c40a0948:3579
+dispatchEventForPluginEventSystem @ chunk-276SZO74.js?v=c40a0948:7173
+dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-276SZO74.js?v=c40a0948:5478
+dispatchEvent @ chunk-276SZO74.js?v=c40a0948:5472
+dispatchDiscreteEvent @ chunk-276SZO74.js?v=c40a0948:5449

docs/devlogs/server/runtimeerror.txt

@@ -1,58 +1,65 @@
-===== Application Startup at 2025-11-28 09:27:13 =====
+===== Application Startup at 2025-11-28 09:42:05 =====
 
-INFO:     Started server process [7]
+INFO:     Started server process [6]
 INFO:     Waiting for application startup.
-INFO: 2025-11-28T09:27:27 - app.main: ============================================================
-INFO: 2025-11-28T09:27:27 - app.main: 🚀 SwiftOps API v1.0.0 | PRODUCTION
-INFO: 2025-11-28T09:27:27 - app.main: 📊 Dashboard: Enabled
-INFO: 2025-11-28T09:27:27 - app.main: ============================================================
-INFO: 2025-11-28T09:27:27 - app.main: 📦 Database:
-INFO: 2025-11-28T09:27:28 - app.main:    ✓ Connected | 44 tables | 6 users
-INFO: 2025-11-28T09:27:28 - app.main: 💾 Cache & Sessions:
-INFO: 2025-11-28T09:27:29 - app.services.otp_service: ✅ OTP Service initialized with Redis storage
-INFO: 2025-11-28T09:27:29 - app.main:    ✓ Redis: Connected
-INFO: 2025-11-28T09:27:29 - app.main: 🔌 External Services:
-INFO: 2025-11-28T09:27:30 - app.main:    ✓ Cloudinary: Connected
-INFO: 2025-11-28T09:27:30 - app.main:    ✓ Resend: Configured
-INFO: 2025-11-28T09:27:30 - app.main:    ○ WASender: Failed
-INFO: 2025-11-28T09:27:30 - app.main:    ✓ Supabase: Connected | 6 buckets
-INFO: 2025-11-28T09:27:30 - app.main: ============================================================
-INFO: 2025-11-28T09:27:30 - app.main: ✅ Startup complete | Ready to serve requests
-INFO: 2025-11-28T09:27:30 - app.main: ============================================================
+INFO: 2025-11-28T09:42:30 - app.main: ============================================================
+INFO: 2025-11-28T09:42:30 - app.main: 🚀 SwiftOps API v1.0.0 | PRODUCTION
+INFO: 2025-11-28T09:42:30 - app.main: 📊 Dashboard: Enabled
+INFO: 2025-11-28T09:42:30 - app.main: ============================================================
+INFO: 2025-11-28T09:42:30 - app.main: 📦 Database:
+INFO: 2025-11-28T09:42:31 - app.main:    ✓ Connected | 44 tables | 6 users
+INFO: 2025-11-28T09:42:31 - app.main: 💾 Cache & Sessions:
+INFO: 2025-11-28T09:42:32 - app.services.otp_service: ✅ OTP Service initialized with Redis storage
+INFO: 2025-11-28T09:42:32 - app.main:    ✓ Redis: Connected
+INFO: 2025-11-28T09:42:32 - app.main: 🔌 External Services:
+INFO: 2025-11-28T09:42:33 - app.main:    ✓ Cloudinary: Connected
+INFO: 2025-11-28T09:42:33 - app.main:    ✓ Resend: Configured
+INFO: 2025-11-28T09:42:33 - app.main:    ○ WASender: Failed
+INFO: 2025-11-28T09:42:33 - app.main:    ✓ Supabase: Connected | 6 buckets
+INFO: 2025-11-28T09:42:33 - app.main: ============================================================
+INFO: 2025-11-28T09:42:33 - app.main: ✅ Startup complete | Ready to serve requests
+INFO: 2025-11-28T09:42:33 - app.main: ============================================================
 INFO:     Application startup complete.
 INFO:     Uvicorn running on http://0.0.0.0:7860 (Press CTRL+C to quit)
-INFO:     10.16.6.70:2924 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.6.70:2924 - "GET /?logs=container HTTP/1.1" 200 OK
-INFO:     10.16.34.155:6801 - "GET /health HTTP/1.1" 200 OK
-INFO: 2025-11-28T09:27:38 - app.api.deps: Checking active user: 43b778b0-2062-4724-abbb-916a4835a9b0, is_active: True, type: <class 'bool'>
-INFO: 2025-11-28T09:27:38 - app.api.deps: User 43b778b0-2062-4724-abbb-916a4835a9b0 is active - proceeding
-INFO:     10.16.18.114:11421 - "GET /api/v1/auth/me HTTP/1.1" 200 OK
-INFO: 2025-11-28T09:27:38 - app.api.deps: Checking active user: 43b778b0-2062-4724-abbb-916a4835a9b0, is_active: True, type: <class 'bool'>
-INFO: 2025-11-28T09:27:38 - app.api.deps: User 43b778b0-2062-4724-abbb-916a4835a9b0 is active - proceeding
-INFO:     10.16.18.114:11421 - "GET /api/v1/auth/me/preferences HTTP/1.1" 200 OK
-INFO: 2025-11-28T09:27:38 - app.api.deps: Checking active user: 43b778b0-2062-4724-abbb-916a4835a9b0, is_active: True, type: <class 'bool'>
-INFO: 2025-11-28T09:27:38 - app.api.deps: User 43b778b0-2062-4724-abbb-916a4835a9b0 is active - proceeding
-INFO:     10.16.11.176:30663 - "GET /api/v1/auth/me/preferences/available-apps HTTP/1.1" 200 OK
-INFO:     10.16.11.176:49895 - "GET /api/v1/tickets/8f08ad14-df8b-4780-84e7-0d45e133f2a6/detail HTTP/1.1" 200 OK
-ERROR: 2025-11-28T09:27:42 - app.services.ticket_assignment_service: Failed to send self-assignment notification: no running event loop
-/app/src/app/services/ticket_assignment_service.py:437: RuntimeWarning: coroutine 'NotificationHelper.notify_ticket_status_changed' was never awaited
-  logger.error(f"Failed to send self-assignment notification: {str(e)}")
-RuntimeWarning: Enable tracemalloc to get the object allocation traceback
-INFO:     10.16.6.70:17030 - "POST /api/v1/ticket-assignments/tickets/8f08ad14-df8b-4780-84e7-0d45e133f2a6/self-assign HTTP/1.1" 201 Created
-INFO:     10.16.6.70:17030 - "GET /api/v1/tickets/8f08ad14-df8b-4780-84e7-0d45e133f2a6/detail HTTP/1.1" 200 OK
-INFO:     10.16.11.176:23737 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.11.176:45766 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.34.155:20217 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.6.70:34100 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.34.155:41867 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.6.70:1574 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.11.176:16400 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.11.176:63121 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.34.155:62014 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.25.209:22027 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.18.114:26652 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.18.114:29820 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.25.209:44298 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.18.114:22934 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.6.70:44658 - "GET /health HTTP/1.1" 200 OK
-INFO:     10.16.18.114:28198 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:5079 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:60771 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:15030 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:52821 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:34619 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:34619 - "GET /health HTTP/1.1" 200 OK
+INFO: 2025-11-28T09:45:12 - app.core.supabase_auth: Session refreshed successfully
+ERROR: 2025-11-28T09:45:12 - app.api.v1.auth: ❌ Token refresh error: When initializing mapper Mapper[Ticket(tickets)], expression 'TicketStatusHistory' failed to locate a name ('TicketStatusHistory'). If this is a class name, consider adding this relationship() to the <class 'app.models.ticket.Ticket'> class after both dependent classes have been defined.
+INFO:     10.16.11.176:26415 - "POST /api/v1/auth/refresh-token HTTP/1.1" 401 Unauthorized
+INFO:     10.16.6.70:60338 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:30463 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:52829 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:60696 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.18.114:56609 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:4192 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:2023 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:27097 - "GET /health HTTP/1.1" 200 OK
+INFO: 2025-11-28T09:48:41 - app.core.supabase_auth: Session refreshed successfully
+ERROR: 2025-11-28T09:48:41 - app.api.v1.auth: ❌ Token refresh error: One or more mappers failed to initialize - can't proceed with initialization of other mappers. Triggering mapper: 'Mapper[Ticket(tickets)]'. Original exception was: When initializing mapper Mapper[Ticket(tickets)], expression 'TicketStatusHistory' failed to locate a name ('TicketStatusHistory'). If this is a class name, consider adding this relationship() to the <class 'app.models.ticket.Ticket'> class after both dependent classes have been defined.
+INFO:     10.16.34.155:59759 - "POST /api/v1/auth/refresh-token HTTP/1.1" 401 Unauthorized
+INFO:     10.16.11.176:9673 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:9673 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.18.114:33528 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:53346 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:52356 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:32440 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:25171 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:25171 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.34.155:47092 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:8190 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.0.39:65512 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.0.39:10423 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.18.114:32065 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.18.114:9598 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:17205 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.11.176:27035 - "GET /health HTTP/1.1" 200 OK
+INFO:     10.16.6.70:62059 - "GET /health HTTP/1.1" 200 OK
+INFO: 2025-11-28T09:56:23 - app.core.supabase_auth: User signed in successfully: viyisa8151@feralrex.com
+ERROR: 2025-11-28T09:56:23 - app.api.v1.auth: Login error: One or more mappers failed to initialize - can't proceed with initialization of other mappers. Triggering mapper: 'Mapper[Ticket(tickets)]'. Original exception was: When initializing mapper Mapper[Ticket(tickets)], expression 'TicketStatusHistory' failed to locate a name ('TicketStatusHistory'). If this is a class name, consider adding this relationship() to the <class 'app.models.ticket.Ticket'> class after both dependent classes have been defined.
+ERROR: 2025-11-28T09:56:23 - app.services.audit_service: Failed to create audit log: One or more mappers failed to initialize - can't proceed with initialization of other mappers. Triggering mapper: 'Mapper[Ticket(tickets)]'. Original exception was: When initializing mapper Mapper[Ticket(tickets)], expression 'TicketStatusHistory' failed to locate a name ('TicketStatusHistory'). If this is a class name, consider adding this relationship() to the <class 'app.models.ticket.Ticket'> class after both dependent classes have been defined.
+INFO:     10.16.18.114:33294 - "POST /api/v1/auth/login HTTP/1.1" 401 Unauthorized
+ 

src/app/models/__init__.py

@@ -44,6 +44,7 @@ from app.models.ticket_expense import TicketExpense
 from app.models.ticket_image import TicketImage
 from app.models.ticket_progress_report import TicketProgressReport
 from app.models.ticket_incident_report import TicketIncidentReport
+from app.models.ticket_status_history import TicketStatusHistory
 from app.models.ticket import Ticket
 from app.models.ticket_assignment import TicketAssignment
 
@@ -109,6 +110,7 @@ __all__ = [
     "TicketImage",
     "TicketProgressReport",
     "TicketIncidentReport",
+    "TicketStatusHistory",
     
     # Incidents
     "Incident",