feat(dashboard): redesign UI to match production design

.claude/rules/11-docker-integration-quick-reference.md

@@ -0,0 +1,385 @@
+# Docker Integration Quick Reference
+
+**Quick answers for common integration test failures. For detailed explanations, see rule 10.**
+
+---
+
+## TL;DR Startup Verification
+
+```bash
+# Check all services health
+docker-compose -f docker-compose.integration.yml ps
+
+# Watch logs for startup
+docker-compose -f docker-compose.integration.yml logs -f
+
+# Quick health check after all services report "healthy"
+curl http://localhost:3100/api/health && \
+curl http://localhost:18789 -H "Authorization: Bearer test-integration-token"
+```
+
+---
+
+## Common Failures & Fixes
+
+### "function digest() does not exist" (GoTrue or PostgREST)
+
+**Fix:**
+```bash
+docker exec mission-control-supabase-db-1 psql -U postgres -d postgres -c "
+  ALTER ROLE authenticator SET search_path TO \"\$user\", public, extensions;
+  ALTER ROLE service_role SET search_path TO \"\$user\", public, extensions;
+"
+```
+
+**Or:** Verify `99-service-role-passwords.sql` is mounted and contains these lines.
+
+---
+
+### "password authentication failed" (GoTrue/PostgREST → PostgreSQL)
+
+**Fix:**
+```bash
+# Verify service role passwords exist
+docker exec mission-control-supabase-db-1 psql -U authenticator -d postgres -c "SELECT 1;"
+
+# If that fails, set passwords:
+docker exec mission-control-supabase-db-1 psql -U postgres -d postgres -c "
+  ALTER USER authenticator WITH PASSWORD 'postgres';
+  ALTER USER supabase_auth_admin WITH PASSWORD 'postgres';
+"
+```
+
+---
+
+### "Port 3001 already in use" (PostgREST port conflict)
+
+**Fix:**
+```bash
+# Kill process on port
+lsof -i :3001 | grep -v PID | awk '{print $2}' | xargs kill -9
+
+# Or change docker port in docker-compose.integration.yml:
+#   ports:
+#     - "3002:3000"  # <- use 3002 instead of 3001
+```
+
+---
+
+### "Mission Control API health check failing" after 2 min
+
+**Check logs:**
+```bash
+docker-compose -f docker-compose.integration.yml logs mission-control | tail -20
+```
+
+**Common issues:**
+- Supabase URL wrong? (should be `http://supabase-kong:8000`)
+- Kong not started? (check `docker-compose ps supabase-kong`)
+- Build failed? (check for TypeScript errors in logs)
+
+---
+
+### "Kong not routing /auth/v1/" (401 on auth endpoints)
+
+**Fix:**
+```bash
+# Verify kong.yml exists and has auth routes
+cat tests/integration/kong/kong.yml | grep -A2 "auth-v1"
+
+# Restart Kong to reload config
+docker-compose -f docker-compose.integration.yml restart supabase-kong
+
+# Test routing
+curl http://localhost:8000/auth/v1/health
+```
+
+---
+
+### "OpenClaw gateway fails to start" (generic error)
+
+**Check logs:**
+```bash
+docker-compose -f docker-compose.integration.yml logs openclaw-gateway | tail -50
+```
+
+**Most likely causes (in order):**
+
+1. **Invalid JSON in openclaw.json**
+   ```bash
+   node -e "JSON.parse(require('fs').readFileSync('tests/integration/openclaw/config/openclaw.json'))"
+   ```
+
+2. **gateway.mode not "local"**
+   ```bash
+   grep '"mode"' tests/integration/openclaw/config/openclaw.json
+   # Should show: "mode": "local"
+   ```
+
+3. **model is string, not object**
+   ```bash
+   grep '"model"' tests/integration/openclaw/config/openclaw.json
+   # Should show: "model": { "primary": "..." }, not "model": "..."
+   ```
+
+4. **auth mode is invalid**
+   ```bash
+   grep '"auth"' tests/integration/openclaw/config/openclaw.json
+   # Should show: "auth": "token" or "auth": "password", NOT "none"
+   ```
+
+---
+
+### "OpenClaw: Unauthorized" (token rejected)
+
+**Fix:**
+```bash
+# Check your auth header
+curl -H "Authorization: Bearer test-integration-token" http://localhost:18789/
+
+# Verify token in startup command
+grep "token test-integration-token" tests/integration/scripts/entrypoint-openclaw.sh
+```
+
+---
+
+### "OpenClaw: Mission Control API unreachable"
+
+**Check logs:**
+```bash
+docker-compose -f docker-compose.integration.yml logs openclaw-gateway | grep -i "api\|connect\|unreachable"
+```
+
+**Fix:**
+```bash
+# Verify Mission Control is running and healthy
+docker-compose -f docker-compose.integration.yml ps mission-control
+
+# Verify URL is correct (should point to mission-control service, not localhost)
+grep MISSION_CONTROL_API_URL docker-compose.integration.yml
+# Should be: http://mission-control:3000 (not http://localhost:3000)
+
+# Test from inside OpenClaw container
+docker exec mission-control-openclaw-gateway-1 \
+  curl http://mission-control:3000/api/health
+```
+
+---
+
+### "Database migration failed" (initial_schema migration error)
+
+**Check:**
+```bash
+docker-compose -f docker-compose.integration.yml logs supabase-db | grep -i "migration\|error" | head -10
+```
+
+**Fix:**
+```bash
+# Verify migrations are mounted correctly
+docker-compose -f docker-compose.integration.yml config | grep migrations
+
+# Restart database to re-run migrations
+docker-compose -f docker-compose.integration.yml down supabase-db
+docker-compose -f docker-compose.integration.yml up -d supabase-db
+
+# Wait for healthy
+sleep 10 && docker-compose -f docker-compose.integration.yml ps supabase-db
+```
+
+---
+
+### "curl: command not found" in health checks
+
+**Not actually a failure.** PostgREST image doesn't have curl, so the health check uses:
+```yaml
+test: ["CMD-SHELL", "bash -c 'echo > /dev/tcp/localhost/3000'"]
+```
+
+This is correct. If you see actual health failures, look at the service logs instead.
+
+---
+
+## Port Cheat Sheet
+
+| Service | Container Port | Host Port | URL |
+|---------|---|---|---|
+| PostgreSQL | 5432 | 54332 | `postgres://localhost:54332` |
+| GoTrue (auth) | 9999 | 9998 | `http://localhost:9998` |
+| PostgREST (data) | 3000 | 3001 | `http://localhost:3001` |
+| Kong (gateway) | 8000 | 8000 | `http://localhost:8000` |
+| Mission Control | 3000 | 3100 | `http://localhost:3100` |
+| OpenClaw Gateway | 18789 | 18789 | `http://localhost:18789` |
+
+---
+
+## One-Command Cleanup
+
+```bash
+# Stop all containers and remove volumes (WARNING: data loss)
+docker-compose -f docker-compose.integration.yml down -v
+
+# Remove dangling volumes
+docker volume prune -f
+
+# Fresh start
+docker-compose -f docker-compose.integration.yml up -d
+docker-compose -f docker-compose.integration.yml logs -f
+```
+
+---
+
+## Verify Each Service (Sequential)
+
+Run these in order to pinpoint which service is broken:
+
+```bash
+# 1. PostgreSQL
+echo "1. PostgreSQL..."
+docker exec mission-control-supabase-db-1 pg_isready -U postgres && echo "✓ OK" || echo "✗ FAIL"
+
+# 2. GoTrue
+echo "2. GoTrue..."
+curl -sf http://localhost:9998/health > /dev/null && echo "✓ OK" || echo "✗ FAIL"
+
+# 3. PostgREST
+echo "3. PostgREST..."
+bash -c "echo > /dev/tcp/localhost/3001" 2>/dev/null && echo "✓ OK" || echo "✗ FAIL"
+
+# 4. Kong
+echo "4. Kong..."
+curl -sf http://localhost:8000/auth/v1/health > /dev/null && echo "✓ OK" || echo "✗ FAIL"
+
+# 5. Mission Control
+echo "5. Mission Control..."
+curl -sf http://localhost:3100/api/health > /dev/null && echo "✓ OK" || echo "✗ FAIL"
+
+# 6. OpenClaw
+echo "6. OpenClaw..."
+curl -sf -H "Authorization: Bearer test-integration-token" http://localhost:18789/ > /dev/null && echo "✓ OK" || echo "✗ FAIL"
+```
+
+---
+
+## Debug Commands
+
+```bash
+# See what's listening on a port
+lsof -i :3000
+
+# Watch service startup in real-time
+docker-compose -f docker-compose.integration.yml logs -f mission-control
+
+# Run a one-off command in a container
+docker exec mission-control-supabase-db-1 psql -U postgres -d postgres -c "..."
+
+# Copy a file out of container
+docker cp mission-control-supabase-db-1:/var/log/postgres.log /tmp/postgres.log
+
+# Check container resource usage
+docker stats mission-control-supabase-db-1
+
+# Inspect network
+docker network inspect mission-control_integration
+```
+
+---
+
+## Config Validation One-Liners
+
+```bash
+# Validate OpenClaw JSON
+node -e "JSON.parse(require('fs').readFileSync('tests/integration/openclaw/config/openclaw.json'))"
+
+# Validate docker-compose YAML
+docker-compose -f docker-compose.integration.yml config > /dev/null
+
+# Validate mission-control Dockerfile
+docker build --dry-run apps/web/Dockerfile .
+
+# Check all JSON files in openclaw directory
+find tests/integration/openclaw -name "*.json" -exec sh -c 'node -e "JSON.parse(require(\"fs\").readFileSync(\"$1\"))" _ {} \;
+```
+
+---
+
+## Before Committing Changes
+
+1. Validate configs:
+   ```bash
+   docker-compose -f docker-compose.integration.yml config > /dev/null && \
+   node -e "JSON.parse(require('fs').readFileSync('tests/integration/openclaw/config/openclaw.json'))" && \
+   echo "✓ All configs valid"
+   ```
+
+2. Test on clean environment:
+   ```bash
+   docker-compose -f docker-compose.integration.yml down -v
+   docker-compose -f docker-compose.integration.yml up -d
+   sleep 60  # Let services start
+   curl http://localhost:3100/api/health  # Should return 200
+   ```
+
+3. Check Git diff for unintended changes:
+   ```bash
+   git diff docker-compose.integration.yml  # Should be minimal
+   git diff tests/integration/openclaw/config/
+   ```
+
+---
+
+## Integration Test Execution
+
+```bash
+# Run integration tests
+docker-compose -f docker-compose.integration.yml up -d
+sleep 60  # Wait for services to be healthy
+
+# In another terminal:
+pnpm test:integration
+
+# Or specific test:
+pnpm test tests/integration/api/heartbeat.test.ts
+
+# Stop services
+docker-compose -f docker-compose.integration.yml down
+```
+
+---
+
+## When Nothing Works
+
+**Nuclear option (complete reset):**
+
+```bash
+# Stop everything
+docker-compose -f docker-compose.integration.yml down -v
+docker volume prune -f
+docker network prune -f
+
+# Remove image to force rebuild
+docker rmi openclaw:local 2>/dev/null || true
+
+# Rebuild and start fresh
+docker-compose -f docker-compose.integration.yml build --no-cache
+docker-compose -f docker-compose.integration.yml up -d
+
+# Wait and verify
+sleep 120
+docker-compose -f docker-compose.integration.yml ps
+curl http://localhost:3100/api/health
+```
+
+---
+
+## Still Stuck?
+
+1. **Check the full prevention guide:** See `rule 10` for detailed explanations
+2. **Read service logs:** `docker-compose logs <service-name>`
+3. **Ask the team:** The 12 issues documented in rule 10 cover ~95% of failures
+
+---
+
+## Last Updated
+
+- **2026-02-05** — Initial quick reference based on integration setup
+- **Changes tested:** All 12 common issues and their fixes