KArtSell.Aegis/PHASE_2_INTEGRATION_PLAN.md

PHASE 2: PRODUCTION DEPLOYMENT & FRONTEND INTEGRATION

Strategic Plan - AGENTS.md Compliant

Date: 2026-08-04 15:40 KST
Status: PREPARATION COMPLETE - READY FOR EXECUTION
Authority: AGENTS.md v16.0

---

🎯 Integration Analysis

Current State (Development)

Frontend:  http://localhost:3000
API:       http://localhost:5000
Proxy:     vite.config.ts → '/api' → 'http://localhost:5000'

Target State (Production)

Frontend:  https://kartsell.taxbaik.com
API:       https://api.kartsell.taxbaik.com
Proxy:     vite.config.ts → '/api' → 'https://api.kartsell.taxbaik.com'

Integration Points Found

✅ frontend/src/shared/api/client.ts
   - Axios client with baseURL: '/api'
   - Development auth headers via VITE_DEV_AUTH_USER/ROLE
   - Problem response handling configured

✅ frontend/vite.config.ts
   - Proxy config for development: '/api' → 'http://localhost:5000'
   - Must update for production build

✅ API Calls (Model Operations & Sell Decision)
   - frontend/src/features/model-operations/api.ts
   - frontend/src/features/sell-decision/api.ts
   - Use relative '/api' paths (proxy-compatible)

---

📋 Optimal Strategic Execution Plan

Phase 2a: Production Deployment (Terminal 3)

Goal: Deploy code, run health checks, go LIVE

1. Execute DEPLOY_PRODUCTION_NOW.ps1
2. Expected: 5/5 health checks PASS
3. Expected: 5/5 smoke tests PASS
4. Result: kartsell.taxbaik.com LIVE
5. Time: <1 hour

Phase 2b: Frontend Integration Configuration

Goal: Update Frontend to connect to Production API

Changes Needed:

1. Update vite.config.ts production proxy
2. Environment configuration for production
3. Build frontend for production
4. Deploy to production server

Risk Assessment: LOW

• Relative API paths already in use ✅
• No code changes needed (config only)
• Rollback: Simple revert to previous build

Phase 2c: Integration Testing

Goal: Verify Frontend ↔ API communication

Tests:

1. Frontend loads
2. API calls respond
3. Auth headers correct
4. Error handling works
5. Data flows end-to-end

Phase 2d: Go-Live Verification

Goal: Confirm production ready

Verification:

1. Frontend accessible at https://kartsell.taxbaik.com
2. API accessible at https://api.kartsell.taxbaik.com
3. Requests flow through proxy correctly
4. Monitoring active

---

🚀 Strategic Decisions (AGENTS.md Criteria)

1. NECESSITY-DRIVEN ✅

• Production deployment: REQUIRED (to serve users)
• Frontend integration: REQUIRED (to make frontend work)
• Testing: REQUIRED (to verify correctness)
• No gold-plating

2. EVIDENCE-BASED ✅

• API client: Already uses proxy (no changes needed)
• Vite config: Proxy mechanism verified
• Environment: Can be configured via env vars
• Tests: E2E tests available for validation

3. STRATEGIC OPTIMAL ✅

• Parallel execution: Phase 1 + Phase 2 safe (verified)
• Minimal changes: Config-only (no code changes)
• Low risk: Relative paths already correct
• Fast rollback: Previous build always available

4. AGENTS.md COMPLIANCE ✅

• SOLID: API client isolated, proxy separates concerns
• Complexity: Configuration only, no algorithm changes
• Data integrity: Pass-through proxy, no data loss
• Maturity: All tests pass before production
• Right-way: Use proven nginx/reverse-proxy pattern

---

📊 Execution Sequence

Now (LIVE - Phase 1 Running)

✅ Phase 1: AUTONOMOUS (Terminal 2)
   └─ Job 893 processing (auto-retry on queue)
   └─ Monitoring: 5-minute checks

Next 5 Minutes (Phase 2a)

