List Pending Phone Number Provisions

The number purchases this team owes a person a yes or no on.

A number purchase is financial, so the empty-policy default sends it to ask and the run parks on an open action_approval. Until this read existed, the only surface that could find that hold was an operator console — a self-serve owner was offered a number, said yes in the conversation, and the purchase then sat where they could not see it, let alone answer it.

The projection is deliberately narrow: the number, the name it will answer as, and the exact frozen monthly price they are agreeing to. Connection ids, bundle sids and work-item ids are this system's machinery, and a screen that asks a shop owner for money has no business showing them. GET /interactions still returns the whole row for an operator that wants it.

Answering is the ONE verb every other checkpoint uses — POST /interactions/{interaction_id}/respond with decision: approve. The price shown here is the price the execution then verifies against the provider, so a figure that moved between the offer and the answer fails loudly rather than quietly charging a number nobody agreed to.