/* Account completion card — what an account still owes after a code sign-in.
 *
 * ALMOST NOTHING LIVES HERE ANY MORE, and that is the point.
 *
 * This sheet used to carry a full set of field, label, input and button rules
 * of its own, on the reasoning that the two surfaces showing this card do not
 * share a stylesheet. They do: login.html, index.html and register.html all
 * load css/login.css, and all three wear .auth-surface. So the card was opting
 * out of the app's control scale for no reason, and looked like it came from a
 * different product than the create-account page it stands beside — shouted
 * uppercase labels, its own input metrics, its own submit colour.
 *
 * It renders .form-group markup and .btn-primary now, like every other auth
 * card, and its heading is the shared brand lockup. What remains below is only
 * what is genuinely particular to THIS card.
 */

.acct-completion { display: block; text-align: left; }

/* The address is already proven — the code that just worked was sent to it. It
   is shown as a statement of who is being set up, not a field to fill in. No
   other auth card has a locked field, so this rule has nowhere else to live. */
.acct-completion .is-locked {
    color: var(--text-muted);
    cursor: not-allowed;
    opacity: 1;
}

/* The consent panel draws itself (consent-gate.js); this is only the room it
   sits in. */
.acct-completion-terms { margin: 1rem 0; }