# Response Draft Recovery

## Goal

An expert must be able to recover a missing response draft after a transient AI-provider or Inngest delivery failure, without manually composing a response solely because automation failed.

## Behavior

1. If automatic draft-event delivery fails after summarization has moved a ticket to `RESPONSE_DRAFTING`, restore the ticket to an expert-reviewable state and mark AI processing as degraded.
2. An expert viewing a degraded ticket without a saved draft sees a retry action adjacent to the expert response controls.
3. Retrying queues a new response-draft event and returns the ticket to `RESPONSE_DRAFTING`.
4. The response-draft Inngest function retries retryable execution failures using Inngest's configured capped retry behavior; a successfully invoked LLM failure continues to save the existing fallback draft.
5. The retry action is not shown to line managers or when a saved draft already exists.

## Done Criteria

- Unit coverage defines when the retry UI is available.
- Integration coverage proves a failed automatic event restores a recoverable ticket state.
- Integration coverage proves an expert retry returns that ticket to `RESPONSE_DRAFTING`.
- E2E coverage proves an expert can discover and invoke the retry control.
- `pnpm type-check` and `pnpm test` pass twice consecutively.