/* Components: nav, buttons, hero, trust strip, section spacing, FAQ
   accordion, testimonials, footer, and the inquiry form. Copied verbatim
   from site/css/global.css lines 62-696 (everything after the reset/
   typography block Task 5 took into base.css, and before the
   prefers-reduced-motion block Task 5 also already took). Read that file
   and transcribe exactly; do not retype from memory.

   Two additions not in global.css, both required by the task brief:
   - .nav.nav--menu-open: durable fix for the white-on-white mobile menu.
     A separate class at three-class specificity so the scroll handler's
     transparent/solid rewrite on every scroll event cannot undo it.
   - min-width: 44px on .nav__toggle: tap-target minimum. Purely additive
     padding target, no visual change.

   Two selectors promoted here from page inline styles because they have
   no other home and losing them silently breaks the page: .btn--outline
   (homepage "Explore catering" CTA - without it the button renders
   borderless and near-black on the dark hero photo, invisible, above the
   fold) and .btn--white (menu page). Neither exists in global.css.

   .inquiry__* (the catering form) is promoted here too, per the task
   brief and the component list in this task's Interfaces. It is not in
   global.css; it lived only in catering.html's inline styles. The error
   state below is the chipotle version from f712472, not the earlier
   Tailwind-red version.

   NOT promoted here: .tag and the nine card components. Their bodies
   differ across the pages that define them (see src/css/pages/*.css and
   the task-6 report for the diffs), so per the brief's escape hatch they
   stay page-specific rather than risk a silent, invisible-to-the-coverage-
   script appearance change on whichever page did not "win" the merge. */

/* ===== Navigation ===== */
.nav {
    position: fixed;
    top: 0;
    left: 0;
    right: 0;
    z-index: 1000;
    padding: 0 3rem;
    height: 72px;
    display: flex;
    align-items: center;
    justify-content: space-between;
    transition: background 0.3s ease, box-shadow 0.3s ease;
}

.nav--transparent {
    background: rgba(16, 25, 33, 0.4);
    backdrop-filter: blur(8px);
}

.nav--solid {
    background: var(--white);
    box-shadow: 0 1px 0 rgba(0,0,0,0.06);
}

.nav__logo {
    font-family: Georgia, serif;
    font-size: 1.6rem;
    font-weight: 700;
    letter-spacing: -0.02em;
    transition: color 0.3s ease;
}

.nav--transparent .nav__logo {
    color: var(--white);
}

.nav--solid .nav__logo {
    color: var(--char);
}

.nav__links {
    display: flex;
    align-items: center;
    gap: 2.5rem;
    list-style: none;
}

.nav__link {
    font-size: 0.95rem;
    font-weight: 400;
    transition: color 0.3s ease, opacity 0.2s ease;
}

.nav--transparent .nav__link {
    color: var(--white);
}

.nav--solid .nav__link {
    color: var(--char);
}

.nav__link:hover {
    opacity: 0.7;
}

.nav__cta {
    font-size: 0.9rem;
    font-weight: 500;
    padding: 0.65rem 1.6rem;
    border-radius: 100px;
    background: var(--chipotle);
    transition: transform 0.2s ease, box-shadow 0.2s ease;
}

.nav--transparent .nav__cta,
.nav--solid .nav__cta {
    color: var(--white);
}

.nav__cta:hover {
    transform: translateY(-1px);
    box-shadow: 0 4px 12px rgba(125, 39, 45, 0.3);
    opacity: 1;
}

.nav__toggle {
    display: none;
    background: none;
    border: none;
    cursor: pointer;
    padding: 0.5rem;
    /* Tap-target minimum. Computes to roughly 40px without this; the
       toggle is the only navigation control a phone user has. Purely
       additive, no visual change. */
    min-width: 44px;
}

.nav__toggle span {
    display: block;
    width: 24px;
    height: 2px;
    margin: 5px 0;
    transition: background 0.3s ease;
}

.nav--transparent .nav__toggle span {
    background: var(--white);
}

.nav--solid .nav__toggle span {
    background: var(--char);
}

/* Applied by the toggle while the mobile panel is open. Three-class
   specificity deliberately outranks .nav--transparent .nav__link, so a
   scroll event flipping transparent/solid underneath cannot make the
   panel unreadable (white links on the white open panel). Expressing
   this as a transparent-to-solid flip does NOT survive, because the
   scroll handler owns those two classes and rewrites them on every
   scroll event: the customer flicks the page to dismiss the panel,
   updateNav() fires, and the links go white again on the still-open
   white panel. Closing below the hero had the mirror bug. */
