Bolt prompt for a hero section

Create a hero section for a project management SaaS in this Bolt project as its own file: src/components/Hero.tsx, imported at the top of App.tsx above the existing content. Touch no other files.

This hero is center-aligned and runs on a strict height budget so it fits a small laptop screen: total rendered height under 720px, so nothing scrolls at 1280x800. Allocate roughly 40px for the chip row, 170px for the headline, 60px for the subhead, 56px for the buttons, 48px for the proof row, and 280px for the visual, plus 64px top and 48px bottom padding. If you run over, trim the visual first.

Contents, all centered in one max-width column:
- Status chip: a small bordered pill naming the category of a project management SaaS.
- Headline: up to ten words with exactly one keyword set in the palette's accent — that keyword is the thing engineering managers at startups most wants.
- Subhead: two short sentences totalling about 25 words — what it does, then who it is for, naming engineering managers at startups directly.
- Buttons: a solid primary labelled "start a free trial" beside an outlined secondary for viewing an example.
- Proof row: an overlapping avatar cluster plus a caption counting teams or users.
- Visual: one wide screenshot-placeholder card, capped at 280px tall.

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.

Responsive: under 640px the buttons stack full-width, the avatar cluster drops to three, and the visual switches to a 4:5 center crop.

Use the instant preview while building — narrow the preview pane for the mobile checks. When done, confirm: (1) no scrollbar appears inside an 800px-tall preview, (2) only Hero.tsx plus one App.tsx import line changed, (3) the accent keyword survives line wrapping intact, (4) the buttons stack correctly at 375px wide.