Per user claude

Apply what a human supplied (form answers, vendor credentials, a server choice). Each completion must be of the kind its setup asks for, or nothing is done. Credential values go to the vendor and are never stored or logged here; naming vault entries instead needs `secret:secret_policy.update`. Each setup commits on its own. A form, credential or `create` completion carries the setup on into creating the server or starting its sign-in, so it needs `mcp_server.create`; without it the whole batch is refused (403) before anything is done. `create` (#4386) connects a new account for a connection, even where existing servers fit, from Runtime Vault references only; later steps never fall back to choosing an existing server unless a `server_choice` says so. A connection that needs a vendor sign-in (OAuth) can't be created here (`oauth_create_not_supported`): connect the account in the app under MCP servers first, then choose it with a `server_choice`. A server choice only binds an existing server and needs no more than the pack write gates.