.nav.nav--menu-open {
    background: var(--white);
    box-shadow: 0 1px 0 rgba(0,0,0,0.06);
}
.nav.nav--menu-open .nav__link,
.nav.nav--menu-open .nav__logo { color: var(--char); }
.nav.nav--menu-open .nav__toggle span { background: var(--char); }
.nav.nav--menu-open .nav__cta { color: var(--white); }

/* Current-page indicator. Referenced site-wide; defined here so every
   page marks the active nav item the same way. */
.nav__link--active,
.nav--solid .nav__link--active,
.nav--transparent .nav__link--active {
    color: var(--chipotle);
    font-weight: 500;
}

.nav--transparent .nav__link--active {
    color: var(--turmeric);
}

/* ===== Buttons ===== */
.btn {
    display: inline-block;
    font-size: 0.95rem;
    font-weight: 500;
    padding: 0.9rem 2.2rem;
    border-radius: 100px;
    transition: all 0.25s ease;
    cursor: pointer;
    border: none;
}

.btn--chipotle {
    background: var(--chipotle);
    color: var(--white);
}

.btn--chipotle:hover {
    transform: translateY(-2px);
    box-shadow: 0 8px 24px rgba(125, 39, 45, 0.35);
}

.btn--outline-white {
    background: transparent;
    color: var(--white);
    border: 1.5px solid rgba(255,255,255,0.6);
}

.btn--outline-white:hover {
    background: rgba(255,255,255,0.1);
    border-color: var(--white);
}

.btn--char {
    background: var(--char);
    color: var(--white);
}

.btn--char:hover {
    transform: translateY(-2px);
    box-shadow: 0 8px 24px rgba(16, 25, 33, 0.4);
}

.btn--outline-char {
    background: transparent;
    color: var(--char);
    border: 1.5px solid rgba(16, 25, 33, 0.4);
}

.btn--outline-char:hover {
    border-color: var(--char);
    background: rgba(16, 25, 33, 0.04);
}

/* Promoted from site/index.html's inline styles verbatim. Used on the
   homepage hero's "Explore catering" button, over the dark hero photo. */
.btn--outline {
    background: transparent;
    color: var(--white);
    border: 1.5px solid rgba(255,255,255,0.6);
}

.btn--outline:hover {
    background: rgba(255,255,255,0.1);
    border-color: var(--white);
}

/* Promoted from site/menu.html's inline styles verbatim. */
.btn--white {
    background: var(--white);
    color: var(--chipotle);
}

.btn--white:hover {
    transform: translateY(-2px);
    box-shadow: 0 8px 24px rgba(0,0,0,0.15);
}

/* ===== Hero (shared pattern) ===== */
.hero {
    position: relative;
    min-height: 85vh;
    max-height: 900px;
    display: flex;
    align-items: center;
    overflow: hidden;
}

.hero__image {
    position: absolute;
    inset: 0;
    width: 100%;
    height: 100%;
    object-fit: cover;
}

.hero__overlay {
    position: absolute;
    inset: 0;
    background: linear-gradient(
        135deg,
        rgba(16, 25, 33, 0.82) 0%,
        rgba(16, 25, 33, 0.6) 45%,
        rgba(16, 25, 33, 0.3) 100%
    );
}

.hero__content {
    position: relative;
    z-index: 2;
    max-width: 680px;
    padding: 0 3rem;
    padding-top: 72px;
}

.hero__headline {
    font-family: Georgia, serif;
    font-size: 3.5rem;
    font-weight: 400;
    color: var(--white);
    line-height: 1.1;
    letter-spacing: -0.02em;
    margin-bottom: 1.25rem;
}

.hero__sub {
    font-size: 1.2rem;
    font-weight: 300;
    color: rgba(255,255,255,0.85);
    line-height: 1.65;
    margin-bottom: 2.5rem;
    max-width: 540px;
}

.hero__ctas {
    display: flex;
    gap: 1rem;
    flex-wrap: wrap;
    margin-bottom: 2.5rem;
}

.hero__proof {
    display: flex;
    align-items: center;
    gap: 1.5rem;
    flex-wrap: nowrap;
    font-size: 1.1rem;
    font-weight: 500;
    color: rgba(255,255,255,0.75);
}

