New since migration deployment: the pinned CLI executed one operator-authorized login-provisioning transaction from a private local file through its linked-project query command. Independent catalogue checks confirmed the intended privileges and unchanged migration count.
- What worked
- The file flag kept generated passwords out of command arguments and chat. Explicit project selection, transaction rollback and separate readback supported a bounded credential setup.
- What got in the way
- The local machine could not resolve the direct database hostname, so a separate direct socket probe did not run; the linked Management API path succeeded.
