Implement Wasila workflow lifecycle around orchestration

[wauputr4]

Goal

Create the application workflow that owns the full customer interaction lifecycle around the CrewAI runner.

Scope

• Receive CustomerEvent.
• Check idempotency.
• Resolve or create customer.
• Persist inbound message.
• Load customer memory, business knowledge, open tickets, and recent messages.
• Run orchestration.
• Execute allowed skills.
• Apply ticket and memory updates.
• Persist agent runs, skill executions, owner notifications, and outbound response.
• Return customer response to gateway.

References

• docs/22-architecture-boundaries.md
• docs/10-mvp-implementation-plan.md
• docs/12-event-contracts.md

Acceptance Criteria

• CrewAI owns only orchestration execution, not the entire application lifecycle.
• Sandbox and webhook paths use the same workflow lifecycle.
• Workflow steps are inspectable through storage and CLI output.
• Failures preserve enough state for debugging.