.hero__proof-item {
    display: flex;
    align-items: center;
    gap: 0.4rem;
    white-space: nowrap;
}

.hero__proof-stars {
    color: var(--turmeric);
    letter-spacing: 1px;
}

.hero__proof-divider {
    width: 3px;
    height: 3px;
    border-radius: 50%;
    background: rgba(255,255,255,0.3);
}

/* ===== Trust Strip ===== */
.trust-strip {
    background: var(--cream);
    padding: 1.5rem 3rem;
    text-align: center;
}

.trust-strip__text {
    font-size: 0.78rem;
    font-weight: 600;
    letter-spacing: 0.2em;
    text-transform: uppercase;
    color: var(--text-light);
    line-height: 1.8;
}

.trust-strip__divider {
    display: inline-block;
    margin: 0 0.75rem;
    color: var(--turmeric);
    font-weight: 300;
}

/* ===== Section Spacing ===== */
.section {
    padding: 120px 3rem;
}

.section__inner {
    max-width: 1100px;
    margin: 0 auto;
}

.section__header {
    text-align: center;
    margin-bottom: 4rem;
}

.section__headline {
    font-family: Georgia, serif;
    font-size: 2.8rem;
    font-weight: 400;
    letter-spacing: -0.02em;
    color: var(--char);
}

/* ===== FAQ Accordion ===== */
.faq {
    background: var(--cream);
    padding: 120px 3rem;
}

.faq__inner {
    max-width: 760px;
    margin: 0 auto;
}

.faq__header {
    text-align: center;
    margin-bottom: 4rem;
}

.faq__headline {
    font-family: Georgia, serif;
    font-size: 3rem;
    font-weight: 400;
    letter-spacing: -0.02em;
    color: var(--char);
}

.faq-item {
    border-bottom: 1px solid rgba(16, 25, 33, 0.12);
}

.faq-item:first-child {
    border-top: 1px solid rgba(16, 25, 33, 0.12);
}

.faq-item__question {
    width: 100%;
    background: none;
    border: none;
    padding: 1.5rem 0;
    display: flex;
    justify-content: space-between;
    align-items: center;
    cursor: pointer;
    text-align: left;
    font-family: Georgia, serif;
    font-size: 1.2rem;
    font-weight: 400;
    color: var(--char);
    line-height: 1.4;
}

.faq-item__question:hover {
    color: var(--turmeric);
}

/* Structural reset, not styling: makes the <h3> inside the question
   button inherit the button's own typography instead of rendering at
   browser-default h3 (bold, ~1.17em, block-level, with margins) inside a
   flex button. Needed by any page using the accordion, which is why it
   lives here rather than in a page stylesheet. Ported from
   site/faq.html:98; not previously accounted for anywhere in src/. */
.faq-item__question h3 {
    font-size: inherit;
    font-weight: inherit;
    font-family: inherit;
    color: inherit;
    line-height: inherit;
    margin: 0;
}

.faq-item__icon {
    font-size: 1.5rem;
    font-weight: 300;
    color: var(--turmeric);
    flex-shrink: 0;
    margin-left: 1.5rem;
    transition: transform 0.3s ease;
}

.faq-item.open .faq-item__icon {
    transform: rotate(45deg);
}

/* This is the global.css mechanism: display: none/block toggled by the
   .open class below, no transition. site/faq.html deliberately overrides
   this with a max-height-based animated version in
   src/css/pages/faq.css, which must also override this rule's
   display: none with an explicit display: block, because a display flip
   is not animatable and would otherwise silently defeat that page's
   max-height transition (the element would not be in the render tree
   while collapsed). If this component is ever consumed by a page that
   wants the FAQ page's animated behavior, copy that page's override
   pattern rather than editing this rule. */
.faq-item__answer {
    display: none;
}

.faq-item.open .faq-item__answer {
    display: block;
    padding-bottom: 1.5rem;
}

.faq-item__answer p {
    font-size: 1rem;
    color: var(--text-secondary);
    line-height: 1.75;
}

/* ===== Testimonials ===== */
.testimonials {
    padding: 120px 3rem;
    background: var(--mist);
}

.testimonials__inner {
    max-width: 1100px;
    margin: 0 auto;
}

.testimonials__header {
    text-align: center;
    margin-bottom: 4rem;
}

.testimonials__headline {
    font-family: Georgia, serif;
    font-size: 2.8rem;
    font-weight: 400;
    letter-spacing: -0.02em;
    color: var(--char);
    margin-bottom: 1.5rem;
}

