Cursor prompt for a pricing section

Add a pricing section to the existing marketing page for a project management SaaS in this repo — a section within the page for engineering managers at startups to scan, not a standalone pricing page (if one exists, leave it alone).

Before writing code, read the file that composes the landing sections and match its conventions: same component directory (components/marketing/ or app/(marketing)/_components/ or wherever siblings live), same styling system as neighboring sections, same export pattern. Create PricingSection there plus a colocated tiers config (three tiers: name, positioning line, monthly and yearly prices, feature list, button label). Insert the section into the page's sequence right after features. Do not reorder or restyle any sibling section, and do not introduce a new UI dependency if the repo already has button and card primitives.

Section anatomy:
- An h2 (the page already owns the h1) stating the outcome a project management SaaS prices against, plus one supporting line.
- Billing toggle with a single state source; annual displays its effective monthly price.
- Three tier cards; the middle one is recommended — badge plus heavier border, and its button is the sole primary variant, labeled "start a free trial". Outer tiers use the repo's secondary button variant.
- Feature lists: base tier complete, upper tiers "Everything in X, plus" with 3–4 deltas; keep every bullet under eight words.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Spacing: reuse the page's existing section-padding utility or token rather than inventing a new value; card gap one step tighter than section padding. Mobile: cards stack with the recommended tier first — reorder with order utilities, not duplicated markup.

Apply the change as a small diff set, run the dev server, and verify: the new section renders between its intended neighbors; toggling billing rerenders all prices; heading levels stay h1 then h2; adjacent sections show no visual diff; lint and typecheck pass.