CrewAI-Instrumentierung

You are adding Execlave (an AI agent governance platform) to an existing Python project that uses CrewAI. Do not rewrite existing Agents, Tasks, or Crews — only attach instrumentation. Rules you MUST follow:1. Install the correct extra: `pip install 'execlave-sdk[crewai]'`. Add it to requirements.txt / pyproject.toml.2. Read `EXECLAVE_API_KEY` from environment variables. Never hardcode keys. Add it to `.env.example`.3. Create exactly ONE Execlave client per process and reuse it: `exe = Execlave(api_key=os.environ["EXECLAVE_API_KEY"])`.4. Call `instrument_crew(crew, exe, agent_id="<stable-kebab-id>")` immediately before `crew.kickoff()`. The import is `from execlave.integrations.crewai import instrument_crew`. The `agent_id` is a stable kebab-case string identifying this crew in the Execlave dashboard — NOT a CrewAI role name.5. `instrument_crew` CHAINS onto any existing `step_callback` / `task_callback`. It never overwrites user callbacks. Do NOT remove or replace callbacks the project already has set.6. `instrument_crew` is IDEMPOTENT — a `_execlave_instrumented` marker is set on the crew so calling it twice is a no-op. Do not guard it with your own "already instrumented" check.7. Wrap `crew.kickoff()` in try/except for `execlave.errors.PolicyBlockedError`. On block, return a structured 4xx payload containing `exc.violations`. Do NOT swallow the error silently.8. Do NOT manually call `exe.enforce_policy` for tool calls — the wrapped `step_callback` enforces before each tool step. Enforcement runs only for steps with a non-empty `tool` attribute; pure-reasoning steps are recorded but not enforced.9. Each `Agent` inside the crew is instrumented in addition to the crew itself, so sub-agent tool calls are captured. You do NOT need to pass each agent separately.10. On process shutdown (ASGI lifespan / SIGTERM handler), call `exe.flush()` so in-flight spans are not dropped.11. JavaScript is NOT supported — CrewAI is Python-only. If the project is Node/TS, stop and tell me. Deliverables:- Edit only the file that builds and kicks off the Crew. One diff per file.- Do not touch Agent, Task, or tool definitions.- Add `EXECLAVE_API_KEY` and optional `EXECLAVE_BASE_URL` to `.env.example`. Reference: https://www.execlave.com/docs/integrations/crewaiAPI reference: https://www.execlave.com/docs/sdk-reference