/* ---------------------------------------------------------------------- */
/* Auth screens — initial loading check + Google sign-in (Sprint 1B Step 2) */
/* ---------------------------------------------------------------------- */

.auth-screen {
  min-height: 100vh;
  min-height: 100dvh;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: var(--space-3);
  padding: var(--space-4) var(--screen-padding);
  padding-top: calc(var(--space-4) + env(safe-area-inset-top));
  padding-bottom: calc(var(--space-4) + env(safe-area-inset-bottom));
  text-align: center;
  background-color: var(--color-bg-warm);
}

.auth-screen__brand-block {
  display: flex;
  flex-direction: column;
  gap: var(--space-1);
}

.auth-screen__brand {
  font-family: var(--font-display);
  font-size: 32px;
  font-weight: 500;
  line-height: 1.15;
  /* F7 final loose-end micro-fix: was --color-secondary (cool navy) — the
     only static, prominent element left rendering in a cool tone against
     an otherwise fully warm screen. --color-primary-dark is the correct
     token per tokens.css's own convention (text needing 4.5:1 contrast,
     not the decorative-only --color-primary), and reads as a confident
     Willow green wordmark instead. --color-secondary itself is untouched;
     the toast background and .btn--primary:active still use it. */
  color: var(--color-primary-dark);
  margin: 0;
}

.auth-screen__tagline {
  font-size: 16px;
  color: var(--color-text-secondary);
  margin: 0;
  max-width: 280px;
}

.auth-screen__loading-text {
  font-size: 14px;
  color: var(--color-text-muted);
  margin: 0;
}

.auth-screen__error {
  color: var(--status-danger);
  font-size: 14px;
  max-width: 320px;
  margin: 0;
}

/* Shared full-width action button styling for auth-screen-family screens:
   the sign-in screen's "Continue with Google" and the no-access screen's
   "Sign out" both use this. */
.auth-screen__action-btn {
  width: 100%;
  max-width: 320px;
}

/* Hide the authenticated app's chrome while a loading/sign-in screen is
   showing, and let the auth screen use the full viewport instead of the
   bottom-nav-reserved padding .app-shell__content normally carries. */
body.auth-screen-active #bottom-nav-mount,
body.auth-screen-active #fab {
  display: none;
}

body.auth-screen-active .app-shell__content {
  padding: 0;
}

/* .app-shell already applies its own top safe-area padding; .auth-screen
   applies its own (space-4 + safe-area) top padding for its centred
   layout, so zero .app-shell's out here to avoid stacking both. */
body.auth-screen-active .app-shell {
  padding-top: 0;
}

/* Links to the privacy notice and terms (on the website). */
.auth-legal {
  display: flex;
  gap: var(--space-3);
  justify-content: center;
  margin-top: var(--space-3);
  font-size: 14px;
}

.auth-legal a {
  color: var(--color-text-muted);
}