Personas and bindings

Many State Cards can require the same Auth Persona. Bind the Persona once on the current machine, then compatible cards can use it in a Clean Session without storing it in each capsule.

Common safe statuses are:

Status	Meaning	What to do
`READY`	The required local binding is available.	Open the State Card.
`AUTH_BINDING_REQUIRED`	No compatible local binding exists.	Bind or re-authenticate the Persona.
`REAUTH_REQUIRED`	The saved session is no longer accepted.	Re-authenticate the Persona.
`AUTH_ORIGIN_MISMATCH`	The binding cannot be used for this origin.	Create a correctly scoped binding.
`AUTH_POLICY_DENIED`	Local credential policy refused the operation.	Check supported OS credential storage and project policy.

Never use an Auth Binding to transfer production or customer credentials through a State Capsule.