Phase 1: Pre-Deployment Checks
├── Verify all services are accessible
├── Check current deployment status
├── Backup current environment variables
└── Run pre-deployment tests

Phase 2: Backend Deployment
├── Deploy backend to Railway
├── Wait for "Deployed" status
├── Run backend health check
└── Verify database connectivity

Phase 3: Auth Server Deployment
├── Deploy auth server to Railway
├── Wait for "Deployed" status
├── Run auth server health check
└── Verify database connectivity

Phase 4: Frontend Deployment
├── Deploy frontend to Vercel
├── Wait for deployment complete
├── Run frontend health check
└── Verify static assets loaded

Phase 5: Environment Configuration
├── Set AUTH_SERVER_URL in backend
├── Set CORS_ORIGINS in all services
├── Verify all environment variables
└── Trigger redeployment if needed

Phase 6: Post-Deployment Verification
├── Run health checks on all services
├── Test inter-service communication
├── Run browser authentication tests
└── Generate deployment report

Phase 1: Service Health Checks
├── Backend: GET /health
├── Auth Server: GET /health
├── Frontend: GET /
└── Database: Connection test

Phase 2: API Testing
├── Test /api/auth/sign-up/email
├── Test /api/auth/sign-in/email
├── Test /api/auth/sign-out
├── Test /api/auth/get-session
├── Test /api/tasks (CRUD operations)
└── Verify authentication middleware

Phase 3: Browser Testing
├── Navigate to login page
├── Fill credentials and login
├── Verify cookie settings
├── Test dashboard access
├── Test task creation/deletion
└── Test logout functionality

Phase 4: Integration Testing
├── Test full user journey
├── Test error handling
├── Test rate limiting
├── Test CORS configuration
└── Test session management

Phase 5: Performance Testing
├── Measure page load times
├── Measure API response times
├── Check for memory leaks
├── Verify resource usage
└── Test under load (optional)

Phase 6: Security Testing
├── Verify HTTPS enforcement
├── Check cookie security attributes
├── Test CSRF protection
├── Verify input sanitization
└── Check for XSS vulnerabilities

Execute: deploy-all
Then: test-all
If tests fail AND rollback-on-failure=true:
  Execute: rollback-all
  Notify: Deployment failed, rolled back
Else:
  Notify: Deployment successful

Phase 1: Identify Last Stable Deployment
├── Query Railway for recent deployments
├── Identify last known good deployment
└── Confirm rollback target

Phase 2: Rollback Services
├── Rollback backend to previous version
├── Rollback auth server to previous version
├── Wait for rollback completion
└── Restore environment variables

Phase 3: Verify Rollback
├── Run health checks
├── Test authentication flow
├── Verify services are operational
└── Generate rollback report

Phase 4: Notify Team
├── Send rollback notification
├── Include rollback reason
├── Attach verification report
└── Suggest next steps

frontend:
  url: https://frontend-peach-xi-69.vercel.app
  platform: Vercel
  deploy_command: vercel --prod

backend:
  url: https://tda-backend-production.up.railway.app
  platform: Railway
  project_id: 1a580b9d-e43b-4faf-a523-b3454b9d3bf1
  service_id: ac8b8441-def7-49e9-af64-47dd171ae1c2
  required_vars:
    - AUTH_SERVER_URL
    - DATABASE_URL
    - CORS_ORIGINS

auth_server:
  url: https://auth-server-production-8251.up.railway.app
  platform: Railway
  required_vars:
    - DATABASE_URL
    - BETTER_AUTH_SECRET
    - CORS_ORIGINS

database:
  provider: Neon PostgreSQL
  connection_pooling: enabled

frontend:
  url: https://staging-frontend.vercel.app

backend:
  url: https://staging-backend.railway.app

auth_server:
  url: https://staging-auth.railway.app

database:
  provider: Neon PostgreSQL (staging branch)

{
  "workflow": "deploy-all",
  "environment": "production",
  "status": "SUCCESS",
  "timestamp": "2025-12-27T10:30:00Z",
  "duration": "5m 32s",
  "deployments": {
    "backend": {
      "status": "DEPLOYED",
      "version": "7bcf9b7",
      "health_check": "PASS"
    },
    "auth_server": {
      "status": "DEPLOYED",
      "version": "8400e1d",
      "health_check": "PASS"
    },
    "frontend": {
      "status": "DEPLOYED",
      "version": "833784f",
      "health_check": "PASS"
    }
  },
  "tests": {
    "health_checks": "PASS",
    "browser_tests": "PASS",
    "integration_tests": "PASS"
  },
  "urls": {
    "frontend": "https://frontend-peach-xi-69.vercel.app",
    "backend": "https://tda-backend-production.up.railway.app",
    "auth_server": "https://auth-server-production-8251.up.railway.app"
  }
}

{
  "workflow": "deploy-test",
  "environment": "production",
  "status": "FAILED_ROLLED_BACK",
  "timestamp": "2025-12-27T10:30:00Z",
  "failure_reason": "Browser authentication test failed: 504 Gateway Timeout",
  "rollback_performed": true,
  "rollback_status": "SUCCESS",
  "previous_version_restored": true,
  "services_operational": true,
  "error_details": {
    "service": "backend",
    "test": "browser_auth_test",
    "error": "Backend cannot reach auth server",
    "http_status": 504
  },
  "recommendation": "Check AUTH_SERVER_URL environment variable in backend service"
}

claude-code /e2e-workflow --workflow deploy-all --environment production

claude-code /e2e-workflow --workflow deploy-test --environment production --rollback-on-failure true

claude-code /e2e-workflow --workflow test-all --environment production

claude-code /e2e-workflow --workflow rollback-all --environment production

claude-code /e2e-workflow --workflow deploy-test --environment staging

Action: Rollback backend to previous version
Notify: Backend deployment failed
Keep: Frontend and auth server on current versions
Test: Verify system still operational

Action: Rollback auth server to previous version
Notify: Auth server deployment failed
Impact: Authentication will continue with previous version
Test: Verify login still works

Action: Rollback all services to previous versions
Notify: Post-deployment tests failed
Reason: Include test failure details
Recovery: Review logs, fix issue, redeploy

Action: Restore previous environment variables
Trigger: Redeployment with correct configuration
Verify: Run tests to confirm fix

name: E2E Workflow

on:
  push:
    branches: [main]

jobs:
  deploy-and-test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2

      - name: Run E2E Workflow
        run: |
          claude-code /e2e-workflow \
            --workflow deploy-test \
            --environment production \
            --rollback-on-failure true \
            --notify slack

      - name: Upload Deployment Report
        if: always()
        uses: actions/upload-artifact@v2
        with:
          name: deployment-report
          path: deployment-report.json

# From local machine
claude-code /e2e-workflow \
  --workflow deploy-all \
  --environment production \
  --notify email

Is service responding? NO → Rollback immediately
Are tests passing? NO → Investigate, rollback if critical
Are users affected? YES → Rollback, fix, redeploy
Is error rate elevated? YES → Monitor, rollback if worsening
All systems nominal? YES → Deployment successful