Create 3 starter workflow templates (research-swarm, code-review-swarm, data-pipeline-swarm)

[shreyanshjain7174]

Three production-quality workflow templates demonstrating different agent collaboration patterns.

Acceptance:

• research-swarm (already exists, polish)
• code-review-swarm: fan-out reviewers
• data-pipeline-swarm: parallel ETL
• Each has docker-compose + Helm overlay
• README per template

[shreyanshjain7174]

Approach note (2026-04-26)

Current state

3 examples already exist:

• examples/research-swarm/ — A2A multi-agent with Docker Compose
• examples/multi-agent-swarm/ — orchestrator-based multi-agent
• examples/sre-incident-response/ — 3-tier cost-aware model routing

Issue asks for

3 starter workflow templates: research-swarm, code-review-swarm, data-pipeline-swarm

Gap analysis

• research-swarm — DONE (exists in examples/research-swarm/)
• code-review-swarm — NOT DONE but agents/graph/registry.py ships a built-in code_review workflow (fan-out security/performance/style review). Just needs an examples/ wrapper with Docker Compose + README.
• data-pipeline-swarm — NOT DONE. Needs a new workflow registered in the registry + example wrapper.

Proposed approach

1. code-review-swarm: Create examples/code-review-swarm/ with Docker Compose, .env.example, README, using the existing code_review registered workflow.
2. data-pipeline-swarm: Create examples/data-pipeline-swarm/ with a new data_pipeline workflow (extract → transform → load pattern, 3 agents).
3. Each example follows the exact structure of examples/research-swarm/: Makefile, docker-compose.yml, README.md, agents/, config/.

Confidence: 85% — code-review example is trivial (existing workflow), data-pipeline needs a new workflow definition that I need to validate fits the registry pattern.

Blocker?

Not a launch blocker. The 3 existing examples are already more than most K8s operator repos ship. I'd downgrade to P2.