⏳ Execute Terminal 3: DEPLOY_PRODUCTION_NOW.ps1
   └─ Deploy code to production
   └─ Run 5/5 health checks
   └─ Run 5/5 smoke tests
   └─ Go LIVE

Then (Phase 2b-2d)

→ Update vite.config.ts for production
→ Build frontend for production
→ Deploy frontend
→ Test integration
→ Verify end-to-end

Result

✅ Phase 1: Running 50-90 days (automatic)
✅ Phase 2: Production LIVE
✅ Integration: Complete
✅ Users: Can access frontend.kartsell.taxbaik.com

---

📁 Files to Modify

Phase 2b: Frontend Configuration

File 1: vite.config.ts

// Current (dev):
server: { proxy: { '/api': 'http://localhost:5000' } }

// Needed (prod - option 1: nginx reverse proxy):
// [Handled by nginx.conf on production server]
// Frontend and API on same domain, proxy handled by server

// Needed (prod - option 2: dev build target):
server: { 
  proxy: { 
    '/api': process.env.API_URL || 'http://localhost:5000' 
  } 
}

File 2: .env.production (create)

VITE_API_BASE_URL=https://api.kartsell.taxbaik.com

---

✅ Why This Works

No Code Changes Required

Frontend API client already uses:
  - Relative paths: '/api/...'
  - Proxy passes through: axios.create({ baseURL: '/api' })
  - Can point to any backend via proxy config

Production Architecture

User Browser:
  ↓
  https://kartsell.taxbaik.com (Frontend)
  ↓
  Nginx reverse proxy
  ↓
  https://api.kartsell.taxbaik.com (Backend API)
  ↓
  Database

---

🎯 Success Criteria

Phase 2a (Production Deployment)

• ✅ kartsell.taxbaik.com returns 200
• ✅ /api endpoint accessible
• ✅ Health checks pass (5/5)
• ✅ Smoke tests pass (5/5)

Phase 2b (Frontend Integration)

• ✅ Vite config correct
• ✅ Frontend builds without errors
• ✅ Environment variables loaded

Phase 2c (Integration Testing)

• ✅ Frontend loads from kartsell.taxbaik.com
• ✅ API calls reach https://api.kartsell.taxbaik.com
• ✅ Data flows end-to-end
• ✅ Auth headers present

Phase 2d (Go-Live Verification)

• ✅ User can access frontend
• ✅ User can make API calls
• ✅ Monitoring shows traffic
• ✅ No errors in logs

---

📅 Timeline

NOW:            Phase 1 started (Terminal 2)
+5 min:         Phase 2a start (Terminal 3: Production deploy)
+60 min:        Production deployment complete
+70 min:        Frontend integration complete
+75 min:        Testing complete
+80 min:        Go-live verification complete

Result:         Both Phase 1 + Phase 2 LIVE in parallel

---

🔐 AGENTS.md Compliance Checklist

• ✅ SOLID: Separation of concerns (proxy layer)
• ✅ Complexity: Configuration-only changes
• ✅ Data Integrity: Pass-through proxy, no loss
• ✅ Necessity: Only required changes
• ✅ Normalization: No DB schema changes
• ✅ Simplicity: Relative paths, clear flow
• ✅ Pattern: Standard reverse proxy pattern
• ✅ Guardrails: Production auth (TLS/HTTPS)
• ✅ Traceability: All changes in git
• ✅ Reliability: Nginx proven reverse proxy
• ✅ Maturity: E2E tests validate
• ✅ Right-way: No shortcuts, standard practice
• ✅ Tech debt: None introduced

---

📝 Next Action

Terminal 3 (Execute Now or in 5 minutes):

cd C:\Job_Roomz\KArtSell.Aegis
.\scripts\DEPLOY_PRODUCTION_NOW.ps1

Expected Output:

✅ Code published
✅ Health checks: 5/5 PASS
✅ Smoke tests: 5/5 PASS
✅ PRODUCTION DEPLOYMENT COMPLETE

---

Status: READY FOR EXECUTION
Authority: AGENTS.md v16.0
Strategic Method: Optimal, parallel, necessary