feat(#93): implement agent spawn via federation

Implements FED-010: Agent Spawn via Federation feature that enables
spawning and managing Claude agents on remote federated Mosaic Stack
instances via COMMAND message type.

Features:
- Federation agent command types (spawn, status, kill)
- FederationAgentService for handling agent operations
- Integration with orchestrator's agent spawner/lifecycle services
- API endpoints for spawning, querying status, and killing agents
- Full command routing through federation COMMAND infrastructure
- Comprehensive test coverage (12/12 tests passing)

Architecture:
- Hub → Spoke: Spawn agents on remote instances
- Command flow: FederationController → FederationAgentService →
  CommandService → Remote Orchestrator
- Response handling: Remote orchestrator returns agent status/results
- Security: Connection validation, signature verification

Files created:
- apps/api/src/federation/types/federation-agent.types.ts
- apps/api/src/federation/federation-agent.service.ts
- apps/api/src/federation/federation-agent.service.spec.ts

Files modified:
- apps/api/src/federation/command.service.ts (agent command routing)
- apps/api/src/federation/federation.controller.ts (agent endpoints)
- apps/api/src/federation/federation.module.ts (service registration)
- apps/orchestrator/src/api/agents/agents.controller.ts (status endpoint)
- apps/orchestrator/src/api/agents/agents.module.ts (lifecycle integration)

Testing:
- 12/12 tests passing for FederationAgentService
- All command service tests passing
- TypeScript compilation successful
- Linting passed

Refs #93

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

docs/1-getting-started/4-docker-deployment/README.md

@@ -36,6 +36,7 @@ docker compose logs -f
 ```
 
 That's it! Your Mosaic Stack is now running:
+
 - Web: http://localhost:3000
 - API: http://localhost:3001
 - PostgreSQL: localhost:5432
@@ -46,6 +47,7 @@ That's it! Your Mosaic Stack is now running:
 Mosaic Stack uses Docker Compose profiles to enable optional services:
 
 ### Core Services (Always Active)
+
 - `postgres` - PostgreSQL database
 - `valkey` - Valkey cache
 - `api` - Mosaic API
@@ -54,6 +56,7 @@ Mosaic Stack uses Docker Compose profiles to enable optional services:
 ### Optional Services (Profiles)
 
 #### Traefik (Reverse Proxy)
+
 ```bash
 # Start with bundled Traefik
 docker compose --profile traefik-bundled up -d
@@ -63,11 +66,13 @@ COMPOSE_PROFILES=traefik-bundled
 ```
 
 Services included:
+
 - `traefik` - Traefik reverse proxy with dashboard (http://localhost:8080)
 
 See [Traefik Integration Guide](traefik.md) for detailed configuration options including upstream mode.
 
 #### Authentik (OIDC Provider)
+
 ```bash
 # Start with Authentik
 docker compose --profile authentik up -d
@@ -77,12 +82,14 @@ COMPOSE_PROFILES=authentik
 ```
 
 Services included:
+
 - `authentik-postgres` - Authentik database
 - `authentik-redis` - Authentik cache
 - `authentik-server` - Authentik OIDC server (http://localhost:9000)
 - `authentik-worker` - Authentik background worker
 
 #### Ollama (AI Service)
+
 ```bash
 # Start with Ollama
 docker compose --profile ollama up -d
@@ -92,9 +99,11 @@ COMPOSE_PROFILES=ollama
 ```
 
 Services included:
+
 - `ollama` - Ollama LLM service (http://localhost:11434)
 
 #### All Services
+
 ```bash
 # Start everything
 docker compose --profile full up -d
@@ -122,6 +131,7 @@ docker compose --profile full up -d
 Use external services for production:
 
 1. Copy override template:
+
    ```bash
    cp docker-compose.override.yml.example docker-compose.override.yml
    ```
@@ -145,6 +155,7 @@ Docker automatically merges `docker-compose.yml` and `docker-compose.override.ym
 Mosaic Stack uses two Docker networks to organize service communication:
 
 #### mosaic-internal (Backend Services)
+
 - **Purpose**: Isolates database and cache services
 - **Services**:
   - PostgreSQL (main database)
@@ -159,6 +170,7 @@ Mosaic Stack uses two Docker networks to organize service communication:
   - No direct external access to database/cache ports (unless explicitly exposed)
 
 #### mosaic-public (Frontend Services)
+
 - **Purpose**: Services that need external network access
 - **Services**:
   - Mosaic API (needs to reach Authentik OIDC and external Ollama)
@@ -298,11 +310,13 @@ JWT_SECRET=change-this-to-a-random-secret
 ### Service Won't Start
 
 Check logs:
+
 ```bash
 docker compose logs <service-name>
 ```
 
 Common issues:
+
 - Port already in use: Change port in `.env`
 - Health check failing: Wait longer or check service logs
 - Missing environment variables: Check `.env` file
@@ -310,11 +324,13 @@ Common issues:
 ### Database Connection Issues
 
 1. Verify PostgreSQL is healthy:
+
    ```bash
    docker compose ps postgres
    ```
 
 2. Check database logs:
+
    ```bash
    docker compose logs postgres
    ```
@@ -327,6 +343,7 @@ Common issues:
 ### Performance Issues
 
 1. Adjust PostgreSQL settings in `.env`:
+
    ```bash
    POSTGRES_SHARED_BUFFERS=512MB
    POSTGRES_EFFECTIVE_CACHE_SIZE=2GB
@@ -334,6 +351,7 @@ Common issues:
    ```
 
 2. Adjust Valkey memory:
+
    ```bash
    VALKEY_MAXMEMORY=512mb
    ```
@@ -394,6 +412,7 @@ docker run --rm -v mosaic-postgres-data:/data -v $(pwd):/backup alpine tar czf /
 ### Monitoring
 
 Consider adding:
+
 - Prometheus for metrics
 - Grafana for dashboards
 - Loki for log aggregation
@@ -402,6 +421,7 @@ Consider adding:
 ### Scaling
 
 For production scaling:
+
 - Use external PostgreSQL (managed service)
 - Use external Redis/Valkey cluster
 - Load balance multiple API instances