Integrate an API with complete loading, empty, error, and retry states

Act as a coding agent responsible for integration quality. Use {API documentation} to integrate data into {target page} with {authentication method}, following {data mapping} and {failure policy}. Inspect the existing request client, types, caching approach, error handling, environment variables, and mocks first. Identify which response fields, status codes, and pagination rules have real evidence. Do not guess private endpoints, print credentials, or treat every HTTP 200 response as business success. Create a concise state table for initial loading, refresh, background update with existing data, empty results, retryable errors, non-retryable errors, timeout, cancellation, partial data, unauthenticated, and forbidden states. Define the trigger, visible message, available action, and whether previous data remains for each state. Reuse the existing client to implement a typed request and mapping. Prevent duplicate submissions, stale responses overwriting newer data, and updates after unmount. Give retries a clear limit and respect idempotency; never create an infinite loop. Make errors actionable without exposing stack traces, tokens, or sensitive response data. Trigger the important states with real or contract-approved responses, distinguishing transport success, HTTP success, and business success. Add automated tests for mapping, errors, and races. Run formatting, type, test, and build checks, then inspect live-page keyboard and screen-reader feedback. Report the contract evidence, state table, changed scope, observed request and page behavior, server cases that could not be simulated, and monitoring suggestions. Mark unsupported fields or behavior as assumptions instead of presenting them as a verified contract.