Lovable prompt for a hero section

Add a hero to the very top of my landing page for a project management SaaS. Change nothing below it — this brief covers one section only.

Build it as a full-width, left-aligned stack rather than split columns:
- Announcement pill: a small rounded chip carrying a short news-style line derived from a project management SaaS (a launch, a version, an integration) plus a chevron; it should be clickable later.
- Headline: verb-first, eight words or fewer, stating what engineering managers at startups gets done with a project management SaaS. Never use the product name as the headline.
- Support line: about 20 words translating the headline into the concrete mechanism, written to engineering managers at startups in second person.
- Actions: the primary button reads "start a free trial" and should be built so I can later connect it to the signup form or auth flow Lovable manages; beside it, a plain text link with an arrow for the demo.
- Trust microcopy: one line directly under the buttons — a star rating plus a count, or a no-card-required style note. Pick one, not both.
- Media band: a wide, short browser-frame placeholder, roughly 280px tall, spanning the content width at the bottom of the section.

Vertical rhythm: 72px top padding, 16px pill-to-headline, 20px headline-to-support, 28px before the buttons, 12px down to the microcopy, 48px to the media band, 64px bottom padding. The full section, media band included, must be visible on a 1366x768 screen without scrolling.

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.

On mobile: the pill truncates to one line, the two actions stack with the primary on top, and the media band crops to a 4:3 center cut.

After building, verify: (1) no scrolling is needed at 1366x768 to see the media band, (2) the primary action is a real button element ready for a click handler, (3) the microcopy stays on a single line at desktop width, (4) the published preview matches the editor preview. Then publish so I can test on a phone.