.testimonials__badge {
    display: inline-flex;
    align-items: center;
    gap: 0.5rem;
    font-size: 0.9rem;
    color: var(--text-secondary);
}

.testimonials__badge-stars {
    color: var(--turmeric);
    letter-spacing: 1px;
}

.testimonials__grid {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 2rem;
}

.testimonial-card {
    background: var(--white);
    border-radius: 16px;
    padding: 2rem;
    border: 1px solid rgba(16,25,33,0.06);
    display: flex;
    flex-direction: column;
    gap: 1.25rem;
}

.testimonial-card__stars {
    color: var(--turmeric);
    font-size: 1rem;
    letter-spacing: 2px;
}

.testimonial-card__quote {
    font-size: 0.95rem;
    color: var(--text-secondary);
    line-height: 1.7;
    flex: 1;
}

.testimonial-card__author {
    font-size: 0.85rem;
    font-weight: 600;
    color: var(--char);
}

.testimonial-card__company {
    font-size: 0.8rem;
    color: var(--text-light);
}

/* Mockup annotation marker (monospace blue debug badge), not a product
   component. Ported because it is part of global.css's rule set and the
   coverage script requires it to find a home; whether it should ship at
   all is a separate, deliberate decision this task does not make. */
.note {
    display: inline-block;
    background: rgba(0,100,255,0.08);
    border: 1px dashed rgba(0,100,255,0.3);
    color: rgba(0,100,255,0.65);
    font-size: 0.65rem;
    font-weight: 600;
    padding: 1px 7px;
    border-radius: 3px;
    font-family: monospace;
    margin-left: 6px;
    vertical-align: middle;
    white-space: nowrap;
}

/* ===== Footer ===== */
.footer {
    background: var(--char);
    padding: 5rem 3rem 2.5rem;
}

.footer__inner {
    max-width: 1100px;
    margin: 0 auto;
    display: grid;
    grid-template-columns: 1.5fr 1fr 1fr 1fr;
    gap: 3rem;
    margin-bottom: 3rem;
}

.footer__brand-name {
    font-family: Georgia, serif;
    font-size: 1.5rem;
    font-weight: 700;
    color: var(--white);
    margin-bottom: 0.75rem;
}

.footer__brand-desc {
    font-size: 0.9rem;
    color: rgba(255,255,255,0.4);
    line-height: 1.7;
    max-width: 280px;
}

.footer__col-title {
    font-size: 0.7rem;
    font-weight: 600;
    letter-spacing: 0.15em;
    text-transform: uppercase;
    color: rgba(255,255,255,0.25);
    margin-bottom: 1.25rem;
}

.footer__col ul {
    list-style: none;
    display: flex;
    flex-direction: column;
    gap: 0.75rem;
}

.footer__col ul li a {
    font-size: 0.9rem;
    color: rgba(255,255,255,0.55);
}

.footer__col ul li a:hover {
    color: var(--white);
}

.footer__bottom {
    max-width: 1100px;
    margin: 0 auto;
    border-top: 1px solid rgba(255,255,255,0.07);
    padding-top: 2rem;
    display: flex;
    justify-content: space-between;
    align-items: center;
    flex-wrap: wrap;
    gap: 1rem;
}

.footer__copy {
    font-size: 0.8rem;
    color: rgba(255,255,255,0.25);
}

.footer__social {
    display: flex;
    gap: 1.5rem;
}

.footer__social a {
    font-size: 0.85rem;
    color: rgba(255,255,255,0.35);
}

.footer__social a:hover {
    color: var(--white);
}

/* ===== Inquiry Form (catering) =====
   Promoted from site/catering.html's inline styles. Not in global.css.
   The error state below is the chipotle version corrected in f712472,
   not the earlier Tailwind-red version. */
.inquiry {
    background: var(--cream);
    padding: 120px 3rem;
}

.inquiry__inner {
    max-width: 640px;
    margin: 0 auto;
}

.inquiry__header {
    text-align: center;
    margin-bottom: 3rem;
}

.inquiry__headline {
    font-family: Georgia, serif;
    font-size: 2.8rem;
    font-weight: 400;
    color: var(--char);
}

.inquiry__form {
    display: flex;
    flex-direction: column;
    gap: 1.25rem;
}

.inquiry__row {
    display: grid;
    grid-template-columns: 1fr 1fr;
    gap: 1.25rem;
}

