/* The standalone pages: privacy, terms, support, about. Factory-owned.
 *
 * Its own stylesheet, deliberately. These four are served as themselves rather
 * than through the app shell — App Review opens them directly, a store listing
 * links straight to them, and they have to render with the app's JavaScript
 * bundle never loading at all. So they cannot use the app's CSS, which on this
 * chassis is a content-hashed asset that only exists after a build.
 *
 * They were linking `/styles.css`, which the 0.1 chassis served from the repo
 * root and the 0.2 chassis does not have. Every one of them rendered as
 * unstyled black-on-white — which is what a reviewer saw when they opened the
 * privacy policy.
 *
 * Tokens are duplicated rather than imported for the same reason: one file, no
 * dependencies, works from a bare URL.
 */

:root {
  /* The brand block. `appfactory site` rewrites what is between these markers
     from app.config.json, so a colour changed after `new` reaches the policy
     pages too. Everything else in this file is left exactly as it is. */
  /* >>> site-tokens */
  --theme: #2f5d3a;
  --accent: #2f5fe0;
  --on-theme: white;
  /* <<< site-tokens */

  /* Sow Now visual standard v2: charcoal neutrals, rose accent (see src/styles/app.css) */
  --bg: #fafafb;
  --surface: #ffffff;
  --line: #eeeff1;
  --text: #1b1d21;
  --dim: #666a73;
  --link: #d42a63;
}

@media (prefers-color-scheme: dark) {
  :root { --bg: #121316; --surface: #1b1d21; --line: #2b2e34; --text: #f7f7f8; --dim: #8e929b; --link: #ff6fa0; }
}

*, *::before, *::after { box-sizing: border-box; }

body {
  margin: 0;
  padding: 32px 20px 64px;
  background: var(--bg);
  color: var(--text);
  font: 15px/1.6 Inter, -apple-system, BlinkMacSystemFont, 'Segoe UI', system-ui, sans-serif;
  font-feature-settings: 'cv11', 'ss01';
  -webkit-font-smoothing: antialiased;
}

main {
  max-width: 68ch;
  margin: 0 auto;
}

h1 { font-size: 2rem; font-weight: 700; letter-spacing: -0.02em; line-height: 1.15; margin: 0 0 8px; }
h2 { font-size: 1.0625rem; font-weight: 600; margin: 32px 0 8px; }
h3 { font-size: 1rem; margin: 24px 0 6px; }
p, li { color: var(--text); }
p { margin: 0 0 14px; }
ul, ol { margin: 0 0 14px; padding-left: 22px; }
li { margin-bottom: 6px; }

a { color: var(--link); }

/* The date a policy was last changed is the first thing a reviewer looks for
 * and the first thing an app forgets to show. */
.updated { color: var(--dim); font-size: .9rem; margin-bottom: 24px; }

.card {
  background: var(--surface);
  border: 1px solid var(--line);
  border-radius: 18px;
  padding: 24px;
  margin-bottom: 16px;
  box-shadow: 0 1px 2px rgb(16 24 40 / 4%), 0 8px 24px -6px rgb(16 24 40 / 8%);
}

/* The one thing on these pages that must never be missed — a crisis line, a
 * "this is not medical advice", a refund deadline. */
.callout {
  border: 1px solid var(--line);
  background: var(--surface);
  padding: 14px 16px;
  border-radius: 12px;
  margin: 0 0 16px;
}

.back { display: inline-block; margin-top: 32px; }
footer { margin-top: 48px; color: var(--dim); font-size: .9rem; }

/* An <img> with width/height ATTRIBUTES — which every image here should have,
   so the page does not jump as it loads — uses that attribute height until CSS
   says otherwise. A rule that sets only `width` therefore STRETCHES the image
   instead of scaling it: a 2360x1640 board rendered 940 wide came out 940x1640,
   and it looks like a bad screenshot rather than a bad stylesheet. These two
   declarations belong together and neither is safe alone. */
img { max-width: 100%; height: auto; }