v0 prompt for a footer section

Build a SiteFooter component for a project management SaaS using Next.js, Tailwind, and shadcn/ui. Generate it as one self-contained file so I can regenerate the footer alone in a later message without touching the sections above it; it slots into an existing landing page as the final import, rendered after the last section. The audience is engineering managers at startups, so link labels should use their vocabulary, not internal team names.

Internal anatomy, top to bottom:
1. Newsletter band — a one-line pitch derived from a project management SaaS (name the concrete thing subscribers receive), a shadcn Input for email, and a submit button one visual size smaller than the hero's, because this is the page's secondary action. End the band with a small text link restating "start a free trial" for readers who scrolled here still undecided.
2. Link columns — 3 or 4 columns whose headings you derive from what a project management SaaS actually is: Product (features, pricing, changelog), Resources (docs, guides, support), Company (about, blog, contact), plus a fourth only if genuinely needed. 4-6 links each, never padded to match counts.
3. Legal row — copyright with the current year, privacy and terms links, and 3-4 lucide-react social icons, all sitting on one baseline.
4. Optional brand moment — the product wordmark at 12-18vw, cropped by the bottom edge, at very low contrast so it reads as texture, not a headline.

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 and responsive rules:
- 96px top padding; 48px from newsletter band to columns; 32px above the legal row; 48px column gap.
- Under 640px: columns collapse to 2-up, the input and button stack full width, and the legal row wraps to two lines with socials first.

After building, check that: every column has a specific heading (never "Links"), the form submits without layout shift, the legal row holds one line at 1280px, the oversized wordmark causes no horizontal scroll, and all footer text passes AA contrast against the background.