.inquiry__label {
    display: block;
    font-size: 0.85rem;
    font-weight: 500;
    color: var(--char);
    margin-bottom: 0.4rem;
}

.inquiry__input,
.inquiry__select,
.inquiry__textarea {
    width: 100%;
    padding: 0.85rem 1rem;
    border: 1px solid rgba(16, 25, 33, 0.15);
    border-radius: 10px;
    font-size: 0.95rem;
    font-family: inherit;
    background: var(--white);
    color: var(--text-primary);
}

.inquiry__input:focus,
.inquiry__select:focus,
.inquiry__textarea:focus {
    outline: none;
    border-color: var(--chipotle);
    box-shadow: 0 0 0 3px rgba(125, 39, 45, 0.1);
}

.inquiry__textarea {
    resize: vertical;
}

.inquiry__submit {
    padding: 1rem;
    border: none;
    border-radius: 100px;
    background: #E00700;
    color: var(--white);
    font-size: 1.05rem;
    font-weight: 500;
    cursor: pointer;
    font-family: inherit;
    transition: all 0.25s ease;
}

.inquiry__submit:hover {
    transform: translateY(-2px);
    box-shadow: 0 8px 24px rgba(224, 7, 0, 0.35);
}

.inquiry__submit:disabled {
    opacity: 0.6;
    cursor: not-allowed;
    transform: none;
    box-shadow: none;
}

.inquiry__success {
    text-align: center;
    padding: 2.5rem 1.5rem;
}

.inquiry__success-heading {
    font-family: Georgia, serif;
    font-size: 1.8rem;
    color: var(--char);
    margin-bottom: 1rem;
}

.inquiry__success-text {
    font-size: 1.05rem;
    color: var(--text-secondary);
    line-height: 1.7;
}

.inquiry__error {
    background: rgba(125, 39, 45, 0.06);
    border: 1px solid rgba(125, 39, 45, 0.3);
    border-radius: 10px;
    padding: 0.85rem 1rem;
    margin-bottom: 0.5rem;
    font-size: 0.9rem;
    color: var(--chipotle);
}

.inquiry__note {
    text-align: center;
    margin-top: 1.5rem;
    font-size: 0.9rem;
    color: var(--text-light);
}

.inquiry__note a {
    color: var(--turmeric);
}

/* ===== Responsive =====
   All three media queries below are ported verbatim from global.css
   lines 638 (1024px), 648 (768px) and 687 (480px). The 768px block is
   what hides .nav__links and shows .nav__toggle: without it the mobile
   nav does not exist, on any page, and no other check in this project
   would notice. The fourth global.css media query (prefers-reduced-
   motion, line 698) is NOT here: Task 5 already ported it byte-identically
   into base.css. */
@media (max-width: 1024px) {
    .hero__headline {
        font-size: 2.8rem;
    }
    .section__headline,
    .testimonials__headline {
        font-size: 2.2rem;
    }
}

@media (max-width: 768px) {
    .nav {
        padding: 0 1.5rem;
    }
    .nav__links {
        display: none;
    }
    .nav__toggle {
        display: block;
    }
    .hero__content {
        padding: 0 1.5rem;
        padding-top: 72px;
    }
    .hero__headline {
        font-size: 2.2rem;
    }
    .hero__sub {
        font-size: 1rem;
    }
    .hero__proof {
        flex-direction: column;
        gap: 0.5rem;
        align-items: flex-start;
    }
    .hero__proof-divider {
        display: none;
    }
    .section {
        padding: 80px 1.5rem;
    }
    .testimonials__grid {
        grid-template-columns: 1fr;
    }
    .footer__inner {
        grid-template-columns: 1fr;
    }
    /* Inquiry form responsive behaviour, ported from site/catering.html's
       own 768px block (not global.css, since .inquiry lives only in page
       inline styles). Promoting the base .inquiry__* rules to this file
       without also porting their responsive behaviour would leave the
       two-column .inquiry__row un-collapsed on mobile. */
    .inquiry {
        padding: 80px 1.5rem;
    }
    .inquiry__row {
        grid-template-columns: 1fr;
    }
    .inquiry__headline {
        font-size: 2rem;
    }
}

@media (max-width: 480px) {
    .hero__headline {
        font-size: 1.85rem;
    }
    .section__headline,
    .testimonials__headline,
    .faq__headline {
        font-size: 1.8rem;
    }
    .inquiry__headline {
        font-size: 1.8rem;
    }
}