Migrate SMS from Bird Connectivity Platform

I am moving an SMS integration from the MessageBird Connectivity Platform to Bird. Route through it with me.
1. Check what you already have before setting anything up. If Bird's MCP server is connected, use its tools. If the Bird CLI is installed and signed in, use that. Either one is enough, and every step below is an action you take with whichever you have. Only if neither is present, follow https://bird.com/docs/ai/set-up-your-agent.md to set one up and sign me in. Every Bird docs page serves Markdown at its own URL with `.md` appended, so fetch that rather than the HTML.
2. Read https://bird.com/docs/guides/sms/migrate/connectivity-platform.md for the field, status and opt-out mapping, and https://bird.com/docs/guides/sms/migrate.md for the order the steps go in.
3. Find and list my Connectivity Platform usage in this repository before you change anything: the send call sites, the originators they send from and whether each is a number or an alphanumeric sender ID, and the status-report URLs they register.
4. Tell me early if I use any of flash, binary, mclass or typeDetails on my sends. None of them carries over, and they need raising with Bird support before a cutover date exists, so I would rather know now than at the end.
5. Then take only the paths that apply to me.
   - If I send with an alphanumeric sender ID: it does not move with the account. Each one is re-created on Bird and re-registered wherever the destination country requires registration, so tell me which countries I send to and what each of them will need, following the sender section of https://bird.com/docs/guides/sms/migrate.md.
   - If I send to US long codes: read https://bird.com/docs/guides/sms/10dlc.md and work through the brand and campaign registration. Read the requirements first. A registration attempt is chargeable and a rejected brand is charged again on resubmit, so show me the exact payload, then wait for me to reply with the words submit the brand, or submit the campaign. A reply that agrees without naming what it is authorising is not authorisation for a chargeable step, and a bare ok go ahead is that shape. One authorisation covers one submission, so ask me again before the campaign even if I have already authorised the brand.
   - Carry over my opt-outs following https://bird.com/docs/guides/sms/opt-outs-and-keywords.md. A Bird suppression is one sender-and-subscriber pair rather than a global list, so if what I kept is a single list of numbers, ask me which originators it should apply to and import it once per originator.
   - Ask me which numbers I want to keep, then open a Bird support ticket for the port, listing those numbers and saying they port from the Connectivity Platform. Route it to a person rather than an automated answer. Give me the ticket ID. The port runs on Bird support's schedule rather than yours, so plan the cutover around it.
6. Test the ported path against Bird's simulated destinations before any real traffic, following https://bird.com/docs/guides/sms/migrate.md. They exercise the send and the webhook handler against real API responses and real signed deliveries without reaching a handset, but a simulated send is billed at the destination's normal rate, so tell me how many you plan to send and keep the smoke test to that. The United States must be enabled and `from` must be a sender valid for the US, or the test numbers reject.
7. Stop and ask me wherever a step needs a decision. Do not point production traffic at Bird until I have seen the simulated-destination results and replied with the words cut over to Bird. Retiring the Connectivity Platform path is a separate step that comes later: ask me again and wait for me to reply with the words retire the Connectivity Platform path. A reply that agrees without naming what it is authorising is not authorisation. Finish by telling me what is left that only a person can do.