fix: add awf-api-proxy to container cleanup

The cleanup script, test fixtures, and docker-manager only removed
awf-squid and awf-agent containers. The awf-api-proxy container
was missing, causing container name conflicts in CI when api-proxy
tests run after a failed/interrupted previous run.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: Mossaka

scripts/ci/cleanup.sh

@@ -12,7 +12,7 @@ echo "==========================================="
 
 # First, explicitly remove containers by name (handles orphaned containers)
 echo "Removing awf containers by name..."
-docker rm -f awf-squid awf-agent 2>/dev/null || true
+docker rm -f awf-squid awf-agent awf-api-proxy 2>/dev/null || true
 
 # Cleanup diagnostic test containers
 echo "Stopping docker compose services..."

src/docker-manager.test.ts

@@ -2134,7 +2134,7 @@ describe('docker-manager', () => {
 
       expect(mockExecaFn).toHaveBeenCalledWith(
         'docker',
-        ['rm', '-f', 'awf-squid', 'awf-agent'],
+        ['rm', '-f', 'awf-squid', 'awf-agent', 'awf-api-proxy'],
         { reject: false }
       );
     });

src/docker-manager.ts

@@ -1352,7 +1352,7 @@ export async function startContainers(workDir: string, allowedDomains: string[],
   // This handles orphaned containers from failed/interrupted previous runs
   logger.debug('Removing any existing containers with conflicting names...');
   try {
-    await execa('docker', ['rm', '-f', 'awf-squid', 'awf-agent'], {
+    await execa('docker', ['rm', '-f', 'awf-squid', 'awf-agent', 'awf-api-proxy'], {
       reject: false,
     });
   } catch {

tests/fixtures/cleanup.ts

@@ -25,7 +25,7 @@ export class Cleanup {
   async removeContainers(): Promise<void> {
     this.log('Removing awf containers by name...');
     try {
-      await execa('docker', ['rm', '-f', 'awf-squid', 'awf-agent']);
+      await execa('docker', ['rm', '-f', 'awf-squid', 'awf-agent', 'awf-api-proxy']);
     } catch (error) {
       // Ignore errors (containers may not exist)
     }