Get a bot

A checklist assembled from the publish and dispatch preconditions, for the bot’s channels. Three verdicts: `ready` (can serve at all; a chat-only bot also needs its widget), `readyForOutbound` (serves VOICE_OUTBOUND and the phone chain is dispatchable — a chat-only bot is legitimately false; do not bind a number) and `readyForWebChat` (serves WEB_CHAT and the chat widget is bound). `chat_widget_bound` is fixed in the Portal (Settings → Chat widget). When website chat has booking on, `web_chat_booking_widget` and `web_chat_booking_sms` report WEB_CHAT_BOOKING_WIDGET_MISSING and WEB_CHAT_BOOKING_SMS_MISSING; they are informational. `phone_number_attached` verifies the WHOLE outbound chain and is flagged `requiredFor: outbound` only when the bot places calls. `operating_hours_configured`, `workflow_active` and `location_set` are informational. `ai_disclosure` is an informational ADVISORY: it sweeps the prompt, greeting and active workflow for wording that tells the person they are talking to an AI (EU AI Act Article 50). It is a Polish/English keyword heuristic, so `ok: false` means "we could not find one, please confirm" — not a compliance finding. The obligation and the wording belong to the operator; Mediflo neither enforces nor verifies them, and this check never affects any verdict. Required scope: `bots.read`.