/* CHG-WEB-004 / PHASE-3 / STEP-05A — Partner Program overview page.
   Page-specific composition glue only: marketing-section/section-split/
   partner-sequence/mechanism-step-index are all reused, unedited, from
   ../styles.css.

   Hero grid geometry applies PRODUCT_PAGE_VISUAL_SYSTEM_v0.1 directly
   (not iteratively — this page starts with the mechanism already
   validated across STEP-04B.3/04C/04D, rather than the padding-only
   attempt STEP-04B.2 needed before the real geometry fix in STEP-04B.3):
   a page-scoped .partners-hero-grid class overrides align-items to
   stretch at 1024px+ on THIS page's own .hero-grid element only
   (../styles.css's shared rule, used by the Homepage and every product
   page, is untouched). The visual panel is a flex column whose svg
   fills remaining height via flex:1 1 0%/min-height:0, scoped to the
   same 1024px+ query so mobile/tablet stacking never risks the flex-
   collapse failure mode documented in STEP-04B.3. The svg uses
   width:100% + explicit preserveAspectRatio="xMidYMid meet" (contain-
   like). No transform:scale() is used anywhere in this file. */

.partners-hero-visual {
    max-width: var(--content-max);
    padding: var(--space-5);
    border: 1px solid var(--hairline-strong);
    border-radius: var(--radius-md);
    background: var(--surface-1);
    display: flex;
    flex-direction: column;
}

.partners-hero-visual svg {
    display: block;
    width: 100%;
    height: auto;
    color: var(--text-muted);
}

.partners-hero-visual-caption {
    flex: 0 0 auto;
    margin: var(--space-5) 0 0;
    color: var(--text-primary);
    font-size: 1.1rem;
    font-weight: 600;
    line-height: 1.5;
    text-align: center;
}

@media (min-width: 1024px) {
    .partners-hero-grid {
        align-items: stretch;
    }
    .partners-hero-visual {
        flex: 1;
        max-width: var(--content-max);
        justify-content: center;
    }
    .partners-hero-visual svg {
        height: auto;
        flex: 1 1 0%;
        min-height: 0;
    }
}

/* Chapter 3 — scenario list. Deliberately plain text rows (role + one
   sentence), not persona cards with portraits/avatars — per instruction,
   "prefer scenario-based presentation rather than persona cards with
   stock portraits." */
.partners-scenarios {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: var(--space-4);
}

.partners-scenario-role {
    display: block;
    margin-bottom: var(--space-1);
    font-family: var(--font-heading);
    font-weight: 600;
    color: var(--text-primary);
}

.partners-scenarios p {
    margin: 0;
    color: var(--text-secondary);
    font-size: var(--text-small);
    line-height: 1.5;
}

/* Chapter 4 — compact "what is not rewarded" list, same pattern as
   .sales-boundaries/.corp-boundaries. */
.partners-nonreward {
    margin-top: var(--space-6);
    padding-top: var(--space-5);
    border-top: 1px solid var(--hairline);
}

.partners-nonreward-heading {
    margin: 0 0 var(--space-3);
    color: var(--text-muted);
    font-family: var(--font-heading);
    font-size: var(--text-meta);
    font-weight: 600;
    letter-spacing: 0.1em;
    text-transform: uppercase;
}

.partners-nonreward-list {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: var(--space-2);
}

.partners-nonreward-list li {
    color: var(--text-secondary);
    font-size: var(--text-small);
    line-height: 1.5;
}

.partners-bounded-note {
    margin-top: var(--space-4);
    color: var(--text-muted);
    font-size: var(--text-meta);
    line-height: 1.5;
}
