Async AI workflows in SwiftUI need a failure state, not only a loading spinner

Many SwiftUI examples stop at loading and success. That is fine for a small demo, but an AI-backed feature has more states to explain: the request was queued; the model or network timed out; the response was incomplete or invalid; the user is offline; the server needs a retry or human review. I am working on a small mobile client for an AI workflow and am trying to keep the state model honest. The client should not guess whether a request worked. It should show the current state and let th...